Every key fob in the building looks exactly like every other key fob in the building. A laptop has a serial plate the size of a business card; a fob has a tiny engraved number that nobody reads, on a black teardrop that lives in pockets, drawers and cup holders. Yet each one is a working credential, and each unreturned one costs a deactivation, a replacement and often a reprogramming fee. Tracking them is less about technology and more about ceremony: making the fifteen seconds of hand-over leave a record. Here is how to set that up for offices, sites and rental properties.
What you will learn
- Why fobs vanish faster than anything else
- The fob register: what to record
- Making identical fobs identifiable
- Issue, return and the overdue list
- Offboarding, move-out and lost fobs
- Running the register without a spreadsheet
- FAQ
Why fobs vanish faster than anything else
Fobs combine every property that makes an asset hard to track:
- They are anonymous. Identical in shape and colour, distinguishable only by a serial in four-point type. When two fobs sit on one ring, even the holder does not know which is which.
- They are tiny. Small enough to live permanently in a coat pocket, fall behind a car seat, or go through the wash - and small enough that losing one does not feel like losing company property.
- They get lent. “Take my fob, I’m in all day” is a sentence nobody logs, and a fortnight later the fob has a new de facto owner.
- They have no return moment. A leaver remembers the laptop; nobody remembers the fob until the access audit finds forty active credentials for thirty staff.
None of this changes the fob. It changes what the register must do: tie every serial to a name, every time.
The fob register: what to record
A fob record is short, which is exactly why it should be complete:
| Field | Why it matters |
|---|---|
| Fob serial | The engraved or printed number - the only physical identifier the fob has |
| Asset ID | Your own code, for labels and conversations, mapped to the serial |
| System / door group | What the fob is enrolled in, so a loss can be assessed quickly |
| Current holder | A named person - employee, resident or contractor, never a flat number or team |
| Issue date | The start of custody and the baseline for any later dispute |
| Return due date | For contractors, visitors and temporary cover - the trigger for chasing |
| Deposit / replacement fee | What applies if it never comes back, agreed at issue rather than argued later |
| Status | Issued, in stock, lost, deactivated - so spares are a count, not a guess |
For rental properties, the holder field does the heavy lifting: a fob assigned to “Flat 12” tells you nothing at move-out, while a fob assigned to a named tenant with a dated issue record settles the deposit conversation before it starts.
Making identical fobs identifiable
You cannot meaningfully label something the size of a thumbnail, so work with what the fob gives you:
- Use the engraved serial as the anchor. Every fob carries a unique number from the access system supplier; the register maps it to your asset ID and holder.
- Add a small QR tag to the ring where practical. A QR label on a sturdy tag - scanned with any phone camera - beats squinting at engraving, and the printed asset ID beneath it covers phone calls. As with master keys, the tag should carry a code, never a door or building name.
- Use colour for sorting, not identity. Coloured rings or sleeves per building or door group make the spares drawer navigable, but colour never replaces the serial - it only narrows the pile.
Tip: photograph the fob’s engraved serial at the moment of issue and attach the photo to the record. Engravings wear, and the photo settles every later “that’s not the fob I was given” conversation in seconds.
Issue, return and the overdue list
The workflow is a standard check-out model, shrunk to fob scale:
- Issue to a named person with a date - and a due date for anyone temporary. Visitors and trades get same-day returns; contractors get the job’s end date.
- Keep spares as a pool. Unissued fobs sit in one drawer as an equipment pool with status “in stock”, counted, so “are there spare fobs?” has a numeric answer.
- Log returns, including condition. Cracked housings and dead trace buttons surface at return, when a swap is cheap.
- Read the overdue list daily. A fob past its due date is an overdue asset like any other - and a visitor fob unreturned overnight is the cheapest security warning you will ever get.
The same routine covers cousins of the fob: gate remotes for car parks and yards behave identically, down to the reprogramming fee.
Offboarding, move-out and lost fobs
For employees, the leaver’s open assignments are the checklist - the fob is on the list next to the laptop, so it stops being the thing everyone forgets. For tenants, fold the fob count into the move-out inspection, with the issue records as the authority on how many were handed over and what fee applies per missing fob.
Lost fobs get three actions, in order: mark the record lost (keep the history), deactivate the credential in the access control system, apply the agreed fee. Keeping lost records rather than deleting them is what reveals the patterns - the site that loses ten a year, the contractor firm that never returns one - and patterns are what you can actually manage.
Running the register without a spreadsheet
Fob spreadsheets fail at the hand-over. The issue happens at a desk or a doorstep in fifteen seconds; the sheet lives somewhere else and demands a second, later step that rarely happens - and one skipped row makes every count after it wrong. The full failure pattern is described in why spreadsheets fail at asset tracking, and fobs are close to its worst case.
An asset management tool like AMPthilly moves the record into the hand-over itself: each fob is an asset with serial, holder, due date, attached photos and a deposit note; issues and returns are timestamped events with a permanent history; the overdue list updates itself; and a QR tag scanned with a phone camera opens the right record at the doorstep, no app install needed. The free plan covers 3 users and 25 assets without a card, which is a full fob drawer - start there and see whether the register survives contact with reception.
FAQ
How do I keep track of key fobs for employees? Register every fob under its engraved serial, assign it to a named person at hand-over, log returns, and let the open-assignments list drive offboarding.
What should a key fob register record? Serial, your asset ID, the system it is enrolled in, holder, issue date, return due date, the applicable fee or deposit, and status.
How do apartment and property managers track fobs? Per named resident, never per flat, with deposits noted at issue. Move-out collects against the open assignments; unreturned fobs are marked lost, deactivated and charged.
What should happen when a fob is lost? Mark it lost in the register, deactivate it in the access system, apply the agreed fee - and keep the record, because loss patterns are the manageable part.
How do I manage a pool of shared or visitor fobs? One drawer, counted, status “in stock”; every issue a named check-out with a due date; overdue list checked daily.
The takeaway
A fob register succeeds or fails in the fifteen seconds of hand-over. Anchor every fob to its engraved serial, assign it to a named person with a date and a fee agreed up front, count the spares, and read the overdue list. The fobs stay small and anonymous - but who holds each one stops being a mystery, and the reprogramming fees stop being a routine cost of doing business.