The Casual Yes: How Informal Approvals Undermine UK Commercial Projects

On a UK commercial project, the most expensive sentence is rarely delivered in a formal meeting. It arrives in an email at 17:42, or as a thumbs-up in a project chat: 'Looks fine to me.' The words feel helpful. They are also, in many cases, the point at which scope, cost and accountability begin to drift.

This is not an argument against speed. Commercial projects cannot wait for a committee every time a drawing changes or a delivery date moves. It is an argument against confusing a comment with an approval. In 2026, with project teams spread across offices, sites and home desks, the casual yes has become a default form of decision-making. The result is a paper trail that looks busy but proves very little.

The comfort of the casual yes

Informal approval feels efficient because it removes friction. A client representative replies 'fine by me' to a supplier's note. A project manager reacts with a thumbs-up in Teams. A director copies in a colleague with 'happy for you to proceed'. Everyone believes the matter is settled. Often it is, until the invoice arrives, the programme slips, or a new stakeholder asks who agreed to the extra work.

The problem is not that people are acting in bad faith. It is that the message rarely answers three questions: who had authority to approve the change, what it would cost in money and time, and what 'done' would look like. Without those answers, a casual yes becomes a weak foundation for a commercial position.

Three gaps that turn friendliness into cost

Authority. A helpful comment from someone who lacks delegated authority is not an approval. Yet in many disputes, the supplier points to an email from a site contact, while the client points to its governance rules. Both may be telling the truth. The gap is structural: no one has made clear who can say yes, to what value, and on whose behalf.

Impact. A change that looks small in isolation can carry a compound cost: additional design hours, a revised programme, extended site presence, lost contingency. If the approval message does not record the price and time effect, those consequences are discovered later, usually at payment stage. By then, the commercial conversation is no longer about the change; it is about the absence of evidence.

Acceptance. 'Looks fine' is not an acceptance criterion. It does not say whether the work is complete, whether the evidence has been provided, or whether the client is accepting a deliverable or merely acknowledging receipt. That ambiguity is fertile ground for snagging lists, withheld payments and repeated rework.

A lightweight approval protocol

The answer is not a heavier bureaucracy. It is a short, repeatable protocol written in plain English and used consistently. UK commercial clients can adopt it without turning every decision into a board paper.

• Name the decision-makers. Record who can approve what, including value thresholds and a named deputy. Keep it to one page and share it with the supplier. If a project manager can approve changes up to a stated sum, say so. If a commercial lead must approve anything affecting the programme, say that too.
• Record cost and time before the yes. Require a simple change note: what is changing, why, the price effect, the programme effect, and any risk to other deliverables. If the answer is 'no cost, no time impact', record that as well. The discipline takes minutes; the absence of it can take months to resolve.
• State acceptance criteria. Define what completion looks like and what evidence will be accepted. A deliverable might be a signed test sheet, a drawing at a specified revision, or a written confirmation that training has been delivered. 'Fine' should never be the test.
• Use one approval channel. Chat is for coordination, not authority. Set a single route for approvals, such as a named email subject line or a shared approval register. A valid reply should include the approver's name, the date, the scope of the approval, and the cost and time effect. Anything less is a comment to be confirmed, not a decision to be relied on.
• Close the loop. Once approved, update the change log, the scope baseline and the payment schedule where relevant. Tell finance. An approval that is not reflected in the project records is only half an approval.

When the informal yes has already happened

Most organisations will find that some decisions have already been made in chat or email. The practical response is not to pretend the record is complete. It is to reconstruct it quickly and honestly. Issue a short ratification note that sets out what was understood, by whom, at what cost and on what date. Ask the appropriate authority to confirm or reject it. That note may expose a gap, but it is better to expose it while the project can still respond than to discover it during a final account negotiation.

Speed with memory

The strongest commercial teams are not the ones that avoid informal conversation. They are the ones that know where conversation ends and authority begins. They keep approvals fast by making the required information small and familiar: a name, a number, a date, a definition of done. That is not bureaucracy. It is commercial memory.

In 2026, UK projects are too interconnected, and too expensive, to rely on 'looks fine to me'. A casual yes can still be a useful start. It should never be the whole record.