Blog
Audit-trail habits for busy close teams
Busy teams do not fail audits because they lack intelligence. They fail because evidence was “going to be filed later,” and later became fieldwork week.
Attach before you announce
If a balance is ready to mark complete in the quarter-close audit app, the supporting file should already sit on the task. Announcing completion in chat without the attachment teaches the team that words count more than artefacts.
Prefer originals over screenshots
Screenshots of bank portals expire in usefulness. Export the statement or the CSV your procedure actually relies on. Screenshots are fine as a supplement when a UI state matters—not as the sole support.
Write one sentence of context
A PDF alone rarely explains a judgement. One sentence—“Accrual based on PO 4412 received 28 Feb, goods not yet invoiced”—saves twenty minutes of reconstruction later.
Protect deep work blocks
Close weeks fill with status meetings. Reserve ninety minutes where the only goal is attaching evidence for three named tasks. Ritual beats aspiration.
Module 3 of Quarter-Close Audit Mastery drills these habits with timed labs. Awkward at first; quieter by the next quarter.