Audit Trail and Change History

Admin & Settings
Reading Time:
3 min read

What is this?

Clue logs changes automatically throughout the system. When someone updates a work order, moves a dispatch, resolves an inspection issue, or changes an asset's status, the system records who did it, when, and what changed. No extra steps needed.

Where to find history

Change history appears in context, right where the data lives:

  • Work Orders - Open any work order and check the History section. See every status change, assignment, cost update, and note added, with timestamps and who made each change.
  • Dispatch Requests - Request history shows every status transition: created, approved, dispatched, completed. Each step logged with the person and time.
  • Inspection Issues - See when an issue was reported, acknowledged, deferred, or resolved. The full conversation trail stays with the issue.
  • Equipment - Asset status changes, transfers between projects, meter reading updates.

Full audit access via API

Admins who need comprehensive audit data can access the full logs through Clue's REST API. This covers every change across the system, not just what is visible in the UI. Useful for compliance audits, investigations, or building custom reports.

The full details

  • Automatic. No setup needed. Logging happens on every create, update, and delete action.
  • Context-specific. History appears on the record it belongs to. Work order history on the work order. Asset history on the asset.
  • Immutable. Logged entries cannot be edited or deleted. The record is permanent.
  • API access. Full audit logs available via REST API for admins and integrations.
  • Exportable. API data can be exported for compliance reporting or external analysis.

Tips

  • Check work order history before escalating. If something looks wrong on a WO, the history shows exactly what changed and who changed it.
  • Use dispatch history for accountability. If a request was delayed, the timestamps show where the bottleneck was.
  • For compliance audits, use the API. The in-app history covers common needs. The API gives you everything.