Scope Definition Risk

The situation

Three prices, three different buildings

Design teams work from intent. Contractors price from documents. Those are not the same thing, and the difference only becomes visible when money is attached to it.

On a mixed use scheme, tender returns came back with a spread wide enough that the client's first assumption was that one contractor had misunderstood the job. In fact all three had read the documents correctly. Each had simply resolved the ambiguities differently, and each had resolved them in its own commercial favour, which is what any competent contractor does.

The client was not comparing three prices for one building. They were comparing three interpretations, and the cheapest interpretation was the one that had excluded the most.

What we found

Scope was not missing. It was described twice

Reconciliation of the model, the drawings, the specification and the Employer's Requirements produced a straightforward picture. Scope was described more than once, in more than one place, in terms that did not match.

01

Facade interfaces appeared in both the structural and the envelope packages, so one contractor priced them twice and another priced them not at all.

02

The specification referred to performance standards the model could not demonstrate, which left the contractor to select an approach and price it.

03

Several BIM objects carried the correct geometry but no specification data. Quantities extracted from them looked authoritative and meant very little.

04

Employer's Requirements described outcomes. Drawings described solutions. Where the two conflicted, precedence was not stated anywhere in the tender documentation.

What changed

Close the ambiguities, not extend the deadline

The scheme did not become cheaper. It became legible, and the client stopped paying a premium for other people's uncertainty.

1

Reissue with the conflicts resolved

Tender documents went out again with the ambiguities closed rather than the deadline extended, which is the cheaper of the two corrections by a wide margin.

2

Name an owner for every interface

Each package boundary received a named owner, so an item could no longer appear in two packages or in neither.

3

Write a precedence order into the documents

A contractor reading a conflict between the Employer's Requirements and a drawing now knew which document governed, and priced accordingly.

4

Make qualifications visible again

Returns came back comparable. Where a contractor still qualified an item, the qualification stood out instead of blending into the general noise of a tender.

Why this happens

Geometry is not scope

A model is a design tool that is repeatedly asked to behave as a commercial one. An object without data is not a quantity. Design teams rarely have any reason to notice the distinction, because it does not affect their deliverable.

Quantities and take-off exists precisely at that boundary, reconciling what the model contains against what the documents require. Subsequently, tendering and procurement determines how that resolved scope is packaged and put to market. Neither works well without the other.

Questions

Asked about scope and its edges

How do I tell whether my scope is actually defined?

Read the document looking for the boundaries rather than the content. A defined scope tells you where one package stops and the next begins, who carries the work between them, and what happens to the interface if either side changes. Most specifications describe what is included and say nothing about the edges, which is where money leaks. If you cannot answer the question who is pricing the connection between these two elements from the document alone, the scope is not defined, however long the specification runs.

Is a scope gap the same as a variation?

Not usually, and the distinction matters commercially. A variation is a change to work that was described; a scope gap is work that was never described by anyone. When a gap surfaces during construction, the contractor has a reasonable argument that it was never priced, and you are negotiating from a position where the work is already needed. Treating the two as the same conflates a change you chose with an omission you did not know about. Only one of those can be prevented at tender.

Whose job is it to spot scope gaps before tender?

In practice nobody owns it unless somebody is appointed to. Designers describe their own packages, the contractor prices what is drawn, and the project manager coordinates programme rather than commercial boundaries. Someone has to read the packages against one another looking specifically for the space between them, which is what a tender and procurement review does before documents are issued. That reading is quick compared with the cost of resolving the same gap once the work is on site.

Can scope be tightened after tenders are returned?

It can be clarified, though clarification after tender is negotiation rather than competition. Once prices are in, any addition to scope is priced by a contractor who knows the alternative is retendering, so the rate you get reflects that position. Where a gap is found late, the honest approach is to price it openly, record it as an addition to the budget and stop describing it as a saving. Pretending it was always included makes the final account harder to defend.

Does design and build transfer scope risk to the contractor?

It transfers responsibility for design development, not responsibility for a scope that was never described. Employer's requirements carry the same exposure as any other document: whatever they leave out, the contractor's proposals will define in the contractor's favour, and the contract will support that reading. Design and build shifts who resolves the gap; it does not remove the cost of the gap, and it does not remove your need to know where the gaps are before you sign.

Related scenarios