System resources

HME Fire Risk Audit user guide

Start here if you need to understand how to use the system. This guide explains the dashboard, audit capture, drafts, review, reports, settings, demo mode, and finance tools in plain language.

Field audits

Capture

Machine inspections, findings, photos, drafts, and submission.

Review control

Approve

Reviewers can approve, return, or escalate without editing findings.

Audit records

Report

PDF and Excel exports with evidence and protected download history.

Business layer

Manage

Users, settings, demo workspaces, invoices, royalties, and licensing.

Who uses the system

Inspector

Completes machine audits, records findings, adds photos, saves drafts, and submits work.

Reviewer

Checks submitted audits, leaves review comments, approves, returns, or escalates work.

Viewer

Reads allocated audit records and exports reports without changing findings.

Client admin

Manages the company workspace, users, approved domains, setup, and access.

Finance or owner

Views invoices, usage, payments, royalties, subscriptions, and commercial records.

Platform super admin

Oversees the full platform, support, technical operations, and commercial truth records.

Start here

1. Use the dashboard to see what is happening

The dashboard is the main operational view. It shows audit volume, high-risk exposure, pending reviews, evidence totals, recent audit records, and the risk profile.

Steps

  1. 1Open the dashboard after signing in.
  2. 2Check the top metrics for audit count, high-risk items, pending review work, and evidence photos.
  3. 3Use the audit list to open a record and check its current status.
  4. 4Use the risk profile to quickly see whether the workspace is carrying low, medium, high, or extreme-high risk items.
  5. 5Start a new audit from the dashboard when your role allows audit creation.

Helpful notes

  1. A client can use this page during a pilot meeting to understand audit activity at a glance.
  2. The dashboard should be the first place managers look before asking inspectors or reviewers for updates.
HME audit dashboard showing metrics, audit table, and risk profile.

Inspector workflow

2. Create a machine audit

The audit workflow is designed for field users. It breaks the audit into structured sections, captures required fields, stores evidence, and allows progress to be saved before submission.

Steps

  1. 1Open New audit.
  2. 2Enter the company, fleet, and machine details.
  3. 3Work through the audit sections one by one.
  4. 4Record the rating, observation, finding, or action for each applicable item.
  5. 5Add photos for findings so the record has visual evidence.
  6. 6Save the audit as a draft if you are not ready to submit.
  7. 7Submit only when all required fields are complete.

Helpful notes

  1. If an item does not apply, write that clearly instead of leaving it blank.
  2. Photos should show both good and bad practice so machine deterioration can be tracked over time.
New audit workflow showing structured machine audit sections.

Field continuity

3. Use drafts when work is interrupted

Drafts help inspectors keep working when an audit is incomplete, interrupted, or temporarily affected by connection issues.

Steps

  1. 1Save an audit before leaving the page or moving away from a machine.
  2. 2Open Drafts to find saved work.
  3. 3Resume the correct draft and continue from the saved audit data.
  4. 4Retry queued work when the device is back online.
  5. 5Submit the audit when the record is complete.

Helpful notes

  1. Drafts reduce the chance of losing field progress.
  2. Offline and real-device testing still needs to be completed before calling the system fully field-production-ready.

Workflow available in the system

This topic uses live product controls when the user has the correct role.

Quality control

4. Review submitted audits

The reviewer workflow separates audit capture from approval. Reviewers check the evidence and comments, then approve, return, or escalate the audit.

Steps

  1. 1Open Reviewer.
  2. 2Select a submitted audit from the review queue.
  3. 3Read the machine details, findings, risk ratings, observations, and evidence.
  4. 4Add reviewer comments.
  5. 5Approve the audit when it is acceptable.
  6. 6Return the audit to the inspector when corrections are needed.
  7. 7Escalate when the audit needs higher attention.

Helpful notes

  1. Reviewers should not change the inspector findings directly.
  2. Returned audits keep a clearer audit trail because corrections happen through the correction workflow.
