Evidence notes that survive an IFRS-minded reviewer
Reviewers trained to chase assertions will ask whether your conclusion still matches the criteria after they read the attachments. Write as if they will.
IFRS-minded readers are not searching for decorative language. They want to know which assertion or control objective you touched, what you observed, and why the observation supports or challenges the objective. When those layers collapse into a single paragraph of adjectives, the file becomes a puzzle.
Use a three-line spine for every item
Criteria. Observation. Conclusion. Keep them visually separate even inside a spreadsheet row. If an exception appears, add a fourth line for impact on the control objective — not a speech about how disappointed you feel.
Name the system of record
Screenshots without system and timestamp force reverse engineering. A footer or caption with environment, user role (if relevant), and capture time keeps the evidence usable months later when staff have rotated.
Stop hiding the criteria in the conclusion
A common failure: the conclusion invents a stricter bar than the criteria stated. Align them, or document a deliberate tightening with approval. Reviewers treat silent tightening as bias.
Where to go deeper
See Module 04 in our flagship course and the evidence chronology drills in the playbook. For enrollment paths, visit pricing.