Whose Sign-Off Ends the Job? The Scope Clause That Settles It Before Work Starts

The engagement letter ran to three pages and read cleanly. A five-person consultancy would document and redesign the prior authorization workflow at a family-owned specialty pharmacy group with four locations, for a fixed fee, over ten weeks, with a final written procedure and staff training as deliverables. Both sides signed in March. In September the consultancy was still working, unpaid on its final invoice, because the pharmacy group's clinical director had not approved the procedure, and nothing in the letter said she was the person whose approval mattered, or what approval would consist of when it came.

The sentence that was never written

The scope described what the consultancy would produce and said nothing about what would happen when it was produced. There was no named approver, no review window, no statement of what a reviewer could reject and on what grounds, and no default that treated silence as acceptance after a fixed number of business days. So the draft procedure went to the operations manager who had hired the firm, who forwarded it to the clinical director, who forwarded it to a pharmacist-in-charge at each site, and four sets of comments came back contradicting each other. Nobody had the authority to resolve the contradiction, because nobody had been given it.

That is the ordinary way these engagements fail. The buyer believes the scope is a description of the work, and it is, but the part that governs the money is the part that defines completion. A deliverable with no acceptance test is not a deliverable; it is a draft in perpetuity, revised at the pace of whichever reviewer is slowest and least accountable. The consultancy had priced ten weeks of effort and delivered close to twenty-six, and the pharmacy group, which had done nothing anyone would call unreasonable, had quietly become the party setting the schedule.

Where the form came from, and what got dropped on the way

The modern scope of work is borrowed equipment. It grew up in construction and in federal procurement, where a statement of work had to be specific enough that a contracting officer could tell, from the document alone, whether the government had received what it bought. That discipline produced a standard shape: deliverables, acceptance criteria, assumptions the price depends on, exclusions, and a written route for changing any of it mid-stream. Professional services firms adopted the shape in the 1990s and 2000s as consulting, design, and technology work moved onto fixed fees rather than open hourly billing.

What traveled well was the deliverables list, because it is the flattering part, the part that reads like a promise. What often got dropped was acceptance, exclusions, and change control, because those read like distrust at the moment of signing and neither side wants to introduce distrust into a document they are hoping will start a relationship. The result is a scope that is precise about output and silent about judgment. Every dispute of the kind the pharmacy group had lives in that silence, and it is a solvable silence, because the missing clauses are short.

Naming the approver, which is not the same as naming the client

The correction the two parties eventually made took one paragraph. It named the clinical director as the sole approver, gave her ten business days to accept the deliverable or return a single consolidated list of specific defects measured against the criteria already written into the scope, and stated that no response inside that window counted as acceptance. It also said that comments from anyone other than the approver would be gathered by the pharmacy group, not by the consultancy, and delivered as part of that one list. Consolidation is the whole mechanism. It moves the work of reconciling internal disagreement back to the organization that owns the disagreement.

Notice who holds the choice here. The buyer picks the approver, and in doing so picks whether the engagement will be governed by one person with authority or by a committee with opinions. Vendors rarely push for that clause, because asking a prospective client to identify a decision-maker sounds like an accusation that the client is disorganized. So the buyer usually has to raise it, and the buyer is the party who benefits most, since a named approver with a clock is the only reliable way to keep an internal review from consuming a schedule the buyer is paying for.

Client obligations are a price term

The second amendment the pharmacy group accepted was less obvious and mattered as much. The original scope had assumed, without saying so, that the consultancy would get four hours of pharmacist time per site during weeks two and three, plus read access to the practice management system. Neither materialized on time, and the consultancy absorbed the delay without a word until it could not. The rewritten version listed those inputs, attached dates, and stated that a missed input moved the delivery date by the same number of days and that anything past fifteen days would be re-priced. Nothing punitive. Just an arithmetic that had previously been unwritten.

Scopes should also say plainly how the work will be performed and by whom, and where the buyer's direction stops. That line has consequences beyond the project: the Internal Revenue Service is responsible for how firms and their outside workers are classified, and behavioral control, meaning who directs the method and hours rather than the result, is one of the things it looks at. A scope that specifies the outcome, the acceptance test, and the reporting rhythm, while leaving the method to the firm, is both cleaner to enforce and cleaner to defend.

What the second engagement looked like

The pharmacy group hired the same consultancy the following year for a smaller piece of work, and the scope opened differently. First page: the deliverable in one sentence, the named approver, the ten-day window, the consolidated-comments rule, the three client inputs with dates, and a short list of things expressly outside the fee, including software configuration and any site added after signature. Change requests went in writing with a price and a date before work resumed. That engagement finished within a week of its estimated date. The work itself was no better. The document around it simply told everyone, in advance, who got to say when it was done.

If you are about to sign, read the scope backward, starting from the last thing it promises, and ask what sentence would let a stranger reading it in six months determine that you got it. If the answer is a person's name and a date, the money is protected. If the answer is a feeling, the schedule belongs to whoever in your own building answers email slowest.