How reports work
Set up a report once: pick a template, set parameters (filter / window / top N), choose a day + time. The ingest cron checks for due reports several times an hour, renders the HTML, emails it to your account address, and stores the rendered body in an in-app archive page.
-
1
Configure
Pick a template, set the parameters (filter / window / top N) and choose a day + time to run.
-
2
Dispatch
The ingest cron checks for due reports several times an hour, renders the HTML and emails it to your account address on schedule.
-
3
Archive
Every rendered run is stored in an in-app archive at
/reports/{id}/runsfor later reference.
Manage them on the Reports page. Each report has a Run now button — fires the same render path immediately, useful for previewing before the first scheduled run.
The templates
Tender Opportunity Digest
Question it answers: "What new tenders matched my filter this week?"
Every public-sector tender published in the period that matches your filter, grouped by buyer with deep links to each notice. Equivalent to a saved-search alert but bundled — useful when per-match alerts are too noisy.
Typical use: weekly digest of high-value IT services tenders across England, every Monday at 7am.
Top Buyers in Your Sector
Question it answers: "Who's spending the most in our market right now?"
Ranked list of public bodies by total contract value awarded in your filter (CPV / region / SME-only) over the chosen window. Total spend, award count, link to each buyer's profile.
Typical use: monthly account-targeting report — the 10 NHS trusts spending most on cyber security in the last 90 days.
Supplier League Table
Question it answers: "Who else is winning in our market?"
Top suppliers by total GBP awarded in your filter over the chosen window. Each row links to the awards page filtered to that supplier so you can see their actual wins.
Typical use: quarterly competitor benchmark — top 20 suppliers in construction works, last 90 days, England.
Bid Pipeline Summary
Question it answers: "How's our bid book doing?"
Your own pipeline — win rate, open pipeline value, value won (in window), average days to decision, by-stage breakdown. Leadership-friendly weekly readout; no manual reporting required.
Typical use: Monday-morning leadership digest. GBP-only sums (mixed-currency totals are misleading).
Market Trends
Question it answers: "Which way is our market actually moving?"
How the market is shifting: notice volume by type, sector spend year-on-year, the forward pipeline by sector, and the spend split by buyer type (central government, NHS, local government).
Typical use: monthly board read-in on where public-sector demand is heading in your sector. Best read monthly — the whole market moves slowly.
Competitive Landscape
Question it answers: "Is our market consolidating, and who owns it?"
How the supplier market is shaped: concentration (the top-5 / 10 / 20 share of spend, plus an HHI score), how much work routes through frameworks rather than open tender, and the current top suppliers by value won.
Typical use: monthly check on whether a handful of primes are taking more of your market, and whether you need to get onto a framework to compete.
Upcoming Procurement Pipeline
Question it answers: "What is coming down the track, before it is a tender?"
The forward pipeline: procurements departments and councils have published in their own forward plans, typically 6–18 months ahead of any tender. Soonest-first, grouped by department, with estimated value, expected timing and a link to the source. Only still-upcoming entries are included.
Typical use: a monthly what's-coming digest, optionally narrowed to one department or a keyword. Best read monthly — the underlying plans are only refreshed every month or quarter.
Scheduling
The form lets you pick a frequency (weekly or monthly), a day, a local time, and a timezone (Europe/London is the default). The runner converts to UTC, fires when due, and recomputes the next run after each dispatch.
DST honoured automatically
A 7am report stays 7am through October's clock change — we recompute the next run after every dispatch instead of adding a fixed 7×24 hours.
The in-app archive
Every run — successful or failed — gets persisted. Each report's View runs link shows the past 25 runs with status and summary. Click any run to see the full HTML body the email contained — useful when you've forwarded the email to a colleague who lost it.
Tips
Get the most out of reports
- ✓Start with one — a Monday-morning Pipeline Summary is the highest-leverage report for most teams. Add the others once you've found the rhythm.
- ✓Window matters — 12 months gives stable rankings; 30 days gives trend signal. Pick the question first, then the window.
- ✓Run now first — configure, run-now, eyeball the rendered email, then leave it on schedule.
- ✓One report, one purpose — resist the temptation to make every report cover everything; separate reports are easier to read and easier to disable later.