ITAM / Asset Tagger
Audit Reports
Review Carlos's Austin office audit, what was scanned, when, and which three devices were missing from the 3rd floor.
Real-world scenario
Maya Chen · IT Manager at Bluewave Labs
After Carlos completes the Austin 3F audit, Maya opens Audit Reports to confirm 82 of 85 devices verified, reviews the three gaps, and signs off on quarter-end physical inventory compliance.
Before you begin
- At least one completed audit session from Audit Mode
- Access to Asset Tagger reports (admin or asset manager)
Overview
Audit Reports store the history of physical verification sessions. Maya uses them for compliance sign-off; Carlos uses them to chase down devices that were in WorkVerge but not found during the Austin walkthrough.
Report contents
- Audit session name, date, and auditor
- List of scanned devices with timestamps
- Total scanned vs expected (when scope is defined)
- Devices not scanned, potential gaps requiring follow-up
Step-by-step
- 1
Open ITAM → Physical Assets → Asset Tagger → Audit Reports
You see a list of completed audit sessions sorted by date.
- 2
Select the Austin session
Click "Austin 3F. Q2 2026" from Carlos's Wednesday walkthrough.
- 3
Review scanned devices
See every device scanned with timestamp, including Sophie's MacBook at 10:14 AM.
- 4
Identify gaps
Compare scanned count (82) to expected scope (85). Three devices in WorkVerge were not found on the floor.
- 5
Export or share with Maya
Use the report for compliance documentation and follow-up assignments.
Example report
Austin 3F. Q2 2026 (Maya's review)
- Auditor: Carlos Reyes
- Date: 2026-06-04
- Scanned: 82 devices
- Expected: 85 (Austin 3F inventory)
- Coverage: 96.5%
- Not scanned: AUS-ENG-019, AUS-ENG-033, AUS-MON-007
- Maya's action: Approve audit with follow-up tickets for 3 gaps
Pair with asset tickets
Related articles