Police equipment is personal in a way most organisational gear is not. A radio, a body camera, and a ballistic vest are issued to a named officer, carried through every shift, and expected back - in known condition - when the assignment, the rotation, or the career ends. Yet many departments still run issue and return on paper cards or a quartermaster’s spreadsheet, which means the honest answer to “who has unit 14?” is often “whoever signed for something in 2023”. This guide covers how departments keep issued equipment accountable: what to track, how to structure personal versus pool issue, and the audit trail that answers questions before they become problems.
What you will learn
- Why issued gear goes missing
- What a department should track
- Personal issue, pool issue, vehicle issue
- An audit trail that answers questions
- Getting started without disrupting shifts
- FAQ
Why issued gear goes missing
A police department combines several loss multipliers that ordinary offices never face:
- The operation never closes. Three shifts hand equipment across a 24/7 boundary, and anything pooled - cameras, radios, spare vests - changes hands at exactly the moment everyone is busiest.
- Gear lives in lockers, bags, and cars. Issued kit disperses to wherever the officer is, so a physical walk-around of the station tells you almost nothing about what the department actually holds.
- Officers move. Transfers between units, promotions, long-term leave, and separations all orphan equipment unless return is a formal step rather than a memory.
- Expiry dates are safety-critical. Ballistic vests carry manufacturer expiry dates, and first-aid and naloxone kits in vehicles date out too. An untracked expiry is not an admin gap; it is an officer wearing protection that no longer counts.
- The budget is public. When the council or an auditor asks where last year’s body camera purchase went, “mostly issued, probably” is not an answer. Records full of ghost assets - items on the books that nobody can produce - surface at exactly the wrong moment.
What a department should track
Track per item anything serialised, issued, or expiry-dated:
- Duty gear - ballistic vests (with expiry dates on the record), duty belts, less-lethal devices, handcuffs by serial where policy requires it.
- Radios and body cameras - the highest-turnover category, and the one incident reviews ask about. Each unit gets its own asset tag and record.
- Armoury items - firearms, optics, and suppression equipment by serial, with the armoury itself as a location so the register shows what is racked versus issued.
- Vehicle kit - first-aid bags, AEDs, fire extinguishers, traffic cones, scene lighting, tyre-deflation devices. Assign these to the vehicle, not a person, so kit survives crew changes.
- Specialist equipment - drones, breaching tools, surveillance kit, and anything signed out per operation.
- Station and community equipment - briefing-room AV equipment, and the PA systems and podium kit that travel to community meetings and school visits.
- IT - mobile data terminals, laptops, and phones, which follow the same issue logic as everything else.
What not to track per item: ammunition, batteries, and uniform consumables. Those are stock, managed by reorder level, not individual records.
Personal issue, pool issue, vehicle issue
Most departmental equipment fits one of three issue models, and choosing deliberately is half the system:
| Equipment class | Issue model | Returned when |
|---|---|---|
| Vests, duty belts, personal radios | Personal issue to the officer | Transfer or separation |
| Pool body cameras, spare radios | Shift checkout from the pool | End of shift |
| First-aid kits, cones, scene lights | Assigned to the vehicle | Vehicle decommissioned |
| Drones, surveillance kit | Per-operation checkout | Operation ends |
Personal issue gives the cleanest accountability and suits anything fitted to the individual. Shift pools suit expensive shared kit - but only if the start-of-shift checkout is a ten-second scan, not a clipboard queue. Vehicle assignment keeps kit with the car across crew changes, with the fleet officer as custodian.
Tip: record each vest’s manufacturer expiry date in the warranty-end field of its record. Filtering the register by expiry then gives you next year’s replacement budget in one view, instead of a locker-by-locker inspection.
An audit trail that answers questions
The register earns its keep when questions arrive. Which camera did the officer carry on the night in question? When was this vest issued, and was it in date? Who had the spare radio that turned up at auction? A department that logs every issue, return, and transfer as an event - rather than overwriting a cell in a spreadsheet - can answer from the record instead of from recollection. This is also where spreadsheets genuinely fail: they hold the current state but not the history, and the history is the point (more on that in why Excel fails for asset tracking). Tracking the full asset lifecycle - purchase, issue, service, expiry, disposal - also keeps decommissioned items from lingering on the books as zombie assets that distort the budget.
One important boundary: this register is for departmental equipment, not evidence. Evidence has its own legal chain-of-custody regime and belongs in a dedicated evidence process.
Getting started without disrupting shifts
- Start with one category. Body cameras or radios are ideal: serialised, countable, and high-stakes. List them with serials and photos.
- Label everything in the category - durable labels on the unit and, for pooled kit, on the docking slot.
- Issue on the record. Check each unit out to its current officer, vehicle, or pool. The register is true from day one.
- Make return a checklist step in every transfer and separation, owned by the quartermaster.
- Expand category by category - vests next, then vehicle kit, then the armoury.
This is the model AMPthilly is built around: printable QR labels scanned with any phone camera in the browser (no app for officers to install), per-person checkouts and returns with condition notes, a permanent audit history on every item, and offboarding checklists that route a leaver’s gear back or on to a replacement. Roles keep visibility sensible - admins see everything, officers see their own issued kit - and SSO and MFA are included on every plan. The free plan covers 3 users and 25 assets with no card required, which is enough to pilot one shift’s camera pool before rolling wider; see pricing for the full tiers.
FAQ
How do police departments keep track of issued equipment? Unique IDs and labels on every item, issue to a named officer, vehicle, or pool, returns logged with condition, and the open-assignments list used as the checklist at transfer or separation.
What equipment should a police department track? Duty gear, radios, body cameras, armoury items by serial, vehicle kit, drones, MDTs, and training AV - especially anything expiry-dated like vests.
How should body cameras be tracked? Personally issued or checked out per shift from a labelled pool, so the register always shows which officer carried which unit on which date.
Can equipment tracking software handle evidence? No - evidence needs a dedicated, legally compliant evidence-management process. Equipment registers cover the department’s own operational gear.
What happens to issued gear when an officer leaves? Their open-assignments list is the separation checklist: every item returns, transfers, or is formally written off, with the event logged.
The takeaway
Police equipment accountability is not a filing exercise; it is the difference between answering an auditor or an incident review from the record and answering from memory. Issue everything to a named officer, vehicle, or pool; make every issue and return an event on the record; put expiry dates where they can be filtered; and close every separation against the open-assignments list. A register like AMPthilly keeps all of that in one place - free to pilot, no card required - but the principle stands with any tool: nothing in the department is anonymous.