Audit · evidence · sign-off
● trail

Audit guide

One door record: inspections → remedials → proof.

Identity, evidence continuity, sign-off and exports that all trace back to the same live record — not a folder of disconnected PDFs and photos.

Chain Evidence PDFs Portal

Regulators and clients sample doors at random — the record should still read cleanly from first inspection through sign-off.

Chain on one ID

Door · FD-201 · history
JunInspection · fail hinge line · photos
JulRemedial raised · linked to same ID
AugWork complete · sign-off captured
SepPDF pack generated · matches register
OctPortal download logged · same pack hash
NovRepeat inspection · prior fail cleared

No rebuilding the story in spreadsheets between steps — that is the core audit promise.

Every line stays on the same door ID — the guide below names gaps teams hit when IDs drift between systems.

Minimum record

Evidence continuity
IdentityStable ID across visits and systems
OutcomesShared vocabulary · comparable severity
MediaPhotos tied to checklist line items
EditsWho changed what · when · visible trail
RetentionPolicy-aligned history · export snapshots dated
AccessRole-scoped views · portal vs workspace

This is the practical test auditors apply when they sample doors at random.

Weaknesses usually show up as broken links between photos, outcomes and the door ID — not as missing prose.

Exports

Client + regulator packs
Generated from live data at point in time
Signatures map to named users where used
Door list in PDF matches filtered register
Guide below covers failure modes + handover
Version note on pack matches export timestamp
Client-visible list matches filtered register view

If two exports contradict each other, something in process is broken — the guide names common causes.

Guide below Reports →

Use the reports playbook next — it walks CSV discipline, PDF naming and portal handover in one thread.