Apply Canadian assurance standards, engagement guidelines, and user decision needs.
Canadian assurance standards guide how the practitioner plans, performs, documents, and reports an engagement. In Assurance cases, the key task is usually to choose the right standards direction for the engagement type and user need, not to recite standard numbers.
The practical task is to distinguish standards from criteria, decide whether the request is a financial statement audit, review, other assurance engagement, agreed procedures, internal audit project, or advisory service, and make sure the report wording does not imply more assurance than the work supports.
This lesson focuses on how to:
This distinction is a frequent source of weak answers. Standards govern the practitioner’s work. Criteria govern the evaluation of the subject matter.
| Item | What it governs | Example question |
|---|---|---|
| Standards | How the practitioner plans, performs, documents, and reports the engagement. | Is this a financial statement audit, review, other assurance engagement, or non-assurance service? |
| Criteria | What the subject matter is evaluated against. | Are the financial statements prepared under the right framework, or is compliance measured against the right rules? |
| Engagement terms | What the practitioner and client agreed to do. | Is the objective, scope, responsibility, report, and limitation clear? |
| User need | Why the engagement is being performed. | Does the user need reasonable assurance, limited assurance, factual findings, or advice? |
For example, an audit of financial statements may use Canadian Auditing Standards for the practitioner’s work and a financial reporting framework as criteria. An assurance engagement over compliance may use a different assurance direction and a grant agreement as criteria.
Use the engagement’s nature and user need to choose the direction. The answer should explain the fit, not just name a label.
| Engagement description | Likely standards direction | Planning implication |
|---|---|---|
| Audit of complete financial statements for broad users. | Canadian Auditing Standards. | Risk assessment, materiality, audit evidence, documentation, and audit report requirements drive the work. |
| Review of financial statements. | Review engagement guidance rather than audit standards. | Limited assurance procedures and report wording differ from an audit. |
| Assurance over controls, compliance, sustainability, or performance information. | Other Canadian assurance guidance appropriate to the subject matter. | Criteria suitability and subject-matter evidence become central. |
| Agreed procedures for specified users. | Procedures-and-findings model rather than assurance conclusion. | Users agree on procedures and draw their own conclusions. |
| Internal audit or consulting project. | Internal audit, advisory, or project guidance rather than external audit standards. | Objectivity, scope, reporting line, and purpose drive the work. |
| Management advisory service. | Non-assurance service. | No independent assurance conclusion should be implied. |
If the requested service does not match the user’s need, recommend a different engagement type. For example, if a lender requires reasonable assurance over annual financial statements, an agreed procedures report over selected balances may not satisfy the requirement.
Standards selection should support the user’s decision, not the practitioner’s convenience.
| User need | Standards implication |
|---|---|
| High confidence for broad financial statement users. | Audit direction may be required. |
| Moderate credibility for financial information. | Review may be sufficient if accepted by users. |
| Confirmation of specific procedures or facts. | Agreed procedures may fit better than assurance. |
| Confidence over non-financial subject matter. | Other assurance guidance may be more appropriate than audit standards. |
| Internal improvement advice. | Consulting or internal audit may be more suitable than assurance. |
| Compliance with a contract or funder requirement. | Follow the engagement type and reporting form specified by the requirement. |
User need also affects distribution. A broad user group usually requires a different report form than a narrow specified-user engagement. If only a lender, funder, or regulator will use the report, restrictions on use may be appropriate.
The selected standards path affects what the report can say. Report wording should match the level of work performed and should avoid implying assurance that was not obtained.
| Selection issue | Communication consequence |
|---|---|
| Audit standards used when audit is required. | Report communicates an audit conclusion based on sufficient appropriate audit evidence. |
| Review engagement selected. | Report wording should not imply audit-level assurance. |
| Other assurance engagement selected. | Report should describe subject matter, criteria, assurance level, and any restrictions. |
| Agreed procedures selected. | Report should communicate procedures and findings, not an assurance opinion. |
| Non-assurance service selected. | Communication should avoid language that implies independent assurance. |
When the client or user asks for a report label that does not match the work, the practitioner should clarify the engagement before acceptance. A “quick audit” request may actually be a review, agreed procedures engagement, or advisory project, depending on the user need and evidence expected.
Standards selection affects the plan. It changes the amount and type of evidence, documentation, supervision, quality review, report wording, and communication with management or governance.
| Planning area | Why standards direction matters |
|---|---|
| Evidence | Audit, review, agreed procedures, and advisory work require different evidence depth. |
| Documentation | Working papers must support the selected engagement type and conclusion. |
| Independence | Assurance engagements require careful independence and objectivity assessment. |
| Criteria | Other assurance engagements depend heavily on suitable criteria for the subject matter. |
| Report wording | The report must match the assurance level and avoid expectation gaps. |
| Quality management | Engagement risk may require consultation, review, or specialist involvement. |
| Step | Question | Output |
|---|---|---|
| 1. Engagement type | What work is being requested? | Audit, review, other assurance, agreed procedures, internal audit, or advisory. |
| 2. User need | What level and type of confidence do users need? | Assurance or non-assurance decision. |
| 3. Standards direction | Which standards or guidance path fits? | Selected direction. |
| 4. Criteria distinction | What criteria evaluate the subject matter? | Criteria reminder. |
| 5. Reporting effect | What should the report or communication say or avoid saying? | Reporting consequence. |
Use this sequence when a case asks whether a proposed engagement is appropriate, whether audit standards apply, whether a report can be issued, or whether a different engagement type would better satisfy users.
| Pitfall | Correction |
|---|---|
| Applying audit standards to every assurance-looking request. | Confirm whether the engagement is actually a financial statement audit. |
| Confusing standards with criteria. | Standards govern the work; criteria evaluate the subject matter. |
| Ignoring user decision needs. | Match assurance level and report form to what users require. |
| Letting report wording imply too much assurance. | Use wording consistent with the selected engagement type. |
| Treating advisory work as assurance. | Avoid assurance language when the practitioner is providing advice only. |