Payment Readiness for Contractors: How to Build a Record That Holds Up

A £40,000 joinery package can be fitted, photographed and handed over, yet still be commercially stuck because nobody can show precisely what was accepted.

The site team believes the work is complete. The client wants a minor adjustment. Accounts has an invoice but no clear approval.

This is where payment readiness for contractors breaks down. Not at the point of payment, but much earlier in the project record.

For bespoke construction, fit-out and specialist fabrication, payment readiness is not simply a matter of sending an invoice on the right date. It is the ability for the relevant people to see what was agreed, what changed, what was delivered, what evidence supports it, who was authorised to decide, and whether the agreed conditions for payment readiness have been met.

That protects both sides.

A contractor should not have correctly completed work held up by vague objections raised after the fact. Equally, a client should not be asked to release money without enough evidence that the agreed work is in place and meets the stated requirements.

What payment readiness for contractors actually means

Payment readiness is a governed commercial position.

It means the work has progressed through a record that connects:

• scope
• milestone and acceptance criteria
• evidence
• authorised review
• acceptance or challenge
• payment request

This is different from saying, “Sent you the photos on WhatsApp mate.”

Photos may be useful evidence, but a message thread rarely establishes which milestone they relate to, whether the images show the agreed specification, who was authorised to accept the work, or whether an issue was raised and resolved.

It is also different from treating practical completion as a single informal moment.

On a high-value bespoke project, one payment may depend on approved drawings, another on materials arriving, another on workshop completion, another on installation, and another on resolution of agreed snags.

The right structure depends on the contract and the project. The principle does not: each commercial step needs a clear basis.

A payment-ready milestone should answer five straightforward questions:

• What work or deliverable was due?
• What acceptance criteria applied?
• What evidence was submitted?
• Who was authorised to accept or challenge it?
• What decision followed, and when?

If those answers live across emails, voice notes, revised drawing folders and individual phones, the project may still move forward.

But when an invoice is challenged, reconstructing the position becomes slow, personal and expensive.

Why completed work still becomes unpaid work

Delayed payments often develop through small gaps in project control.

An installer receives a site instruction to alter a finished detail. The workshop acts quickly to protect the programme. The cost and time effect are discussed but never confirmed.

Later, the client says the alteration was included. The contractor says it was a variation.

Both may genuinely remember the conversation differently.

Or a drawing is revised after manufacture begins. The revised version is in an email, but the instruction to proceed against it is verbal.

The item arrives on site and is criticised against an earlier expectation.

By then, the question is no longer just whether the work looks right.

It is which decision governed the work.

The invoice then becomes the place where unresolved project decisions surface.

Accounts cannot fix that. Neither can another payment chase.

The commercial team needs a reliable record before the request for payment is made.

There is a trade-off here.

Too much administration can slow a fast-moving project and frustrate experienced teams. Too little discipline leaves significant decisions dependent on memory.

The aim is not to document every conversation.

It is to capture the decisions that change scope, cost, time, quality, responsibility, acceptance or payment readiness.

Build payment readiness through four project actions

The useful sequence is straightforward: set the milestone, submit evidence, make an authorised decision, then make the payment request against a clear project record.

Each step needs enough structure to be useful later without turning the site team into contract administrators.

1. Set milestones with acceptance criteria

A milestone should describe a meaningful commercial point, not merely an internal activity.

“Joinery package complete” may be too broad if the project needs to distinguish workshop sign-off, delivery, installation and final acceptance.

Define what is expected at each point.

This might include an approved drawing revision, material specification, sample approval, delivery note, installation photographs, commissioning record or client walk-through.

It may also include what is outside the milestone, such as separately priced alterations or items awaiting another trade.

Acceptance criteria need to be proportionate.

A bespoke bronze screen may need finish samples, fabrication photographs, dimensions, delivery evidence and installation sign-off.

A minor site protection item may need far less.

The point is that the parties can see in advance what will support the commercial decision.

2. Submit evidence against the right milestone

Evidence is strongest when it is linked to the exact thing it is intended to prove.

A photo should sit against the relevant milestone or change, not disappear into a general project gallery.

A delivery note should identify the package and date.

A drawing should carry its revision status.

A site instruction should record who issued it, what was requested and whether the consequences were agreed.

