A Construction Approval Workflow You Can Prove

A site instruction can take less than a minute: “Can you just move that detail over slightly?” The commercial consequences can last months.

Once manufacture has started, materials have been ordered or labour has been booked, a casual instruction is no longer casual. A construction approval workflow gives the team a way to record what was asked for, what it changes, who needs to decide and what evidence will show whether the agreed requirement has been met.

For high-value bespoke work, this is not administrative decoration. Joinery, specialist metalwork, fit-out packages and architectural finishes are often judged against details that cannot be reduced to a simple tick box.

The project needs enough discipline to protect the client from treating work as accepted when it does not meet the agreed requirement, and enough clarity to protect the delivery team from being asked to absorb undocumented change.

Why informal approval breaks down

Most approval failures do not begin with bad intent. They begin with pressure.

The programme is tight, someone is on site, a drawing is open on a phone, and the fastest route appears to be a message, a call or a verbal instruction.

The problem arrives later.

The contractor says, “You approved that on site.”

The client says, “That is not what we agreed.”

Someone sends photographs from WhatsApp. Someone else finds an older drawing in an email thread.

Neither side can easily establish the complete decision: which version was being discussed, what effect the change had, whether the cost or programme consequence was understood, what evidence was later submitted, and whether the finished work was actually accepted or challenged.

Project-management software can schedule tasks and store documents. Messaging platforms are useful for quick coordination. Neither automatically creates a reliable governance record for a material decision.

A workable approval process connects the decision to its scope, acceptance criteria, evidence, authority and commercial consequence.

The four stages of a construction approval workflow

A disciplined workflow does not need to slow down a project. It needs to distinguish between ordinary coordination and a decision that carries real consequence.

In practice, the workflow connects four stages:

1. agree and activate the milestone and its criteria;
2. submit evidence against those criteria;
3. record the authorised decision;
4. establish whether the work is ready to progress commercially.

1. Agree and activate milestones around real decisions

A milestone should represent a meaningful point at which a project party needs confidence before work progresses commercially.

That might be approval of shop drawings before manufacture, confirmation of a material sample, completion of first-fix installation, delivery to site, or sign-off of a finished room.

The milestone and its acceptance criteria should establish what has been agreed and how success will be judged before the governed work proceeds through that stage.

“Complete joinery package” is too vague.

A clearer milestone might identify the approved drawing revision, specified finish, hardware schedule, installation location, tolerances where relevant, and any exclusions or dependencies.

This is where acceptance criteria matter.

They are not an attempt to turn bespoke work into a commodity. They provide a shared basis against which the relevant evidence and later decision can be understood.

Some criteria will be objective, such as a delivery note, dimensions or fire certification. Others will require judgement, such as grain matching, alignment or finish quality.

The point is not to eliminate judgement. It is to make the basis of that judgement visible before commercial consequences depend on it.

There is a trade-off. Overly detailed criteria can create needless administration for a small or low-risk package. Loose criteria leave too much room for memory and interpretation.

The appropriate level depends on the value, complexity, lead time and consequence of getting the decision wrong.

2. Submit evidence against the agreed criteria

Evidence is not just a folder of photographs taken at the end of a job.

It should answer the practical question being decided: has the stated condition been met?

For a manufacturing milestone, that could include dated photographs, inspection records, material certificates and the relevant approved drawing.

For delivery, it may include a delivery note, photographs of the goods, a site receipt and records of any visible damage.

For installation, it might include photographs from agreed viewpoints, commissioning information, snag records and confirmation that relevant dependencies have been completed.

Context is what gives evidence its value.

A photograph without a location, date, item reference or connection to an acceptance criterion can still be useful, but it is easier to challenge or misinterpret later.

A well-organised evidence submission shows what it relates to, who submitted it, when it was submitted and which milestone or criterion it supports.

The delivery party benefits because completed work is not left to be inferred from a claim in an invoice.

The client benefits because a decision can be based on something more useful than “we are ready for payment”.

Both parties can see what has actually been presented for review.

3. Record the authorised acceptance, challenge, approval or rejection

