Most construction disputes do not begin with one huge mistake.
They usually start with something much smaller.
A conversation that was not written down. A detail that two people understood differently. A change agreed quickly on site. Work that was covered before anyone recorded what was underneath.
Weeks later, the people involved remember the same moment in different ways.
That is where tension starts.
I’m Stuart Deadman, a Norfolk-based construction leader and entrepreneur. One of the simplest lessons I have learned is that clear records protect everyone involved in a build.
Photos are a big part of that. But the real principle is wider:
Record important information while it is clear, not after it becomes a problem.
Most people associate construction photography with marketing.
Finished kitchens. Completed extensions. Before-and-after images. Drone shots showing how far a development has come.
Those photographs are useful, but some of the most valuable images on a build are never shared publicly.
They show:
These photographs are not glamorous. They are evidence.
They give the project team something objective to return to if a question arises later.
Construction projects contain hundreds of conversations.
Some happen in formal meetings. Others happen quickly on site, on the phone or while walking through a room.
People are busy. Circumstances change. Several weeks may pass before a decision becomes relevant again.
Relying on memory creates risk because two honest people can remember the same conversation differently.
One may remember a change as approved. The other may remember it as an idea that still needed pricing.
One may believe a finish was accepted. The other may think they were only shown a sample.
That does not automatically mean anyone is being dishonest. It means the information was never closed down properly.
A short written record can prevent that.
A useful rule on any build is:
If it is going to be hidden, record it before it is covered.
Once a wall is boarded, a floor is poured or landscaping is completed, confirming what sits underneath becomes much harder.
That can create problems during later maintenance, future alterations or questions over workmanship.
A hidden-work photo should make sense to someone who was not standing beside the photographer.
That usually means capturing:
A random close-up of a pipe or cable may mean very little six months later. Context is what turns an image into a useful record.
Documentation should begin before the main work starts.
A photographic condition survey records the existing state of the property and any areas affected by access, deliveries or construction activity.
It can include:
This protects the homeowner, contractor and project team.
If damage is discovered later, there is a clear starting point. It becomes easier to establish whether something existed before work began, occurred during the project or is unrelated.
The purpose is not to prepare for an argument. It is to remove one.
Photos can show what happened physically, but they do not always explain why.
That is where a decision log helps.
A decision log can be very simple. It should record:
This is particularly useful for choices involving layouts, finishes, fittings or sequencing.
It also helps prevent decisions from drifting.
A project can lose days or weeks because one choice remained unresolved while different people assumed someone else was dealing with it.
A visible record makes ownership clearer.
Changes are normal in construction.
A client may choose a different finish. An existing building may reveal something unexpected. A design may need adjusting once work begins.
The problem is not the change. The problem is allowing work to proceed before the consequences are understood.
A variation record should explain:
Relevant drawings, photographs or product references should be attached where useful.
This protects the client from unexpected costs and protects the contractor from carrying out additional work without clear approval.
It also gives the team a reliable answer to the question: “How did we get here?”
Documentation becomes less useful when it is scattered across text messages, emails, messaging apps, notebooks and verbal conversations.
A project does not necessarily need complicated software, but it does need a consistent home for important information.
That could be a shared project platform, structured folders or a clearly managed email process.
The system matters less than the discipline behind it.
Everyone should know where to find:
When the latest information is easy to find, fewer people work from outdated assumptions.
Documentation should not only appear when something goes wrong.
A short weekly update can prevent uncertainty from building in the first place.
A useful update might include:
The update does not need to be long.
Its job is to make the project visible.
Clients should not have to chase for basic information, and project teams should not have to reconstruct the previous week from memory.
A dependable rhythm creates confidence.
People often think records only matter when a dispute has already started.
In reality, documentation can improve the way a project runs long before that point.
When decisions are recorded, people tend to make them more carefully.
When work is photographed, teams are more likely to check it before covering it.
When variations require approval, vague conversations become clearer.
When ownership is visible, unresolved tasks are harder to ignore.
The record is useful, but the discipline it creates is even more valuable.
There is a balance.
Recording every minor conversation can create noise and make the important information harder to find.
The aim is not to document every movement on site. It is to capture information that could affect:
A good system is simple enough to be used consistently.
If it takes too long or nobody understands it, people will stop following it when the project becomes busy—which is exactly when it is needed most.
Before work begins:
During the build:
Before handover:
None of this is particularly complicated.
That is the point.
A build is a major investment, and it often involves months of decisions, disruption and financial pressure.
Even good relationships can become strained when people feel uncertain.
Clear documentation removes some of that uncertainty.
It gives clients confidence that work is being managed properly. It gives contractors evidence of what was completed and approved. It helps designers, trades and project managers work from the same information.
Most importantly, it moves difficult conversations away from memory and emotion and back towards facts.
Photos cannot guarantee that a project will never encounter a problem.
They can, however, make problems easier to understand, resolve and learn from.
That can save far more than the build itself.
It can save the relationship around it.
Continue exploring:
The Last Yard Mindset: How to Keep Moving Without Losing Yourself by Stuart Deadman There are moments in business, endurance and life when looking at the whole journey does more harm than good. The finish feels too far away. The problem looks too big. You start adding tomorrow’s pressure to today’s tiredness, and suddenly even […]
by Stuart Deadman A lot of people talk about community like it’s a marketing layer. A nice story you add when business is going well. I’ve never seen it that way. I’m Stuart Deadman, and for me community is responsibility. If you’re building something — a company, a platform, a reputation — you’ve got a […]
The Suffolk Back Yard Ultra is a simple format (4.167 miles every hour), but it becomes a powerful leadership lens: pacing, composure under fatigue, and repeating the basics when you want shortcuts. This post explains what the event teaches about holding standards under pressure, and how to apply it to teams, projects and decision-making.