Every line in rebiddate comes from a public government record and links to it. Here is each record we read, how often we pull it, what it proves, and what it doesn't.
County data as of .
Latest weekly build: to .
Check a line yourself: look up your area, then press any source link.
Pull. Every Monday our data run pulls each source below again, straight from the agency's own site or open-data API. For bid tabs, that's the new and
recent ones; the rest are read again about once a month.
Join. A county contract is tied to its bid tab by the solicitation number, then by group or area, then by the firm's name. Federal awards are tied to a firm by
its federal ID (UEI). We never treat two firms as one because their names look alike.
Check. Before a line is used, every name, amount and date in it is read again from the government file it came from. One mismatch and the line is dropped.
Gate. The whole build then has to pass our tests, including a known case for every wrong record anyone has reported. If any fails, nothing new goes out and last
week's feed stays up.
Send. The Monday email is built from the newest week that passed. If a source is down that Monday, we keep our last good copy of it and pull again the next day.
The records we read
Montgomery County's records first, then the federal ones. Each tag says what the record can and can't tell you.
Montgomery County contracts list
Montgomery County, Maryland, open-data portal (dataset vmu2-pnrc)
The recipient USAspending lists for an award, and the federal obligations to date.
The end of the current period of performance, and the latest date it could run to with every option.
Whether it was competed, set aside, an AbilityOne award or an order under an existing contract.
What it does not prove
The total price of the contract. Obligations to date are only what the government has committed so far.
A date it will be bid again. The end date is only the current option period.
The firm's exact legal name. The recipient name can differ; we match firms by their federal ID (UEI).
That you can bid on it next time. Set-asides are listed with who could bid; sole-source and AbilityOne awards are labelled not open to bid.
SAM.gov contract opportunities
U.S. General Services Administration, SAM.gov (public Get Opportunities API)
We pull it
Every Monday
Publisher updates
As agencies post
Our latest copy
What it proves
That a federal bid or award notice is posted on SAM.gov, with its responses-due date and place of performance.
What it does not prove
That your firm is eligible. Many notices are set aside for certain kinds of business.
Two lists that put federal work in the right place
Census Bureau metro area delineation (2023). Which counties count as the Washington metro, so a federal job in Norton, VA doesn't land in a Montgomery County feed. Source: Census metro delineation file (list1_2023.xlsx)
VA national cemetery list. Where a VA cemetery job really is, when the award lists the vendor's own address as the place of work. Source: VA national cemetery list
Business names on federal records from before 4 Apr 2022 can come from Dun & Bradstreet. Where they do, the name is D&B Open Data, credited here as USAspending and SAM.gov
ask. Sources: USAspending.gov on Dun & Bradstreet data ; SAM.gov terms of use
How we know it's right
Separate check,
28 of 30 matched on every field. 2 did not.
A separate check, with code that shares nothing with our engine, re-derived 30 randomly chosen findings from the agencies' own records on 8 Nov 2026. 28 matched on every field compared. In the other 2, a card that adds up orders under one parent contract left out one active order under that contract.
Drawn at random
30 of 84
Matched every field
28
Mismatched
2
Fields equal
178 of 180
Planted errors caught
26 of 26
The 30 were drawn from every finding the product showed that day, in all 53 areas it covers (product run 2026-11-07T14:39Z-36079b0),
by a seeded draw anyone can repeat (seed 2026-11-08). For each one the check fetched the agency's own record (the county's open-data rows and bid tab pages, USAspending.gov
and SAM.gov) and compared the holder, every amount, the end date and other dates, every bid line, the competition type, the source links and, for cards that add up several orders,
whether every active order is counted. Before it ran, the check had to catch deliberately wrong values: it caught all 26.
The 2 mismatches
CUSTOM LAWN SERVICE, INC., General Services Administration / Public Buildings Service contract 47PM0825A0002: the card adds up 8 orders ($697,089.26 obligated) and left out active order 47PM0825F0058 ("LANDSCAPING SERVICES AT MULTIPLE DC, MD AND VA LOCATIONS", $3,152,664.50 obligated, ends 31 May 2027). Every value the card shows is right for the orders it names.
SRS GROUNDS, LLC, Department of Defense / Department of the Air Force contract FA286022D0001: the card adds up 3 orders ($4,404,000.20 obligated) and left out active order FA286023F0011 ("ROOF VEGETATION FOR ANGB HQ UNDER GMSR IDIQ", $305,486.70 obligated, ends 31 Jul 2027). Every value the card shows is right for the orders it names.
Record links open the agency's machine-readable record (JSON), the version anyone can check without a login, or the SAM.gov notice. For a card that adds up orders, the link opens the
parent contract.
An earlier check
On , before launch, the engine's release check re-derived 30 randomly drawn findings of its first build from fresh fetches of
the government records: 30 of 30 matched, field by field.
Every week, not just once
The checks above were one-time. The weekly run repeats the field-by-field part on every line: our code re-reads each fact from the government's file before it's used, a line that
doesn't match is dropped, and nothing goes out until the whole build passes. That weekly check compares each value with its own record. It doesn't look for an order that a card
leaves out, which is what the 8 Nov 2026 check found.
Every line in the feed has a Wrong record? button. Each report is emailed to a co-founder with the line it's about, and once a wrong line is fixed it becomes a permanent
test case, so the same mistake can't ship again.
The words we use
We use the record's own terms, so a line never says more than the record does.
Listed as the contractor
The firm the agency's own contract record names. We take the holder only from that record, never from who bid lowest.
End date on the record
The date the county's contract record gives. It is not a rebid date: a contract can be extended, bridged or cancelled.
Can be extended to
The latest date the county says the contract may be extended to. It doesn't mean an extension happened.
As tabulated
A bid total exactly as the county's bid tab prints it, over the county's estimated quantities. Not yearly pay.
Flagged outlier
A total far out of line with the rest of its row, which can be a typing slip on the tab. We still show it as tabulated, with the flag next to it.
Obligations to date
Federal money committed to an award so far, as USAspending reports it. Not the size of the contract.
Current period of performance
The federal award's current option period. With its options, an award can run longer.
Small-business set-aside
A federal award only firms under the SBA size standard (or in a program such as 8(a) or HUBZone) could bid on. Listed with the open items, with a badge that says who could bid.
Open to bid
What we count: contracts let by open competition, small-business set-asides and Montgomery County LSBRP reserves. Set-asides and LSBRP contracts carry a line that says who could bid.
Not open to bid
Sole-source and AbilityOne awards and orders under an existing contract. We list them on one labelled line, never count them and never call them an opportunity.
Competition not stated on the record
An award whose record does not say how it was competed. Never counted as open to bid.
What we cover
Live: Montgomery County Government (MD), plus federal grounds, tree and snow work at sites in the District of Columbia; Charles, Frederick, Montgomery and Prince George's counties, MD; Arlington, Clarke, Culpeper, Fairfax, Fauquier, Loudoun, Prince William, Rappahannock, Spotsylvania, Stafford and Warren counties,
VA; and the cities of Alexandria, Fairfax, Falls Church, Fredericksburg, Manassas and Manassas Park, VA. That's the Maryland, DC and Virginia part of the Washington metro area as the Census Bureau draws
it. Its one West Virginia county, Jefferson, gets federal work only, like the rest of West Virginia.
Source: Census metro delineation file (list1_2023.xlsx)
Not covered yet: Montgomery County Public Schools, Montgomery Parks (M-NCPPC), WSSC Water, the City of Rockville and the City of Gaithersburg.
Anywhere else in the US: federal work only, labelled as such.
Next: Chicago and Cook County. It's on hold until its records pass the same checks, and we never show it as live before then.
The county's terms
Montgomery County asks every app that uses its open data to show this notice, word for word (terms of use §5). It's here and at the foot of every page.
Source: county open-data terms of use
The data made available here has been modified for use from its original source, which is Montgomery County, Maryland ("the County"). THE COUNTY MAKES NO REPRESENTATIONS OR WARRANTIES AS TO THE COMPLETENESS, ACCURACY, OR TIMELINESS OF ANY DATA. THE COUNTY EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE COUNTY MAKES NO REPRESENTATION OR WARRANTY AS TO THE WEBISTE OR APPLICATION USING DATA DRAWN FROM DATA.MONTGOMERYCOUNTYMD.GOV OR FOR THE USEFULNESS OR INTEGRITY OF THE WEB SITE OR APPLICATION. The data is subject to change and possible deletion, temporarily or permanently. It is understood that the information contained in the web feed is being used at one's own risk.
rebiddate is not affiliated with or endorsed by Montgomery County. We don't use the county's seal, flag or logo (terms §7). Source: county open-data terms of use
More on what the publishers' terms ask of us: Public records.
For agency web teams
If you found this page in your logs, these requests are ours. They identify themselves as:
We read public pages and public APIs only. We never sign in to an agency site, fill in a form or download bid documents.
We send one request at a time and back off when a server is busy. The county's open-data portal asks for one second between requests in its robots.txt, and we wait longer than
that, at least 1.1 seconds. Source: data.montgomerycountymd.gov/robots.txt
On apps.montgomerycountymd.gov, where the bid tab and solicitation pages are, robots.txt sets no delay. We wait at least 2 seconds between pages there.
Source: apps.montgomerycountymd.gov/robots.txt
We never use the staff names, emails or phone numbers in these records to contact anyone.