Backflow leads
Backflow leads built from source-traceable public records
A lead here is a single thing: a building where a named agency's own system showed a backflow assembly past its test interval on a stated date, delivered with the address, the device, the dates and the identifier needed to check it at that agency. No scraped phone numbers, no scored intent, no purchased list.
§01 Definition
What the word is doing here, and what it is not doing
Most lists sold to trades are contact databases filtered by industry code. This is a different object, and it is worth being blunt about the difference before anything else on the page.
What a row is
- A building, identified by the address the agency holds for the assembly.
- A device: type, size, and where published, manufacturer and model.
- A last-test date and, where the agency computes one, a next-test-due date.
- The agency's own compliance value, carried through unchanged.
- The source dataset or request, and the date the file was pulled.
What a row is not
- Not a confirmed job. It is a compliance signal on a date, nothing more.
- Not a decision-maker's name, phone number or email. Utilities do not release account-holder details, and none are requested.
- Not exclusive by default, unless a territory has been agreed as such in writing.
- Not a live feed. It is a dated extract, and it starts ageing the moment it is written.
The contact route is the property, not a person: a licensed tester turns up at the service address. That is why no page on this site offers owner contact details.
§02 A row
One record, with the address withheld
Real values from a file released by the City of Lubbock on 23 June 2026, except for the service address, which is withheld on this page because publishing it would identify a specific property. In a delivered file the address is the whole point and is present.
| Column | Value | Origin |
|---|---|---|
Address |
Withheld here | agency |
Manufacturer |
AMES |
agency |
Model No |
2000SS |
agency |
Size |
3" |
agency |
Last Inspection |
2025-04-23 |
agency |
Next Inspection |
2026-04-30 |
agency |
Current/Overdue |
Overdue |
agency |
source_ref |
city records request, released 2026-06-23 |
provider |
lead_status |
baseline, recurring or new against the prior pull | provider |
suppression_reason |
empty unless the row is being held back | provider |
Scroll the table sideways for the remaining columns.
Provider-derived columns are labelled as such rather than presented as agency data. The full 26-column layout used for a packaged compilation is set out on the fields and sample page.
§03 Territories
Where records exist, and what stage each one is at
Stated at the stage each territory has actually reached, because the gap between "records obtained" and "release built" is where most claims in this trade quietly sit. One packaged release has been built end to end, and it is a gas-piping compilation rather than a backflow one.
| Territory | Agency compliance state | Stage |
|---|---|---|
| Lubbock, Texas | 3,202 devices marked overdue of 39,909 held, at release | Extract held, 2026-06-23 |
| Columbus, Ohio | 3,186 devices marked past due of 37,658 held, at release | Extract held, 2026-06-17 |
| Gainesville, Florida | 4,685 commercial devices carrying the utility's overdue flag, of 4,847 supplied | Extract held, 2026-06-23 |
| New York City | Backflow summonses and their hearing status, not device-level test dates | Source verified, not yet packaged |
| Clearwater, Florida | None. The city states it maintains no next-test date and no compliance status. | Not offered |
Scroll the table sideways for the remaining columns.
Counts are the agency's own status values as delivered on the dates shown, and they have moved since. Every jurisdiction approached, including the ones that charged or refused, is listed in the availability index.
§04 Volume
Honest arithmetic on how much there is
The figures above are stock, not flow: they count what was overdue on one day, not how many new records appear each month. Nobody should buy a compliance list without knowing which of those two they are being sold.
What is known
Two of the three utilities released a full inventory alongside the status field, and both showed about eight per cent of devices past due on the day: 3,202 of 39,909 in Lubbock, 3,186 of 37,658 in Columbus. Gainesville supplied only the overdue set itself, so no comparable ratio can be taken from it.
What is not known
No second pull has been taken from any of the three, so the rate at which devices fall overdue in them has not been measured here. Anyone quoting a monthly figure for a territory like these should be asked what it was measured against.
Where flow has been measured, it has been unflattering and is published anyway. In the Queens gas compilation, the twenty-one days to 17 July 2026 produced no net-new qualifying buildings and a fall of 41 against a base of about 27,200. Fire-protection flow across the whole of New York City was put at roughly fifteen qualified records a month after about three quarters of keyword matches were rejected on reading. Both are on the coverage page with their dates.
§05 Checks
What runs before a file is written
A fixed set of release checks, with the measured value recorded beside each one and shipped inside the workbook. Nine of the ten are hard: a failure stops the build and there is no file to send.
- Every expected column present, and no row lacking the evidence that justifies it.
- Identifier coverage above threshold, so rows can be looked up at the agency.
- No duplicate keys in the working queue.
- Every source carrying the timestamp the agency last updated it.
- Exempt or excluded categories confirmed absent from the output.
- The active count compared against the previous pull, so a collapse or a spike is caught rather than shipped.
The full check report from the most recent packaged release, with thresholds and measured values, is reproduced on the overview page. The rules behind them are on the method page.
§06 Limits
What an overdue record does not establish
A public compliance signal is not a confirmed job, and treating it as one is the fastest way to waste a week. Every limit below applies to every row in every file.
- The test may already have been performed and not yet posted. Agency systems lag field activity.
- Another contractor may hold the account. Public records rarely say who tests a building.
- The property may have changed hands or use, or the assembly may have been removed.
- An overdue flag applies the agency's interval rule. It is not a judgement about risk or enforcement.
- Data ages from the moment it is pulled. Re-verify at the source before contacting anyone.
- No outcome data has been returned from any delivered file to date, so nothing on this site states a conversion rate, a win rate or a job value.
The returned-outcome sheet
Every compilation ships with a blank sheet for sending results back. Rows marked worked, won or dead drop out of the next queue, so the same address is not presented twice.
It is empty because it has never been returned. When that changes, what it shows will be described plainly, including if it is unflattering.
Not a government document
§07 Contact
Find out what exists before anything else
Send the trade you are licensed for and the area you cover. The reply says which records exist there, whether the agency maintains a compliance state, roughly how many rows that comes to, and where the gaps are. If nothing usable is published for your area, that is the reply, and it costs nothing to find out.
No pricing is published on this site. Email is the only channel, and there is no form, no newsletter and no tracking.
What a first exchange covers
- Which record types are published where you work, and which are not.
- A sample file with the real column layout.
- The as-of date, the source, and how to check a row yourself.
- What the data cannot tell you.