Construction Payment Certification and Payment Readiness

A payment application can be technically correct and still sit unanswered because nobody can see, in one place, what was agreed, what changed, what evidence exists and whether the relevant work has reached the required acceptance state.

Construction payment certification is often experienced as an accounting event at the end of the month. In practice, the commercial decision depends on what the contract requires, what work has been completed, what has changed, what evidence exists and who has authority to assess it.

On bespoke fit-out, joinery and specialist fabrication projects, making that decision traceable can reduce the ambiguity surrounding payment readiness.

That distinction matters when the project team is relying on a site conversation, a revised drawing issued after manufacture began, or a message saying, “Sent you the photos on WhatsApp mate.”

Those things may provide useful context. They are rarely a reliable basis for assessing a payment application or establishing the project record that supports it.

Bespea does not perform payment certification. It provides a governance and evidence layer that can help authorised parties understand the evidence, acceptance status and decision history associated with a payment stage.

What construction payment certification should establish

In practical terms, payment certification is a contractual process through which an appropriately authorised person assesses work, materials, variations or other relevant items against the applicable agreement and determines what may be certified.

The exact process depends on the contract, appointments and allocation of authority. A quantity surveyor, contract administrator, employer's agent, project manager or client representative may have different responsibilities on different projects.

Bespea does not replace those roles or determine contractual entitlement.

The underlying commercial questions are more consistent:

Can the paying party understand the basis of the application?

Can the delivering party show the evidence supporting its position?

Can the team identify what has been accepted, challenged or remains unresolved?

And can the resulting decision be attributed to someone with the relevant authority?

For a straightforward commodity package, a percentage-complete assessment may sometimes provide much of the required information.

High-value custom work can be different.

A reception desk can be substantially manufactured and delivered to site, yet still face a challenge because the stone, finish, dimensions or integration differ from the agreed requirement.

A joinery package can be fully installed while acceptance remains unresolved because snagging, test records or other agreed conditions have not yet been addressed.

Good governance does not mean treating every payment application as a dispute waiting to happen.

It means reducing avoidable ambiguity before the commercial decision has to be made.

Why payment applications become difficult

Many difficult payment assessments are not caused by arithmetic.

They arise because the record connecting scope, change, evidence, acceptance and authority has broken down.

A contractor may say a variation was instructed on site. The client may accept that a discussion took place but dispute its extent, price or programme consequence.

A designer may have issued a revised detail, but nobody recorded whether it superseded the previous requirement, whether additional fabrication was authorised or what had already been committed when the revision arrived.

The work may be complete in the workshop while another party understands completion to mean installed, tested and accepted on site.

Each party can have a reasonable account of events.

The problem is that the project may have no shared decision history capable of showing what information existed, who had authority to act and what decision followed.

This becomes particularly difficult where the payment process begins only after the work has been completed.

By then, people may be reconstructing decisions from email chains, marked-up drawings, photographs on personal phones and messages that lack context or a clear decision.

The payment application becomes the point at which scope, change and acceptance are argued retrospectively.

That is late, expensive and damaging to relationships.

Payment readiness is not the same as payment

Payment readiness should be treated as a project-governance status, not as the movement of money.

It records whether the agreed governance conditions associated with a payment stage have been addressed and what, if anything, remains unresolved.

That distinction is important.

Payment readiness does not certify payment.

It does not determine contractual entitlement.

It does not guarantee that payment will be made.

It does not override valuation, notices or other contractual requirements.

And it does not move or hold money.

Those consequences remain governed by the contract and the relevant authorised parties.

What payment readiness can provide is a clearer factual position for review.

Has the stated milestone or element of work been achieved?

What evidence supports that position?

Has the relevant submission been accepted or challenged?

Is anything still unresolved?

Who has authority to make the next decision?

For a specialist manufacturer, the relevant evidence might include approved shop drawings, fabrication photographs, inspection records and delivery notes.

For a fit-out contractor, it may include installation photographs, test certificates, snag status and evidence associated with acceptance of a defined area or milestone.

For the client, the same record can help distinguish between an application supported by agreed project requirements and one where material conditions remain unresolved.

The evidence should remain proportionate to the consequence.

A large or high-risk milestone may justify a more complete evidence set than a routine interim item.

Too little evidence creates uncertainty. Requiring every possible document for every minor decision creates friction of another kind.

The objective is not maximum documentation.

It is the right evidence connected to the right requirement and the right decision.