Evidence does not itself create acceptance. It establishes the factual basis on which an authorised person can accept, challenge or request more information.

If an issue is visible, recording it is better than pretending it does not exist.

A clear challenge with an owner and required action can preserve progress where a vague objection simply holds the invoice hostage.

3. Accept or challenge through the right authority

Acceptance should not be assumed from silence unless the contract expressly provides for that outcome.

Nor should every minor issue automatically stop an entire package from progressing.

A governed workflow should allow an authorised party to accept the milestone, challenge it with stated reasons, or record an outstanding item where the contract and project process allow it.

That distinction matters.

“Not what we agreed” is not a useful project record.

The east elevation panel differs from approved drawing J-214 Rev C; replacement required before final retention release.

Authority matters as much as wording.

A site manager may be able to confirm access or installation sequencing but may not have authority to approve a value-changing variation.

A designer may approve appearance but may not have authority to make a commercial acceptance decision.

The project should make clear who can decide what.

Authentication, membership or job title alone should not be treated as authority for a consequential project decision.

4. Make the payment request against a governed record

Once the milestone has reached the payment-ready state defined by the project and contract, the payment request can point to a clear commercial record.

The invoice remains a financial document.

Payment readiness is the supporting project position.

That record should make it possible to see:

• the agreed milestone
• the acceptance criteria
• submitted evidence
• recorded changes
• challenges or outstanding items
• the authorised decision
• the decision history
• relevant timestamps

Keep the stages distinct: evidence is not acceptance; acceptance is not payment readiness; payment readiness is not a payment instruction; a payment instruction is not settlement.

This does not guarantee that payment will arrive on time.

Bespea is not a bank, payment processor or escrow provider. A governance record cannot remove a genuine dispute or override the contract.

It can make the payment conversation substantially more factual.

Instead of reconstructing the position from inboxes, phones and memory, the relevant parties can review the milestone, evidence, decisions, challenges and history that led to the payment-ready position.

Treat changes as commercial events, not site chatter

The fastest route from a reasonable instruction to an argument is to carry out changed work before recording what changed and who accepted the consequence.

That does not mean every instruction must wait for a lengthy formal process.

On some projects, urgent action is necessary to prevent delay or damage.

In those cases, record the instruction immediately, identify the decision-maker, state the known impact and mark any commercial point still to be agreed.

A temporary attributable record is still better than no record at all.

The essential distinction is between a request and an agreed change.

A client asking, “Can we move that return by 50mm?” is not automatically an approved variation.

It becomes a governed change when the revised scope, likely impact and authority to proceed are recorded according to the project process.

This protects clients from unexpected additions and contractors from absorbing work undertaken in good faith.

It also prevents a common end-of-project problem: several small changes that seemed manageable in isolation become a material unpaid balance when added together.

Create a record that can survive a difficult conversation

A healthy project does not need formal evidence every day.

But the record must still be usable when relationships become strained, people leave, or memory changes.

That means preserving history rather than quietly overwriting it.

The original scope, later change, evidence submission, acceptance and challenge should remain connected.

If a drawing is superseded, the project should show that it was superseded, not make it appear that it never existed.

If a decision changes, the basis for the later decision should remain visible.

Bespea supports this through governed milestones, controlled changes, evidence submissions, Decision Passports and Proof Packs designed to preserve attributable and tamper-evident project history.

The purpose is not legal theatre.

It is to give project teams a commercial decision they can explain and evidence later, whether they are discussing a payment certificate, resolving a snag or explaining a variation to a client representative.

Start before the next invoice is due

Trying to create payment readiness at the point of invoicing is usually too late.

Start with the next meaningful milestone.

Agree what it covers.

State what evidence is required.

Identify who has authority to accept or challenge it.

Record any change that affects its value, timing or criteria.

Then preserve the decision that follows.

The result is not paperwork for its own sake.

It is fewer moments where completed work is met with, “That is not what we agreed,” and nobody can quickly show the answer.

Protect the project before there is a dispute, while the facts are still clear and the next decision can still be made properly.

For practical guidance on construction milestone acceptance criteria and fixed challenge windows, see the related guides. For the wider project process, read how Bespea works or learn about the Decision Passport.