Audit assets

Phase 1 preview — pages render fixture data only; no changes are saved.
Selected
1
Eligible
1
Blocked / skipped
0
Would change
1
Would stay as is
0
  • Batch rule: every asset is processed on its own; one failing doesn't undo the others.
  • Every audited asset gets one `audit` activity row (location = the submitted location, note, audited-by) and a webhook message; there is no `update` row.
  • Assets are processed in one loop: a failure on one asset doesn't undo the others.

Selected assets (1)

AssetCurrent stateVerdictReason / noteWould become Actions
TC-00025
Lost conference laptop
Lost/Stolen · Not checked outWould proceed Archived: legacy audits it anyway (there is no status or assignment restriction).Last audit: Never audited → 2026-10-13 01:44 Next audit: unchanged

Details

Where the assets were found; it is logged either way.
Leave empty to keep each asset's next audit date (checked-rows audit only: the scanner defaults it, the single audit form clears it).

Activity this would write (1)

Action typeAssetTargetLocationNoteChanged Actions
Audit — — — — —
Cancel Submitting is not available in Phase 1 — this page is a UI preview.