An audit is a record that someone physically confirmed a device is where it should be.
From a device's detail page, choose Record audit. The modal asks for:
Auditor — optional.
Notes — optional.
Next audit due date — optional. "Leave blank for default interval."
All three fields are optional, so recording an audit can be a single click.
An AI assistant connected over MCP can record an audit too, using the record_asset_audit tool. It rolls the due date forward exactly like the app does, and the resulting entry is tagged with the connection as its source, so it's distinguishable from an audit recorded in the UI. See Connecting an integration and Connecting an AI assistant (MCP) for details.
If you enter a next audit due date, AssetBolt uses it.
If you leave it blank, AssetBolt adds your organization's default audit interval to today. That interval lives in Settings → Preferences and defaults to 365 days.
Either way, the device's next-audit-due date is updated and an audit record is written.
A device is due for audit when its next-audit-due date has passed, or when it has never been audited at all.
That second case matters: a freshly imported fleet is entirely overdue until you audit it once.
The Audit status report lists devices by audit state. The reporting dashboard shows an overdue-audits count, highlighted in red when it's above zero. Reports require a Pro plan or higher.
Audit due and Audit overdue are available as automation trigger events, so you can have AssetBolt notify you rather than checking — see Automations.
Two different things share a word.
An asset audit is the physical check described here — someone laid eyes on the laptop.
The audit log is the immutable record of every change made in AssetBolt: who edited what, and when. That's covered in Roles and permissions and viewable under Settings → Audit log.
