Controls in practice
What a useful internal-control review should leave behind
A field guide to process ownership, testable evidence and actions that management can actually close.

Start with the decision, not a generic checklist
A useful review begins by identifying what the process must achieve, which failures would matter and who relies on the result. A checklist can help organise work, but it cannot replace an understanding of the transaction flow, systems, people and evidence involved.
This framing keeps the review proportionate. It also prevents a long list of observations that are technically correct but commercially irrelevant.
Map the process and its evidence
Walk the process from initiation to recording, approval, execution and reporting. For each material step, identify the person responsible, the system or document used, the control objective and the evidence that would show the control actually operated.
- The event or risk that triggers the control
- The named control owner and any reviewer
- The frequency and population covered
- The evidence retained and where it is stored
- The escalation route when an exception is found
Separate design gaps from operating failures
A control may be well designed but inconsistently performed, or performed diligently without addressing the real risk. Those are different problems and need different remedies. Design gaps require a better control; operating failures require clearer ownership, capacity, training, evidence or supervision.
The report should state which condition exists and the evidence supporting that conclusion. Avoid assigning a high rating solely because a policy is missing when another effective control already addresses the risk.
Leave management with a closeable action plan
Every agreed action should identify the risk addressed, the deliverable, one accountable owner, a realistic date and the evidence required for closure. Broad actions such as “strengthen controls” cannot be tested or closed.
The final pack should therefore contain a concise process map, control matrix, evidence register, prioritised findings and an action tracker. That is the difference between a review that records weaknesses and one that helps management change the process.