The variation nobody logged
A change gets agreed standing in a stairwell. By the time it reaches the QS there is no record of who asked for it, so it lands as a goodwill gesture instead of a priced variation.
The Source of Truth engine
Site Sidekick keeps one record of what your project agreed, built from site visits, documents and the day's back-and-forth. Every sentence carries a citation back to its source, so a variation gets settled with evidence instead of memory.
Start free · No card required · iOS, Android and web
What a fuzzy record costs
Nobody on a live job has time to minute a corridor conversation. So the record gets assembled months later, from memory, by the person with the most to lose.
A change gets agreed standing in a stairwell. By the time it reaches the QS there is no record of who asked for it, so it lands as a goodwill gesture instead of a priced variation.
You know a late client decision cost you nine working days. Proving it means trawling six months of WhatsApp, email and half-remembered meetings — usually while the claim window closes.
Two people gave two answers. Only one reached the subcontractor. Nobody notices until the work is in, and the rework comes out of your margin.
The engine
A structured, cited record you could hand to a client, a QS or a solicitor, plus a short list of questions that need a human answer.
01 — Source of Truth
Upload your Scope of Works and it becomes the spine of the record: every claim files under the work it belongs to, plus standing sections for the things that always matter — timeline, variations, budget, site conditions, compliance.
Partitions to Level 2 are metal stud with 30-minute fire rating.
Scope of Works · row 42Second-floor partitions are to be upgraded to a 60-minute fire rating.
Site walk · 12 Mar · 14:32 · DaveThe upgrade was accepted by the client and priced as a variation.
Open Question resolved · Priya · 13 Mar02 — Cited Search
“When did the client approve the substitution?” comes back as a plain answer with the evidence attached — the recording, the timestamp, the person, the document row. Open any citation and you land on the source itself.
The 60-minute partition upgrade was raised on the Level 2 site walk on 12 March and accepted by Priya (Client PM) the following day.
Every sentence above resolves to a source you can open. Anything that didn't resolve was never shown.
03 — Open Questions
When a site conversation cuts against the scope, or two inputs disagree, nothing gets guessed. The conflict is raised as a decision for a person, answerable in one click from the office or the van.
The drawing register shows revision C; the RFI response references revision B. Which is current?
Who is supplying the ironmongery — main contract or client direct?
Shaft works held until lift schedule sign-off.
Resolved by Priya · 19 Mar · logged to Timeline & Delays
How it works
01
Hit record on the way round site. It keeps running with the screen off and the phone in your pocket, then uploads when you have signal.
02
Scopes, drawings, RFIs, specifications, site photos, notes and the project's team chat. PDF, DOCX, XLSX, CSV — all of it becomes citable source.
03
Diarised transcription separates the voices and names them. Claims are extracted input by input, then organised into the framework your Scope of Works defines.
04
Contradictions surface as one-click decisions. Every resolution is stamped with who decided, when, and what they decided — and files itself into the record.
The guarantee
If it isn't cited, it doesn't get shown.
A summary is where fabrication hides, so nothing here rests on one. The engine is never allowed to name its own source: citations are derived in code from the claim's reference, then checked by a separate verifier against the raw source text.
Anything that doesn't resolve to a real source is dropped — not hedged, not reworded. And if a conclusion would require joining two documents together, that is not a claim. It becomes an Open Question for a person to answer.
It is deliberately conservative. The record comes out shorter, and every line of it will survive being read back to you across a table.
At scale
Three people or three hundred, the record has to hold the same shape — and it has to stay defensible long after the people who made it have moved on to the next job.
Roles that match a site
Admin, Collaborator, Submitter and Viewer. Submitters can record and upload but read nothing back — the right shape for subcontractors and suppliers who should contribute without seeing the commercial picture.
Immutable inputs
Transcripts and extracted document text are append-only, and citations pin to character spans within them. Nothing in the source can be quietly rewritten underneath a claim that cites it.
Append-only audit trail
Decisions, Variations and Communications are extracted once at ingestion and never re-derived. Resolving an Open Question writes an attributed, timestamped artefact into the trail.
Speaker attribution
Diarisation separates the voices on a recording and names them from how people introduce themselves. Enrol a voice once and it is recognised across the project.
Your Scope of Works is the spine
Upload the SOW spreadsheet and it becomes the section framework of the record. Scope rows become the baseline, and a later value that contradicts one always raises a confirm-the-change question.
Off the record, by design
Private and direct conversations are deliberately excluded from the engine. Only the project's open channel is on the record, so people can still speak freely.
Capture that survives the site
Background recording on iOS and Android. Photo batches upload in chunks and retry when signal returns. A dropped connection halfway up a scaffold does not lose the walk.
No waiting around
Transcription and extraction run as background pipelines with retries and a watchdog. A two-hour site walk processes while the team gets on with the job.
Beyond construction
We built this where an undocumented decision costs the most money. But nothing in the engine is construction-specific — underneath, it is a citation-disciplined record of what a project's people actually committed to. Any field where a conversation quietly becomes an obligation has the same problem, and usually the same broken fix: a paper trail assembled after the fact, from memory, under pressure.
Pricing
Whoever starts the job pays for it. Everyone else — your subbies, the client, the architect — joins free, on every plan, forever. Start on one project and move up when the record is doing enough work to be worth paying for.
Free
Free
One project, to see whether the record earns its keep.
Solo
£19/month
For a sole trader or small crew running a few jobs at once.
Trade
£49/month
The working tier for a contractor with jobs on the go.
Business
£99/month
For principal contractors and multi-site programmes.
A job is one project in the app — one site, one client, one job number. Your plan limits how many you have running at once, not how many you do in a year. Finish one, start the next; only live jobs count.
They do. Whoever started the job carries it, and everything uploaded to it comes out of their storage — including your photos and recordings.
It works the other way round too. On your jobs, you carry the storage for everyone you've invited. That's the trade: you pay for your own jobs and nothing else.
Because it would break the thing you're paying for. If adding the plasterer to a job costs you another monthly fee, you won't add them — and then their side of the story never makes it into the record.
The whole point is one account of what was said and agreed, with everyone in it. Charging by the head works against that, so we don't.
New photos, videos and documents pause until you free some space or move up a plan. Recordings keep working — a storage limit should never be the reason a conversation on site went unrecorded.
Nothing you've already uploaded is deleted or hidden, and you can see exactly what's using the space in your settings.
Your record stays yours. We don't delete finished jobs and we don't hold your evidence back — a paper trail that vanishes with a plan change would be worth nothing.
Record one site walk this week. If the record it builds is wrong, you will know within a day — and if it is right, you already have the evidence for the first variation of the job.
Start free · No card required · Cancel any time