7 Common Bespoke Project Disputes Explained

A joinery package is installed, the client says it is not what they expected, and the contractor replies: “That’s not what we agreed.”

Both may be acting in good faith.

The problem is that the agreement exists across marked-up drawings, a site conversation, several emails and photos sent on WhatsApp. This is how common bespoke project disputes begin — not necessarily with poor work, but with an incomplete record of what was agreed, what changed and who had authority to decide.

Bespoke work carries more judgement than commodity work. A finish can be technically compliant yet feel wrong to a designer. A late site instruction can look minor until it affects manufacture, access, sequencing and programme. Completed work may be ready for review but not yet payment-ready because the required evidence, acceptance conditions or decision have not been recorded.

The objective is not to turn every project into a legal exercise. It is to make important decisions visible, attributable and possible to prove later.

Why bespoke projects create particular friction

High-value fit-out, specialist fabrication and architectural joinery are often developed while delivery is under way. Dimensions are confirmed on site. Samples evolve. Interfaces with other trades become clearer only after ceilings are opened or services are installed.

Flexibility is often necessary.

The commercial risk appears when that flexibility becomes informal.

“Can you just alter that?” may be a reasonable request. But it is not a complete project decision unless the revised requirement, potential effect on cost and programme, and authority to proceed are clear.

The same applies when a contractor identifies an issue. An email raising a concern is not the same as a decision resolving it.

A good project record protects all parties. It allows the client to see what changed and why. It allows the delivering party to show the evidence supporting a request for acceptance. Where there is a challenge, it gives the team a shared factual starting point rather than a contest of recollection.

1. Scope drift disguised as small requests

Scope drift rarely arrives as a single dramatic change.

It accumulates through requests to move a light fitting, alter a shadow gap, add backing, revise ironmongery, remake a sample, return for a further visit or coordinate around another trade’s late work.

Each request can sound too small to formalise. Together, they can consume margin and extend programme. By the time an invoice is questioned, the project team may be trying to reconstruct dozens of decisions from messages and memory.

The practical control is to distinguish clarification from change.

If a request alters an agreed drawing, material, finish, quantity, sequence, access requirement or acceptance expectation, it should be considered against the project’s change-control process.

The record should make clear:

• what changed;
• who requested it;
• which agreed information it affects;
• the likely commercial or programme consequence;
• what supporting evidence exists; and
• who had authority to approve, reject or request further information.

The purpose is not bureaucracy. It is to prevent a small informal request from becoming a large retrospective disagreement.

2. Verbal site instructions with no accountable owner

Site conversations keep projects moving. They are also a poor place to leave a material decision.

“The architect said to do it this way” becomes difficult when the architect recalls suggesting an option rather than authorising additional work.

The issue is not that verbal communication should be forbidden. It is that a material instruction should be confirmed while the detail is still fresh.

A concise record can identify the instruction, who gave it, the relevant location or drawing, the expected consequence and the action being proposed.

The party with the appropriate authority can then accept it, challenge it or request clarification.

That distinction matters for clients too. It reduces the risk that a cost is presented later as an approved variation when the original conversation was exploratory rather than an instruction to proceed.

3. Drawings change after procurement or manufacture starts

A revised drawing issued after materials are ordered may be entirely legitimate.

It may also have consequences that are not visible from the revision cloud alone.

A changed dimension can mean new sheet material, revised CNC programmes, wasted components, altered installation tolerances or additional visits.

The dispute often concerns timing and authority as much as the technical change itself.

Was the contractor working to the approved information available when manufacture began?

Was the later drawing an instruction, design development or correction?

What had already been committed?

Who had authority to determine the next step?

For material revisions, preserve the decision history. Record the drawing version governing the work, when the revision was received, what had already been committed, the evidence available at the time and the resulting decision.

Photographs, purchase orders, production records and marked-up drawings can all help establish the position without relying on a retrospective explanation months later.

4. Acceptance criteria that are subjective or arrive too late

“High quality” is an expectation, not a complete acceptance test.

In premium work, judgement is unavoidable, particularly around grain matching, sheen, shadow lines, alignment and visual consistency. But judgement should not be left entirely until handover.

Where appearance matters, agree the reference point early. That might be an approved sample, control panel, drawing detail, mock-up, room-by-room standard or stated tolerance.

