Working note / Evidence

Design the evidence trail before the review.

Why record design belongs beside control design, not at the end of the audit calendar.

ControlLedger editorial example · 17 October 2026

Begin with the judgement

An evidence request is easier to answer when it names the control, relevant period and decision it needs to support. Without that context, teams often assemble a folder that is large but difficult to interpret.

Record the activity as it happens

A dated decision, a clear population and a reference to the operating record help a reviewer understand the result. A later reconstruction should be identified as such. Do not imply that it provides the same assurance as a contemporaneous record.

Make exceptions visible

The trail should include unresolved items and the authority for accepting or escalating them. An apparently clean summary can conceal a weak process when exception handling is missing. Preserve the uncertainty so the next decision is informed.

Use it in a review

Write down the question, name the record that could answer it and identify the person who can explain its limits. If those three things do not line up, refine the enquiry before gathering more material.

Related working notes

Give risk a decision owner.

Close a finding with evidence, not an intention.

Independent illustrative business content. This is not a standard, a client result or a certification claim.