FROM THE POST THAT GOT 200K VIEWS

Eight Operatives. Full Shift.
Four Hours Doing Nothing.

Standing time costs UK contractors millions. Not because it happens, but because nobody records it properly.

The concrete didn't arrive. The access road was blocked. The design information wasn't issued. But the evidence? Gone before the QS ever saw it.

Book a Consultation
Costain Balfour Beatty Murphy Amey Kilnbridge Circet

Six Ways Standing Time Evidence Dies Before the QS Sees It

Standing time isn't a compensation event. It's the cost consequence of one. But that cost disappears when the evidence falls apart.

1
It Gets Buried in Payroll

Supervisors redistribute idle hours into productive time because they think it affects pay. The allocation sheet looks clean. The standing time never existed.

2
The Diary Entry Says Nothing Useful

"Delayed due to third party." Which one? How many operatives? For how long? A vague entry is the same as no entry when it reaches the PM.

3
Nobody Links It to a Cause

Four hours waiting for design information doesn't feel like an event. It feels like a normal Tuesday. Nobody connects it to the instruction or access issue that caused it.

4
Cumulative Fragments Never Get Joined Up

Two hours here. Ninety minutes there. Each fragment sits in a separate diary entry. Nobody spots the pattern. Nobody totals it up.

5
The Eight-Week Clock Runs Out

Clause 61.3 gives you eight weeks to notify. Standing time accumulates slowly. By the time anyone spots the pattern, the window has closed.

6
Your Own Records Contradict You

The diary says "gang stood down 3 hours." The allocation sheet shows them productive all shift. The PM uses that contradiction to challenge the entire claim.

Your people were on site. Your equipment was running. You deserve to be paid. But only if you can prove it.

The Cost Nobody Counts

40%
of legitimate CEs go unnotified

£50M Option C contract. 3% in variations. That's £1.5M in compensation events.

40% go unnotified. That's £600,000 left on the table. Per project. Quantum you've already earned, sitting in diaries nobody's reading commercially.

Three live projects? Five? Do the maths.

What Gather Does Differently

Late access (60.1(2)). Scope changes (60.1(1)). Late design info (60.1(3)). Weather (60.1(13)). Gather's AI maps standing time to the specific clause that triggers recovery. No other tool does clause-level alignment.

Structured Capture at Point of Entry

Resources. Duration. Location. Cause. Four structured fields in the existing diary flow. No separate form. No free text.

Automatic Cause Linking

The AI matches standing time to the instruction, design change, or access issue that caused it. The connection a QS makes manually in an hour happens automatically.

NEC4 Clause-Level Alignment

Each event maps to a specific clause, 60.1(1) through 60.1(19). Standing time arrives on the QS dashboard already categorised with clause references attached.

Records That Survive Scrutiny

Date, time, location, resources, cause, mitigation, notices, photos. All linked to the programme activity. Records built to withstand a PM assessment, not a retrospective reconstruction three months later.

The Five-Minute Fix

Here's what a five-minute entry at end of shift looks like inside Gather.

1
Supervisor Records Standing Time

Open the app. Select "standing time." Allocate resources, hours, cause, and a photo. Faster than writing a text.

2
AI Connects It to the Contract

The QS AI Agent links standing time to existing CEs, identifies the NEC4 clause, and checks the notification timeline. By morning, the commercial team has a flagged item.

3
QS Reviews a Complete Position

All standing time linked to this CE, total hours, cost impact, notification status. One consolidated view. Ready to submit.

Cost recovery and time impact. Site to commercial dashboard instantly.

Costain Balfour Beatty Murphy Amey Kilnbridge Circet
Nick Mansell

"Using Gather, we were able to slash 11% of total project cost on the TfL 4LM project. The platform saved us at least 100 hours on providing assurance documents alone. I was so impressed, I decided to invest in Gather."

Nick Mansell, Senior Project Manager, Transport for London

Stop Losing Money You've Already Earned

Your teams are already recording standing time. Just not in a way that survives a PM assessment.

15 minutes. Your contract type. No slides.

Book a Consultation

No commitment. No follow-up calls unless you ask.

Questions We Get Asked

Yes. The mobile app takes five minutes per shift and works offline with voice-to-text entry. Site supervisors capture records faster than paper diaries, especially in poor weather. We designed it for people wearing gloves in the rain, not people sitting at desks. Adoption rates exceed 90% within the first month.
Most teams are capturing records within two weeks. We configure your contract type, import your programme and WBS, and train your site teams. Complex enterprise rollouts with multiple integrations typically take four to six weeks.
Yes. Construction Cloud, Microsoft 365, and Power BI. Records and evidence flow directly into your contract management system.
Three things. First, we're built by quantity surveyors who understand NEC4, JCT, and FIDIC contracts natively, not bolted on. Second, our QS AI Agent identifies 40% more compensation events than manual review. Third, we take responsibility for adoption, training your supply chain directly so your team doesn't become tech support.
Pricing is based on the value of works Gather manages, not the number of users. Your whole team gets access without per-seat charges.

Indicative annual subscriptions:
Up to £10m/year: £12,000 subscription, £2,000 setup
£10m to £50m/year: £40,000 subscription, £7,000 setup
£50m to £100m/year: £55,000 subscription, £10,000 setup
Over £100m/year: From £70,000 subscription, £12,000 setup

Training is £1,400 per day on site or £450 per session online.

Final pricing depends on project count, estimated users, disciplines, and supply chain integration. Book a demo and we'll quote for your specific situation.