Essential Practical Completion Records That Stand Up

Practical completion is often treated as a date to chase rather than a decision to prove.

That is how a project reaches handover with a completed installation, a waiting invoice and the familiar response:

“That’s not what we agreed.”

Essential practical completion records create a clear account of what was required, what was delivered, what changed, what remains outstanding and what an authorised person decided on the evidence available at the time.

For high-value joinery, specialist fit-out and bespoke fabrication, the problem is rarely a total absence of information. There may be photographs on WhatsApp, marked-up drawings in email, delivery notes in a site folder and verbal instructions remembered differently by everyone involved.

The difficulty is connecting those fragments to the agreed scope, the relevant acceptance criteria and the actual completion decision.

A practical completion record should not be a retrospective bundle assembled when payment has already become difficult. It should be a working governance record that allows the project team to assess the basis for payment readiness against a clear history of scope, evidence and decisions.

What practical completion records need to establish

The phrase practical completion can mean different things under different contracts and appointments. The applicable project documents determine the formal contractual position.

Operationally, however, the record needs to answer a small number of direct questions.

• What scope was due at this milestone?
• What acceptance criteria applied?
• What evidence was submitted?
• Does that evidence relate to the correct scope and current approved information?
• Are there defects, omissions, challenges or separately recorded residual items?
• Who has authority to make the relevant decision?
• What decision was actually made?

Without those answers in one attributable record, practical completion becomes vulnerable to interpretation.

A contractor may say the joinery was installed, protected and ready for inspection. A client may say an issue was raised during a walkround. Both statements might be true, yet neither resolves whether the issue relates to an agreed requirement, a minor residual item, a material departure, an approved change or something outside the contractor's scope.

The record is not there to eliminate judgement. Bespoke work involves judgement.

It is there to ensure that judgement happens against a visible basis rather than through scattered messages and fading memory.

Set the completion standard before work is inspected

A completion record starts long before the final inspection.

The milestone should identify the relevant scope, current approved drawings or specifications, installation location and acceptance criteria. Where finish, alignment, tolerance, operation or integration matters, say so clearly.

“Install feature wall” is not a useful completion standard on its own.

It leaves open questions about panels, shadow gaps, finish consistency, access panels, interfaces with lighting, protection and cleaning.

The requirements need not become an unreadable contract within a project platform. They do need to be specific enough that the delivery team knows what evidence to submit and the reviewer knows what decision they are being asked to make.

This matters especially where drawings change during manufacture or on site.

If a revised detail was agreed, the completion record should point to that controlled change and show its effect on the relevant scope, acceptance criteria, cost or programme where applicable.

Otherwise, an inspection can end up comparing completed work with a superseded drawing.

There is a trade-off.

Overly detailed criteria can slow simple packages and encourage box-ticking. Too little detail leaves the parties arguing about quality only after work is complete.

The right level depends on the value, complexity, consequence and visibility of the work.

A concealed bracket does not need the same evidence trail as a hand-finished reception desk, but both need a defined basis for acceptance.

Keep scope, changes and completion connected

One of the most expensive failures occurs when a site instruction is treated as if it were automatically an approved change.

“Move it 50 mm” may be clear in the moment, but it may affect fabrication, associated trades, access, finish lines, programme, cost and responsibility for remedial work.

If an instruction changes the agreed scope, the record should distinguish the request from the decision that authorises the change.

Record what changed, who requested it, the relevant consequences and whether the person making the subsequent decision had authority to do so.

A message, drawing revision or site conversation is not automatically authority to alter every commercial consequence of the project.

At practical completion, the team should not have to reconstruct whether a visible difference is a defect or an authorised variation.

That distinction can affect acceptance, payment and the working relationship long after the installers have left site.

Submit evidence that can be reviewed

Photographs are useful, but “Sent you the photos on WhatsApp mate” is not a completion record.

Images need context: what they show, where they were taken, when they were submitted and which milestone, scope item or acceptance criterion they are intended to evidence.

A proportionate evidence submission may include photographs of the finished installation and key interfaces, delivery notes, commissioning or test results, cleaning and protection records, warranties, care information, marked-up drawings and confirmation that specified remedial items have been addressed.

For manufactured work, it may also include shop inspection records or finish samples where these formed part of the agreed acceptance route.

The aim is not administration for its own sake.

It is to make review possible without relying on one person's recollection.

Evidence should be connected to the relevant governed milestone rather than buried among weeks of project correspondence.

Time and attribution matter.

A photograph submitted after a challenge is not necessarily unreliable, but it is different from evidence recorded during the completion inspection. Clear timestamps and attributable submissions allow the sequence to be understood without pretending that the record itself decides the underlying technical issue.

Evidence also does not equal acceptance.

A contractor can provide evidence that work was carried out. An authorised person still has to make the relevant decision against the agreed requirements.

That separation matters.

“We completed it” and “the authorised party accepted it” are not the same event.

Authority must be explicit

Many completion disputes are also authority disputes.

A site manager may confirm that an installation can proceed. A designer may comment on appearance. A project manager may coordinate the programme. A client representative may have authority to make a particular acceptance decision.

