Preparing decision evidence for an audit
When a review arrives, the questions are always the same, whether it comes from internal audit, a regulator, a due diligence team or a dispute. Who approved this, when, on what basis, and can you prove the record hasn’t changed since? The expensive part is reconstructing answers you could have been recording all along.
What reviewers actually ask
- Authority: who made the call, and were they entitled to?
- Process: did the decision follow your own stated policy, with the right approvals in the right order?
- Basis: what information and alternatives were considered at the time?
- Integrity: is the record contemporaneous, and can you show it hasn’t been altered since?
- Follow-through: did what was approved actually happen?
Why reconstruction fails
Most organisations answer audits by archaeology: exporting email threads, scrolling chat history, and interviewing whoever is left. It’s slow, and it’s weak. Threads show discussion, not approval; documents are editable after the fact; and the person who knew the basis for the call may have left. Evidence assembled after the question is asked is always worth less than a record made at the time.
What good decision evidence looks like
| Property | In practice |
|---|---|
| Contemporaneous | The record was created when the decision was made, not reconstructed for the audit. |
| Attributed | Named driver, named approver, named reviewers. Roles, not “the team”. |
| Complete | The decision, the why, the alternatives rejected, the policy route it followed. |
| Tamper-evident | History is append-only; every edit, approval, and bypass is itself on the record. |
| Exportable | You can hand the reviewer a package, not a screen-share of your chat history. |
Preparing before the request arrives
- Inventory your decision types. Which kinds of decisions would a reviewer care about? Spend over a threshold, data handling, security exceptions, vendor selection.
- Write the approval policy down. Who must sign each type, in what order, and what triggers escalation or re-approval.
- Centralise the records. One system of record beats five tools and a folder convention, especially under time pressure.
- Test the export. Run the drill: pick last quarter’s riskiest decision and assemble its evidence. Time it. That’s your audit readiness.
Worked example: connect a change to the version approved
Fictional evaluation example. The versions and dates below are illustrative review targets, not rows taken from a Traceway export or its Demo workspace.
Suppose a team approves a one-year vendor renewal, then proposes a three-month bridge after a new service requirement arrives. For this exercise, its policy requires a named approver to approve a change to the renewal term. Ask each tool you are considering to demonstrate the sequence using a decision you are authorised to share.
| Point in the exercise | Evidence to request | What the reviewer should establish |
|---|---|---|
| Version 1 approved — 1 October, 09:00 UTC | The one-year renewal, its rationale and rejected alternative; the approver’s identity and role; the approval time and a reference tying that action to version 1. | Which exact wording received approval, and the stated basis for that approval. |
| Version 2 proposed — 8 October, 11:00 UTC | The proposed three-month term, the reason for the change, its author and time, and the relationship to version 1. | What changed. Version 1’s approval does not, by itself, approve the proposed term under this policy. |
| Version 2 approved — 9 October, 14:00 UTC | The reviewed version 2 contents, the required review and approval events, and the earlier version and approval still available in the history. | Which version is now approved and how to recover the earlier decision without rewriting it. |
A name and timestamp alone do not show which version was approved. Follow the reference from the approval event to the contents it approved, then compare that with the later version. A product may represent a change as a new version or as a linked replacement decision; ask how it preserves that relationship.
Check the exported result away from the application
- Ask an authorised operator to export the evidence for this exercise. Note which records it covers, the workspace or environment, the time window and the export time. Confirm who can generate the export and how the intended reviewer can receive it.
- Open the result without relying on the live page. Find the earlier and later contents, their rationale, the change history and each required sign-off. Record missing items rather than filling the gaps from memory.
- Match each approval to the version or replacement it covers. Check that a proposal is distinguishable from an approved decision and that the earlier approval remains recoverable.
- Establish what the export contains and what it only links to. Check whether those links still require an account, whether the reviewer can access the supporting material and how the package can be checked using the product’s documented verification method.
Keep the results as evaluation findings. A package-integrity check does not establish that the approver read the material or that the decision was right. If a version, approval reference or supporting item cannot be retrieved, leave that part unproved.
Use the decision record template to prepare the record before running this exercise. Apply the same test to the tools you already use and to any new candidate, with your own approval policy, intended permissions and evidence requirements.
For decisions documented in an ADR or pull request, follow the manual Git-revision and business-approval handoff and record the result in the approval workflow scorecard. The handoff uses public template files; it does not demonstrate a Traceway integration or approval export.
How Traceway implements this
Traceway writes every decision to an insert-only, tamper-evident history (approvals, edits, and bypasses included) with roles routed by decision type, so following your policy and proving you followed it are the same act. When the review comes, you export the evidence instead of reconstructing it.
The current Security & data statement describes what the trail proves and its limits. In a demo, ask to run the same evidence check using your intended roles and a record you are authorised to share.
Traceway is a platform for recording and approving business decisions. When a decision changes, its owners can see which commitments to revisit.
Stop losing the why.
Traceway is the system of record for decisions: AI capture, real governance, an audit-grade trail, and a chain from strategy to the work.
Book a demo