Every building has a list of keys that exists nowhere except in people's heads: the back door, the letterbox, the alarm room, the cupboard with the till. The register replaces that folklore with a table — and the whole discipline fits in five rules.
The test
Can you name everyone who can open the building right now? Not "roughly" — name them: the cleaner, the weekend casual, the contractor from the fit-out two years ago, the ex-manager whose key "was never really returned". If the answer needs a walk to the staff room board, the site doesn't know who can open it, and everything downstream (alarm codes, insurance claims, incident investigations) inherits the guess.
One row per key
A notebook beats a $2,000 access system nobody maintains. The columns do the work: Key ID (an etched code like K-12, never the door name), what it opens, type (standard / restricted / master / fob / code), cut date, issued to (name + role), issued date with signature, status (issued / returned / lost / retired), and return date with received-by initials.
A signature at issue time is the whole insurance claim, later. "Returned" with no date is still issued.
The five rules
- Whoever issues, records. No key leaves the drawer without a row signed by both sides. The thirty seconds at issue time is the only moment the evidence is free.
- Masters never leave the building. A master key is a key to every argument on the site. It never rides on the same ring as daily keys — a lost daily ring must not be a lost master.
- Departures close rows before goodbyes close doors. Key return is part of the exit checklist, before the final pay is confirmed. A warm departure with an open key row is a cold problem in three months.
- A lost key is a lock-change event. Not a wait-and-see. Rekeying a door is trivial next to an incident you cannot explain.
- Copies are issued, not improvised. "I got it cut at the hardware place" is how a site ends up with nine keys for one door and records for two.
Two rows, never one edit
When a key moves from Dana to Priya, the register gets two events: Dana's row closes (returned, dated, initialed) and Priya's row opens (issued, dated, signed). Editing Dana's row to say "Priya" destroys the history — and the history is the point. Six months later the question is never "who has K-12 now"; it is "who had K-12 in the week of the 14th."
Fobs follow the same law with one addition: a collected fob still opens the door until the system deactivates it. Alarm codes are keys that copy themselves for free — change them on departure, don't hand them down.
The traps
- The drawer of unknown keys (twenty keys, no owners).
- The master on the daily ring (convenient for four years, catastrophic in one afternoon).
- The departed-staff key never chased ("ah, they're gone now" is a permanent uncontrolled copy of the building).
- The row edited instead of appended (a register with no history answers today's question only).
- The register nobody signs (rows without signatures are folklore with formatting).
Two sites, one lost cleaner's key
A bakery with the register knew exactly what was on the lost ring (front, back, storeroom — no master), rekeyed two doors for $180 the same day, and issued a new ring by Thursday. One morning of disruption.
A neighbouring cafe, no register: nobody could say what was on the ring or who else held cuts. The insurer asked. Weekend rekey of every lock, no sleep, and still no list of who held what. Same lost ring: $180 versus a weekend and an answer they still don't have.
The full page — the quarterly five-minute cabinet count, the return receipt, and the copy-paste register template — lives on the ops notes site. If you want the exit-day sequence this plugs into (keys, accounts, badges, code word), the First 30 Minutes checklist is free, and the Ops Starter Kit ($14) makes the whole offboarding fillable.
Top comments (0)