Hiring a Big Firm? Five Lines in the Scope of Work That Decide What Happens Later

The scope of work is signed by people who will not do the work. That is the structural fact behind most of what goes wrong later, and it gets sharper the larger the provider is, because a big firm has a sales organization, a delivery organization, a billing organization and a support organization, and the document is the only thing that travels intact between all four. Everything else, the tone of the pitch meeting, the verbal reassurance about turnaround, the sense that someone understood your situation, stops at the first handover. What is written survives. What was said does not.

1. Who actually performs the work, by role rather than by name

A proposal from a large provider usually features the people who wrote it. The engagement partner, the senior consultant, the principal architect: these are real people with real credentials, and in many cases they will appear at kickoff and then again at the closeout presentation. In between, the hours are billed by staff you have not met. That is not a scandal, it is how leverage works and it is part of why the rate is what it is. The check is whether the document names the roles, the seniority mix and the substitution rules. If a named individual leaves, does the scope require notice, and does it require an equivalent replacement or merely a warm body at the same rate?

2. What counts as finished, and who is allowed to say so

Acceptance language is the quietest expensive clause in the document. When a scope says deliverables will be provided and does not say what makes them acceptable, the practical consequence is that the provider's invoicing schedule advances on delivery while your internal sign-off has no defined test to run. You end up arguing about quality after you have already paid the milestone, which is a much weaker position than arguing before. A workable acceptance clause states the artifact, the review window in business days, who at your organization signs, and what happens on rejection. It should also say that silence past the review window is deemed acceptance, because large providers will insist on that anyway and it is better to know the clock exists.

3. The dependencies you owe them, with dates attached

Most scopes include a section on client responsibilities, and most clients skim it. That section is where your own delays get converted into their revenue. Access to systems, availability of subject matter experts, decisions on open questions, sample data, a badge for the building: each item is a place where a large provider can stop, log standby time, and invoice for a team that is sitting still. Read that section as a schedule of your obligations, then ask who inside your organization actually owns each one and whether that person knows. The second-order effect of an unowned dependency is not a missed date. It is a rescheduling fee, a re-mobilization charge, and a delivery team reassigned to another account for three weeks.

4. Exclusions, and the price of everything on the other side of them

Exclusions are useful. A scope that lists what is not included has been read carefully by somebody, and it tells you where the boundary sits before you find it by accident. The follow-up question is the one people skip: what does it cost to cross that boundary mid-engagement? A change order priced at a published rate card, with a stated minimum increment and a turnaround commitment for approval, is a manageable event. A change order priced at negotiation, raised while your project is half built and your alternatives have narrowed, is not. The Federal Trade Commission oversees fair dealing in commercial contracting practices, but no regulator will retroactively set a price you failed to fix while you still had leverage.

5. What you are holding at the end, and who supports it

The final handover is the one that determines your cost of ownership for years, and it is usually described in a single line about knowledge transfer. Press on it. The specifics that matter are documentation in an editable format, credentials and administrative access transferred out of the provider's accounts and into yours, source files rather than exports, and a named remediation window during which defects are fixed at no charge. Large providers often route post-delivery questions to a support desk staffed by people with no memory of your engagement, so ask whether the delivery team remains reachable, for how long, and at what rate. A scope that answers this leaves you self-sufficient on the day the invoice clears.

None of these five checks require a lawyer, and all of them are easier to raise before signature than after, when the provider's incentive to accommodate you is at its highest and the cost of a revised paragraph is an afternoon. Ask for the changes in writing, ask the delivery lead rather than the salesperson whether the revised language is workable, and keep the marked-up version. The document you negotiate is the one that will be read, months from now, by strangers deciding what they owe you.