Control Review Atlas
Financial auditing guidance for internal control reviews — mapped as a working atlas
Use this page as a orientation layer before you enroll. It mirrors the checkpoints we teach, without replacing a live Lab seat.
What the Atlas covers
Internal control reviews fail quietly when scoping, testing, and reporting speak different dialects. The Atlas lines those dialects up: which assertion you claim, which control you trust, which artifact proves the trust, and how you close an exception.
It is intentionally opinionated. We favor durable system trails over anecdotal “the manager said,” and we treat last year’s matrix as a hypothesis — not a relic to photocopy.
Review flow
-
Frame the cycle
Name the reporting period, entities in scope, and which financial statement lines drive attention. Record what you deliberately leave out.
-
Bind controls to assertions
Every key control should answer completeness, accuracy, existence/occurrence, rights/obligations, valuation, or presentation — or explain why entity-level coverage substitutes.
-
Walk, then test
Confirm the process still matches the narrative. Only then design samples. Outdated narratives are the most expensive false comfort in a review.
-
Write the trail
Evidence indexes, deviation tables, and issue wording belong in the same pack. Readers should not hunt chat logs for the conclusion.
When to go deeper
If your team already argues about sample sizes or severity labels, move from the Atlas into the Internal Control Review Lab. If the friction is only ITGC linkage, the Workshop on the courses page is the shorter path.
Korea-facing notes
Subsidiary packs feeding a parent auditor often need bilingual captions on evidence indexes. The Atlas checklist flags where a translator’s note should sit so reviewers do not treat a gloss as primary evidence.