Monolith Forensics
  • Monolith Resources
    • Accessing Monolith
  • Monolith Features
    • 🏁Getting Started
      • Basic License Terms
      • Monolith Desktop Setup
      • Login & 2FA
      • SSO Login
      • First Steps
    • On-Premises Deployments
      • Managing Licensing
      • Requirements
      • Monolith Containers (Docker)
      • Deployment
        • .env
        • docker-compose.yml
        • Docker Installation
        • How to Deploy
        • Useful Commands
      • Monolith Data
      • Backups
        • Restoring Backups
      • Updates
      • Custom Domains and TLS
      • Connecting to File Shares
      • Update MySQL Container
      • Using External MySQL Database
      • Manually Update User Email
    • Monolith UI Features
      • Tables
      • Query Filter
      • Global Search
    • Cloud Security
      • Security Overview
      • Single Sign On (SSO)
    • Hardware Integrations
      • Dymo Label Printers
      • Printer Recommendations
      • Scanner Recommendations
      • Signature Tablets
    • Case Reports
      • Report Templates
        • Template Variables
        • Template Examples
      • Monolith Case Reports
    • Storage Items
    • Audits
      • Creating Audits
      • Viewing and Accessing Audits
      • Audit Features & Layout
      • Auditing Items
      • Using a scanner
    • People
      • Clients
        • Client Page
    • Lab Management
      • Forensic Software
      • Equipment
    • Settings
      • System
      • Email Notifications
      • Organization Info
      • Editor Templates
      • Relay Settings
        • Basic Details
        • User Management
        • Relay Instructions
        • Custom Field Options
      • Item Number Formats
      • Case Types
      • Case Statuses
      • Case Progress
      • Evidence Types
      • Evidence Progress
      • Item Labels
      • Custom Fields
      • Task Templates
      • Time Entry Categories
      • QA Checklist Items
      • QA Issue Types
      • Admin Log
      • Integrations
  • Monolith API
    • API Access
      • API Endpoints
      • Authentication
    • Info API
    • Cases API
      • Get Cases
      • Create Case
    • Evidence API
      • Get Evidence
      • Create Evidence
      • Update Evidence
      • Delete Evidence
      • Migrate Evidence
    • Locations API
      • Get Locations
    • Chain of Custody API
      • Get COC Records
      • Create COC Records
    • Clients API
      • Get Clients
      • Create Client
    • Inquiries API
      • Get Inquiries
      • Create Inquiries
    • Tasks API
      • Get Tasks
      • Create Task
    • Monolith Endpoints
  • About Monolith Forensics
    • Support
    • Privacy Policy
    • End User License Agreement
Powered by GitBook
On this page
  • How to Audit an Item
  • Verifying the item location
  • Verifying the item's details
  • Audit Procedure
  • Failing an audit item
  • Passing an audit item
  • Audit methods
  • Audit logs
Export as PDF
  1. Monolith Features
  2. Audits

Auditing Items

PreviousAudit Features & LayoutNextUsing a scanner

Last updated 1 year ago

Each of the status tabs can be used to navigate through the items being audited.

How to Audit an Item

Auditing an item typically involves at least two procedures:

Verifying the item location

One type of audit requires the auditor to compare the location of the item listed in Monolith with its actual location in the forensic lab or designated evidence storage.

For Example, consider the following item:

According to Monolith, this item is currently located within the Calgary office, at the Evidence Room group, and at the AAA location.

Verify the location by finding the physical item in your posession and check if its actual location in reality matches the location recorded in Monolith.

Verifying the item's details

The other type of audit requires the auditor to verify all the item's details and not just the location. This type of audit requires more work but can be useful in maintaining accurate data in your Monolith database.

Audit Procedure

Failing an audit item

If the item's location or other details are incorrect, use the status selector of the item to mark it as "Failed". This will open a meu where you can enter a note about why the item failed.

You can then fix the item right away by updating the location or details in Monolith, or you can wait until you have audited all items first.

Once the status update is submitted, the audit item card is moved to the "Failed" tab.

Passing an audit item

If you determine that the details and location of the item are correct, you can then mark the item as having passed its audit.

This may also occur after you have failed the item and then updated the item with accurate information.

The process to pass an item is identical to failing an item. You simply update its status to "Passed" and enter a note about why it passed.

Audit methods

When updating an audit item's status, the audit method will update whenever you pass or fail an item.

The audit methods currently used are "Manual" and "Scanned". Using the status selector to update the item's status will set the audit method to "Manual" as it represent that the auditor manually passed or failed the item without using a scanner.

The "Scanned" method is discussed in more detail here: Using a scanner

Audit logs

The audit logs record each time and audit item's status is updated. These logs include a timestamp, auditor, and the notes entered at the time of audit.

These logs can be used for documentation or to keep track of why items did not pass an audit and then repair the items as needed.

The audit logs can also be viewed within the audit items detail's page.

Here is an example of the audit logs from this evidence items details page:

Pending Items Audit Tab
Audit Item
Failing an audit item
Passing an audit item
Audit Logs