A scope of work is the part of the agreement you will reread most often. When a firm says "that was part of the job" or you say "that was never included", the scope is the only thing either of you can point to. This guide shows how to write one for accounting work so that it can settle that argument in a few minutes.
Country-neutral. Nothing below depends on a particular country's law. How a contract is enforced does depend on where you work and on the governing law it names, so check your own regulator and have counsel adapt the wording to your engagement and jurisdiction. General information, not legal advice.
What a scope of work is
A scope of work states the tasks you will perform, on which records, to what standard, by when, and what you will hand over. It is usually the core of a statement of work (see Statement of work vs engagement letter vs contract), but the same content can sit inside a short engagement agreement for a small job.
It is not the firm's engagement with its client. The client's engagement letter sets what the firm will deliver to the client. Your scope describes the slice of that work you are responsible for. Ask the firm which parts of its own engagement your slice supports, because your work is only useful if it fits.
The nine parts of a clear scope
1. Purpose and context
One or two sentences: "Prepare tie-out and support workpapers for the year-end financial statements of the named engagement, for review by the firm's engagement team." Name the engagement by the firm's own reference, not by a client name, if the firm wants to keep names out of the document. Whatever you call it, both sides must be able to identify the same job.
2. Records and inputs
List what the firm will supply and by when: trial balance, bank statements, prior-year file, client schedules, access to the firm's workspace. Say what happens if inputs are late. A sentence such as "delivery dates move day for day with late inputs" protects you from a deadline you cannot meet through no fault of your own.
3. Tasks and procedures
Name each task in verbs and quantities. Compare:
- Weak: "Help with the audit file."
- Better: "Tie the draft balance sheet and profit and loss statement to the final trial balance; prepare lead schedules for cash, receivables, fixed assets and payables; cross-reference every figure to its support."
Count what can be counted: number of bank accounts, number of schedules, number of statements. A count turns a vague promise into something you can finish and the firm can check.
4. Standards and methodology
State which standard or template the work is prepared to, and who supplies it. For example, "prepared on the firm's workpaper templates under the firm's documentation policy". The firm decides what its file must contain. Writing the standard into the scope is how you record that you are meeting the firm's requirement, and it separates the result you owe from the way you get there.
5. Deliverables and format
List each deliverable, its format and its destination: "completed workpaper sections uploaded to the firm's workspace; review notes in the firm's standard note format". Specify the evidence of completion, such as a sign-off line, a checklist or a status message.
6. Review and acceptance
Say who reviews your work, how comments reach you, how many rounds of fixes are included, and how long the firm has to respond. A line such as "up to two rounds of review comments are included; further rounds are handled under a change order" prevents the quiet growth of the job.
7. Timeline
Give a start date, interim dates if needed, and a final date, each tied to its input. If the firm may offer files and you may decline them, say that too, so that availability does not become an obligation by accident.
8. Fees and expenses
Link the fee to the scope: a fixed fee for the defined deliverables, a per-file fee for a defined file type and size, or an hourly rate with an estimate and a cap. Say what the fee excludes. The detail of rates and payment terms belongs in the agreement; the scope is where the measure of work is set.
9. Exclusions
The exclusions clause is the cheapest protection in the document. List what is not included: "The scope does not include preparing tax returns, communicating with the client, signing or issuing any report, or testing beyond the schedules listed." State what you will do if you see something outside scope: tell the firm, in writing, and wait for a change order.
A worked example (illustrative)
This is an invented example to show the arithmetic.
A firm offers you a compilation-type file: a set of financial statements for a small business with 3 bank accounts, 1 loan and 12 months of transactions. The scope says you will reconcile each bank account for 12 months, prepare a loan schedule, and draft the statements.
You estimate 2 hours per bank account per year of reconciliations, which for 3 accounts is 3 x 2 = 6 hours. You estimate 1.5 hours for the loan schedule and 4.5 hours for drafting. The estimate is 6 + 1.5 + 4.5 = 12 hours. The scope states "estimated at 12 hours; any increase above 15 hours (12 plus 25 percent) needs written approval before work continues." The 25 percent margin is 12 x 0.25 = 3 hours, so the approval point is 12 + 3 = 15 hours.
The numbers are not a market benchmark. They show a method: break the work into counted units, estimate each, add them, set an approval point, and write it down.
Scope checklist before you sign
- Does the scope name the engagement or file so both sides mean the same job?
- Are inputs and their dates listed, with a rule for late inputs?
- Are tasks stated in verbs and counts?
- Is the standard or template named, and who supplies it?
- Are deliverables listed with a format and a place to deliver?
- Is the review process stated, including the number of fix rounds?
- Are start and finish dates tied to inputs?
- Is the fee tied to defined deliverables?
- Are exclusions listed, including signing or issuing anything?
- Is there a stated way to change the scope?
Frequently asked questions
How detailed should a scope be?
Detailed enough that someone who was not in the conversation can tell whether a given task is in or out. A page is usually enough for a file-level job. A scope that runs to many pages for a small task is hard to keep current.
Who writes the scope, me or the firm?
Either. If the firm sends one, check it against the nine parts and ask for changes in writing. If you write it, send it before work starts and ask for a written acknowledgement.
What do professional standards say about scope?
Professional standards place requirements on the firm's own engagement terms with its client. For audits, AU-C section 210, Terms of Engagement, says the agreed terms should be documented in an audit engagement letter or other suitable form of written agreement (paragraph .10). The AICPA auditing standards in the sources have the current text. They do not set the terms between you and the firm, so your scope has to do that work.
Should the scope say I will not sign anything?
Yes. State that the firm's responsible professional signs and issues, and that you prepare or review work for the firm. It makes the roles clear to everyone who later reads the file.
What if the scope turns out to be wrong?
Stop and say so before spending the extra time. Use a change order to record the new scope, time and fee. See Change orders for accounting engagements.
Sources
- AICPA Code of Professional Conduct (full text, PDF): https://pub.aicpa.org/codeofconduct/ethicsresources/et-cod.pdf
- AICPA Statements on Auditing Standards currently effective (AU-C sections): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective