Key Register
The Key Register records every key, fob and access card, who holds it and what it opens, with an immediate alert when a key is marked Lost.
14 days free, $0 today — App Builder comes with every suite.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Commercial property management · Facilities management · Construction and field services · Manufacturing · Education and institutional campuses
Overview
The Key Register is a working MangoApps mini app for controlling physical keys and access devices. Managers and admins record each Door key, Fob, Access card, Cabinet key or Vehicle key with a required Key ID, what it Opens, and its current Status. Optional custody details include Site, Issued to, Issued on, Return by and Notes, so the register shows both the asset and the person responsible for it.
The app is useful when keys move between employees, contractors, locations, vehicles or restricted rooms and a spreadsheet or clipboard no longer gives a dependable answer. The Currently held view shows active custody, Past return date highlights held items whose return date falls within the last 365 days, Lost isolates reported losses and Spares shows unissued backup items. The Overview screen provides a metric row and chart, Who has what provides a holder-focused grid, and Full register provides the complete record list.
This is an append-only register: records are never deleted, and the Status field tracks whether an item is Held, Returned, Lost or Spare. That preserves the issue history when a key is lost or returned. Only managers and admins add records. The template is not a replacement for a full electronic access-control system, lock-management process or physical key cabinet procedure, and it does not automatically deactivate a badge or change a lock.
Standards & compliance context
- The append-only design supports access-control record-keeping by preserving the history of issued, returned and lost keys rather than deleting custody records.
- For secure facilities, use the register alongside your site access policy and any requirements for visitor, contractor or badge control.
- A Lost status and notification support prompt review, but they do not themselves revoke an access card, replace a lock or satisfy every local security procedure.
- Limit record entry to managers and admins and review workspace permissions so key-custody information is available only to appropriate personnel.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Add the Key Register template to your MangoApps workspace and confirm the managers and admins who will maintain its records.
- Decide who is permitted to add records, then agree on a consistent Key ID format and how your team distinguishes Held, Returned, Lost and Spare.
- Create or update a record when an item is issued by entering its Key ID, Type, Opens, Site, Issued to, Issued on, Return by and Status.
- Review the Currently held, Past return date, Lost and Spares views alongside the Who has what and Full register screens to check custody and outstanding returns.
- When a key is reported lost, change Status to Lost and use the Key reported lost notification to begin the required access-control follow-up.
- When custody changes, update the existing record's Status and relevant notes rather than deleting it, so the register retains the item's lifecycle.
Best practices
- Use a unique Key ID for every physical key, fob, card, cabinet key and vehicle key before issuing it.
- Describe the access clearly in Opens, such as the room, entrance, cabinet or vehicle, so a holder can be identified without decoding internal shorthand.
- Always record Issued to and Issued on at handover, and add Return by when the item is temporary or time-limited.
- Review Past return date regularly because a Held record can remain there after its expected return date until someone resolves it.
- Change Status to Returned, Lost or Spare instead of creating duplicate records for the same item.
- Use Notes for handover context or follow-up, but keep the core custody facts in their dedicated fields.
- Check the Lost view after the Key reported lost notification and document the physical or access-control response outside the register where required.
- Reconcile the Spares view against the physical key cabinet so an item is not marked Spare when it is actually assigned.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does the Key Register track?
It records Door keys, Fobs, Access cards, Cabinet keys and Vehicle keys. Each record includes the Key ID, what it opens, Site, Issued to, Issued on, Return by, Status and Notes. This makes the register suitable for physical keys and access devices managed by a facilities team.
Who can add records to the Key Register?
Only managers and admins add records, which keeps key custody data under controlled ownership. Other staff can be recorded in the Issued to field when a key is handed over. Define your internal handover process so every issue, return or loss is recorded promptly.
How often should the register be updated?
Add a record when a key or access device is issued, and update the record when it is returned, becomes Lost or is designated Spare. Review the Currently held and Past return date views at a cadence that matches your access-control risk, such as weekly for active sites.
What happens when a key is reported lost?
A manager or admin changes the Status field to Lost. The Key reported lost automation then notifies the app owner, creating a prompt for follow-up such as recovering access, changing a lock or cancelling an access card. Keep the record rather than deleting it so the loss remains part of the custody history.
Can this replace a spreadsheet or clipboard key log?
It is designed to replace an informal spreadsheet or clipboard register with a working app added to your MangoApps workspace. The app provides typed fields, saved views and screens for finding current holders, overdue returns, lost items and spares. It also adds an alert for status changes to Lost.
Can we customize the fields and status values?
The template can be customized for your key-control process after it is added to your workspace. You may need additional fields or status options for local procedures, such as a replacement reference or deactivation state. Keep Key ID, Opens and Status consistently populated so the existing views and screens remain useful.
Does the template integrate with door-control or badge systems?
The supplied template contains the Key Register fields, views, screens and the Key reported lost notification automation. It does not claim an integration with a door-control, badge or inventory system. Discuss any required connection or workflow customization in a demo.
How should we roll this out across multiple sites?
Start by agreeing on Key ID naming, the meaning of each Status option and who is allowed to add records. Enter active held keys first, including Site, Issued to and Return by where applicable, then add spares and known lost items. Use the Who has what screen to check the initial data with site managers before relying on the register.
Related templates
Ready to use this template?
Key Register runs on a platform app included with every MangoApps plan — pick a suite and it comes along.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
