The audit trail

The audit trail is the compliance spine’s foundation: a complete, tamper-evident record of everything that happens to your controlled records. It’s the single most important piece of evidence in a regulated system, and in TraceUnified it’s a by-product of normal work rather than something assembled before an inspection.

What every entry captures

Each audit entry records the essentials of an action: who performed it, the action taken, the change itself — the before and after — the timestamp, and a link to the signature where one applied. This is what lets the trail answer not just “something changed” but “this person changed this field from this value to that value, at this time, and signed for it.”

Across every module

The audit trail spans the whole platform — requirements, architecture, tests, risk, SBOM, reviews, releases, training. There isn’t a separate, partial log per module; there’s one consistent record of activity across all of them. From the Compliance module you can review it and filter by module, by type of action, by user, or by searching, so you can answer a precise question rather than scrolling an undifferentiated log.

Tamper-evident and complete

The trail is tamper-evident: entries can’t be edited or deleted to tell a different story, and the record is captured automatically as actions happen rather than entered after the fact. This is what gives it evidentiary weight — an auditor can rely on it precisely because no one can quietly curate it.

Evidence as a by-product

The defining idea of the platform is that compliance evidence accumulates as you work. The audit trail is that idea made concrete: every governed action — every edit, transition, signature, and approval — lands in the trail the moment it happens. When an inspection asks “show me the history of this record,” the answer already exists, complete and trustworthy.

The spine, assembled

Controlled states define how records move, electronic signatures gate the controlled moves, and the audit trail records all of it permanently. Together they’re the compliance backbone every module shares. Part two of this section covers the frameworks this backbone supports and the verification that proves you’re ready.