Signed With a Firm, Not a Person? Five Things the Scope of Work Must Say First

The scope of work is the only part of the paperwork that describes the job itself, and in a firm of any size it is also the document that decides which of forty people ends up on your account. Everything else in the packet governs money, liability and termination. The scope governs reality. When the provider is a single operator, the gap between what the scope says and what gets done is narrow, because the person who wrote it is the person doing it. When the provider is an organization with departments, that gap is institutional, and it has to be closed in writing before anyone starts.

1. The name of the person doing the work, and what happens when they leave

Large providers sell with their strongest people and staff with whoever is available in week three. That is not deception, it is capacity management, and it is the single most common theme buried inside otherwise positive reviews of established firms: the pitch was excellent, the delivery was somebody else. A scope that names the lead, the backup, and the percentage of hours each is expected to carry turns an assumption into a term. Ask for a reassignment clause too, one that requires written notice and gives you a short window to object, because the person assigned in January is rarely the person on the file in June.

The same paragraph should say whether any part of the work is subcontracted, and to whom. Firms that white-label a specialty, tax preparation inside a bookkeeping practice, structural review inside an architecture practice, drafting inside an engineering practice, are not doing anything unusual. You simply want to know, because the subcontractor's calendar becomes your schedule risk and their insurance becomes part of your exposure. A provider comfortable with its own bench will write this down without hesitation.

2. Deliverables written as finished conditions, not as activities

There is a meaningful difference between a scope that promises to review your vendor contracts and a scope that promises a written memo identifying termination rights, auto-renewal dates and assignment restrictions across a named list of eighteen agreements, delivered as a single document. The first describes effort. The second describes a thing that either exists on your desk or does not. Activity language is where billing disputes are born, because effort can always be characterized as having occurred. Insist that every item ends in a noun you could hold, open or forward to someone else.

Quantities belong in the same sentence. How many agreements, how many site visits, how many rounds of revision, how many stakeholder interviews, how many pages. Larger providers usually have internal estimates behind their price, built from staffing models and historical hours, and they will share the assumptions if you ask plainly. Once the quantities are on paper, an overrun becomes a conversation about a change order rather than a conversation about whether you are being unreasonable.

3. The exclusions, and the boundary with whoever is working next to you

Exclusions read as defensive, and clients skim them, which is precisely why they decide so many arguments. In an organization, exclusions also mark internal borders: the consulting arm does not do the implementation, the audit team does not advise, the design group does not pull permits. Those divisions exist for licensing and independence reasons that are entirely legitimate, and they are invisible from outside unless the document spells them out. Read the exclusion list as a map of who else you will need to hire, and price that gap now rather than in week six.

Then handle the seam. If another vendor, an internal team or a general contractor is working adjacent to this scope, the document should say who coordinates, how often, and what information passes between them. Seams are where schedules slip, because each side reasonably believes the other owns the handoff. One named coordinator, with a standing check-in on the calendar, resolves most of it before it starts.

4. How a change gets priced, and who inside your own organization can approve it

Every scope changes. The question is whether the mechanism was agreed when both sides were calm. A workable clause states the form a change request takes, the turnaround for a priced response, the rate or rate card applied, and the schedule impact expressed in days. It should also state that work outside the scope does not proceed until the change is signed, which protects you from the retroactive invoice and protects the provider from doing unpaid work on a verbal nod. Large firms almost always have this machinery already, often inside a client portal with a change log and version history.

Name your own approver, singular, and tell the provider in writing. The expensive version of this failure is familiar: a junior person on your side says yes in a hallway, the firm documents the instruction correctly, and the invoice arrives with your own employee's name on it. Authority limits, a dollar threshold above which a second signature is required, cost nothing to add and prevent an entire category of dispute. The Federal Trade Commission oversees how businesses represent terms to the people buying them, and the practical protection in any individual engagement still comes from the specificity of what both sides signed.

5. What counts as acceptance, and what acceptance releases

Payment schedules tied to dates reward the passage of time. Payment schedules tied to deliverables reward completion, which is what you are actually buying. The scope should pair each milestone with the specific deliverable that triggers it, give you a defined review period, and say what happens if you say nothing. Deemed acceptance after ten business days is reasonable and common; silence meaning acceptance on delivery is not. Equally, state how many correction rounds are included, because unlimited revision is a promise no firm can keep and most will not honor.

Define the close-out package too. Final files in editable formats, not just locked exports, plus passwords, working papers, drawings, data extracts and a short transition memo, all delivered before the final payment clears. Providers with real process hand this over routinely, and the ones that resist tend to generate a recognizable pattern in their reviews: service that was fine until the client tried to leave. One complaint about an offboarding is a grudge. Six, across three years, is a policy.

Read the finished scope against the reviews you already read before you chose, and see whether the specific weaknesses other clients described are addressed anywhere in the document. If the recurring criticism is staffing churn, look for the reassignment clause. If it is scope creep, look at the change mechanism. A good provider will close those gaps in a redline the same week, and the engagement starts with both sides looking at the same picture.