What actually gets disputed​

On small UK housebuilding and contracting jobs, the same themes repeat:

• Unsigned or unclear variations — "I thought that was included."
• Instruction vs variation — client-directed change never formally priced.
• Programme impact — delay costs argued without a contemporaneous record.
• Retention and defects — snags conflated with disputed variations.

None of this requires a six-figure software rollout to improve. It requires habit and a single job record.

Document from day one​

1. Log client instructions when they happen​

Whether by email, portal, or site meeting note: capture what changed, when, and who instructed it. Tie it to the job—not a personal inbox.

2. Price variations before work proceeds where possible​

Your contract terms may require this. Even when they do not, pricing early surfaces disagreement when you can still negotiate—not at handover.

3. Keep a running contract forecast​

Approved additions and omissions should update the live forecast. At final account, you are reconciling a number you have both been watching—not surprising each other.

4. Use photos and diary entries as supporting evidence​

Site diary entries with dated photos back up programme and scope arguments. They are not a substitute for signed approvals, but they fill gaps when memory fades.

Where software helps (and where it does not)​

Software cannot fix a bad contract. It can stop good jobs going bad because details lived in WhatsApp.

SiteHut keeps instructions, CVIs, and variations on a live register with contract forecast and optional approval workflows aligned to your quote terms. See how we approach this on the homepage FAQ.

For a deeper product walkthrough:

• Variations in SiteHut
• RFIs and project communication
• Snagging and handover

When spreadsheets are still enough​

If you run one job at a time, variations are rare, and everyone is in the same van at 7am—you may not need change yet. When you add a second active job or external clients who email instead of visiting site, that is usually when the "search party" through threads starts costing real money.

This article is general industry guidance, not legal advice. Rhodri has spent 35+ years in UK contracting and housebuilding; Andrew built SiteHut to encode those workflows in software.

Why spreadsheets break down​

Spreadsheets work until they do not. The usual failure points:

1. Version drift — two people update different copies of the same register.
2. Lost context — the WhatsApp photo that "approved" a change is three screens above the message you need at final account.
3. No running forecast — variations live in a tab that nobody updates until month-end.

A minimum viable variation register​

Whether you use SiteHut or a spreadsheet today, every job benefits from the same fields:

Rhodri has seen too many final accounts turn into arguments because step five was "someone said yes on site" with no record.

Moving off pure spreadsheets​

When you are ready for software, look for:

• Job-scoped records — variations live on the job, not in a shared drive folder.
• Client sign-off without extra seats — secure links or a portal view for that job only.
• Live contract forecast — approved variations update the running total automatically.

SiteHut handles this on the job timeline alongside programme and invoicing. If you are still comparing approaches, see our honest take on SiteHut vs spreadsheets and WhatsApp.

Learn more in the docs​

• Variations guide
• Quotes and contracts
• Getting started

Andrew builds SiteHut; Rhodri brings 35+ years of UK construction commercial experience to how we design variation workflows.

The Core Problem​

Most builders are stuck using spreadsheets that break, or legacy software that takes six months to learn. We realized there was a massive gap for something fast, modern, and built specifically for the workflows of housebuilders.

What's Next?​

We'll be posting weekly updates here on our engineering progress, new features, and tips for managing your trades and projects more effectively. Stay tuned!