Reviewer queue showing audits awaiting review.

Client evidence

5. Generate reports and exports

Reports turn audit records into shareable PDF and Excel files. Stored reports are protected so users must have permission before downloading them.

Steps

  1. 1Open Reports.
  2. 2Find the audit record that needs to be exported.
  3. 3Open the report detail page.
  4. 4Generate or download the PDF report.
  5. 5Generate or download the Excel export when spreadsheet analysis is needed.
  6. 6Use stored report files when you need to reopen previously generated exports.

Helpful notes

  1. Demo reports are watermarked so they are not mistaken for legal compliance records.
  2. Production report storage needs Vercel Blob configured before live legal record storage is complete.
Reports page showing export controls and report records.

Workspace setup

6. Set up the company workspace

Settings are where workspace identity, team setup, approved company email domains, branding, and future licensing controls live.

Steps

  1. 1Open Settings.
  2. 2Confirm the account and company profile details.
  3. 3Add approved company email domains so workspaces can avoid personal email signups.
  4. 4Open Users to invite team members when your role allows it.
  5. 5Use Onboarding to complete company setup before normal operations.
  6. 6Use branding settings for report identity and future company theme controls.

Helpful notes

  1. Company users should ideally use work email addresses for a professional, controlled workspace.
  2. The onboarding page helps client admins complete setup before entering day-to-day operations.
Workspace settings page showing profile, domains, and foundation cards.

Safe testing

7. Try the demo without touching real records

Demo mode is intended for prospects, testers, and training. It creates isolated data so testers can explore without affecting real client workspaces.

Steps

  1. 1Open the login page.
  2. 2Choose Try demo when demo mode is available.
  3. 3Explore the dashboard, audit records, review flow, reports, and settings using simulated data.
  4. 4Reset the demo workspace when you need a fresh environment.
  5. 5Use separate demo sessions for separate testers.

Helpful notes

  1. Demo data should stay inside demo accounts only.
  2. Normal accounts should not contain simulated audit records.

Workflow available in the system

This topic uses live product controls when the user has the correct role.

Commercial workflow

8. Use finance tools for licensing and billing

The finance area supports the commercial model behind the platform: subscriptions, included usage, overages, active machines, archived machines, invoices, payments, royalties, and agreements.

Steps

  1. 1Open Finance when your role allows billing access.
  2. 2Review subscription and billing-account status.
  3. 3Check usage records for audits and machines.
  4. 4Generate invoice drafts for billing periods.
  5. 5Open invoice pages to review line items, totals, payment status, and receipts.
  6. 6Use royalty and agreement areas to track the commercial arrangement.

Helpful notes

  1. This section is sensitive and should only be visible to approved finance, owner, or platform roles.
  2. Payment provider integration, including Ozow if selected, still needs final production setup.
Finance dashboard showing billing, usage, and commercial controls.

What is available now

Audit workflow

Capture, drafts, review, correction, approval, and exports are implemented.

Access control

Roles and permissions separate inspectors, reviewers, viewers, admins, finance, and platform owners.

Reports

PDF and Excel exports, protected downloads, and report history are available.

Commercial layer

Invoices, payments, royalties, agreements, and usage billing foundations exist.

Workspace setup

Settings, approved domains, onboarding, team invites, and branding foundations are in place.

Evidence controls

Evidence and reports use protected routes, hashes, snapshots, and audit trail records.

Before full production

Final setup still matters.

  • The local system is close to pilot-ready for controlled testing.
  • The public production URL still needs Clerk authentication before real users can safely sign in.
  • Permanent production evidence and report storage needs Vercel Blob.
  • Production emails need Resend credentials and a verified sending domain.
  • Payment collection needs a selected provider, such as Ozow, plus webhook and reconciliation setup.
  • Real-device mobile, camera, offline, and field QA must still be completed before full production use.