An engagement plan specifies the audit procedures assigned to particular processes, accounts, and transaction classes, including their purpose and expected coverage. It converts established strategic decisions into instructions that the engagement team can execute, supervise, and revise as evidence develops.
The prior-year plan supplies useful knowledge about accounts and processes, but its conclusions depend on conditions that may have changed during the current period. The auditor compares planned work with actual hours, findings, unresolved matters, and subsequent developments before retaining any approach.
The starting package normally contains these materials:
- The prior-year plan and completed audit programs, including explanations for procedures added or removed during fieldwork.
- Process descriptions, relevant controls, assessed risks, misstatements, control deficiencies, and matters requiring follow-up in the current year.
- Prior client assistance request listings, delivery problems, actual staff hours, review notes, and information about specialist involvement.
- Current trial balances, transaction volumes, personnel responsibilities, contractual terms, system changes, and the engagement's established scope and milestones.
The auditor evaluates changes in the current period by connecting each new fact to the affected accounts and planning assumptions.
Common mistakes
- Wrong population boundary. Combining both applications into one undifferentiated annual export conceals the July 1 boundary needed for the revised billing work.
- Unchanged information request. Retaining only R1 through R4 omits R5's conversion evidence and R6's independent dispatch population needed for shipment-completeness testing.
- Wrong testing direction. Increasing recorded-sales selections addresses recorded entries; shipments omitted throughout July through December require the separate source-to-record procedure.
Bottom line
- A current engagement plan updates prior knowledge and specifies procedures for the assigned processes, accounts, and transaction classes.
- Plan rows connect assertions, risks, reliance decisions, procedure purposes, nature, timing, extent, staff, and supporting requests.
- Understanding control design and implementation differs from testing operating effectiveness and obtaining substantive evidence.
- Control testing is necessary when reliance is intended or substantive procedures alone cannot provide sufficient appropriate evidence.
Exam shortcut
Mark the changed fact and effective date first. Split the affected transaction population before revising any procedure, request, or hour estimate. For a matrix task, read across each row: risk, assertion, purpose, evidence, timing, extent, staff, request. Fill the missing operational link. For a request-list task, replace vague entries such as “billing data” with fields, period filters, reconciliation totals, an owner, and a due date.
The full lesson (about 5,891 words, 39 min read) adds 2 worked examples, all 6 common mistakes, a self-check, free in the app.
Learning objectives
- II.A2
Browse all free CPA AUD lessons or jump into free CPA AUD practice questions.