The question is not whether every imperfection is acceptable. It is what the parties agreed would demonstrate that the item met the required standard.

Acceptance should also be connected to a defined milestone.

A contractor needs to know when work can be presented for review. The authorised party needs sufficient evidence to assess it properly.

If the submission is challenged, the challenge should identify the relevant criterion, location or issue rather than leaving an entire package indefinitely unresolved.

Where the agreed project process includes a review or challenge window, that period should also be explicit. A governed submission should reach a recorded outcome rather than disappear into open-ended project limbo.

5. Evidence exists, but is scattered and hard to use

“Sent you the photos on WhatsApp mate” may be true.

It does not necessarily establish what those photographs prove, when they were taken, which room or item they relate to, which requirement they support, or whether an authorised party reviewed them.

Fragmented evidence creates delay even when nobody is behaving badly.

The site manager has images on a mobile phone. The workshop has production photographs. Delivery notes sit in email. The client representative has comments in a messaging thread. Finance has an invoice but no clear record showing the status of the relevant milestone.

Evidence becomes commercially useful when it is connected to the decision it supports.

For example, a completion submission might include labelled installation photographs, delivery notes, test records, the applicable drawing and the acceptance criteria being addressed.

The authorised party can then accept or challenge the specific submission, creating a timestamped decision connected to the evidence that existed at that point.

The difference is important: having evidence somewhere is not the same as having a usable evidence record.

6. Completed work becomes disconnected from payment readiness

A contractor can finish work and still be unable to progress towards payment because the route from completion to acceptance has not been defined.

The client may be waiting for snag information, warranties, photographs or confirmation that an interface is complete. The contractor may believe those requirements were already satisfied.

This is often described as a payment dispute, but the underlying problem may have occurred earlier.

The parties have not clearly connected the commercial milestone to the evidence and acceptance conditions required for it to become payment-ready.

A stronger operating discipline is to define the milestone and its acceptance criteria, submit the required evidence, allow the authorised party to accept or challenge the submission, and create a clear record of the resulting payment-readiness status.

The exact requirements depend on the contract and project.

A manufacturing-stage milestone may require approved shop drawings and material records. Practical completion may require installation evidence, snag status and formal acceptance.

What matters is that the conditions and decision process are understood before the invoice becomes the point at which everyone discovers they interpreted the milestone differently.

Payment readiness is not the same as moving money. It is a record that the agreed governance conditions associated with a payment stage have been addressed.

7. Responsibility is unclear at the interfaces

Specialist packages often fail at the edges.

A joinery item does not fit because the opening changed. A fabricated feature cannot be fixed because the substrate is unsuitable. A finish is damaged after another trade takes possession of the area.

Everyone may have a plausible account, but there is no shared record of inspections, warnings, dependencies, decisions and handovers.

Interface issues require more than photographs taken after the event.

Record the condition observed, the relevant dependency, the evidence available, the action required and any decision about proceeding.

If the team elects to continue despite a recorded risk, that decision should be attributable to the person or organisation with the relevant authority.

This does not determine legal liability.

It preserves the factual and decision history that contract administrators, advisers, insurers and project leaders may later need when assessing what happened.

Common bespoke project disputes need earlier decisions

The best time to deal with a dispute is before it becomes one.

That means recording a material decision when an instruction is given, not reconstructing it when an invoice is challenged.

It means establishing the acceptance test before installation rather than inventing one afterwards.

And it means connecting evidence to the milestone, authority and decision it supports instead of searching for disconnected records months later.

Bespea provides a governance and evidence layer alongside the systems project teams already use.

Its Decision Passport is designed to preserve the history around governed decisions: what changed, what evidence supported the position, who had authority to act, what decision was made and when it occurred.

Proof Packs provide a portable, tamper-evident record that can be reviewed when the relevant project history needs to stand on its own.

Bespea does not replace the contract, project professionals or existing project-management systems. It is not legal advice, escrow or a payment-holding service, and it does not determine legal liability.

Its role is narrower and more practical: preserve a trustworthy record connecting evidence, authority and decisions throughout the project.

Projects will still encounter change, pressure and disagreement.

The important question is whether, when that happens, the team can establish what was agreed, what changed, what evidence existed, who had authority to decide and what decision followed — while there is still time to protect the relationship, the work and the commercial outcome.