How it works

Most published procurement activity is not worth acting on.

This is how we decide what reaches you. Every signal passes through seven gates. Most do not.

  1. 01Known sources only

    41 vetted procurement portals. Nothing from outside them enters. No open-web scraping, no recycled listings.

    41 portals · 15 lanes

  2. 02Clean shape, or it’s out

    Malformed rows are rejected. Duplicates are caught before anything is scored.

    0 malformed admitted

  3. 03Reject more than you keep

    More ways to fail than to pass. Weak language gets cut here.

    427 accept · 704 reject terms

  4. 04Scored against every sector

    Each signal is tested against every sector it could fit. Most fit none.

    6,955 scores per cycle

  5. 05Three outcomes

    Every signal ends in one of three states — archived, held for later, or sent to you. Most end archived.

    4,058 archived · 42 held · 31 sent

  6. 06Every send is on record

    Every signal we send carries the reason it reached you. Nothing arrives without a named operator behind it.

  7. 07Published, not hidden

    Every cycle we publish what was removed and why. If the filter is wrong, it is visible. See the latest →

Every run publishes what was removed and why. See the latest · /rejection-receipts →

/methodology

SQL behind every headline number

Each figure on this page is bound to a specific table and column. Queries published verbatim.

 /incident-log

Public incident log

Tracked incidents with status, date, and mitigation — when something needs attention, it is named and recorded.

 /rejection-receipts

Latest rejection summary

What was removed and why, across eight categories, from the most recent run.