by Stuart Deadman
People hear “documentation” and think it’s corporate admin. In reality, it’s one of the most practical ways to keep a project calm.
When a build gets stressful, it’s rarely because somebody woke up wanting an argument. It’s usually because two people remember the same moment differently. A decision was made verbally. A detail was “assumed”. A change was agreed, then forgotten. And suddenly you’ve got a classic he-said-she-said situation, and nobody wins.
I’m Stuart Deadman, and I’ve learned that good documentation doesn’t slow work down. It speeds it up, because it removes uncertainty.
It doesn’t mean endless paperwork. It means capturing a few key things consistently:
That’s it. If you do those four things well, you prevent 90% of the arguments that drain time and energy.
Photos aren’t for social media. They’re for clarity.
They help with:
A simple rule we use: if it’s going to be hidden later, photograph it now.
Projects don’t slip because people are lazy. They slip because decisions drift.
A decision log can be as simple as a running note:
It keeps everyone honest and stops the “we were waiting on you” vs “nobody told me” loop.
Most builds change. That’s normal.
What isn’t normal (but is common) is changing things without writing it down. That’s how budgets drift and relationships sour.
A clean variation process is simple:
Not because we’re being awkward, but because it protects both sides.
You don’t need fancy software. You need consistency:
The goal isn’t to create admin. The goal is to remove grey areas.
You don’t need to be technical. Ask:
If a builder gets defensive about those questions, that’s useful information.
If you want the simple templates we use (weekly update + decision log + variation log), request them via the contact form.
Useful next pages:
