EntryStandard is a compliance middleware layer for LSLR program administration. It sits between the program's outreach activity and the program's obligation to prove that activity happened. Everything else — the homeowner portal, the e-sign ceremony, the dashboards — exists to feed one artifact: the record.
Every attempt is an event
Each outreach attempt — mailing, SMS, email, phone call, door hanger, field visit — is recorded as a discrete, timestamped event against the specific property, with the method used. Responses are events too: a homeowner opening their portal link, viewing their property, accepting the electronic-transaction disclosure, signing, refusing, or acknowledging as an occupant. Nothing is summarized at capture time; counts and rollups are always derived from the underlying events, never stored in their place.
Refusals and non-responses are outcomes, not failures
A documented refusal is a compliance outcome. So is a documented non-response after the required attempts. EntryStandard treats both as first-class records: a refusal is captured with the same ceremony and integrity protection as a signed consent, and a non-responsive property is identifiable at any time as one whose attempt-and-method count meets the applicable requirement without a response. Programs report on these outcomes; they do not explain their absence.
The ledger is append-only and tamper-evident
Events enter an append-only ledger in which each record is cryptographically chained to the one before it for that property. Records cannot be updated or deleted — corrections are new events, so the history of the record is itself part of the record. Any retroactive alteration of a stored event breaks the chain and is detectable on verification. The design details are on Security & Evidence.
Consent is a ceremony, not a checkbox
Right-of-entry signatures follow a structured electronic-signature ceremony: disclosure presented and affirmatively accepted, signer identity and claimed authority captured, role rules enforced (a tenant cannot grant the property interest), and the executed instrument rendered to a final document whose SHA-256 fingerprint is stored in the ledger alongside the signature event. The archived document and its fingerprint travel together.
Audit-ready export
For any property, the system produces the complete event history — attempts, methods, dates, outcomes, document fingerprints — in chronological order with chain verification. For a program, it produces the rollup a primacy agency asks for: which properties consented, which refused, which are non-responsive after conforming effort, and the record behind each classification.
What EntryStandard does not do
EntryStandard does not schedule crews, manage construction, or replace the program's project-management tooling. It is deliberately narrow: it is the documentation layer, designed so that the entities doing the work — municipalities and their engineering firms — can adopt it without displacing anything they already run.
To evaluate ES-R records against your program's requirements: structured pilot review.