EntryStandard

Sample Export

The ProofPack

This is what a program produces when a reviewer says: show me.

If you only read one thing: for each unreplaced property, the program needs a file. EntryStandard creates that file while outreach and field work happen, labels how each record entered the file, and exports a ProofPack when asked.

A ProofPack is the property-level export of the EntryStandard record: a cover sheet with the chain-verification result, the chronological event record (every attempt, method, date, and outcome), the reasonable-effort rollup derived from those events, any instrument or evidence fingerprints, and closing record-source and verification notes. The sample below is entirely synthetic — a fictional city, a fictional property, labeled sample hashes, and a SAMPLE watermark on every page — but the structure is exactly what a reviewer receives.

Sample ProofPack — consented property (PDF)
The full arc: five attempts, four methods, disclosure ceremony, executed instrument with its SHA-256 fingerprint.

Sample ProofPack — non-responsive property (PDF)
The harder case, and the one the record exists for: an absentee owner who never answers, a tenant routed to acknowledgment (an occupant cannot grant the property interest), conforming effort across five methods, no executed instrument, a not-crew-ready classification — and the complete no-access documentation the state asks for. This is the record that matters when nothing happened.

In a Mock No-Access File Audit, a sample ProofPack is built from the program's own record types — see engagements.

Watch the 3-minute walkthrough — a narrated tour of the synthetic Alder Run program: worklist, non-responsive drilldown, record-source labels, verification, and the ProofPack export. The demonstration shows record structure and verification; it is not legal advice or a compliance opinion.