How the feed works, and how its count is earned.

This page is the method, published in full: how a public document becomes a record, how a record is verified, how the count for an area is computed, and the lawful use rule every source is held to. A subscriber never has to take the feed's word for any of it.

For the reader companion to this page, see Resources: plain language explainers on how to read a bid record, what bidding stage means, and how a count is verified.

The feed, end to end

Every record travels the same three steps, and each step leaves its evidence on the record.

1. The filing

A permit is issued, a solicitation is published, a procurement posting goes up. Public records, created by the project itself. Nothing enters the feed from anywhere else.

2. The record

The same project arriving from three sources becomes one record, with its stage history kept intact and its source named on it, so you can check it yourself.

3. The pursuit

The record is scored against your trade or your category and lands on your list while the bid window is open, with the deadline attached, and every later change lands as a dated event.

How a count is computed

One count per metro, counted the same way every period, and the method is published with it.

🔢One project counts once, however many sources reported it; duplicates are merged into a single record before anything is counted
✔️Only records checked against their source document are counted; an unchecked record is not a countable record
🎯Every count names its scope: the metro or category, the stage, and the period it covers, and nothing outside that scope is folded in
📅The count for an area is published before the area opens for sale, and republished every period after, on the same basis
🚫If the count is thin, the area does not open; the count is the gate, not a marketing figure set after the fact

How a record is verified

Verification is a read, not a label. A record earns its place in the feed by being checked against the document it came from.

📄The source document is read, and the record's fields are checked against it: project, location, stage, deadline, documents
📍The source is named on the record, with the date it was read, so any subscriber can go to the same document
🕘Stage changes are kept as a dated history on the record; nothing is overwritten, so the record always shows what it said and when
🔁Addenda are recorded as events in that history, including deadline moves, with both the old and the new date kept
🚫A record that cannot name its source does not enter the feed

The lawful use rule

The feed is built only on data it may lawfully use, and the rule is stated here so it can be held to.

⚖️Every source has its terms read and recorded before a single record is taken from it
🔇Where a source is silent about reuse, it is treated as not permitted until counsel confirms otherwise; silence is never read as permission
📄Published documents are read for their facts: the project, the deadline, the specified products, the firms the documents name
🚫The documents themselves are never republished; plans and specifications are their authors' work, and the feed sells the facts they contain, not the documents

Join the waitlist See the coverage areas