Key & Access Register
Who holds a key, a fob, an access card or an alarm assignment to a shared building — a hall, a clubhouse, a studio, a rehearsal room, a lock-up unit. This is the register nobody keeps until the locks have to be changed and nobody can say how many keys exist, or who had the one that left with a committee member three years ago. Read this part first: do not type an actual alarm code, PIN or password into this tool. It records that someone has been given access, and which physical key or credential they hold — never the secret itself. What you type is saved unencrypted in this browser, on a device other people may use, and it can be exported to a plain CSV that then travels anywhere. A list of who holds what is useful to have on a shared laptop; a list containing the code is a spare key left on the doorstep. Keep the secret wherever your group already keeps secrets, and keep the register here. The columns that do the real work are the identifier stamped on the key and the "signed for" record: a register that says "Sam has a key" cannot tell you which key came back, and an unsigned issue is the one that is always disputed. Record who authorised it and why they hold it, so the list can be reviewed by someone who was not there. This is a record only. It offers no guidance on physical security or key control, and says nothing about what to do after a loss — that depends on your building, your agreement and where you are.
Your database
Fields
| Field | Type |
|---|---|
| Type of access held | select |
| What it opens (door, gate, area, building) | text |
| Identifier stamped or written on it | text |
| Holder's name | text |
| How to reach the holder | text |
| Their role, and why they hold it | text |
| Date issued | date |
| Issued / authorised by | text |
| Signed for? | bool |
| Where the signed record is filed | text |
| Deposit taken? | bool |
| Deposit amount held | number |
| Date returned | date |
| Returned to | text |
| Status | select |
| Other notes | text |
Frequently asked
Where is my data stored?
Only on this device, in your browser. Nothing is ever uploaded — a lending register holds members' names, phone numbers and home addresses alongside a list of what is worth taking, and that is not a combination to hand to anyone else's server. Export to CSV to back it up, to print it for a committee meeting, or to move it to another device.
Does it follow anything up or work anything out for me?
No. It stores exactly what you type and nothing else. It watches no date, sends no message and no email, contacts no borrower on your behalf, works out no charge, and does nothing while the tab is closed. Silence from this tool never means an item came back — it means nobody has looked. Put the due date in whatever calendar actually interrupts you, and use this to hold the detail behind it: what went out, to whom, and in what state.
Can I store the alarm code here so key holders can look it up?
No — this tool is the wrong place for it, and it is built not to hold one. Everything typed here sits unencrypted in the browser of whatever machine it was entered on, survives in that machine's profile, and is one click from a plain-text CSV that can be emailed, synced or left in a downloads folder. A register that quietly becomes the place the code lives has turned an inventory into the thing worth stealing, and nobody notices until it is copied. Record the credential, not the secret: the type of access, the identifier on it, the holder, the date issued, who authorised it. If people need a code, hand it over the way your group already hands over sensitive things, and use this register to record that access was given and later withdrawn.