Why now
- The rule creates an annual state documentation burden for lack-of-access cases — this becomes reportable before it becomes controversial.
- The file has to be made while outreach happens. If the file is missing at closeout, the program is no longer documenting. It is reconstructing.
- Once the phase closes, reconstruction is slower, weaker, and staff-dependent.
- A Mock Audit tests the current file before a reviewer does.
Could your team produce the no-access file in two minutes?
Pick one unreplaced property. Can your team show who was contacted, by what methods, on what dates, what role each person had, whether access was refused or incomplete, whether the waiver path was documented, and why the property was not crew-ready — and show when the record was created and preserved — not merely that it was assembled for the review?
If the answer requires emails, spreadsheets, paper forms, contractor notes, and staff memory, the program does not have a file. It has a reconstruction project. At some point a reviewer, auditor, counsel, or records requester will pick that property and ask a simple question: show me.
The record has to be made while outreach happens
A file assembled at closeout is weaker than a record created during the workstream. EntryStandard shows when an event occurred, when it was recorded, where the record came from, and whether it was verified. Every event shows its record source: recorded live, imported from another system, entered later, reconstructed during review, unsupported, or system-derived — so a late spreadsheet import is labeled differently from a live resident signature or staff field capture.
What EntryStandard does
- Intake. Upload the worklist export you already have — from GIS, inventory, survey, or contractor systems. EntryStandard maps fields, flags duplicates and missing data, and produces a Match Quality Report before anything enters the program.
- Record. Outreach, signatures, refusals, non-response, waiver status, field attempts, and crew-ready status become events in one append-only ledger — created as the work happens, beside the tools crews already use.
- Produce. Generate the ProofPack, No-Access Register, status export, and verification receipt when someone asks — the state, the engineer, counsel, or a reviewer.
The applicable requirement, in one sentence: where owner consent is required, the rule requires a documented reasonable effort to obtain it — at least four attempts by at least two methods (40 CFR §141.84(d)(3)(i)); states may require more. Full detail on the Record Standard page.
Who this is for
EntryStandard is for programs that:
- have unreplaced properties due to refusal or non-response;
- keep access records in paper, Survey123, DocuSign, mail logs, contractor notes, or spreadsheets;
- are entering construction or closing out a phase;
- need to show no-access documentation to the state, engineer, counsel, or a reviewer;
- want a sidecar record layer without replacing GIS or construction systems.
It is not for programs that:
- can already produce the complete no-access file in two minutes;
- want a full inventory platform or construction scheduling;
- want legal advice or a compliance opinion.
The difference between a record and a claim
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.
- Audit survival. Attempt counts, methods, dates, and outcomes are first-class records — including refusals and non-responses, which are compliance outcomes in their own right.
- Review posture. Records are captured at the time of the event, with source, actor, both timestamps, and integrity protection visible — the characteristics counsel looks for. Whether a record is admissible is counsel's determination, not ours.
- Turnover-proofing. Programs run for years; because the record is structured and append-only, institutional memory does not leave with the person who kept the spreadsheet.
The full integrity design — hash chain, daily signed anchoring, record-source labels, document fingerprinting — is on Security & Evidence. Funding context: most LSLR work is SRF/BIL-funded, and documentation gaps surface as closeout friction, drawdown delays, and questioned costs — when federal or state funding is under scrutiny, the best record wins.
Start without deployment
A Mock No-Access File Audit reviews up to 15 sample properties and shows what your current workflow can produce. If your records are solid, the memo says so. If they are scattered, the memo shows what can and cannot be reconstructed. For $9,500 flat, we test the hard fact pattern on up to 15 sample properties.
Request Mock Audit scope · How it fits · How the record works · The Record Standard · For engineering firms