> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/using-monolith/evidence-management/audits/auditing-items.md).

# Auditing Items

Verify Evidence and Storage Items during an Audit, record passed or failed results, and review the resulting Audit history.

The **Auditing Items** workflow is where your team verifies the physical items included in an Audit.

Items begin in a **Pending** state. As each item is reviewed, mark it as **Passed** or **Failed** based on whether its physical location and recorded information match what you expect.

Use the status views at the top of the Audit to move between:

* **All**
* **Pending**
* **Passed**
* **Failed**

The counts displayed with each view update as the Audit progresses.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FhxIq21a6CnoMJosUnIZu%2Fimage.png?alt=media&amp;token=6f0c26b4-3e7c-4622-9a8f-fbd882684c9f" alt=""><figcaption><p>Pending Items Audit Tab</p></figcaption></figure>

### How to Audit an Item

Auditing an item generally involves verifying:

1. The item's physical location
2. The item's recorded details, when applicable

Open or review the item card in the Audit and compare the information shown in Monolith with the physical item in your possession.

### Verify the Item Location

Each Audit item displays its recorded location information.

For example, an Evidence Item might show a Location Path such as:

**Calgary / Evidence Room / AAA**

This indicates that Monolith expects the item to be located:

* In the **Calgary** Office
* Within the **Evidence Room** Location Group
* At the **AAA** Location

Locate the physical item and confirm that its actual location matches the location recorded in Monolith.

See [**Item Locations**](/monolith/using-monolith/evidence-management/item-locations.md) for information about how Offices, Location Groups, and individual Locations are used to track Evidence and Storage Items.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FXjKROez203csMVj6omEw%2Fimage.png?alt=media&amp;token=c4f1b25a-24ac-463e-b88e-303300764665" alt="" width="503"><figcaption><p>Audit Item</p></figcaption></figure>

### Verify the Item Details

An Audit can also be used to confirm information about the item itself.

Review the available Evidence or Storage Item information and compare it with the physical item or your organization's records.

This can help identify inaccurate or outdated information that should be corrected in Monolith.

## Audit Procedure

### Fail an Audit Item

If the item's location or other reviewed information does not match the expected record, change the item's Audit status to **Failed**.

When marking an item as Failed, enter a note describing the issue.

For example:

* Item is not in the recorded location
* Item label does not match the Monolith record
* Recorded item details need to be corrected
* Additional investigation is required before the item can be verified

After the status is updated, the item moves to the **Failed** view.

The underlying Evidence or Storage Item can then be reviewed and corrected as needed.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2F7S1SJztniReLWJpLsNjN%2FAudit%20Item%20Failed.gif?alt=media&amp;token=f32abb32-988a-44d3-919c-b86208a43038" alt=""><figcaption><p>Failing an audit item</p></figcaption></figure>

## Pass an Audit Item

If the item's location and reviewed information are correct, change the Audit status to **Passed**.

Enter a note when additional context about the verification is useful.

An item that previously failed can also be marked as Passed after the underlying issue has been corrected and the item has been verified again.

After the status is updated, the item moves to the **Passed** view.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FLewcPEBrda3ds4CTWz1g%2FPassing%20an%20Audit%20item.gif?alt=media&amp;token=b386f4e1-91bc-4609-a7c3-95ee5cc34a66" alt=""><figcaption><p>Passing an audit item</p></figcaption></figure>

### Audit Methods

Monolith records how an item was verified during the Audit.

Common Audit methods include:

* **Manual:** The auditor reviewed the item and updated its status directly in Monolith.
* **Scanned:** The item was located and verified using a supported barcode or QR code scanning workflow.

When you manually change an item's status to Passed or Failed, the Audit method is recorded as **Manual**.

See [**Using a Scanner**](/monolith/using-monolith/evidence-management/audits/using-a-scanner.md) for information about scanning items during an Audit.

### Audit Logs

Each time an Audit item's status is updated, Monolith records the activity in the **Audit Logs**.

Audit Log entries can include:

* Timestamp
* Audit Item
* User
* Audit Status
* Notes entered during verification

These logs provide a historical record of the Audit process and can help explain why an item failed, what was corrected, and when it was later verified.

Audit history associated with a specific Evidence Item can also be viewed from that item's **Audit Logs** area.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FpJI2J7uugt3CZRoi8kP0%2Fimage.png?alt=media&amp;token=347ab2a4-7607-457e-b226-40cb22b469a0" alt=""><figcaption><p>Audit Logs</p></figcaption></figure>

### Recommended Audit Workflow

A typical item verification process is:

1. Start with the **Pending** items.
2. Locate the physical item.
3. Compare its location and applicable details with the Monolith record.
4. Mark the item **Passed** if the information is correct.
5. Mark the item **Failed** and document the issue if something does not match.
6. Correct the underlying Evidence or Storage record when needed.
7. Reverify failed items after corrections are made.
8. Review the remaining Pending and Failed items before completing the Audit.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FmS6CZhEBQZR5iWdgCrB6%2Fimage.png?alt=media&amp;token=f8d9bec4-5cb6-472a-9ef5-918799dcf069" alt=""><figcaption></figcaption></figure>

### Related Documentation

* [**Audits**](/monolith/using-monolith/evidence-management/audits.md)
* [**Creating Audits**](/monolith/using-monolith/evidence-management/audits/creating-audits.md)
* [**Viewing and Accessing Audits**](/monolith/using-monolith/evidence-management/audits/viewing-and-accessing-audits.md)
* [**Audit Features & Layout**](/monolith/using-monolith/evidence-management/audits/audit-features-and-layout.md)
* [**Using a Scanner**](/monolith/using-monolith/evidence-management/audits/using-a-scanner.md)
* [**Item Locations**](/monolith/using-monolith/evidence-management/item-locations.md)
* [**Evidence Items**](/monolith/using-monolith/evidence-management/evidence-items.md)
* [**Storage Items**](/monolith/using-monolith/evidence-management/storage-items.md)
