Door register · stable IDs
● register

Door register

One stable ID — every visit, remedial, and export.

The door ID is the anchor in the register. Inspection history, evidence, and outputs stay joined up when the identity does not drift between people or visits.

Naming Locations Repeat visits

IDs are cheap to get right on day one and expensive to repair after exports and QR tags ship.

QR & labels

Scan opens record · FD-204
REGISTER ID: FD-204

The tag points to the record — the ID lives in the register. Reprint or replace the label without losing the door’s history.

Last scan: 09:41 · Inspector mobile · Level 2 east

Rebind logged when door replaced — old ID archived, not deleted.

Treat the QR as a shortcut, not the source of truth for identity.

If two tags resolve to different rows, stop printing until the register is reconciled.

Location hierarchy

Property · Riverside House
▸Client · Acme Facilities
▸Building · Riverside HouseOK
▸Level 2 · East wing
▸Door · FD-204 · Store 12
▸Alias · “Store 12 (east)” → same ID
▸Import row · maps to FD-204 · verified

Use the same spelling and structure every time — “Lobby” and “lobby” silently split filters and reports.

Export a location report before go-live — duplicates show up faster in a pivot than on site.

What breaks registers

Policy pitfalls
!Location drift — inconsistent wording fragments the register.
!Reused IDs — breaks audit trail for old and new doors.
!Duplicate records — new row on repeat visit instead of same door.
!Shared IDs — two physical doors pointing at one row.
!Import clashes — PDF line does not map to a live ID.

Lock the scheme before scale — the full checklist is in the guide below.

Checklist below Door register →

Pair with the QR rollout guide when you move from spreadsheet to tagged doors.