Quality & Source Proof
Vendor Radar is only useful if buyers can trust where a signal came from. This page publishes lightweight production proof for our signal corpus and explains the quality rules we use before a signal reaches a customer dashboard.
Live Production Proof
These numbers are pulled from Vendor Radar's production database when this page renders.
| Published customer-visible signals | 14,595 |
| Signals linked to a source document URL | 14,595 (100%) |
| Processed source documents | 48,254 |
| Suppressed or rejected signal rows tracked | 30,571 |
| Latest published signal generated | June 1, 2026 |
| Last refreshed | June 1, 2026 at 8:18 PM UTC |
Published Output Is the Quality Lens
We measure quality by the signals that survive extraction, classification, provenance checks, lifecycle review, and suppression discipline. Raw scraped documents are not the product. Published, source-linked, forward-looking signals are.
Source-Link Policy
Every published signal should trace back to a public source document whenever the source provides a stable URL. Customer-visible records include the government body, signal type, service category, document date when available, and a link to the original public record.
Suppression Policy
Signals are suppressed before publication when they are stale, duplicate an existing record, lack forward-looking procurement relevance, point to the wrong body, overstate what the source says, or fail source-faithfulness checks. We would rather publish fewer records than inflate counts with noise.
What This Does Not Claim
Vendor Radar does not claim every monitored body publishes documents every day, and not every public document contains an opportunity. The proof that matters is whether published signals are useful, current, source-linked, and honest about what the public record supports.