Engagement Risk Management Checklist

Steps a public accounting firm runs to identify, assess, and respond to risk on an attest or tax engagement — from client acceptance through partner sign-off and workpaper archive.

6 sections 22 steps Collects data
1

Client Acceptance & Independence

  1. Run conflict check in the practice management system
    • Search Karbon, Canopy, or TaxDome for prior or current relationships with the prospect, its owners, and related parties. Common misses: a partner's spouse on the board, a referring attorney who is also a tax client, or a subsidiary the firm bookkeeps for.

  2. Confirm independence under the AICPA Code
    • For attest engagements (audit, review, compilation with assurance), apply the full AICPA independence standard. Watch for nonattest services like bookkeeping or 401(k) administration that breach independence on review or audit clients. SSARS preparation engagements have a reduced standard but still require disclosure.

  3. Contact predecessor auditor per AU-C 210
    • Required for new audit engagements. Obtain client consent in writing, then ask the predecessor about disagreements with management, fraud or illegal-act concerns, and reasons for the change. Skipping this step is a peer-review finding.

  4. Document the client acceptance decision
    • Risk-rate the engagement (low / moderate / high) considering industry, ownership complexity, going-concern indicators, and prior preparer disputes. Managing partner signs off on any moderate-or-higher engagement before the engagement letter goes out.

    Collects list
  5. Document required acceptance safeguards
    • For conditional acceptance, record the specific safeguards required: concurring partner review, expanded scope, fee escrow, or a kill-switch clause in the engagement letter. The acceptance memo names each safeguard and who owns it.

2

Engagement Risk Identification

  1. Review prior-year workpapers and review notes
    • Pull last year's risk register, management letter, and unresolved review notes from the engagement file. Recurring issues (e.g., late bank recs, weak revenue cutoff, unsupported AJEs) are next year's risks until the controller can demonstrate a fix.

  2. Hold fraud brainstorming session per AU-C 240
    • Required on every audit. Whole engagement team participates — partner, manager, seniors, and IT specialist if applicable. Cover incentives, opportunities, and rationalizations; presume revenue recognition fraud risk and management override of controls. Document the discussion in the engagement file.

  3. Map industry and entity-level risk factors
    • Document inherent risks specific to the client's industry — construction WIP and percentage-of-completion estimates, SaaS deferred revenue, dealer floor-plan financing, nonprofit donor restrictions. Cross-check against AICPA industry audit guides.

3

Risk Assessment & Materiality

  1. Set planning and performance materiality
    • Use the firm's benchmark policy — typically 5% of pre-tax income for profitable companies, 0.5–1% of revenue for break-even or loss companies, 1–2% of net assets for nonprofits. Performance materiality is usually 50–75% of planning materiality. Document the benchmark and the rationale for any deviation.

    Collects number
  2. Perform preliminary analytical procedures
    • Run year-over-year and budget-vs-actual analytics on revenue, gross margin, A/R aging, A/P aging, and key ratios. Variances over performance materiality without a documented business explanation become risk factors carried forward to the audit program.

  3. Score ROMM at the assertion level
    • For each significant account and disclosure, rate inherent risk and control risk by assertion (existence, completeness, valuation, rights & obligations, presentation). Significant risks — those requiring special audit consideration under AU-C 315 — must be listed individually with planned response.

    Collects list
4

Risk Response Planning

  1. Tailor the audit program to significant risks
    • Boilerplate audit programs from Caseware or CCH ProSystem fx are a starting point, not a deliverable. Each significant risk needs a linked procedure with clear assertion coverage, sample size justification, and tickmark legend. Generic 'review for reasonableness' steps fail peer review.

  2. Decide on controls reliance versus substantive testing
    • For each significant cycle (revenue, purchasing, payroll, financial close), decide whether to test controls and reduce substantive work, or go fully substantive. Reliance requires walkthroughs plus operating-effectiveness testing — don't choose reliance unless the budgeted hours actually cover both.

  3. Assign risk owners on the engagement team
    • Each significant risk gets a named owner — usually a senior or manager — accountable for executing the planned response, clearing review notes, and reporting status weekly. Avoid concentrating all risks on the in-charge senior; spread by competency and availability.

  4. Schedule valuation or IT specialist support
    • Goodwill impairment, complex derivatives, ESOP valuations, and ITGC testing on large ERPs need specialists booked early — they're scarce in busy season. Lock dates in the engagement calendar before fieldwork starts, not when the senior hits the issue.

5

Risk Monitoring During Fieldwork

  1. Track open risks in the weekly status meeting
    • Standing 30-minute meeting with partner, manager, and seniors. Walk the risk register: status, blockers, PBC items overdue, fee budget burn. Risks dropped without explanation reappear at year-end as missed adjustments.

  2. Reassess risks when new information surfaces
    • Discovery during fieldwork — a related-party transaction not previously disclosed, a covenant breach, a subsequent-event lawsuit — triggers a planned reassessment. Document the new risk, the changed response, and partner approval before continuing.

    Collects list
  3. Update the risk register with new exposures
    • Add the new risk with assertion, planned procedure, owner, and target date. If the new risk is significant, update the AU-C 315 risk assessment memo and notify the EQR partner. Email the controller a list of additional PBC items needed.

  4. Escalate scope changes through a change order
    • If the new risk expands hours by more than the engagement letter's threshold (typically 10%), issue a change order to the client before incurring the work. Absorbing scope creep silently is the fastest way to blow the realization rate on the engagement.

6

Engagement Wrap-Up

  1. Obtain the management representation letter
    • Letter must be dated the same day as the audit report and signed by the CEO and CFO. Include representations on fraud, related parties, going concern, subsequent events, and any uncorrected misstatements (the SUM schedule). Do not release the report without the signed letter in hand.

  2. Complete partner EQR sign-off
    • Engagement Quality Review partner is independent of the engagement team. Reviews significant judgments, financial statements, and report wording. All EQR notes cleared before report release; document concurrence in the engagement file.

    Collects signature Collects paragraph
  3. Archive workpapers per firm retention policy
    • Documentation completion date is 60 days after report release for non-issuers (AU-C 230); 45 days for issuers (PCAOB AS 1215). After that date, no additions or deletions without a documented reason. Retention is typically 7 years for audits, longer for tax workpapers in IRS-extended jurisdictions.

    Collects file

Use this template

Copy it to your account, customize the steps, and run it with your team in minutes.


Sections 6
Steps 22
Category Accounting
Price Free to start
Need a different process

Browse hundreds of free templates across every team and industry.

Back to template library

Run Engagement Risk Management Checklist with your team

Customize the steps, assign roles, set a schedule, and keep a complete record for every run.