Show the evidence behind completed assurance tasks

What this means for your practice

Define what evidence a task needs and who accepts it. The software should support the organisation's assurance process without presenting a task count as proof of compliance.

What to ask before you choose

Ask to mark a fictional task finished without its required evidence. The gap should remain visible to its owner and reviewer. Start with one real task type and agree what useful evidence looks like. A completion count cannot replace the organisation's actual assurance judgement.

Explain the difference between done and accepted

Choose one task and ask the owner and reviewer to describe what they each mean by complete. The owner may have carried out the work, while the reviewer still needs a record showing what was done. The system should make those positions clear without implying that a tick is an independent assurance judgement.

Agree proportionate evidence for the particular task and identify who can accept it. A document, a dated record or a demonstration may serve different purposes; uploading more files does not automatically make the evidence better. Try a fictional task with missing evidence, an unsuitable attachment and a replacement provided after review. The owner should understand what needs correcting, and the reviewer should know which version is being considered. Keep unresolved questions visible in the management view. The useful result is a clear route from the task to the work and its review, with decisions about requirements and assurance left to the organisation's authorised people.

How to check the result

Count completed tasks still awaiting evidence acceptance.