An audit trail is the history behind a record: who entered it, when, what changed, the old and new values, and who approved it. In construction finance, it covers things like budget revisions, change order approvals, invoice coding, pay app edits and lien waiver receipts. A good audit trail can’t be edited by the people whose actions it records.
Why it matters
Owners on cost-plus and GMP jobs audit costs. Surety and lenders review financials. Disputes and claims turn on who knew what, and when. And as AI starts drafting entries, you need to see which actions came from a person and which came from software, and who approved them.
Worked example
Illustrative: INV-4471 from Volt Electric for $48,200 exceeds the remaining commitment on PO-118 by $6,150. The audit trail shows the invoice was received, flagged at three-way match, held by the AP clerk, reviewed by the PM, and released only after a change order raised the PO, each step with a name and timestamp.
Common mistakes
- Relying on spreadsheets where anyone can overwrite a cell without a trace.
- Logging changes but not the reason or the approval.
- Letting shared logins make “who did it” impossible to answer.
How os.construction handles it
We’re building an audit trail into the data core so every change, human or agent-drafted, is recorded with who approved it. It’s in development with founding contractors.