Insights/Variations and site change

The Friday afternoon problem

A verbal instruction on a blocked programme can get the work moving quickly. The problem comes when the written record never follows. Here's what can get lost, and what to capture before everyone leaves site for the weekend.

Portrait of Arez Sajeel, Director & CTO at Sterling Origin and Lead Developer of LedgerCaptureArez SajeelDirector & CTO | Lead Developer

Posted 2 October 2026·Updated 2 October 2026

A construction worker in a high-visibility jacket and hard hat taking notes on a busy site, overlaid with the LedgerCapture logo.

It is late on a Friday. The programme is tight, a trade is in the way, and someone with authority says the thing everyone has heard before: move it, we'll sort the paperwork on Monday.

The crew faces an awkward choice. Push back for a formal instruction and risk holding things up, or get on with the work and hope the paperwork catches up later.

The work usually gets done. The record often does not.

Why it keeps happening

Programme pressure is real. On a busy site, getting the work moving can feel more important than stopping to document every change.

Then Monday comes.

Other trades are in. The area has changed. The person who gave the instruction is dealing with something else. The details are harder to remember, and the photos that would have made the situation obvious were never taken.

That is the Friday afternoon problem: the gap between what happened on site and what the commercial team can evidence later.

What gets lost

Without a clear site record, you can end up trying to explain a straightforward change weeks or months after it happened.

You may have:

  • No clear description of what changed and why
  • No photographs showing the area before or during the work
  • No record of who gave the instruction
  • No acknowledgement while everyone still agreed on what had happened
  • A final account discussion where "we were told to do it" meets "there's nothing on file"

That does not necessarily mean the work cannot be valued or recovered. It does mean the position can be harder to substantiate.

On a sizeable package, several small undocumented changes can add up. The issue is not always the work itself. It is the lack of evidence around the work.

What helps before people leave

You do not need a long form in the rain. You need enough to show what happened:

  • Capture it while it is visible - a short description, quantities where you can, and photographs of the area and the work.
  • Name the instruction - record who asked for the change and what they asked for, in plain language.
  • Get an acknowledgement while the context is fresh - that could be a signature, a site record, or whatever review route the project uses.
  • Give the office a complete record - one clear record with the relevant photos and information attached is much easier to use later than a string of messages nobody can piece together.

A practical habit

Treat "we'll sort it Monday" as a trigger, not a promise.

If the change affects programme, scope or cost, capture a basic record before the site empties.

Monday can then be about dealing with the variation, valuation or commercial follow-up.

It does not have to be about working out what happened on Friday.

That is where a simple site recording habit makes a difference. The aim is not more paperwork for the sake of it. It is making sure the important facts are recorded while the people, work and instructions are still easy to identify.

LedgerCapture is built around that habit: quick capture on site, acknowledgement while the details are fresh, and a clear record for the office when variations, payment and commercial discussions come around.

If "we'll sort it Monday" sounds familiar on your projects, View packages or Contact to talk through whether LedgerCapture fits how your team works.

LedgerCapture is published by STERLING ORIGIN LIMITED, registered in Scotland (SC890658).