Run an audit by scoping it to a location, category or department, then walking that scope scanning each item as verified or missing. Closing the count captures a signature and a note, and produces an exportable document with the scope, date and discrepancies.
An audit in Stackroom is a cycle count: walk a location or category, mark each asset present or missing, and close with a verifiable sign-off.
- 1Start an audit
Scope it to a location or category. Stackroom lists the expected assets.
- 2Verify each item
Scan or tap to mark each asset verified or missing as you go.
- 3Close and sign
Add a completion note and signature, with the custodian recorded per item.
- 4Export the evidence
Download a CSV of the audit for finance, insurance or a compliance file.
Run short, regular cycle counts by location instead of one giant annual count — it's faster and catches drift early.
Frequently asked questions
How is an audit different from the asset register?
The register is what you believe you own. An audit is what somebody physically confirmed was present, on a date, with the discrepancies recorded. Only the second constitutes assurance, which is why a register export does not satisfy an auditor.
Do I have to count everything at once?
No, and it is better not to. Scope counts to a floor, department or category and rotate through the year. The coverage is the same and discrepancies surface while somebody still remembers what happened.
What happens to items recorded missing?
They stay flagged against the asset with the audit that found them, so the follow-up is a worklist rather than something to reconstruct. The next count can see whether it was resolved.
Can an audit be done from a phone?
Yes, and that is the intended way. Scanning each item where it stands records the verification at the moment of checking rather than transcribing a clipboard afterwards, which is where counting errors are introduced.