A practical workflow for payment readiness

Payment readiness works best when it is part of project governance from the beginning rather than reconstructed at the end.

The sequence is straightforward:

Define the milestone → establish acceptance criteria → submit evidence → authorised review → accept or challenge → record the outcome → establish payment-readiness status.

1. Define the milestone and acceptance criteria

Define what the milestone covers, what is excluded, what evidence will be expected and who has authority to act.

“Joinery complete” is not a useful acceptance criterion on its own.

A more useful definition might identify the relevant area, approved drawing revision, finish reference, installation state and required snag status.

The objective is to give both sides something capable of being assessed against an agreed reference point.

2. Submit evidence against the requirement

Evidence may include dated photographs, delivery notes, inspection sheets, test results, approved drawings and records of relevant site instructions.

The purpose is not to create a larger document folder.

It is to connect the evidence to the requirement it is intended to support.

That connection matters because evidence without context can still leave the reviewer asking what the photograph, document or record is supposed to establish.

3. Allow the authorised party to accept or challenge

The person or organisation with the relevant authority should be able to accept the submission, challenge a defined issue or request specified further information where the governing process allows it.

A response such as “not happy with this” gives the team little basis for resolution.

A useful challenge identifies the requirement or issue being challenged and creates a record of what must be addressed next.

Where the agreed project process provides a review or challenge window, that period should also be explicit so the submission does not remain indefinitely unresolved.

4. Record the decision and payment-readiness status

Evidence does not make the commercial decision by itself.

Once the submission has been reviewed, the resulting decision should be recorded together with the authority under which it was made and the evidence available at that point.

The payment-readiness status can then reflect the governed outcome.

If part of a milestone is accepted while another part remains challenged, that distinction should be visible rather than forcing the project into an artificial all-or-nothing position.

This does not replace contractual valuation, payment notices, certification provisions or other requirements.

It gives the authorised parties operating those processes a clearer and more traceable project record.

Control variations before they contaminate the valuation

Variations are one of the places where payment assessment becomes most exposed.

Bespoke work changes for legitimate reasons.

Site dimensions differ. A client changes a finish. A design detail becomes impractical to manufacture. Another trade creates an interface problem. Existing conditions reveal something that could not reasonably be confirmed earlier.

The risk is not change itself.

The risk is allowing changed work to proceed without a usable record of what changed, why it changed, what consequences were identified and who had authority to decide what happened next.

A useful change record should identify the original requirement, the instruction or reason for change, the revised requirement, available evidence, likely cost or programme consequence and the relevant decision.

Where value cannot immediately be agreed, the project record should accurately reflect the actual position rather than retrospectively presenting an unresolved matter as approved.

Without that discipline, a contractor may include additional work in an application because it believes the work was necessary or instructed, while the client sees an unapproved extra.

Neither position is strengthened by a screenshot of an informal message that cannot be reliably connected to scope, authority and a recorded decision.

Make the decision history portable

A project record needs to remain understandable when people change roles, relationships deteriorate or an external adviser needs to establish what happened.

That means preserving more than final documents.

The sequence matters.

What was required?

What changed?

What evidence was submitted?

Who had authority at the relevant point?

Was the submission accepted or challenged?

What remained unresolved?

What decision was eventually recorded?

Bespea provides a governance and evidence layer for this purpose.

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 of relevant project evidence and decision history when that record needs to be reviewed independently of the day-to-day project workflow.

Bespea does not certify payment, determine contractual entitlement, hold funds or provide legal advice.

It does not replace the contract, quantity surveyor, contract administrator, employer's agent or other project professionals.

Commercial and contractual decisions remain with the relevant authorised parties.

Bespea's role is narrower: preserve a trustworthy record connecting evidence, authority and decisions throughout the project.

The discipline that protects both sides

A contractor deserves a prompt and fair assessment when it has delivered properly documented work.

A client deserves confidence that a payment assessment can be traced back to agreed scope, supported progress and the relevant project decisions.

Neither interest is served by turning payment certification into a contest of memory.

Define the milestone while the scope is clear.

Establish the acceptance criteria before they become contentious.

Record material changes while they are being discussed.

Connect evidence to the requirement it supports.

Allow the authorised party to accept or challenge the submission.

Record the resulting decision and payment-readiness status.

Then let the contractual payment process operate from a project history that can still be understood months later.

The objective is not to make Bespea the decision-maker.

It is to make the decisions that matter easier to understand, attribute and prove.