Friday, Written Down: A Five-Point Client Update That Keeps Disputes Off the Critical Path

Most arguments on a UK trade project do not begin on site. They begin in the space between what one party believes was agreed and what the other believes was merely mentioned. That space widens quietly during the week and is at its widest on a Friday afternoon, when the client is thinking about the weekend, the site manager is thinking about next week's labour, and nobody has written anything down.

A five-line email, sent every Friday, closes most of that gap. It is not a report. It is not a newsletter. It is a short, factual record that protects the programme, the relationship and, in due course, the invoice.

Why Friday, and why five lines

Friday works because the week is still fresh and the following week is still changeable. A note written on Monday describes a week that has already begun; a note written on Friday describes a week that has finished and a week that can still be adjusted. It also lands before the client's own week ends, which means a decision requested on Friday has a reasonable chance of being made before Monday.

Five lines works because it is sustainable. A weekly update that runs to three pages will be abandoned by the third week. A weekly update that fits on one screen will still be going in March. Consistency matters more than detail: a thin record every week is worth more than a thorough record once a quarter, particularly if the matter later reaches an adjudicator or a county court.

The template

Save the following in your drafts folder and adapt it per project. Five headings, no more.

1. Work completed this week. Plain description, no adjectives. "First fix electrical to plots 4–9 completed and tested" is enough. If a client asks for more detail later, this line is the anchor.

2. Next steps. What you intend to do next week, and where. This is the line that demonstrates forward planning and gives the client a chance to intervene before you have committed labour.

3. Client actions required. Named person, specific action, specific date. Not "client to confirm selections" but "Client to confirm kitchen tile choice to us by Wednesday 18 November so the tiler can start on the 23rd." A date turns a request into a record.

4. Risks, changes or decisions. Anything that has changed since last week: a late delivery, a design query, a site access restriction, a verbal instruction that needs confirming. Flag it here even if it feels minor, because minor items have a habit of becoming the argument six weeks later.

5. Cost and timing implications. This line is the one firms leave out, and it is the one that matters most. If there is no cost or timing impact, say so explicitly: "No change to the agreed price or completion date." Silence on this point is where disputes breed, because silence can later be read as agreement, or as concealment, depending on who is doing the reading.

Tone: factual, not editorial

The update should read as though it was written by someone who wants the job to go well. That means neutral language and no invitations to argue. Avoid "unfortunately", "as you will appreciate", "we are still waiting for", and "just to clarify". Each of these signals frustration and invites a reply in the same register.

Instead, state position and consequence. "Delivery of the steel lintels has moved to 24 November. This puts the blockwork start back by three working days. We will confirm the revised completion date once the delivery is on site." There is nothing to argue with in that sentence, and nothing has been conceded.

Do not apologise for delays that are not yours. Do not editorialise about the client's architect. Keep the register flat and the facts straight, and the client will match it.

Evidence: keep it tidy and keep it together

A weekly note is only as useful as the material behind it. Photograph progress on the same day each week, with the date visible. Keep delivery notes, signed site instructions and variation confirmations in a single folder per project, named by date. Where a verbal instruction is given, write it into line 4 the same day and ask for confirmation by reply.

Send the update to a named individual, copy whoever holds the purse strings, and quote the purchase order or contract reference in the subject line. A standard subject format — project name, week ending date — makes the thread searchable months later, when someone asks what was agreed in October.

What it does for cashflow

An application for payment is far harder to challenge when it is preceded by twelve Friday notes that each flagged the work, the change and the cost. The client who says "I never knew that was extra" has to explain why they did not reply to the line that said so, in writing, with a date attached.

If matters do escalate, the chronology writes itself. A solicitor or adjudicator reading twelve consecutive weekly updates has a clear picture of what happened and when. That is considerably cheaper than reconstructing events from memory and site diaries, and it often shortens the argument before it becomes a formal dispute.

When the client pushes back

Some clients will reply at length, or at nine in the evening, or both. Keep the response short: acknowledge, restate lines 4 and 5, and offer a call. Do not negotiate a variation by email after hours. The Friday note is a record, not a debate, and treating it as one preserves its value.

The habit

Fifteen minutes on a Friday, a saved template, a standard subject line and a folder per project. That is the whole system. Firms that run it for a few months tend to find that the Friday note becomes the first thing a client reads, and the last thing anyone needs to argue about.