EntryStandard

How It Fits

A sidecar access-record layer, not another LSLR platform.

EntryStandard works beside the systems already used for inventory, GIS, public communication, construction management, and reporting. Your existing platform identifies the line. EntryStandard documents the access outcome.

The division of labor

A program's inventory, GIS, and construction systems answer where the lead lines are, what the material classification is, which addresses are in the program, and what the construction status is. EntryStandard answers a different set of questions — the ones a reviewer asks about access:

  • Who was contacted, by what method, and when?
  • Who responded, and what authority did they hold — owner, tenant, occupant, trustee, manager, agent?
  • What document was shown, and in what version?
  • Was right-of-entry granted, refused, or was a waiver presented?
  • Was the property non-responsive after the required attempts?
  • Is the property actually crew-ready — and can the record be exported and verified?

EntryStandard is not the system of record for inventory. It is the system of record for access outcomes. That distinction is the whole product.

How the record moves

Existing systems inventory · GIS · comms construction · reporting worklist EntryStandard outreach · ROE · refusal waiver · non-response tenant routing · crew-ready append-only ledger status fields ProofPack Program archive counsel · state review audit · closeout identifies the line, runs the program owns the access record keeps the defensible file
No GIS migration, no construction-management replacement, no deep integration required for a pilot. EntryStandard owns one narrow thing: the defensible access record.

The three-file model

For an early program there is no integration project. The operating model is three exchanges of ordinary files.

1 — Property worklist in

A CSV or export from the existing system: program and property identifiers, address and unit, PIN/parcel, utility account, owner and mailing address, occupant if known, service line status, program phase, contractor package.

2 — Access status out

Fields that go back into the existing system: access status, ROE status, refusal status, waiver status, reasonable-effort status, attempt and method counts, crew-ready, last event timestamp, and a ProofPack reference.

3 — ProofPack archive

A per-property evidence packet — summary PDF, event-ledger CSV, document fingerprints, evidence index, chain-verification result. See a sample ProofPack (synthetic).

Deployment modes

Mode 1 — Mock Access Audit

No integration. Sample or exported records from the current workflow; output is an access-risk scorecard, gap memo, and sample ProofPack.

Mode 2 — CSV pilot

No API required. The program sends a property worklist; EntryStandard returns status fields and ProofPacks. Suited to a 250–500 property phase.

Mode 3 — Status sync

Scheduled export or API sync of access statuses back to the program's tracker. Scoped only after the CSV workflow has proven useful.

Mode 4 — Embedded / OEM

For incumbents and engineering firms that want the ES-R record engine inside their own platform. See For platform vendors.

What a pilot requires

For a 250–500 property pilot, EntryStandard needs:

  • A property worklist export.
  • The approved ROE, refusal, and waiver forms.
  • Program outreach rules and channels.
  • A contact for city or firm review.
  • A desired status-export format.

What it does not require:

  • Replacing GIS.
  • Replacing an inventory, public-communication, survey, or e-signature system.
  • Migrating historical inventory.
  • Connecting to billing systems.
  • Changing construction-management software.
EntryStandard is CSV-first and low-disruption by design. If the workflow does not make the access record cleaner, it does not deserve to expand.

For platform vendors

An incumbent inventory or program-management platform can add a form. The harder thing — and the thing EntryStandard is — is a defined access-record standard with refusal and waiver logic, tenant/occupant routing, ledger verification, and ProofPack export. If your platform already manages inventory, communications, or construction status, EntryStandard can supply the access-record subsystem beside it, as a sidecar or as an embedded ES-R conformance layer.

Start a conversation, or take the summary with you: No Rip-and-Replace — how EntryStandard fits into an existing LSLR stack (PDF).