Scoping
Writing scope notes that survive fieldwork
Scope notes fail quietly. The engagement letter sounds precise, the audit planning workflow app has a tidy list of procedures, and the junior still asks—on Monday morning—what “limited revenue testing” actually means for this client.
The gap is usually linguistic. Partners write for lawyers. Seniors write for software fields. Juniors need verbs and owners. When those three audiences are not reconciled before kickoff, fieldwork invents a fourth version.
Start from the letter, not the template
Open the signed letter and highlight every clause that implies work. Ignore the boilerplate about professional standards for a moment. What remains should become named procedures in the app—each with an owner and a “done when” statement.
If a clause cannot become a procedure, either the letter is decorative or the plan is incomplete. Both are planning defects, not junior defects.
Write “done when” in the same field juniors open
Many teams keep completion criteria in a memo nobody opens after Friday. Put the criterion next to the procedure in the workflow app. Example: “Revenue cut-off sample agreed to dispatch notes for the final five business days; exceptions logged with invoice references.”
Ban orphan owners
Every procedure needs a named person, not a grade. “Senior” is not an owner when three seniors rotate across entities. If the app only supports roles, add the person’s name in the first comment and keep it updated when staffing changes.
Run a five-minute mismatch check
Before releasing the pack, read the letter’s highlighted clauses aloud against the app list. Anything in the letter missing from the app—or present in the app without letter cover—gets resolved before the planning meeting ends. That habit alone removes most week-one surprises we hear about in office hours.