An ID badge does two jobs at once. It tells people who the wearer is, and on most modern systems it opens doors. Track it like a low-value printable and you inherit the worst of both: photos of ex-employees still circulating as apparent staff, and live credentials gathering dust in kitchen drawers. Treat badges as issued, returnable assets instead, and the register stays a mirror of who can actually get in. Here is how to run badge tracking from the printer to a leaver’s last day.
What you will learn
- How badge records drift
- What to log for every badge
- Issuing and replacing badges
- Getting badges back at offboarding
- Visitor and temporary badges
- Tools that keep the badge register honest
- FAQ
How badge records drift
Badge tracking rarely fails on day one - the first badge is printed at onboarding and duly noted. The drift comes later:
- Replacements without retirements. A lost card is reprinted as a favour, the old number is never cancelled, and one person now has two live credentials.
- The printer log masquerades as a register. It records what was printed, ever. It says nothing about what is active, lost, returned or destroyed.
- HR and security keep different lists. The people list and the access list are maintained by different teams, and nobody owns the reconciliation between them.
- Visitor badges evaporate. Numbered cards leave at the rate visitors forget them in pockets, and the pool is never counted.
- Offboarding collects the laptop, not the lanyard. A badge feels too trivial to chase, so it is the item that most reliably leaves with the leaver.
Each drifted record is small. Collectively they mean the honest answer to “who can get into the building?” is “we are not sure” - which is exactly the gap a review of your internal controls will find.
What to log for every badge
| Field | Why it matters |
|---|---|
| Badge number | The printed serial that ties the plastic to a person and to the access system |
| Holder | A named person, or a named pool for visitor cards - never “reception” |
| Issue date | Anchors the badge’s history and supports periodic access reviews |
| Access level or zones | What the card opens - the first thing a security review asks for |
| Status | Active, lost, returned, deactivated, destroyed - “lost” is a status, not a mystery |
| Replacement chain | Which badge superseded which, so old numbers are provably dead |
| Return date and condition | Closes the loop at offboarding; “snapped and binned” is a fine note |
| Template version | Flags old designs that should no longer be trusted at the door |
Issuing and replacing badges
Issue every badge as a recorded event against a named person - the same motion as handing over a laptop or a key, just smaller. Where badges are part of a starter kit, issue the kit together so one record covers the lot.
Replacement is where discipline pays. The sequence is fixed: deactivate first, reprint second. Mark the lost badge lost, kill its number in the access system, then print the replacement as a new record linked to the old one. Done in that order, a found-again card is harmless plastic; done in reverse, you have parallel live credentials and no way to know which one walked.
Tip: never reuse a badge number, even after a card is destroyed. A unique number per physical card is what makes the replacement chain - and every door log that references it - unambiguous years later.
Getting badges back at offboarding
The register makes offboarding mechanical: the list of items still assigned to the leaver is the checklist, and the badge is a line on it alongside the laptop and the gate remote. Record the badge’s return and condition, then deactivate it in the access system as a separate, confirmed step - collection and deactivation are two different protections, and you want both logged.
Remote leavers need one extra move: a due date on the badge return, so an unreturned card surfaces on an overdue list in a week instead of in next year’s audit. If the card never comes back, the deactivation step has already contained the risk - but record the loss anyway, because the plastic still carries your branding and a face.
Visitor and temporary badges
Visitor badges are a lending pool, and pools survive on counting. Number every card, sign each one out to a named visitor and host on arrival, sign it back in at departure, and count the pool at close of business. Temporary staff badges - contractors, seasonal hires - sit between the two models: issue them like employee badges but with an end date attached, so expiry is an event the register raises rather than a fact nobody notices. A visitor badge that opens no doors still deserves the count: it is a prop of legitimacy, and props of legitimacy are exactly what tailgaters want.
Tools that keep the badge register honest
The standard tooling is a spreadsheet column in an HR file, and it fails quietly: it records that someone “has a badge” as a state, while everything that matters - losses, reprints, returns, deactivations - happens as events the sheet never sees. The badge list and reality part ways within months, the pattern described in why Excel fails for asset tracking.
An asset management tool like AMPthilly treats each badge as an asset with a holder, status and full history: issues and returns are recorded events with dates and condition, replacements are noted on the record, and the audit history shows every change permanently - the trail an access review actually wants. Badges can be issued in bulk as part of an onboarding kit, and the register is searchable by holder or status in seconds. The free plan covers 3 users and 25 assets, no card required - a clean way to pilot the approach on one team before rolling it out via pricing tiers.
FAQ
How do you track employee ID badges? As issued, returnable assets: badge number, holder, issue date, access level and status in one register, with issues, replacements and returns logged as dated events.
What should a badge issuance log include? Badge number, holder, issue date, what it opens, current status, the replacement chain and the return date and condition when it comes back.
What is the right process when an employee loses their badge? Deactivate first, reprint second - mark the old badge lost, kill it in the access system, then issue the replacement as a new linked record.
How do you make sure badges come back at offboarding? The leaver’s still-assigned list is the checklist. Record the return, deactivate the card as a separate confirmed step, and set a due date for remote leavers.
How should visitor badges be tracked? As a numbered pool: signed out to a named visitor and host, signed back in at departure, counted daily.
The takeaway
A badge register is really an answer to one question: does the set of live credentials match the set of current people? Issue every badge as an event, deactivate before reprinting, let the register drive offboarding, and count the visitor pool daily. None of it is hard - it just has to happen every time, which is exactly what a register enforces and a spreadsheet hopes for.