Keys have a habit of disappearing into pockets. A landlord, a caretaker or a club secretary is then left asking who had the shed key in March. I want one list: who asked, which key, why, and who said yes.
Who it is for
Landlords and property managers, school and club caretakers, small offices and shared workspaces that hand out keys, fobs or gate tags.
What each question is for
- Which key and which door: the exact key, not "the office key".
- Reason: a lost key and a new starter are handled differently.
- Copies and dates: show how many keys are out and for how long.
- Approver: who said yes, so you can ask them.
- Hand-back box: a plain reminder.
What a requester's AI would ask
"Which door is the key for?" Then "Why do you need it?" Then "By what date?" It shows the answers and sends them only after a yes. See agent-fillable forms.
Before you use it
The form is a key log sheet. It does not issue keys or open doors. Hand keys over in person and note the hand-over yourself. A lost key may mean a new lock, so book that as a repair with a work order request. Temporary passes for guests fit a visitor registration form. See IT and operations forms and forms for real estate and landlords.
Questions
Does the form show who has which key now?
Not on its own. Each row is a request. Keep your own list of keys out, or sort the CSV by `door_or_unit` and `return_by` to see what should be back.
What if a key is lost?
The reason list has a lost key choice, plus a field for when it was last seen. Use that to decide whether a lock change is needed, and book it as a repair.
Can contractors request keys?
Yes. The reason list has contractor access. Ask who approved the request and set a return date, so you can chase the key when the job is done.