Free Key Log Template for Property Managers (And When to Stop Using One)

If you're reading this, you probably keep your key records in a spreadsheet. That's fine — most property teams start there. Here's a template you can copy right now, and then an honest explanation of the exact moment it will start lying to you.

The key log template (copy-paste ready)

Paste this into Google Sheets, Excel, or Notion. These are the columns that actually matter after you've been doing this for a year:

ColumnWhat goes in it
Key Set IDA short, unique label — e.g., MAPLE-01, OAK-MASTER, WESTBROOK-BOILER
Property / AddressThe street address or client name the key belongs to
Key TypeFront door / mailbox / master / boiler room / side gate / garage
# of CopiesHow many physical keys exist for this set
Checked Out ToName of the person who currently has it
Date OutWhen they took it (date + time)
Due BackWhen it should be returned
Date ReturnedWhen it actually came back (leave blank while out)
Return LocationOffice drawer / lockbox #4 / pegboard hook B-7
Notes"Only opens side gate," "copies 2 & 3 missing since March," "do NOT give to contractors"

Add one row per key set, not per physical key — unless you have so few keys that per-key tracking is realistic (under 10 keys total, you don't need this article).

A few rules that keep the template usable:

  • Make Key Set IDs human-readable. MAPLE-01 beats K-00482 every time someone is shouting it across a parking lot.
  • Fill in Date Out the moment the key leaves the hook. Not "later." Later is how you get a log that says the key is in the office when it's in someone's van.
  • Leave Date Returned blank until the key is physically back. Don't pre-fill it. The blank cell is your signal that the key is still out.
  • Review the log every Friday. Any row with a blank Date Returned and a Due Back in the past is your to-do list.

That's the template. It works — up to a point.

When the spreadsheet starts lying to you

Every spreadsheet-based key log fails the same way, at roughly the same scale. Here are the signs you've hit the wall:

You manage more than 20 properties. At 20 key sets, the log is a page long. At 50, it's unscannable. You stop reading it; you start searching it, and searching a spreadsheet for "who has the Jubilee Road keys" is slower than texting three people.

Multiple people update it. The moment two people edit the same row — one marks a key returned, the other marks it out to a different person — you have a conflict that nobody notices for days. Google Sheets shows the conflict; it doesn't resolve it.

There are no timestamps you can trust. A spreadsheet tells you a key is "out." It doesn't tell you it went out at 7:42 this morning, that it's now 31 hours overdue, and that the person who took it left for a long weekend. You find out on Monday.

Nobody gets an alert. The most expensive phrase in key management is "I thought you had it." A spreadsheet has no idea a key is overdue. It waits for you to notice, and you notice when someone else needs the key — which is too late.

The audit trail can't be exported or shown to a client. When a client asks "who accessed my property last Tuesday," a hand-edited spreadsheet is not a document you want to hand them. It looks like what it is: a best-effort guess.

The honest graduation point

Here's the line. If any two of these are true, the template above is costing you more than it's saving:

  • You spend more than 30 minutes a week reconciling the key log
  • You've re-keyed a property in the last 12 months because a key was "lost" (meaning: unaccounted for, not actually missing)
  • A cleaner, contractor, or agent has texted you "do you have the X keys?" in the last week
  • You manage keys across more than one physical location (office + properties + team members' vehicles)
  • You can't answer "who has the key to 14 Maple Court right now?" in under 10 seconds

If you're past that line, the upgrade isn't a bigger spreadsheet. It's a system that timestamps every key movement, flags overdue keys automatically, and keeps an audit trail you didn't have to remember to update.

What that looks like in practice

A QR-based key log works the same way as the template, but the "filling in" happens by scanning a tag:

  • Each key set has a printed QR code on the ring.
  • The person taking the key scans it with their phone — the system records who, when, and which property.
  • When they return it, they scan again — it's marked back, timestamped.
  • Any key not returned inside your threshold (say, 24 hours) flags red on a dashboard — you see it before anyone else needs it.
  • The whole log is searchable and exportable, so "who had the Oak Street keys last Tuesday" is a 5-second query, not a forensic investigation.

The template above is free, and it's the right starting point for a team with 10 keys and one location. The reason to stop using it isn't that it's bad — it's that the cost of the gaps it leaves (re-keying, downtime, liability) is higher than the cost of replacing it. A $27/month system that prevents one re-key has paid for itself for a year.

If you'd rather start from a process than a spreadsheet, read how to manage keys for property management. And if you're weighing hardware against printed tags, we compared QR key tags vs RFID key cabinets side by side.

Ready to put this in place? Compare plans for our key tracking software — $27/mo, no per-seat fees — or read how property teams use Track My Keys.

Start with the template, then upgrade when it breaks

Copy the template. Use it this week. If by Friday you've already missed a return, had to text someone about an overdue key, or couldn't answer "who has what" without opening the sheet and scrolling — you've got your answer about how much longer it'll serve you.

Stop losing keys. Stop losing hours.

When you're ready, start a 14-day free trial of Track My Keys — $27/month for your whole team, no hardware, no per-seat fees. Bring your key set list, print the QR tags, and let your team scan for two weeks. The difference between a log you maintain and a log that maintains itself is the difference between hoping and knowing.