Ask a supervisor who currently has a specific radio, and you’ll usually get one of two answers. Either they know right away, or they say “let me check” and go flip through a binder, call the last shift, or dig through a spreadsheet. The second answer isn’t a sign of a careless team. It’s a sign the tracking method can’t keep up with the gear.
Custody transfer history is just a plain way of describing something every agency already does: handing equipment to a person, and eventually getting it back. The question is whether that handoff leaves a clear, searchable record behind — or whether it lives only in someone’s memory until an auditor asks for proof.
QMS7 builds that record automatically, as a normal part of assigning and returning equipment. Nobody has to remember to log anything separately. Here’s how it actually works, from the moment an item goes out to the moment an auditor asks about it.
What “Custody” Means in QMS7
In QMS7, custody has a simple definition: who currently has an asset and the full history of who has had it before. That’s it. But that one idea touches almost everything your agency does with equipment day to day — issuing gear at shift change, tracking down an overdue radio, or pulling together proof for an audit six months from now.
The key point is that custody isn’t a separate task layered on top of your normal process. It’s a byproduct of it. Every time an item is assigned or returned, QMS7 records who, what, and when — without anyone stopping to fill out a second form.
Step One: Assigning an Item
Every asset in QMS7 — a radio, a rifle, a patrol vehicle, a case of gloves — has its own detail screen, and one tab on that screen, Checkouts, is where custody starts.
To issue an item:
- Open the asset’s record and select the Checkouts tab.
- Select the employee who’s receiving it.
- Enter a due-back date and a quantity if it’s a bulk item.
- Add any notes.
- Capture a signature at the point of handoff.
That last step matters more than it looks like it should. Once the signature is captured, QMS7 automatically generates a signed receipt. Nobody has to remember to print anything or file it away. The receipt already exists, tied to that exact transaction, the moment the hand-off happens.
Issuing works the same way from the other direction, too. Instead of starting with the asset, you can open an employee’s record and assign an item directly from their Assignments tab. At a busy shift change, that’s often faster — you’re already on the person’s screen, not hunting through the asset list for each item they’re taking.
Step Two: Seeing Who Has What, Right Now
Once an item is assigned, QMS7 doesn’t make you go looking for the answer later. There are several places that same information shows up automatically:
- The asset’s own Checkouts tab shows who has it right now, and its full assignment history before that.
- An employee’s Assignments tab shows everything currently issued to that person, plus every item they’ve had in the past, each with its due date and a return action built right in.
- The Dashboard shows live counts for assigned items agency-wide, so a supervisor can see the big picture without opening a single record.
- The global scan bar, available on every screen, resolves a scanned barcode straight to the matching asset or employee — so “who has this?” is a scan away instead of a search.
This is where custody transfer history starts to pay for itself. The question “who has that radio?” stops being a research project and becomes a lookup that takes seconds.
It also covers the opposite question just as well: what happens when something doesn’t come back on time. Any item past its due-back date shows up automatically in two places — a table right on the Dashboard, and a full Overdue Returns queue listing every late item across the whole agency, with a one-select action to process the return from that same list. Nothing stays overdue just because nobody happened to notice.
Step Three: Returning an Item
Returning an item closes the loop the same way issuing it opened one — on that same Checkouts tab.
To return an item:
- Open the asset’s record (or the employee’s) and find the active checkout.
- Record the condition it came back in.
- Flag it if it needs service.
- Note where it was returned.
- Capture a signature.
That service flag isn’t just a note for later. If an item comes back flagged as needing attention, QMS7 automatically opens a maintenance record for it once the return is finalized — the flag starts the job rather than sitting unread in a comment field. The item’s status also switches to reflect that it’s out of service, so nobody accidentally hands it to the next officer in line.
And just like issuing, the return produces its own signed receipt — proof not just that something was handed out, but that it came back, in what condition, and when.
Every Hand-Off Builds a Timeline
A single checkout-and-return is one transaction. Custody transfer history is what you get when you string all of those transactions together over an item’s entire life — or an employee’s entire career with your agency.
Two places pull that full timeline together:
- Every asset has an Activity tab showing the complete audit trail for that specific item — every action taken on it, who did it, and when.
- A system-wide Audit Log does the same thing across your entire agency, not just one item. Entries can be filtered by module and date range, and each one can show the original values against whatever was changed.
The Audit Log also records something a paper sign-out sheet never could: the channel through which a transaction came — Counter, Scan, Kiosk, Locker, or System. That means your agency doesn’t just know who had an item and when. You know exactly how that hand-off happened, whether it was a counter checkout, a quick scan during a busy shift, or an after-hours locker pickup.
Custody Transfer History Doesn’t Stop at the Counter
Not every handoff involves a single item and a single counter interaction, and QMS7’s custody tracking isn’t limited to that scenario either.
Kits let your agency group several items — a patrol bag, a traffic-stop kit, a forensics field kit — into a single unit that is issued and returned as a single transaction, rather than scanning each item separately. The custody history still tracks each individual item in that kit, even though your staff only handled one handoff.
Smart Lockers extend custody tracking to after-hours pickups with no counter staff involved at all. An officer badges in at a locker panel, and QMS7 runs the exact same checkout process used at the counter — the transaction lands in the same ledger either way. There’s no signature pad on a locker door, so instead of a drawn signature, the receipt records how the person authenticated at the panel. Chain of custody remains unbroken whether an item is moved through a counter, scanned, or placed in a locker.
What This Means at Audit Time
An auditor’s question is almost always some version of the same thing: prove who had this, and when — the same standard of accountability that professional guidelines like the IACP’s Property & Evidence Control model policy call for. On paper, that question means pulling binders, cross-referencing dates, and hoping nothing is missing or illegible.
With custody transfer history built into every checkout and return, the answer is already sitting there. A signed receipt exists for the hand-off. An Activity tab exists for the item. An Audit Log entry exists for the agency as a whole, down to the exact channel the transaction came through. None of it required a separate step — it’s what was already happening every time gear moved in or out.
That proof doesn’t have to stay locked inside the software, either. QMS7’s Reports module can build a custody transfer history report straight from the Custody & Assignments module, or line it up next to the Audit Trail for the full picture — filtered by date range, division, status, or category.
Results can be exported as a print-ready PDF for a binder or a CSV file for a spreadsheet, and a report covering a quarter of a million records finishes in about fifteen seconds, so a fleet-wide pull doesn’t stall out the way an export from an old system might. Once a report is built the way your agency likes it, it can be saved and run again later with the same filters, or cloned as the starting point for the next one — so putting together what an auditor wants takes minutes, not a trip back to square one.
That’s the real value of treating custody as a byproduct of the normal process instead of an extra task: by the time anyone asks the question, the answer has already been written down.
If your agency is still piecing custody transfer history together after the fact instead of having it ready before anyone asks, reach out to your ERIN Technology representative to see how QMS7 handles it from the first assignment on.
