How to Document Scope Changes on Fit-Out Projects

A client points at a finished joinery detail and says, “That’s not what we agreed.” The studio replies, “You asked for it on site.” Someone finds a WhatsApp thread, a marked-up drawing with no date, and a voice note nobody can play in a meeting. The work may be excellent, but nobody can prove anything.

That is why knowing how to document scope changes matters on high-value fit-out, bespoke manufacturing and joinery projects. A scope change is not just a design decision. It can alter cost, programme, materials, interfaces, responsibility for delay and, ultimately, whether an invoice is ready to be paid.

The aim is not to make every small decision painful. It is to make material changes visible, priced, accepted and traceable before they become a dispute.

Why fit-out scope changes become disputes

Projects rarely go wrong because a variation was requested. They go wrong because the request becomes work before its consequences are agreed.

A client may ask for a darker stain, a revised door profile or extra lighting after fabrication has started. A project lead may ask a contractor to move an opening to suit another trade. A site manager may say, “Just get it done and we’ll sort it later.” Each request may sound reasonable. But once the revised work is underway, the commercial position becomes harder to recover.

Photos sent on WhatsApp, emails with several different drawing versions, and verbal instructions in site meetings all create fragments of a story. They do not create a shared record. They are difficult to search, easy to misunderstand and open to argument over what was approved, by whom, and when.

A proper scope-change record protects both parties. The provider can show why additional time or cost was incurred. The client can see precisely what is changing before authorising more spend. Neither side has to rely on memory after the work is installed.

Start with a clear scope baseline

The strongest process starts with a simple rule: no material change moves into procurement, fabrication or installation until the requested change has been recorded and reviewed. There will be genuine emergencies, particularly on live sites, but these should be treated as exceptions with a clear retrospective record, not as normal practice.

You cannot document a change properly if the original scope is vague. Before the project starts, establish the baseline against which change will be measured. This should include the relevant drawings and specifications, inclusions and exclusions, milestone dates, price or payment schedule, and acceptance criteria.

Acceptance criteria deserve particular attention. “High-quality finish” is not an acceptance criterion. It is an invitation to a subjective argument. A better criterion identifies what will be checked: veneer species and finish sample, handle model and position, alignment tolerance, quantity, dimensions, delivery location or installation standard.

Where a scope document refers to drawings, identify the revision number. Where it refers to a finish sample, photograph and label it. If the client has selected an option, record the selection rather than leaving it buried in an email chain. The baseline should be a point of reference both parties can recognise.

Create the variation record when the request arrives

A change record should begin when the request is made, even if the answer is “not yet priced” or “not feasible as requested”. That early record prevents the most common later disagreement: whether the change was ever requested at all.

Give each proposed change a unique reference and record the date, requesting party, affected area or item, and a plain-English description. Attach the source material, such as a marked-up drawing, site photograph, design instruction or meeting note.

Avoid descriptions such as “amend wardrobe” or “revise reception desk”. They are too loose to be useful. State what is changing. For example: “Replace the approved lacquered MDF front panels to the Level 2 reception desk with rift-cut oak veneer, including revised edge detailing and sample approval.”

The record should also state what is not changing. If only the front panels are changing, say that the carcass dimensions and drawer hardware remain as previously agreed. Clear boundaries stop a small variation quietly becoming a wider redesign.

Show the cost and programme effect before work proceeds

A request is not an approved variation merely because it has been logged. Before approval, explain its implications in terms the decision-maker can act on.

State the change in price, whether that figure is fixed or provisional, and what assumptions sit behind it. Set out the programme effect, including lead-time implications, resequencing, access requirements and any impact on dependent trades. If there is no impact, record that too.

For complex work, separate the immediate instruction from items still requiring confirmation. A client may approve a revised material direction but need to select a final finish from samples. In that case, the record should make clear what has been authorised, what remains open, and the point at which delay will affect the programme.

Do not hide uncertainty to make a variation easier to approve. If a site condition may require additional work after opening up, describe the allowance and the approval route for any excess. Commercial clarity is fairer than a low initial figure followed by an avoidable surprise.

Record who decided, and any conditions

The record needs a decision from someone with authority to make it. “The team were happy with it” is not enough when an additional invoice lands later.

Capture whether the change is approved, rejected, approved subject to conditions, or pending further information. Record the decision-maker’s name, role, date and any stated limitations. If approval is conditional on a revised sample, payment, landlord consent or architect sign-off, make the condition visible.

A fixed challenge window can help where the project parties have agreed one in advance. It gives the client a fair opportunity to raise a specific objection while preventing completed, evidenced work from being held up indefinitely by silence. The time period must suit the contract and the nature of the decision. A same-day response may be realistic for a minor site instruction, but not for a significant redesign with budget implications.

What to include in a scope-change record

For material scope changes, a consistent record should include:

• a unique reference, date, project area and requesting party;
• the original approved scope and the precise proposed amendment;
• supporting drawings, photos, samples, meeting notes or site evidence;
• the price effect, tax treatment, assumptions and payment treatment;
• the effect on programme, procurement, fabrication, access or other trades;
• the acceptance criteria for the revised work; and
• the named approval, conditions and date the instruction becomes live.

This is not paperwork for paperwork’s sake. It is the minimum information needed to decide whether work should proceed and whether the project record supports payment readiness under the agreed project process.

Keep evidence connected to the approved change

The change record should not end at approval. It should follow the work through the relevant milestone.

If the change involves a new material, retain the approved sample, supplier confirmation and delivery documentation. If it affects fabrication, capture workshop photographs, revised production drawings and quality checks. If it affects installation, capture dated site photographs, snag records and the final acceptance evidence.

Evidence should be tied to the change reference and to the relevant milestone, rather than left in a general project photo folder. Otherwise, people are forced to reconstruct the story later: which photos relate to the original scope, which show the variation, and whether they were taken before or after the client’s instruction.

This also improves the client’s position. They should not be asked to approve additional payment simply because a contractor says the revised work is complete. They should be able to review evidence against the stated acceptance criteria. That is payment readiness: a clear chain from agreed scope, to approved change, to proof of completed work.

Keep a shared record that preserves the history

A shared record works best when it does not allow a decision to be quietly overwritten. If a price changes, preserve the earlier proposal and add the revised one with the reason for the revision. If an approval is withdrawn, record when and why. If an instruction is superseded by a later drawing, connect the records.

This does not mean every internal discussion belongs in the project file. Teams still need room to explore options. The formal record should capture the point at which an option becomes a request, a commercial proposal or a decision that affects delivery.

Bespea structures this process around milestones, acceptance criteria, evidence submissions and recorded decisions, creating a traceable project record rather than another stream of untracked messages. Bespea does not hold project funds. The parties continue to use their agreed payment arrangements, while Bespea provides a traceable record of scope, decisions, evidence and acceptance.

The six-month reconstruction test

If the project paused six months from now, could an independent person understand what changed, why it changed, what it cost, who approved it and whether the revised work met the agreed standard?

If the answer is yes, you have given the project a far better chance of staying commercially fair when pressure builds.