Educational guides on how workplace documents fit together — which document is typically completed before another, what is used alongside it and what follows. Connected to workplace forms, checklists and registers. Informational only — not legal advice; employers remain responsible for required documents and compliance.
What a key and lock issue workflow is
A key and lock issue workflow is the chain of documents used to control physical keys to a site, building or restricted area — an authorised request, the issue of the key, a key register tying each key to a holder, and the return or reissue when access ends or a key is lost.
This page is an educational overview of how those documents connect. It is not an official template and not legal advice — the employer or site occupier decides how keys are controlled.
Why these documents connect
Key documents connect because physical keys are easy to lose track of: the request and authorisation control who gets one, the register records who holds what, and the return step closes the loop. Without the register and return, keys circulate long after they should have been recovered.
Linking them avoids the common gaps where nobody knows who holds a key, where lost keys are not acted on, and where former staff still hold keys.
The typical sequence
- Required before: an authorised request stating who needs which key and why.
- Used with: issue of the key recorded against the holder.
- Used with: a key register kept current as keys move.
- Used with: a lost-key process that may require re-keying a lock.
- Completed after: return of the key when access ends.
- Completed after: periodic reconciliation of the register against keys held.
Who owns each step
- A manager or area owner usually authorises key requests.
- Facilities or security issues keys and keeps the register.
- An administrator runs reconciliations and chases returns.
- The employer or site occupier remains responsible for security and for compliance.
Common mistakes
- No register, so key holders are unknown.
- Keys not recovered when people leave.
- No action on a lost key, leaving a lock compromised.
- Issuing more keys than necessary.
Records and retention (high level)
Key registers and issue records are generally kept by the employer for as long as keys are in circulation and a period afterwards, in line with security needs and data-protection duties.
This page does not state a required period — confirm retention with the applicable law and the official authority.
Sharing the workflow as a PDF
Key requests and the register are commonly completed and stored as PDFs, or exported from a facilities system. Exporting to PDF supports the record; it does not make key control official or guarantee compliance.
Employer notes
- Authorise key requests and issue only what is needed.
- Keep a register tying each key to a holder.
- Recover keys when people leave or change role.
- Act on lost keys, including re-keying where needed.
Key holder notes
- Look after the keys you are issued.
- Do not copy or share keys.
- Report a lost key immediately so action can be taken.
- Return keys when you no longer need them or are leaving.
Country considerations
Expectations for physical security and the data involved vary by country and by sector, and the official authority differs. This page is general and high-level — not a statement of any country’s law and not legal advice.
Confirm current requirements with the official authority for your country and a qualified professional.
Who is responsible
The employer or site occupier is responsible for the security of its premises and for the data involved, and for compliance. This page is an educational overview with a template example; it does not determine your process and does not transfer responsibility.
Export, edit and share documents
The documents, policies and templates this involves can be exported, edited, signed, stored and shared as PDFs with the HELPERG PDF Editor.
Free, printable HR & employment resources
Practical, ungated resources to put this into action — no signup.