Fixed Challenge Windows in Construction: How to Make Acceptance Clear

A bespoke reception desk is installed, photographed and presented for sign-off. The client says they need time to review it. Two weeks later, the invoice is questioned because a detail that was visible on day one is now said to be unacceptable.

The problem is not necessarily that either side has acted unreasonably. The project did not establish a clear route from delivery to review, challenge, acceptance and payment readiness.

A fixed challenge window is a defined period during which an authorised party can review submitted work or evidence against agreed criteria and raise a documented challenge. It is not designed to force rushed approval. It makes clear what is being reviewed, against which criteria, by whom, using what evidence and by when.

For high-value joinery, specialist fit-out and custom fabrication, acceptance is rarely as simple as confirming that something arrived on site. A client may need to assess finish, alignment, operation, materials, interface details and whether approved changes have been incorporated. The contractor also needs to know when completed work has been properly presented for review, rather than remaining indefinitely in a state of “We are still looking at it.”

Why informal challenges create commercial risk

Most project teams do not deliberately leave decisions unclear. Instructions and objections often arrive through whichever channel is open: a phone call from site, a WhatsApp message, an annotated screenshot, an email or a comment during a walk-through. Each may be useful operationally, but none necessarily establishes the complete decision record.

“Sent you the photos on WhatsApp mate” does not establish which photographs were reviewed, what they were intended to prove, which acceptance criteria applied or whether the recipient had authority to accept the work. “That’s not what we agreed” is equally difficult if nobody can identify the drawing revision, finish sample, specification or approved change that defines what was required.

An open-ended review process can leave completed work commercially unresolved while the project waits for comments that may never arrive. The specialist contractor may already have paid labour, suppliers and material costs. The client may reasonably be unwilling to approve work without adequate evidence. Both sides need a clear transition from completed work to a documented decision.

A fixed challenge window does not remove anyone’s right to raise a genuine problem. It makes the timing, subject and basis of a challenge visible. If no challenge is raised, the record can show that the agreed review opportunity expired without a documented objection. That fact does not, by itself, turn silence into contractual acceptance. Any legal or commercial consequence depends on the underlying contract and the administration process agreed by the parties.

The governance record should preserve what happened. It should not invent consequences.

Start with a milestone that can actually be reviewed

A challenge window is only useful if everyone understands what is being reviewed.

“Joinery complete” is usually too broad. A clearer milestone might be:

Level 3 bedroom joinery installed and ready for review.

That milestone could reference:

• the applicable drawing revision;
• the approved veneer or finish sample;
• the relevant hardware schedule;
• agreed alignment and visible-quality requirements;
• any testing or operational checks; and
• the evidence expected at submission.

For a fabricated metal staircase, the criteria might cover dimensions, finish, fixings and installation condition. For bespoke cabinetry, they might include approved veneer selection, door alignment, operation, protection and final installation photographs.

Not every criterion can be reduced to a number. Bespoke work involves professional judgement, but expectations should still be made as explicit as reasonably possible before fabrication or installation begins.

The project should also establish who has which role in the decision. One person may upload evidence, another may provide technical comments, and a site manager may confirm access or installation conditions. The person authorised to accept or formally challenge the milestone may be somebody else entirely. Authority should not be inferred because someone is copied into an email or belongs to the same WhatsApp group.

Submit evidence that answers the decision being requested

When the milestone is ready, the delivering party should submit evidence against the agreed criteria. Depending on the work, that may include:

• dated photographs;
• delivery records;
• marked-up drawings;
• inspection records;
• test results;
• commissioning information; and
• material certificates.

Evidence needs to answer the actual question being asked.

Twenty unlabelled photographs may be less useful than six clearly linked to the correct room, component and acceptance criterion. A delivery note may prove that something arrived on site, but it does not prove that the installed work complies with the approved design. A photograph may show a finish at a particular time, but not that moving hardware operates correctly. A commissioning sheet can demonstrate testing, but not that a visible finish matches the agreed control sample.

The party requesting a decision should show the evidence supporting it. The person reviewing it should be able to see exactly what they are being asked to accept or challenge.

Open a defined and proportionate challenge window

There is no universally correct number of days.

