AEC definitions

What Is Scope Creep?

Last reviewed: September 2026

Scope creep is the gradual addition of work, or of a higher standard, without a corresponding change to the contract. It shows up as informal requests, extra meetings, and 'while you're here' tasks that never become a change order. The cost lands on whoever was too polite to price it.

REQUEST FOR INFORMATIONRFI-016PROJECTRIVERSIDE HOTELTOARCHITECT OF RECORDDRAWING REFA-201, DETAIL 4/A-501DATE10/14/2026QUESTIONSKETCH SK-1RESPONSEANSWEREDSEE REVISED DETAIL 4/A-50110/21/2026COST IMPACT: NONE | SCHEDULE IMPACT: NONE1234

What you're looking at

Request for Information, annotated

An RFI with its log number, the drawing it asks about, a sketch of the question, and the design team response.

  1. 1RFI number and log reference
  2. 2Drawing and detail in question
  3. 3Question with a sketch attached
  4. 4Response from the design team
Is
Added work or standard without a contract adjustment
Is not
A documented change order or an allowance reconciliation
Common sources
Informal field direction, undefined scope, gold-plating
Lands on
The party that performs it without pricing it
Prevented by
A written scope and a used change process
Test
Did the contract documents already require this?

Definition

Scope creep

Some growth is legitimate change. Scope creep is the part that skips the instrument. A drawing revision with an ASI or a change order is not creep. A pattern of field instructions, unmarked sketches, and raised expectations is. The defense is dull: a scope of work, a rule that extra work needs written authorization, and a log. Calling every owner question creep is as wrong as absorbing real additions. The test is whether the contract documents already required the work.

In depth

Separate creep from the contract

If the specifications already required the mockup, performing it is not creep. If they did not, adding it in a meeting is. Read the documents before you label the request.

Small items accumulate. A log of 'minor' favors is the creep, even when no single item felt worth a form.

Where it starts

Thin scope, a client who directs the field, and a team that treats the change process as hostility. Designers who answer 'sure' on site without writing an ASI create work the contractor cannot price and the owner did not approve.

Gold plating is the team's own version: delivering a higher standard than the documents to impress, then discovering it was free.

The change path is the product

Field direction that affects cost or time should stop at an RFI, an ASI, a proposal request, or a change directive. Pick the form the contract names. Do the work after it exists, unless the contract allows proceeding.

A proposal request is not an attack. It is how the owner decides with a number in view.

Contemporaneous notes beat memory

Daily reports, emails, and marked drawings dated when the request was made are the evidence. A claim assembled at the end from memory will be called creep by the other side and a claim by you, with little proof either way.

Time impact belongs in the same record if the extra work affected the critical path.

Politeness is not a payment method

You can say yes and still price it. The sentence is: we can do that, here is the change form.

Refusing to write it down is what makes the relationship expensive.

Examples

Scope creep on a real project

  • 01

    The owner asks the superintendent to add three outlets. The work waits for a proposal request. That is a change, not creep.

  • 02

    Weekly site walks add finishes the documents do not show, and nobody logs them. The cost appears at the end as an argument.

  • 03

    The design team details a custom bench the outline never had, and the contractor builds it without a price. Both sides created creep.

FAQ

Frequently asked questions

It is work or a higher standard that enters the job without a change to the price or time. Documented change orders are not scope creep.

Write the scope, require authorization before extra work, and use proposal requests so the owner sees the cost. Log small items instead of treating them as favors.

No. Work the contract already required is performance. Work the owner adds through a signed change is a change. Creep is the addition that skips that path.

Often the party that performed it without a change instrument. That is why the cost should be priced before the work, not discovered in the final account.
What Is Scope Creep? | Nomic