Conflicting Advice on a Scope of Work? Write It for the Four People Who Read It Weekly

Ask three competent people what a scope of work should say and you will get three documents that barely resemble each other. The attorney wants defined obligations, limits on liability, and a clean path for termination. The project manager wants sequence, access windows, and a named decision-maker. The trade association template wants line items priced by unit. None of them is wrong, and that is the problem: the advice conflicts because each adviser is protecting a different failure. The way out is not to merge all three. It is to decide which readers will open this document during an ordinary week, and write for them.

Why the three versions disagree, and what that tells you

Legal drafting is written for the week the relationship fails. Operational drafting is written for the fifty weeks it works. A priced line-item schedule is written for the moment money moves. Each is optimized for a different reader in a different mood, which is why splicing them produces a document that is long, internally contradictory, and quietly ignored on site. Notice which failure each adviser has personally cleaned up, because that is what they are drafting against. Then ask a narrower question that has an actual answer: over the next several months, who will consult this page, and what will they be trying to settle when they do?

The four people whose work sits next to your decision

In most professional services engagements the same four readers appear. The coordinator or scheduler, who is booking crews, deliveries and access, and who needs to know what has to be finished before the next trade can start. The subcontractor or specialist, who bid off your document and will do exactly what it describes and nothing adjacent to it. The person who processes invoices, whether that is a bookkeeper, a controller or you at a kitchen table, matching a bill against something you agreed to. And the outside reviewer: an inspector, a lender, an insurer, or a licensing board. Your document either answers them or generates a phone call.

None of these people reads the whole thing. They read the paragraph that touches the decision in front of them, on a Tuesday, with someone waiting. That is the practical test of a scope of work: can a reader find the one line they need in under a minute, and is that line unambiguous enough that they act on it without checking with you? A document that requires interpretation gets interpreted, usually by whoever is standing closest to the problem. Write so that the interpretation you would have given is already on the page.

What to write down, and in what order

Start with boundaries rather than tasks. State what is included, then state what is excluded in the same specificity, because exclusions are where week-to-week friction actually lives. Permits, disposal, patching, cleanup, temporary protection, storage, utility disconnection, and the removal of whatever is discovered behind the wall all belong in one place, assigned to somebody by name or role. Then describe sequence and dependency: what must be complete before the next stage begins, and what happens to the schedule if it is not. Then name the decision points, the moments where someone will have to choose a finish, approve a substitution, or authorize additional work.

Attach an approval path to each decision point. Who can say yes, in what form, and within how long. This single provision prevents more disputes than any liability clause, because most conflict on a job is not about bad faith but about a choice made by whoever happened to be present. Say plainly that verbal approvals do not change the price, then give a change mechanism that is easy enough that people use it. A one-page change order that gets signed is worth more than an elegant clause that gets bypassed. The Federal Trade Commission oversees how services are represented to consumers, and the same discipline applies internally: what the document promises and what the crew does should be the same thing.

Separating what you can still undo from what you cannot

Distinguish reversible decisions from irreversible ones and mark them on the page. Paint color, fixture selection, and most finishes remain open until late. Structural changes, penetrations through a roof or slab, tree removal, and anything that alters a system's capacity are effectively permanent, and they are usually scheduled early, when the least information exists. Put the irreversible items behind a stated hold: they do not proceed until a named person confirms in writing. This costs a day or two. It removes the failure mode where you learn about a permanent choice from a photograph, after the trade that made it has moved to another site.

The same logic governs the commercial terms. Deposits, mobilization fees, and custom-order payments are hard to claw back once material is cut, while retainage and final payment stay available as leverage until the work is accepted. Write down what acceptance means, in observable terms, and who performs it. Then write down the documents you expect at the end: warranties, lien releases, closeout paperwork, as-built markups, manuals, and the final permit sign-off. In five years, when a component fails or you sell the property, those documents are the whole of your position, and they are only ever assembled if the scope asked for them.

Testing it against an ordinary week

Before anyone starts, run the document forward through a routine week rather than a catastrophe. A truck arrives a day early. A sub finds an unexpected condition at ten in the morning. An invoice appears for something you thought was included. A crew member asks whether they can use the driveway. If each of those has a locatable answer, the scope works. If two of them route to you personally, decide whether you want to be that available for the duration, and if not, delegate it on the page with a name attached.

Conflicting advice usually means you have been handed several good answers to questions you had not yet separated. Separate them, decide which reader you are writing for in each section, and the document gets shorter rather than longer.