The audit question
At some point in your program's life, a primacy-agency reviewer, an auditor, or opposing counsel will pick a property your program classified as non-responsive and ask a simple question: show me. Show the four attempts. Show the two methods. Show the dates — and show that this record existed at the time, not that it was assembled for this review.
Most programs would answer with a spreadsheet, a mail-merge log, and a former contractor's email archive. That is not an answer; it is a reconstruction project.
The funding assumes the record
Most LSLR programs are built on federal money — the Bipartisan Infrastructure Law directs $15 billion to lead service line replacement through the Drinking Water State Revolving Fund, much of it as grants or principal-forgiveness loans. Money that arrives this way arrives with federal documentation obligations attached: recipients are subject to single-audit requirements, and program costs that cannot be supported with documentation can be questioned and disallowed — repaid, after the pipe is already in the ground.
The customer-side replacement is where that scrutiny concentrates, because it is public money spent on private property. What makes that expenditure proper is the right-of-entry record: the executed instrument, the authority of the person who signed it, and — for every property that refused or never answered — proof of conforming effort to obtain access. The consent file is not paperwork about the project. It is the legal basis on which the most examined dollars in the program were spent.
A program can hold this exposure for years without feeling it. The funding is awarded, the contractor is working, the replacement count is climbing — and the file that has to support all of it is a spreadsheet no one has read since the person who kept it left. EntryStandard exists so that the record underneath the money is as auditable as the money.
This risk is easy to carry without knowing it, because it accumulates on the properties where nothing happened — the letters that got no reply, the doors that never opened. And it cannot be repaired later: the legal value of an access record is that it was created at the time of the outreach. Contemporaneous documentation is the one thing a program cannot go back and create. The moment a program discovers the gap is the moment it is no longer fixable — which is why the record layer has to be in place while outreach is happening, not when the audit letter arrives.
Not ready for a deployment conversation? Programs start with a fixed-fee Mock Access Audit — reviews begin at $7,500, credited toward a pilot.
The difference between a record and a claim
When an ordinary compliance record is examined, the uncomfortable question is not only what the record says. It is whether the program can show when the record was made, whether it was changed, and whether anything was added later.
A spreadsheet entry that says “attempted 3/14/2027” may be accurate. But by itself, it is still just an entry. If the file is later edited, copied, merged, exported, or reconstructed from emails and contractor notes, the record may not carry a single integrity trail showing exactly what changed and when.
EntryStandard is designed to work more like a bound logbook than a loose-leaf binder. Each event is recorded in sequence and sealed to the event before it. A correction is not an edit; it is a new event. If a stored event is later altered or inserted into the past, the chain no longer verifies.
That changes the posture of the program. The team that documented its outreach should not have to rely on “trust us” when the file is examined. It should be able to produce a property-level record whose sequence, document fingerprints, and integrity checks can be reviewed directly.
That is the premise of EntryStandard: not just storing access records, but making them easier to defend.
The record is the deliverable
When a service line cannot be replaced because access was not granted, the program's protection is its record. EntryStandard produces a complete, tamper-evident count of attempts and methods for every property — who was contacted, when, how, and what happened — maintained as an append-only ledger and exportable in audit-ready form. The system is designed to document the reasonable-effort requirements of 40 CFR §141.84 and the documentation obligations that follow from them.
Complete access records also serve the program's purpose: properties documented as refused or non-responsive are properties a program can classify, report, and manage with a supportable access record — without pretending the outreach status is unresolved. That is what keeps replacement rates moving and gets lead out of the ground faster. Future obligations, including ownership-change outreach or state-specific requirements, remain governed by the applicable program rules.
EntryStandard runs beside the tools a program already uses — GIS, field survey apps, e-signature platforms, inventory and construction systems — as the record layer underneath them, displacing none of them.
Built for examination, not for demonstration
- Audit survival. Primacy-agency reviews and program audits examine attempt counts, methods, dates, and outcomes. Every one of those facts is a first-class record in EntryStandard, not a note field — including refusals and non-responses, which are compliance outcomes in their own right.
- Litigation posture. Records are captured at the time of the event, by the system performing the work, with cryptographic integrity protection. The record structure is designed to support admissibility as business records and to rebut after-the-fact claims that outreach did not occur.
- Turnover-proofing. Programs run for years; staff and contractors change. Because the record is structured and append-only, institutional memory does not leave with the person who kept the spreadsheet.
- Procurement safety. EntryStandard conforms to a published, versioned record specification — ES-R v1.0 — with a public crosswalk to the regulatory text. Specifiers can cite the standard rather than a vendor's marketing.
Where EntryStandard fits
EntryStandard does not replace the systems already used to manage service line inventories, GIS layers, communications, construction packages, or state reporting. Those systems identify the line and manage the program. EntryStandard documents the access outcome.
A program can begin with a simple property worklist exported from its inventory, GIS, public-communication, survey, or contractor system. EntryStandard manages the right-of-entry, refusal, waiver, non-response, and crew-readiness record for each property, then returns status fields and a ProofPack archive. No GIS migration, no construction-management replacement, no deep integration required for a pilot. How it fits.
The federal floor, stated plainly
For customer-side replacement, the reasonable-effort requirement of 40 CFR §141.84 means no fewer than four attempts to reach the customer using at least two different methods. States may require additional attempts or specific methods, and several do. EntryStandard counts attempts and methods per property against the applicable requirement and shows, at any moment, which properties have a complete record and which do not.
Where to start
Run a Mock Access Audit · How the record works · The ES-R specification and regulatory crosswalk · For engineering firms administering LSLR programs · Structured pilot review