Owner scope change vs design gap, told apart in practice

Owner scope change vs design gap is the most consequential distinction in change order administration. One is the owner buying something new. The other is somebody delivering what was already bought, and they arrive looking identical.

Two things that look the same on a change order form

A change order arrives. It describes work, it carries a price, and it says the work is additional.

Underneath that identical presentation sit two quite different events.

An owner scope change is the owner asking for something that was not in the documents. A different finish, an additional room, a relocated wall, a higher specification. The owner wanted something new and the owner pays for it, which is correct and uncontroversial.

A design gap is work that was always required for the building to function but was not properly shown in the documents the price was built from. Nobody asked for anything new. The building always needed it and the documents did not say so.

Who funds a design gap is a different question, and one that depends on the contract, the design agreement and the standard of care, which is a matter for your counsel rather than for a cost reviewer.

What is consistent is that an owner who does not make the distinction funds both from the same pocket without ever knowing which is which.

The question that settles owner scope change vs design gap

One question, asked about the documents rather than about the work.

Would the building have functioned as described in the original documents without this work?

If yes, and the owner now wants something different, it is a scope change. The building was complete and the owner is buying more.

If no, and the work was always necessary for the building described to operate, it is a design gap. The documents were incomplete and the work is not additional in any meaningful sense.

The question is useful because it is answerable from the drawings and the specification, without anybody agreeing on intent, and because it does not depend on who is asking.

It also produces a third answer on some items, which is that the work was shown but in a way that could reasonably be read two ways. That is an ambiguity rather than a gap, and it is resolved by the order of precedence clause and by whatever the contractor recorded as its assumption, which is covered in drawings against the specification.

Worked distinctions

Four examples, because the principle is easier to see than to state.

A relocated conference room wall. The owner asks for it in month nine. The building functioned without the move. Scope change.

A fire damper missing from the mechanical drawings at a rated wall penetration. The building cannot pass inspection without it. It was always required. Design gap.

An upgraded lobby stone. The specified stone was available and compliant. Scope change.

Structural support for rooftop equipment shown on the mechanical drawings and absent from the structural ones. The equipment cannot be installed without it and it was always required. Design gap.

The second and fourth are the ones that get quietly paid as scope changes on a great many projects, because they arrive as change orders, they are priced as change orders, and nobody asks the question.

That is not anybody behaving badly. A contractor submitting a change order for a missing fire damper is doing exactly what the contract asks. The classification is the owner job and nobody else has a reason to do it.

There is a fifth case worth naming because it causes the most disagreement: design development. The documents showed a system generically and the final design is more extensive than the generic version implied. Whether that is a gap or the ordinary progression of design depends on how generic the original really was, and reasonable people differ.

The practical answer is to classify it as its own category rather than forcing it into one of the other four. A running total of design development items is informative on its own, and it avoids a monthly argument about which box it belongs in.

A worked example

A project at month fifteen with $2.4 million of executed change orders, reported as one figure.

Classified by the question above: owner scope changes $1.3 million across twenty two items. Design gaps $860,000 across thirty one items. Unforeseen conditions $190,000 on two items. Ambiguities $50,000 on three.

The $1.3 million is uncontroversial and it is the owner money properly spent.

The $860,000 is a different conversation, and it is one the owner can only have because somebody classified the log. What happens next depends on the design agreement and on advice from counsel, and it may well end with the owner funding most of it anyway.

What changes regardless is the forward view. Thirty one design gaps in fifteen months predicts more of them, and that prediction belongs in the remaining exposure. Reported as one $2.4 million figure it predicts nothing.

Why the classification has to happen early

Three reasons, and the third is the one that matters most.

Evidence is fresher. The drawings at the time, the request for information, the response and the sequence are all available in month three and reconstructed with difficulty in month fifteen.

Notice periods are live. Most contracts and most design agreements carry time limits, and a classification made late may find that the useful period has passed.

And the pattern is actionable while there is time to act. A project generating design gaps at a steady rate in the first six months is telling you something about the documents, and the response, which is usually a focused review of the areas producing them, is worth doing in month six and pointless in month eighteen.

The mechanism itself is simple. Each change order gets a cause field, filled in when it is raised, using the question above. It takes seconds per item and it has to be agreed at the start, because retrofitting it means reading a year of paperwork.

That is the same discipline as reporting change orders by cause rather than by total, described in the cause written on a change order.

What to do before you sign

1. Require a cause field on every change order, with an agreed set of categories.
2. Agree the categories in writing: owner scope change, design gap, unforeseen condition, ambiguity.
3. Agree that the question above is the test, so classification is not a negotiation each time.
4. Require the change order log reported monthly by cause, with a running total for each.
5. Read the design agreement alongside the construction contract, not separately.
6. Establish the notice periods that apply to each category, and who watches them.
7. Review the pattern at month six and act on what the design gap rate is telling you.

Item three is what keeps the process from becoming a monthly argument. A test agreed in advance is applied; a test argued each time is abandoned within a quarter.

Item seven is where the money is. The classification is not mainly about recovering the past, which is difficult and often not worth the relationship. It is about seeing a pattern early enough to change what the rest of the project produces.

The scope options for this reading sit in the review packages.

What we do

We set the classification up before signature, so the cause field exists from the first change order, and we classify the log where a project is already running. The output is a split by cause with a running total and a forward view of what the pattern implies. We describe what the documents show and leave questions of entitlement and standard of care to your counsel. The work sits in the cost and change exposure assessment.

Questions people ask