Sweep official funding sources and run a cited preliminary eligibility screening against a versioned applicant profile, with honest per-source coverage

A private funding-opportunity radar. It sweeps official grant sources on a schedule, registers every call with per-source coverage, extracts material facts with citations, and runs a cited preliminary eligibility screening against a confirmed, versioned applicant profile. Screening is decided by a structured rules engine that returns pass, fail, or unknown - and unknown stays visible rather than being papered over. A charcoal, lime and teal board shows the full pipeline from queued to assessed.

What it does

Sweep the official funding sources on a schedule and register every call, with per-source coverage recorded honestly.
Extract the material facts from each call, every one carrying a source document and a locator.
Screen each call against the confirmed applicant profile and record a verdict of pass, fail or unknown.

What you get

A registry of every call found, with per-source coverage.
Material facts extracted with citations, so no claim floats without a source.
A cited preliminary eligibility screening bound to a profile version.
A board showing the whole pipeline from queued to assessed.

What it needs

The company the radar is for
Its registration number and country
The controlling entity, if there is one
Which official funding sources to sweep
The timezone the sweep runs in

The sweep and the assessment drain run on the app platform clock, in your own timezone.

You confirm the applicant profile before anything is screened against it. A verdict that cannot be established stays unknown rather than being decided for you.

Who runs it

Finance, the R&D leads and whoever owns the bid read the same board. A verdict says what it rests on, and the evidence behind it is one click away.

One board, not a spreadsheet each: The pipeline from queued to assessed is in one place. Nobody rebuilds the eligibility question from scratch, and nobody argues from a stale copy.
The profile is confirmed by a person: Nothing is screened against a profile until someone confirms it. Revise it and the verdicts are re-bound to the new version, so you always know which facts a result stands on.
A poor match is recorded, not chased: A call the company is not a fit for is written down as such. That is a result the team can rely on, not a gap in the board.

What stays yours

Private to the company it serves: The radar is private. Commercially sensitive project detail stays confidential, and the agent never speculates about it.
Every fact names its source: A material fact carries a source document and a locator. No claim on the board floats without something behind it.
Unknown stays unknown: A structured rules engine returns pass, fail or unknown. An unknown controller is preserved as unknown, never assumed, and the verdict stays visible instead of being papered over.
The record stays in your workspace: The profile versions, the registered calls, the cited facts, the rule packages and every verdict live in the radar's own store.

Questions

Which sources does it sweep?: The official funding sources you select at install. The registry ships EU Funding and Tenders and UKRI, and both are swept by default.
What is per-source coverage?: An honest record of what each source returned on each sweep, including when a source failed or returned only part of its calls. A gap is written down rather than hidden behind a full-looking board.
How is eligibility decided?: By a structured rules engine, not a written opinion. It returns pass, fail or unknown for each rule, and the verdict is a preliminary screening bound to a profile version, a call revision and a rule package version.
Why does a verdict say unknown?: Because a rule could not be established from the evidence available. The group-SME test needs the controlling entity, so an unknown controller produces an unknown verdict that stays on the board until it is resolved.
What is the applicant profile?: The versioned record of the company being assessed: its name, registration number, country of establishment and controlling entity. It is registered or revised from a deck or a strategy document, and every verdict names the version it used.
What drives the schedule?: The app platform clock is the single execution source. It fires the sweep and the assessment drain in the timezone you chose at install. There is no separate agent-side schedule.
Can I change the sources or the timezone later?: Yes. Both are answers given at install rather than code, and the sweep binds to them.
Is the board open to anyone?: No. A typed API serves the board and the evidence views, and it is authenticated. An anonymous caller is refused.

See which funding calls you are genuinely eligible for, and why.

Install it, confirm the applicant profile, and the first sweep registers the open calls with the evidence behind every verdict.

Browse all Bolter blueprints