Counting & Verifying
The scan page is where an audit actually happens: one person, one phone, walking a floor with a hand on the equipment. It is built for exactly that, and it is deliberately usable with no camera, no barcode scanner and a poor connection.
ams/audits/scan/…), or use the Scan button on the campaign's card. It
needs the Perform Audits permission and nothing else — an auditor does not need to be
able to plan or certify anything.
Three ways to identify an asset
All three land in the same box, and all three work the same way afterwards.
| How | What to do |
|---|---|
| Type it | Enter the asset tag, the serial, or the code from the label. Press Enter. |
| Hardware scanner | Point and pull the trigger. A scanner types the code and presses Enter for you — nothing to set up. |
| Phone camera | Press Use camera and hold the label in view. Optional; see below. |
What you see before you commit
Identifying an asset does not record anything. The page first shows you what it thinks you are holding — the title, tag, serial and category — together with what the register expected: who should have it, where, and which caretaker is answerable. You compare, then you record. Two warnings can appear at this point:
| Message | What it means |
|---|---|
| This item already has a result | Somebody has counted it. Not a refusal — recording again replaces the earlier verdict, which is sometimes exactly right — but you should know before you do it. |
| This asset is not in the campaign's scope | You have found something the campaign was not looking for. Recording it adds it, which is usually what you want: an asset in the room is a fact regardless of what the plan said. |
Recording what you found
Leave the result on "Decide from what I record" and the conclusion is worked out from the condition, location and serial you enter — which is what you want most of the time. Override it when you already know: an asset you simply cannot find is Missing, and nothing else on the form matters.
Where the campaign requires a photo, the page asks for one and will not accept the finding without it. That rule is set on the campaign, not here — see Audit Campaigns.
Counting the same thing twice is safe
Why it may refuse to let you count something
Most campaigns are set so that the person holding an asset may not audit it. If you are the recorded holder, the page will decline and ask for somebody else to count that item. It is not a permissions problem — an audit somebody performs on their own equipment evidences nothing, which is the whole reason the rule exists.
Progress and the recent list
The bar at the top is the campaign's real progress, recalculated from the items each time you record — not a local tally that could drift from what your colleagues are doing. Underneath, Just counted shows your last few submissions so you can see at a glance that what you meant to record is what went in.
Counting a single asset without a campaign
An asset's own page still carries a Record audit action, and it still works exactly as it did: pick the condition, set when the next audit is due, add a note. What changed is that if that asset happens to be in an open campaign and has not been counted yet, the count lands on that campaign's line too — so a floor walk and a campaign can no longer record two versions of the same day's count and disagree.
A note on handheld scanners and integrations
Companies running dedicated scanning hardware can post counts directly through the API, using a scope granted for auditing alone — deliberately narrower than the permission to edit the register, since a scanner needs to record counts and nothing else. The same retry protection applies: send the same observation twice and the second is recognised rather than counted.