Week six.
The contractor is claiming the second-floor cabling was included in the original price. The client is certain it was a separate item. The project manager is sitting in a meeting that has run for forty minutes and produced no resolution.
Nobody wrote it down.
The scope document that would have ended this conversation took forty-five minutes to write. The dispute that replaced it consumed six weeks of management time, a revised forecast, and a relationship that has not fully recovered.
This pattern appears on almost every project that drifts. Not at month twelve. At week six. When “was that included?” becomes the project’s most expensive recurring meeting.
The assumption that makes week six inevitable
Most project teams believe the scope is clear after kickoff. The meeting happened. Slides were presented. Everyone left aligned.
“They were not aligned. They were polite.”
Alignment in a meeting is not the same as a shared understanding of what is and is not included. One is a social signal. The other is a written document.
“We all know what’s included” is the sentence most often spoken six weeks before a dispute about what was included.
The written scope document is not bureaucracy. It is the single artefact that makes the kickoff alignment real.
What happens when the scope is written — and what happens when it isn’t
On a cross-border fit-out programme across four African countries, the client’s brief was clear in principle: refurbish the operational facilities to a defined standard. No written scope. No acceptance criteria.
Week four: the contractor completed the electrical installation. The client said it was not to standard. The contractor pointed to the brief. The brief said “defined standard.” Neither side had defined it. Three weeks of back-and-forth. A partial redo. A revised cost.
On the next programme in the same region — same client, different site — a scope document was written before mobilisation. Four pages. Forty-five minutes to produce.
Week four: contractor completed the installation. Client reviewed it against the acceptance criteria. Signed off same day.
“Same client. Same contractor. Same type of work. Different outcome. Nothing changed in the contractor’s capability. Nothing changed in the client’s expectations. Only the document changed.”
A multi-country airport infrastructure programme across four African countries was delivered 10% below budget. The scope was locked before mobilisation on every site. “Was that included?” was asked twice across the entire programme. Both times, the answer was in the document.
The scope document — four components, forty-five minutes
A scope document does not need to be long. It needs to be complete.
A specific list of what is being delivered. Not “the refurbishment” — the specific areas, systems, finishes, and standards. Measured where possible. Referenced to drawings where they exist.
“Electrical installation to IEC 60364, all areas shown on drawing REV-3. Includes distribution board replacement. Excludes external cabling.”
Explicitly named. The items most likely to be disputed later are almost always the ones that were close enough to the scope boundary to be genuinely ambiguous. Name them now.
“Structural works. External infrastructure. IT cabling. Furniture and fixtures. Anything not shown on drawing REV-3.”
The conditions you are taking as true that, if wrong, would change the scope or price. If any assumption proves false, the scope conversation reopens — but on a known basis.
“Price assumes uninterrupted site access Monday–Friday 07:00–18:00. Drawings assumed accurate; any discrepancy to be raised within 48 hours.”
How you will know the work is done. Not “to the client’s satisfaction” — a specific, observable standard. Written in advance. Agreed by both sides before work starts.
“Electrical installation: all circuits tested and certified to IEC 60364. Certificate provided by licensed contractor. Client sign-off within five working days.”
One meeting. Forty-five minutes. One document. Signed before mobilisation.
The next time “was that included?” comes up — you open the document. The debate ends in sixty seconds.
The reasons teams skip this — and why each one is wrong
“We do not have time to write a scope before we start.”
You have forty-five minutes. The scope conversation will happen regardless. The question is whether it happens before work starts — forty-five minutes — or after — six weeks and a cost revision.
“The client will not agree a detailed scope before we start.”
A client who will not agree what is included before you start is a client who will dispute what is included after. Frame it as: “Can we spend forty-five minutes confirming we both have the same picture?” Almost no client refuses.
“The scope will change anyway.”
It will. That is precisely why you need a baseline. Change is only manageable relative to something fixed. Without a written scope, every change is a dispute. With one, every change is a measurable deviation.
The cost that never appears in the budget
The direct cost of a scope dispute is visible: rework, revised forecasts, delay claims. The indirect cost is not: the management hours spent adjudicating, the relationship damage, the credibility loss when the steering committee asks why the forecast changed again.
Across thirty countries and more than €2B of capital projects, programmes that started with written scope baselines consistently generated fewer change-order disputes, fewer forecast revisions, and fewer management escalations.
“The scope document is the cheapest insurance available on any project. It costs forty-five minutes. It pays back every time.”