A simple delivery confirmation may require only a short review period. A complex handover involving specialist inspection, consultant input or physical access may reasonably require longer. The appropriate period depends on factors such as:

• the contract;
• the complexity and value of the work;
• the programme;
• availability of authorised reviewers;
• whether physical inspection is required; and
• whether consultant input is necessary.

What matters is that the period is agreed, recorded and visible before there is a dispute. A challenge window designed only after an invoice becomes contentious is unlikely to create confidence.

What makes a useful challenge?

A meaningful challenge should identify the specific issue being raised.

Compare “Not happy with the finish” with:

Door fronts to the master dressing room do not match the approved veneer control sample dated 14 May. See photographs 3 to 6. Please propose an inspection and remedial options.

The second statement gives the project something it can work with. A useful challenge should identify, where relevant:

• the milestone;
• the acceptance criterion involved;
• the issue being alleged;
• supporting information; and
• the requested next action.

This gives the delivering party a fair opportunity to inspect the issue, respond and propose the appropriate next step. It also reduces the risk of an objection gradually changing as memories and commercial positions change.

Record the outcome before the invoice becomes the argument

At the end of the review process, the project record should show what happened. The outcome might be:

• accepted;
• challenged;
• accepted with agreed actions; or
• awaiting a defined inspection or further evidence.

Where a challenge exists, it should not disappear into a separate message thread. The record should show who raised it, the evidence associated with it, the response and what happened next.

This is also where payment readiness becomes clearer. Payment readiness does not mean a platform has decided that an invoice is legally due. It means the authorised parties can see whether the agreed milestone was reached, the required evidence was submitted, the review opportunity occurred, a challenge was raised, and any agreed acceptance conditions connected to the commercial decision have been satisfied. The contractual consequence remains governed by the project’s own agreement and administration process.

Fixed challenge windows are not a shortcut to deemed acceptance

Poorly designed challenge windows can create false confidence.

Sending incomplete evidence at 5pm on Friday and relying on a very short deadline is not good governance. Neither is setting a review period that ignores the practical need for a site inspection, consultant input or client availability.

Fixed challenge windows work best when they are proportionate and agreed in advance. They should sit alongside the project contract and established administration process, not replace them. Expiry of a challenge window should not automatically be described as acceptance unless the parties’ contractual arrangements expressly support that consequence.

The project can safely establish the factual record:

The evidence was submitted, the review period was available, and no documented challenge was recorded during that period.

Those facts may later be important. The governance system should preserve the facts rather than manufacture a legal conclusion.

The value is the decision history

In a well-governed workflow, the important point is not simply that a deadline expired. The project should be able to connect the milestone, applicable acceptance criteria, submitted evidence, authorised reviewer, any challenge, the response and the recorded outcome.

Months later, a project director, adviser or commercial manager may need to understand why a variation was approved, why a defect was raised after installation or why an invoice remained unresolved. A proper record can show the original scope, relevant drawing, evidence submitted, date the review period opened, challenge raised, response provided and final outcome.

That becomes a decision people can prove, rather than one everyone remembers differently.

Where Bespea fits

Bespea provides a governance and evidence layer for these project decisions. It can help structure the relationship between milestones, submitted evidence, acceptance criteria, authorised decisions and the record that follows.

The purpose is not to make every project interaction bureaucratic. It is to preserve what was agreed, what evidence was submitted, who had authority, what was challenged, what response followed and what outcome was recorded. Those records can form part of a Decision Passport and, where appropriate, a Proof Pack that can be reviewed later.

Bespea is not legal advice, an escrow provider, a bank, an insurer or a substitute for contractual professionals. Its role is practical: make important project decisions easier to reconstruct and harder to rewrite after the fact.

Not every disagreement will disappear. Bespoke work involves judgement, changing site conditions and legitimate differences of opinion. A project with a clear review process and an evidence-backed decision history is in a stronger position than one governed by recollection, scattered photographs and conflicting messages.

Agree the review period while the project is calm. Do not wait until the invoice becomes the argument.

For more on milestone evidence and acceptance criteria and evidence before payment, see the related Bespea guides. The wider project process is described in how Bespea works.

A review window only works when the milestone explains what is being assessed. See the guide to milestone acceptance criteriafor practical examples.