Audit
How audit behavior works in TrialStack as the reviewable history around changes, decisions, and governed workflow actions.
Why it matters
flowchart LR
Change[Change] --> Audit[Audit trail]
Audit --> Accountability[Accountability]
Audit explains how TrialStack preserves a reviewable history around changes, decisions, and governance-sensitive actions.
How it works
flowchart LR
History[History] --> Audit[Audit]
Justification[Justification] --> Audit
Approval[Approval state] --> Audit
The product keeps history, justification, approval state, and related activity visible so teams can understand what changed, who changed it, and why a decision was made.
When to use it
flowchart TD
Sensitive[Change is sensitive] --> Audit[Read audit trail]
Routine[Change is routine] --> Still[Still useful]
This concept matters when the team needs to review a sensitive change, explain how a record evolved, or prove that an action did not happen silently.
What to watch for
flowchart LR
Audit[Audit] --> Ops[Operational use]
Ops --> Review[Daily review]
Audit is not only for administrators or inspectors. It is part of normal operational work whenever the history of a decision matters.