Key Points
- The project produced 36 clarified ISAs and one quality control standard (ISQC 1), all effective for periods beginning on or after 15 December 2009.
- Every clarified ISA follows the same five-section structure: Introduction, Objective, Definitions, Requirements, and Application and Other Explanatory Material.
- About half the standards received substantive new requirements alongside the redrafting, not just cosmetic reformatting.
- The "shall" convention replaced ambiguous present-tense language, so auditors can now distinguish mandatory actions from explanatory guidance without interpretation.
What is ISA Clarity Project?
Before 2004, ISAs mixed requirements with guidance in running prose. Auditors in different jurisdictions read the same paragraph and reached different conclusions about what was mandatory. The IAASB launched the Clarity Project to fix that structural problem. Between 2004 and March 2009, the board redrafted every ISA using a standard template. Requirements (signalled by "the auditor shall") sit in their own numbered section. Application and other explanatory material (the A-paragraphs) sits separately and supports the requirements without creating additional obligations.
Of the 36 clarified ISAs, 16 received substantive revisions on top of the redrafting. ISA 540 (Auditing Accounting Estimates) and ISA 550 (Related Parties) were among the standards that gained new requirements during the process. The remaining 20 were redrafted only, meaning the substance stayed the same but the structure changed. The IAASB also issued a clarified ISQC 1 (now superseded by ISQM 1). National standard-setters then adopted or converged with the clarified ISAs. The Dutch NV COS, for instance, mirrors the clarified ISA structure, and the AFM's inspection methodology references the "shall" requirements directly when assessing compliance.
Worked example: Hoffmann Maschinenbau GmbH
Client: German engineering company, FY2025, revenue EUR 28M, HGB reporter. The engagement team at a mid-sized WPK-registered firm is performing its first-year audit of Hoffmann under ISAs adopted in Germany (IDW transposition of clarified ISAs).
Step 1 — Identify the requirement paragraphs
The senior pulls ISA 315 (Revised 2019) and isolates every paragraph containing "the auditor shall." ISA 315.13 requires the auditor to design and perform risk assessment procedures to obtain audit evidence that provides a basis for identifying and assessing risks of material misstatement. The legacy programme referenced "understanding the entity" without linking to a specific requirement number.
Step 2 — Map application guidance to the work programme
ISA 315.A17-A30 provides guidance on how to obtain an understanding of the entity's internal control. The senior cross-references each A-paragraph to the requirement it supports. The legacy programme had combined the guidance and the requirement into a single narrative instruction, making it impossible for the reviewer to see which steps were mandatory.
Step 3 — Update the file structure
The engagement team restructures its planning memorandum so that each section header references the ISA objective (e.g., "Objective per ISA 315.11") and each working paper cites the specific "shall" paragraph it addresses. Hoffmann's prior auditor had documented procedures under topic headings alone ("Revenue testing," "Inventory count") with no ISA references.
Conclusion: The mapping exercise for Hoffmann took approximately 14 hours of senior time but produced a file that an external inspector can trace requirement-by-requirement, which is the outcome the Clarity Project was designed to enable.
Why it matters in practice
Teams often cite ISA paragraph numbers from the application material (A-paragraphs) as if they impose requirements. They do not. Only the numbered paragraphs in the Requirements section of each clarified ISA create obligations. The IAASB Preface, paragraph 15, states that the auditor "shall" comply with a requirement unless the requirement is conditional and the condition does not exist. Confusing an A-paragraph explanation with a "shall" requirement leads to either unnecessary procedures or missed mandatory steps.
The AFM and FRC have both noted in inspection cycles that some firms updated their methodology manuals to the clarified ISA structure but did not update the underlying work programmes. The result is a methodology document that references the correct paragraph numbers while the actual engagement file still follows pre-Clarity formatting, creating a disconnect that inspectors identify during engagement quality reviews as a failure to implement the standards consistently.
Clarified ISAs vs. pre-Clarity ISAs
| Dimension | Clarified ISAs (post-2009) | Pre-Clarity ISAs |
|---|---|---|
| Structure | Five standardised sections per ISA: Introduction, Objective, Definitions, Requirements, Application Material | Running prose mixing requirements and guidance in a single narrative |
| Identifying requirements | "The auditor shall" signals every mandatory action | Present-tense verbs ("the auditor considers," "the auditor obtains") left the mandatory/optional boundary unclear |
| Application guidance | A-paragraphs in a separate section, cross-referenced to the requirement they support | Guidance woven into the same paragraphs as requirements |
| Objectives | Each ISA states an explicit objective for the auditor | Objectives were implicit or absent in many standards |
| Substantive content | 16 ISAs received new requirements during the redraft process | The previous versions reflected whatever content existed before 2004 |
The distinction matters because pre-Clarity engagement files often documented procedures without tracing them to specific requirements. When an inspector asks "which ISA paragraph requires this step?", a pre-Clarity file may not have an answer. The clarified format was designed to make that traceability automatic, both for the engagement team building the file and for the reviewer or inspector evaluating it.
Related terms
Frequently asked questions
Did the Clarity Project change what auditors actually have to do?
For roughly half the standards, yes. Sixteen of the 36 ISAs received substantive new requirements alongside the structural redraft. ISA 550 (Related Parties) gained new procedures for identifying related party relationships, and ISA 540 expanded the requirements around accounting estimates. The remaining 20 ISAs changed in structure only; the obligations stayed the same.
How do I tell which ISA paragraphs are requirements and which are guidance?
Requirements appear in the section headed "Requirements" and use the phrase "the auditor shall." Application and Other Explanatory Material paragraphs carry an "A" prefix (e.g., ISA 315.A17) and sit in a separate section. The Preface to the IAASB Pronouncements, paragraph 14, confirms that A-paragraphs do not impose additional requirements but are relevant to the proper application of the requirements they support.
Do local standards like NV COS or IDW follow the Clarity format?
Most jurisdictions that adopted ISAs transposed the clarified structure. The Dutch NV COS mirrors the ISA numbering and "shall" convention. IDW in Germany adopted the clarified ISAs with limited national additions. Where local requirements go beyond the ISA, they are typically flagged as additional "shall" paragraphs or presented in a separate national appendix.