A governed decision should be explicit, not silence mistaken for consent.

The available decision should depend on the party's authority and the exact project context, rather than treating every reviewer as interchangeable.

Depending on that context, the relevant authorised party may need to accept or challenge a submission, or approve or reject the relevant governed action.

A challenge is not necessarily a dispute.

It may be entirely legitimate.

A client may identify that a handle finish differs from the agreed sample. A delivery party may point out that the sample changed after procurement. A Studio may determine that the evidence does not yet demonstrate the agreed criterion.

A proper workflow gives these issues a place to be raised while the facts are still available.

What matters is that the decision is connected to the exact scope, evidence and criterion in question.

“The workmanship is poor” is difficult to act on.

“The veneer joint at the east elevation does not match the agreed sample reference and needs review” is specific enough to investigate, respond to and resolve.

Authority matters as much as the decision itself.

The person who can comment on aesthetics may not have authority to approve a variation. The person who can confirm that goods arrived on site may not have authority to determine a commercial consequence.

A reliable record therefore needs to preserve not only what was decided, but the context in which the authorised decision was made.

4. Connect governed acceptance to payment readiness

The purpose of a construction approval workflow is not to automate payment or decide who is legally right.

It is to make payment readiness easier to assess from a governed record.

When the relevant milestone has reached the required governed outcome, the commercial team has a clearer basis for determining what should happen next.

That record may include the original scope, approved changes, evidence submitted, acceptance or challenge history, relevant decisions and timestamps.

It gives the commercial process a connection to the work rather than leaving accounts teams to reconstruct the project from emails, voice notes and site photographs.

This is particularly valuable where staged payments support procurement and specialist manufacture.

A delivery party should not have to wait indefinitely for a response to work that has been properly evidenced.

Equally, a client should not be expected to treat work as payment-ready simply because a deadline has arrived when the agreed acceptance basis remains unresolved.

Payment readiness is not the same as holding, moving or automatically releasing money. The payment itself can remain directly between the parties under their agreed commercial arrangements.

Change control is where the workflow earns its keep

The original scope is only part of the record.

Bespoke projects change.

A wall moves. A consultant issues a revised detail. A client selects a different finish. Site conditions require an alternative fixing method.

The relevant question is not whether change can happen. It is whether the change is captured before it becomes an argument about cost, time or quality.

A material change should identify the request, the reason, the affected scope, the drawing or specification revision, the proposed cost and programme effect where known, and the decision required.

If work must proceed urgently, the record should say that too, including the known instruction, assumptions and what remains subject to confirmation.

There are occasions when the full commercial consequence cannot be priced immediately.

That is not a reason to leave the instruction undocumented.

Record the instruction, the known impact, the assumptions and the route for agreeing the outstanding value.

Putting material decisions in writing does not mean every answer must be available at once. It means uncertainty is visible rather than buried in a chat thread.

Build a record that survives pressure

The real test of a workflow is not whether it looks tidy at the start of a project.

It is whether, six months later, a new commercial manager, client representative or adviser can understand the decision history without relying on the memories of people who have moved on.

Bespea can sit alongside existing drawings, emails and project-management systems to provide a governed evidence and decision record rather than asking teams to abandon the tools they already use.

Its Decision Passport preserves the basis and history of governed decisions.

Proof Packs provide a portable, tamper-evident export of relevant governed evidence and decision history. Public Verify can be used to verify integrity and authenticity without making the underlying project record public.

The underlying governance record is designed around append-only, tamper-evident history so that important events are preserved rather than silently rewritten when a relationship becomes difficult.

That does not make Bespea an escrow provider, payment processor or legal adviser.

It does not replace contracts, professional judgement or existing project-management tools.

It helps authorised parties establish what was agreed, what changed, what evidence supports the work, what was accepted or challenged and whether the governed record supports the next commercial step.

Start with the decisions that carry real consequence: approval before manufacture, changes after instruction, evidence before sign-off and governed acceptance before payment readiness.

When the project can show who was authorised to decide, what they decided, which evidence supported it and what happened next, the team no longer has to reconstruct the truth after the relationship comes under pressure.