Key Log Book: Free Template and How to Run One Properly
October 14, 2026 · 10 min read
A key log book is a permanent, bound record of every key you own and every time one was issued and returned. It has two parts: a key register that lists each key once, and an issue log that records who received a key, when, when it is due back and when it came back. Together they answer one question: who holds which key, and since when.
That is what separates a key log book from a daily key sign-out sheet. A sign-out sheet sits next to the key box and gets replaced when it fills up. A log book is the long-term record. It survives staff changes, it is what an auditor asks to see, and it is where you go when a key has been missing for three months and nobody remembers who had it last.
Below is a template you can copy today, the rules for running it, and the points where a paper register starts costing more than it saves.
Free key log book template
A working key log book has two sections. Put them in the same book, or the same spreadsheet file on two tabs. Keep them together, because the issue log only makes sense against the register.
Part 1: Key register
One row per key. You fill this in once, when a key enters your inventory, and update it only when a key is added, lost, destroyed or rekeyed.
| Key no. | Description (what it opens) | Key type | Copies held | Location stored | Restricted? | Date added | Status |
|---|---|---|---|---|---|---|---|
| K-001 | Main entrance, Building A | Unique | 1 | Key cabinet, hook 1 | Yes | 2026-10-14 | In use |
| K-002 | Plant room, Building A | Unique | 1 | Key cabinet, hook 2 | Yes | 2026-10-14 | In use |
| AC-01 | Visitor access cards | Bulk | 20 | Reception drawer | No | 2026-10-14 | In use |
What each column is for:
- Key no. A short unique code you stamp or tag onto the key itself. Never reuse a number, even after a key is destroyed. A reused number corrupts the history of both keys.
- Description. What the key opens, written so a new colleague understands it. "Plant room, Building A" beats "PR-A".
- Key type. Unique for a single physical key with its own history, such as the only key to a specific door. Bulk for interchangeable items you count by quantity, such as visitor cards or padlock keys that are all the same.
- Copies held. How many exist. For bulk items this is the total stock. For unique keys it is usually 1; if you hold two copies of the same door key, give each its own number.
- Location stored. Where the key lives when it is not issued. This is what you check against during an audit.
- Restricted? Master keys, keys to cash rooms, server rooms and plant rooms. These get stricter rules and more frequent audits.
- Date added / Status. When the key entered the register, and whether it is in use, lost, destroyed or retired. Never delete a row. Change the status.
Part 2: Key issue log
One row per handout. This is the running record, and it never gets thrown away.
| Date issued | Key no. | Qty | Issued to (name) | Company / department | Issued by | Due back | Signature out | Date returned | Received by | Signature in | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-10-14 | K-002 | 1 | A. Berg | Nordic HVAC AB | M. Lind | 2026-10-16 | AB | Boiler service | |||
| 2026-10-14 | AC-01 | 5 | Event crew | Marketing | M. Lind | 2026-10-15 | JK | ||||
What each column is for:
- Issued to and company. A named person, always. "The cleaning company" is not a holder. If a contractor collects a key, record both the individual and their employer.
- Issued by / Received by. Who on your side handed the key out and who took it back. When something goes wrong, you need to know who was at the desk.
- Qty. For bulk items. If 5 cards go out and 3 come back, write the 3 in the notes and leave the line open until the last 2 are returned.
- Due back. Mandatory, even for same-day handouts. A line without a due date can never be overdue, which means it will never be chased.
- Signature in. The most important signature in the book. It is your proof that the key came back.
How to run a key log book day to day
The template is the easy part. A key register only works when the routine around it is boring and consistent.
- Register before you issue. No key leaves the cabinet unless it has a row in the register. New keys from the locksmith get a number on the day they arrive.
- One book, one desk. All handouts and returns go through the same person or the same point. Keys never pass from one colleague to another directly. They come back to the desk and go out again, with two lines in the log.
- Use a bound book with numbered pages. If you keep it on paper, a bound book with numbered pages is harder to quietly edit than loose sheets. Write in pen. Correct mistakes with a single line through and initials, never correction fluid.
- Check open lines every week. Scan the issue log for rows with no return date where the due date has passed. That is your overdue list. Contact each holder the same day.
- Reconcile against the register regularly. Count what is physically in the cabinet, add what the issue log says is out, and compare with the register. Any gap goes straight to your lost-key procedure. Our key audit checklist walks through this step by step.
- Archive, never discard. When a book is full, label it with the date range and store it. Old books are the history you will need when a key is reported missing.
If you do not yet have written rules for who may hold which keys and what happens when one is lost, put those in place first. The key control policy guide has a template.
Where a paper key register breaks down
A bound key log book is a real improvement over no record at all. For a single office with a few dozen keys and one careful owner, it can be enough. But it has limits, and they tend to show up at the worst moment.
The book only knows what people write in it
Every handout made in a hurry, after hours, or while the book's owner is away, is a key with no record. Paper cannot make itself mandatory. The keys most likely to go missing are the ones issued in a rush, which are exactly the ones least likely to be logged.
Overdue keys stay invisible until someone looks
A due-back column is only useful if someone reads it. The book does not notice that K-002 was due back on Thursday. Overdue keys get discovered during the weekly check if it happens, or when the next person needs the key and it is not there.
Answering questions means reading handwriting
"Which keys does Nordic HVAC hold right now, across all our buildings?" "Who has held the plant room key this year?" In a paper key register, every one of those is a manual search through pages, and sometimes through archived books in a drawer. Questions that span more than one key or one site become small research projects.
One book per site, no full picture
If you run three buildings, you have three books. Nobody can see everything that is out in one place. Master keys and keys that travel between sites fall into the gap between two books.
A spreadsheet fixes less than you'd think
Moving the template into a spreadsheet makes it searchable and gives you unlimited rows. It does not fix the core problems. It still depends on someone typing every handout, nothing flags itself as overdue, and any edit silently overwrites what was there before, which is the opposite of what a permanent register is for. Shared spreadsheets also tend to end up behind one shared login, so you lose who changed what. We cover that trap in why a shared login ruins your sign-out log.
When to move your key log book to software
Stay on paper if you have one location, a stable group of key holders, and a person who reliably checks the book every week.
Move to a digital key register when any of these become true:
- Contractors or external companies regularly hold your keys
- You manage more than one site or key cabinet
- A key went missing and the book could not tell you who had it
- An insurer, landlord or head office has asked for evidence of key control
- The person who owns the book is leaving
If you manage keys across several buildings for tenants and vendors, our guide to property management key tracking covers the register layout and move-out checks.
guardable keeps the same structure as the template above. Your key register becomes a list of items: unique keys tracked individually with their own history, bulk items like access cards tracked by quantity. Each handout is an order to a client with a due date, and availability updates the moment a key goes out. Returns can be full or partial, so if 3 of 5 cards come back, the other 2 stay visibly out. Anything past its due date flags itself on the dashboard, the orders list and the client's page, and you can send an overdue reminder email instead of chasing people in the corridor.
The part a paper book cannot match is the history. Every handout and return is recorded in an immutable audit trail: who issued the key, who received it, who took it back, and exactly when. Nothing can be quietly corrected afterwards. For multiple sites, each site can run as its own workspace with its own permissions. For a broader look at what to expect from a digital system, see our guide to key management software.
Frequently asked questions
What is the difference between a key log book and a key register?
A key register lists every key you own, once, with what it opens and where it is stored. A key log book usually contains the register plus an issue log that records every handout and return over time. The register tells you what exists. The issue log tells you who had it and when.
What should a key issue register include?
At minimum: date issued, key number, quantity, the named person who received it, their company or department, who issued it, the due-back date, the return date, who received it back, and signatures for both handout and return. The due-back date and the return signature are the fields most often skipped and the ones that matter most.
How long should I keep a key log book?
Keep completed books for as long as the keys in them are still in use, and longer if your insurer, landlord or internal policy sets a retention period. The value of a log book is its history, so archive full books rather than discarding them.
Can I use Excel as a key logbook template?
Yes, the two tables above work as two tabs in a spreadsheet. Just be aware that a spreadsheet does not flag overdue keys, relies on someone updating every row, and lets edits overwrite earlier entries without a trace. If you go that route, our equipment tracking spreadsheet template shows how to structure it.
How do I move an existing key log book into software?
Enter each key from your register once, add the people and companies who regularly hold keys as clients, then record every handout from today with a due date. Log the keys that are out right now as open orders. You do not need to retype old books. Archive them, and within one cycle of handouts your digital record is complete.
Ready to retire the book? Start tracking your keys in guardable, free. Every handout logged with a due date, overdue keys flagged automatically, a permanent history for every key. Up to 50 items, unlimited orders and unlimited users, no credit card and no time limit.