Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 55 additions & 3 deletions content/knowledge-base/run-your-first-audit.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: "Run Your First Audit"
description: "Step-by-step guide to running your first physical inventory audit in Shelf — from creating the session to exporting the PDF report. Covers the 7-day free trial."
category: "Assets"
date: "2026-04-17"
updated: "2026-08-24"
updated: "2026-08-28"
layout: "knowledge-base"
---

Expand Down Expand Up @@ -81,6 +81,32 @@ Those two buttons sit on assets you have **not** scanned yet as well as on the o

![Audit scan page with the progress bar and each scanned row marked Expected or Unexpected](https://qliecghuzfchfjwaisyx.supabase.co/storage/v1/object/public/website-images/features/audits-scan.webp)

### Undoing a Scan

Scan the wrong label and you can take it straight back off. Every scanned row on the scan page carries a **bin icon** at the end of it, and clicking it removes that scan from the audit.

What happens next depends on what you scanned:

- **An asset that was on the expected list** goes back to **Not scanned**, and the time of the scan and the name of the person who made it are cleared with it. It is as though nobody had reached that shelf yet.
- **An asset that was not on the list** leaves the audit entirely. Nothing but the scan put it there, so removing the scan removes the row.

The Found, Not scanned and Unexpected counts are then recounted from the rows themselves rather than nudged down by one, so the totals can never drift away from the list they summarise. The **Activity** tab records who removed which scan.

You are not limited to the scans you made in this sitting. Reopening the scan page restores everything already recorded on the audit into the list, so a mis-scan from yesterday morning is as removable as one from a minute ago.

Removal only works while the audit is still running. Once it is **Completed** or **Cancelled** its numbers have been reported, and Shelf refuses the change with *"This audit is no longer live, so its scans cannot be changed."*

### If an Asset Is Deleted After It Was Scanned

An audit is a historical record, so a scan keeps its meaning even after the asset behind it is gone. Every scan stores the asset's name and whether the audit expected it, at the moment it is scanned.

Delete that asset later and the scan page still shows the row, named **"Camera body A (deleted)"**, still counted as found, and still badged **Expected** if the audit had expected it. The row becomes read-only, since there is no asset left to open, comment on or photograph. A scan recorded before Shelf began storing names, whose asset has since gone, reads **"Deleted asset"** with the code that was scanned.

A live asset always shows its **current** name, not the stored one, so renaming an asset mid-audit is reflected straight away. The stored name is there to survive deletion, not to freeze naming.

One thing to know: the asset table on the audit's **overview** lists the assets the audit is scoped to, and a deleted asset is no longer one of them, so it has no row there while the audit's counts still include it. The scan page is where the full scan history lives.


---

## Step 4: Review Results
Expand All @@ -105,11 +131,23 @@ Use the **Filter by audit status** dropdown to isolate items for follow-up. The
When scanning is done:

1. Click **Complete Audit** (bottom-right of the scan page, or from the Actions dropdown on the overview)
2. Shelf sends a **summary email** to the audit creator with final counts
3. From the completed audit's overview, click **Actions → Download Receipt** to export a **PDF report** with found/missing/unexpected breakdowns
2. Check the **Audit Summary** in the confirmation dialog. It states the Expected, Found, Missing and Unexpected counts one last time, and completing cannot be undone
3. Add a **Completion Note** and up to five photos if you have closing observations. Both are optional, and both print in the receipt's Findings section
Comment thread
coderabbitai[bot] marked this conversation as resolved.
4. Confirm with **Complete Audit**. Shelf sends a **summary email** to the audit creator with final counts
5. From the completed audit's overview, click **Actions → Download Receipt** to export a **PDF report** with found/missing/unexpected breakdowns

The PDF is your compliance artifact — hand it to insurance, your manager, or file it for regulatory review. It carries a **Findings** section as well as the counts: your completion note and its photos first, then one block per asset holding what was written about that item next to the pictures taken of it.

### Completing an Audit Where Nothing Was Found

An audit that turns up nothing is still a finding, and often an urgent one: the cupboard is empty, the van was cleared out, the room was cleaned before anyone counted it. You can complete it.

The confirmation dialog says what that decision means before anything is written:

> No assets were scanned. Completing now marks all 20 expected assets as missing.
Comment thread
coderabbitai[bot] marked this conversation as resolved.

Confirm and every expected asset is recorded as **Missing**, exactly as an asset you scanned past would have been. The receipt, the counts and the audits list all read the same way they would after any other completion.

---

## After the Trial
Expand Down Expand Up @@ -159,6 +197,20 @@ Findings holds what **people** recorded. Shelf's own trail (statuses changing, t

Yes, and it is one of the more useful things you can do. **Add comment** and **Add image** appear on rows that are still **Not scanned**, so you can photograph the empty slot or write down what the storeroom manager told you. The note stays on the audit record and prints in the receipt's **Findings** section, whether or not that asset was ever scanned.

### I scanned the wrong thing. Can I take it back?

Yes, while the audit is still running. Click the **bin icon** at the end of the scanned row on the scan page. An expected asset returns to **Not scanned** with the scan time and scanner cleared; an asset that was not on the list disappears from the audit altogether. The counts are recounted from the rows, and the **Activity** tab keeps a record of who removed what.

Reopening the scan page restores every scan already on the audit, so this is not limited to the ones you made in this sitting. A **Completed** or **Cancelled** audit refuses the change: its numbers have already been reported.

### Can I complete an audit if I found nothing at all?

Yes, and Shelf tells you what that means first. The confirmation dialog says *"No assets were scanned. Completing now marks all N expected assets as missing."* Confirm and every expected asset is recorded as **Missing**. An empty cupboard is a finding worth putting on the record, not a reason to leave the audit hanging.

### What happens to an audit if I delete an asset that was already scanned?

The scan stays. Its row on the scan page keeps the name the asset had when it was scanned, marked **(deleted)**, and it still counts toward the audit's found total and still shows whether the audit expected it. The row is read-only from then on, because there is no asset page left behind it. The asset table on the audit's overview lists the assets the audit is scoped to, so a deleted asset has no row there.

### Can multiple people scan the same audit?

Currently, each audit session supports a single assigned scanner. For large-scale audits, create multiple sessions scoped to different areas and assign each to a different team member.
Expand Down
18 changes: 18 additions & 0 deletions content/updates/an-audit-can-be-corrected-while-it-runs.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: "An audit can be corrected while it runs, and its record survives a deleted asset"
description: "Remove a mis-scan from a live audit and the counts recount themselves, complete an audit where nothing was found, and keep a scanned row readable after its asset is deleted."
date: "2026-08-27"
image: "https://qliecghuzfchfjwaisyx.supabase.co/storage/v1/object/public/website-images/features/audits-scan.webp"
readMoreUrl: "/knowledge-base/run-your-first-audit#undoing-a-scan"
layout: "update"
---

Three changes to audits, all of them about the audit record being honest rather than merely tidy.

**A scan you did not mean to make comes back off.** Click the bin icon at the end of a scanned row on the scan page. An asset that was on the expected list returns to **Not scanned**, with the time of the scan and the name of the person who made it cleared; an asset that was never on the list leaves the audit entirely, because nothing but the scan put it there. The Found, Not scanned and Unexpected counts are then recounted from the rows rather than nudged down by one, so a total can never drift away from the list it summarises, and the **Activity** tab keeps a record of who removed what. Reopening the scan page restores everything already recorded, so yesterday's mis-scan is as correctable as this minute's. A **Completed** or **Cancelled** audit refuses the change: its numbers have been reported.

**An audit where nothing was found can be completed.** It used to sit there with the Complete button greyed out and no explanation, which left the most alarming result an audit can produce, an empty room, as the one result you could not put on the record. Completing is now offered, and the confirmation says what it means before anything is written: *"No assets were scanned. Completing now marks all 20 expected assets as missing."* Confirm and every expected asset is recorded as **Missing**, with the same receipt and the same counts as any other completion.

**A deleted asset no longer erases the scan that found it.** Every scan now stores the asset's name and whether the audit expected it, at the moment it is scanned. Delete the asset afterwards and its row survives, reading **"Camera body A (deleted)"** and still badged Expected if the audit had expected it, instead of the blank row marked Unexpected it used to become. Scans recorded before this shipped have been filled in from their assets, so the protection covers your existing audits rather than only the ones you run from here. A live asset still shows its current name: the stored one exists to survive deletion, not to freeze naming.

Removing a scan is also available to the Companion app now through the mobile API. The button for it arrives in a future app release.
Loading