Site capture

The site diary works when it works for everyone.

Most site diaries fail for the same reason: they only ever take. The foreman fills in a form, the information goes upstream, and nothing comes back. Make it a two-way system — give him something genuinely useful every morning — and he keeps it maintained. That discipline compounds all the way up.

The environment is hostile to writing anything down.

A foreman is moving between three areas of a site, in and out of a van, PPE on, rain coming sideways. He notices the ground is softer than expected, makes a call, adjusts the sequence, keeps things moving. He has done his job.

At the end of the day he is supposed to log it. He knows it matters. But he is tired and driving home, and by the time he gets to it — if he gets to it — he is reconstructing something that happened eight hours ago from memory. The specific detail, the judgement he made in the moment, the reason he changed the sequence: that texture is gone. What gets written down is a summary of a summary.

It is not a discipline problem. It is a design problem — and the fix is not to ask harder.

Voice note in. Morning brief out.

Thirty seconds in his own words, while it is still fresh. He checks the summary, corrects anything wrong, and approves it before it goes anywhere. In return, the brief is waiting before he sets foot on site. No new app, no login — just WhatsApp, the way he already uses it.

07:30 — before he is on site

Cuprix Huddersfield · Neil Crossley
  1. Morning Neil. Huddersfield briefing:

    • Raft pour still on for next week — sand shortfall being chased
    • Adam needs the block count on the west gable by end of day
    • Pedestrian markings at the gate flagged yesterday — re-mark before pour traffic
    • Dry until 14:00, rain expected late afternoon
    07:30
  2. Is the pump coming in the main gate or round the back?

    07:36
  3. Round the back, same as the ready-mix. Ring the office if there is an issue getting in.

    07:37

07:52 — as it happens

Cuprix Huddersfield · Neil Crossley
  1. 0:38 Voice note, 0:38

    07:52
  2. Three things off that one — a short delivery, a near miss and a risk to the pour. Logged against Huddersfield.

    07:52

    ConfirmRevise

  3. Confirm

    07:53

18:00 — he approves it before anyone upstream sees it

Cuprix Huddersfield · Neil Crossley
  1. Evening Neil. Here is what I picked up today:

    • Sand delivery 2t short of the 6t ordered — remainder due Thursday
    • Near miss at the gate, reversing dumper, markings worn away
    • Resupply needed before next week’s pour
    • West gable block count logged
    18:00
  2. Anything to add or change before this goes up?

    18:00
  3. Markings are done, I did them after dinner break

    18:04
  4. Updated: pedestrian route at the gate re-marked and photographed. Does that look right?

    18:05
  5. That’s it

    18:05
  6. ✓ Sent up to Adam. Good work today Neil.

    18:05

Nothing goes upstream that the person who was there has not confirmed. That is what makes the record worth anything later.

Run it for a few months and something accumulates.

Not just a record of today — a searchable account of what has actually happened across every job, each entry approved by the person who was standing there. This is one week of one demonstration project:

  • Sites running5
  • Operatives on site70
  • Captures in a week5 Each one thirty seconds to a minute and a half, spoken on the move.
  • Records they produced23 One row per atomic fact, each with its own category — not one blob per note.
  • Forms anyone filled in0

Ask the system what is happening.

A director should not have to chase a contracts manager who chases a foreman to find out what happened on a job last week. The information is already there — it just needs somewhere to go.

Cuprix All sites · Graham Whitmore
  1. Any ground condition issues flagged across sites this week?

    09:14
  2. Two, on one site:

    • Wakefield — eastern edge running wet, will not hold a batter. Logged Friday by Barry.
    • Same site — no response from the drainage authority in five weeks, so the excavation phase cannot close.
    09:14
  3. Monday’s progress meeting decided to re-profile the eastern edge rather than sheet-pile it, and to off-hire the 20T excavator on Friday regardless. Adam is re-pricing it for the 26th.

    09:14

That answer crosses two things that used to live apart: what came off site, and what a meeting decided about it.

The same loop, on a real phone.

Recorded · Instagram Information gets lost between the site and the office every day No new app, no new login. Voice notes and photos get transcribed, structured, and routed upstream once they are confirmed.

Two ways to go from here.

See it working

Walk the project yourself

Five sites, seeded with a week of captures. Open any record and you get the words it came from, and the reasoning that turned them into rows. Nothing you click can break.

Open the workspace

Or talk it through

Bring your own site

If your firm already uses a capture tool, this makes it work better — a foreman who gets a useful morning brief is a foreman who keeps his records up to date. Worth half an hour either way.

Get in touch