Audit Viewer

Review exported audit data locally before you share or print anything.

Overview

Audit Viewer is an online SimDuty page that reads the audit export format (simduty_audit_export_v1) in your browser. Export the file in Compliance / ELD > Records > Export JSON, then open it here. Nothing is uploaded to a server.

Use this page when you need to inspect day-level compliance evidence from a saved export, especially for findings, finance entries, timeline sequencing, and printable reports.

Estimated time: 6 minutes Purpose: online audit review Output: printable compliance report
Required

Export JSON from Compliance / ELD Records and open the saved audit file in the viewer.

Required

Confirm the selected compliance day before trusting any summary or timeline reading.

Required

Review critical findings first, then warnings, before using the report for decisions.

Recommended

Toggle local time when comparing UTC timestamps against your own timezone.

Recommended

Print DOT Report when you need a shareable record of the review.

Optional

Hide routine snapshots to reduce noise in the timeline table.

Open the online Audit Viewer: use it after exporting JSON from Records.

Quick path

  1. Open Compliance / ELD > Records and click Export JSON.
  2. Open the online Audit Viewer and load the exported simduty_audit_export_*.json file.
  3. Select the compliance day you want to inspect.
  4. Read Day Summary first, then Findings, Finance, and Timeline.
  5. Toggle local time or hide routine snapshots if needed, then print the DOT report.

Viewer controls

  • Drop file here / click to choose: loads the JSON export from your device.
  • Change file: replaces the current export without leaving the page.
  • Compliance day: filters the report to the selected day.
  • Show local time: converts the timeline display for easier operator reading.
  • Hide routine snapshots: removes low-value snapshot events from the timeline table.
  • Print DOT Report: opens the print flow for a shareable report.

Tabs and signals

Day Summary

  • Shows operational status, vehicle context, duty capacity, cost exposure, and quality signals.
  • Use it first to confirm the loaded export and understand the current day at a glance.

DOT Lite Findings

  • Groups findings into Critical, Warning, and Info buckets.
  • Start with critical items, then warnings, then informational evidence.
  • Use open and resolved defect lists to understand what still needs attention.

Finance

  • Lists financial entries with game time, category, event, amount, and description.
  • Use it to trace costs, refunds, penalties, or any finance-impacting audit event.

Timeline

  • Shows OFF/SB/D/ON duty events, sequence markers, and the current now line.
  • Use it to understand what happened during the day, not just the final status.

Interpretation guide

  • Audit Viewer reads the exported file in your browser. If the file looks wrong, the usual fix is to reload the correct export.
  • OK TO DRIVE means no critical blockers were detected in the current filtered view.
  • Use the compliance day selector before interpreting any summary card or finance line.
  • UTC Timestamp and Game Time are different views of the same event; use local time when comparing against your timezone.
  • If the report is going to support a review, resolve or document critical findings before printing.

Path and reference

Main paths:

  • Open the online Audit Viewer.
  • Audit Viewer: Day Summary
  • Audit Viewer: DOT Lite Findings
  • Audit Viewer: Finance
  • Audit Viewer: Timeline
  • simduty_audit_export_v1 - expected audit export format.
Related docs: Compliance / ELD - Records and audit

Validation checkpoint

  • The correct JSON export is loaded without errors.
  • The selected compliance day matches the day you intended to review.
  • Critical findings were checked before reading finance or printing.
  • Timeline and finance entries match the event sequence you expected.
  • The printed report was verified if you needed a shareable copy.

Quick support

  • If no file loads, confirm you exported a JSON audit file and that the filename matches the simduty_audit_export_*.json pattern.
  • If the day list looks empty or wrong, reload the export or switch to the intended compliance day.
  • If the timeline is noisy, enable Hide routine snapshots to reduce non-essential entries.
  • If the report needs to be shared, use Print DOT Report after verifying the summary and findings.

FAQ

  • Does Audit Viewer upload my file? No. The viewer processes the export locally in your browser and does not upload it to a server.
  • Which file does it expect? A SimDuty audit export JSON file using the simduty_audit_export_v1 format.
  • Which tab should I read first? Start with Day Summary, then move to Findings, Finance, and Timeline.
  • Why use local time? It makes event comparison easier while keeping UTC visible in the timeline.
  • What if the report looks stale? Reload the correct export and verify the selected compliance day before reading it again.