Those activities are not automatically interchangeable.

Being able to view, comment on or participate in a project does not automatically give someone authority to accept work or bind the project commercially.

The record should therefore identify who is authorised to make the relevant decision and preserve that attribution with the decision itself.

If authority changes, that change should be recorded rather than inferred from who happened to send the latest email.

This does not need to make the workflow slow.

It makes the consequence of the decision clear.

Make the decision explicit: accept or challenge

Silence, a thumbs-up reaction or an invoice processed by accounts can all be interpreted differently later.

The governed completion decision should be explicit.

Where the evidence supports the agreed requirements, the authorised person can accept the relevant milestone.

Where the requirements have not been met, the evidence is insufficient, or there is another clear basis for objection, the milestone can be challenged.

A proper challenge identifies the relevant requirement, the observed issue, supporting evidence and the response required.

“Quality not acceptable” is too vague to resolve.

“The veneer grain on the east-facing cabinet does not match the approved sample referenced in the finish schedule” gives the delivery team something that can be checked, answered and, if necessary, rectified.

A challenge is not automatically proof of a defect or an admission of responsibility.

It may expose a workmanship issue, an unclear interface, a late change, superseded information or an expectation that was never part of the agreed scope.

The purpose of the record is to preserve the basis of the decision so the parties can address the actual issue.

Where further evidence is required before an acceptance or challenge can be resolved, that requirement should also be recorded explicitly rather than hidden in informal correspondence.

Keep residual items separate from the acceptance decision

Minor outstanding work should not be converted into an ambiguous third decision.

Residual items can be recorded separately, with the item, owner, required closure evidence and, where appropriate, due date clearly identified.

Whether those items affect practical completion depends on the applicable contract, their significance and the authorised commercial decision.

A missing touch-up and a material failure against an agreed requirement are not equivalent merely because both appear on a list.

Keeping residual items explicit and separate preserves the meaning of the underlying acceptance or challenge.

It also protects both sides.

The client has a visible record of work still requiring attention. The delivery team is not left with an undefined list that expands after the event.

Separate a challenge from a rewrite of history

Projects become difficult when the record can be quietly altered after a disagreement.

A completion record should preserve what was submitted, what evidence existed, who had authority, what decision was made and what happened afterwards.

That does not mean mistakes cannot be corrected.

It means a correction should appear as a subsequent attributable event rather than silently replacing the history that preceded it.

The original decision, its basis and later action should remain traceable.

This is the difference between a folder of files and a decision you can prove later.

Bespea is designed as a governance and evidence layer around this problem.

It connects governed milestones, evidence, changes, acceptance and challenge into an attributable history. Its Decision Passport is designed to preserve the decision history, while Proof Packs provide a tamper-evident way to package relevant governed records for later verification.

Bespea sits alongside existing drawings, email and project-management systems rather than requiring teams to replace the tools they already use.

It does not replace the contract, professional advice or the authority of the people appointed to make project decisions.

It also does not decide who is right.

The purpose is to make the important project history provable.

Link completion to payment readiness, not automatic payment

A completion record can contribute to the basis for a payment decision, but it should not be confused with payment itself.

The commercial route may still require valuation, certification, retention calculations, tax treatment, notices or other contractual steps.

Evidence of completion does not automatically establish that a particular amount must be paid.

Nor should acceptance of one governed milestone be represented as automatic settlement of every commercial issue on the project.

What a governed completion record can establish is a clear basis:

• what scope was relevant;
• what evidence was submitted;
• what changed;
• what decision was made;
• who made it;
• what challenges remain open; and
• what residual items remain separately recorded.

That gives the relevant parties a clearer basis for assessing payment readiness without Bespea becoming the payment rail.

Bespea does not hold client money, release funds or act as escrow.

Payment can continue through the appropriate contractual and payment arrangements.

The governance record answers a different question:

What became ready for the next commercial decision, on what evidence and under whose authority?

That clarity matters on both sides.

Clients should be able to see the basis on which completed work is being presented for commercial progression.

Contractors should be able to show that work was submitted and reviewed against defined requirements rather than relying on a retrospective assertion that it was complete.

A practical record for the final week on site

In the final week, the project team should be able to look at one governed view of the relevant milestone and understand:

• the approved scope;
• the applicable acceptance criteria;
• controlled changes affecting it;
• the evidence submitted;
• the authorised reviewer;
• the acceptance or challenge;
• open challenges; and
• separately recorded residual items.

If those pieces are spread across personal phones, inboxes and informal site conversations, the project is carrying avoidable commercial uncertainty.

The best practical completion records are not necessarily the longest.

They are the ones that make it possible to answer a difficult question without reconstructing the project from fragments:

What was agreed, what was evidenced, who had authority, and what decision was actually made?

Put that record in place before the handover walkround.

Define the criteria.

Connect the evidence.

Confirm the authority.

Record the decision.

Preserve what happened next.

That gives everyone a clearer basis to accept completed work, challenge genuine issues and progress commercial decisions without rewriting project history.