A project disputed months later: the proof that stops you giving in

A client calls back six months after handover, about a crack near a window or damp in a basement. The site manager half remembers a minor snag, maybe cleared, maybe not. The photos are on the phone of the fitter who installed the window, who has since left the company. With nothing to prove either way, the company redoes the work at its own cost, to keep the relationship from souring.

The short answer: a construction dispute is won or lost on proof, almost never on the law. The useful answer is what a case file needs to contain, and when to build it.

What loses a dispute, and it isn't the law#

In most disputes raised months after a project ends, the company is not actually in the wrong. It loses because it has nothing to show:

• a snag was flagged verbally, never written down or dated;
• a photo of the surface before work exists, but nobody knows where;
• the handover report was signed, but on a pad left in the van;
• the material installed is not recorded anywhere, while the client blames a different one.

Faced with a client who states their case with confidence, a company that hesitates about its own facts almost always gives in. The goodwill gesture costs less than a dispute it senses it cannot back up.

What a proof file needs to contain, project by project#

Four pieces cover most disputes, provided they exist at the right moment, not reconstructed afterwards.

None of these pieces needs to be elaborate. A time-stamped photo and two lines of text are enough. What matters is that they are taken at the right moment, and that someone knows where to find them six months later.

A worked example#

Take a renovation company of under ten people, running around fifteen projects a year. Suppose one client in eight comes back with a dispute within a year of handover, and half of those get settled with a free fix or a discount, for lack of enough proof to discuss them. These are hypotheses, to adjust with your own figures.

This figure only counts the goodwill gesture itself. It does not count the time spent hunting for a photo that cannot be found, nor the owner's time spent on a case they cannot back up.

What changes with an application built for the company#

When every piece is attached to the project the moment it happens, the case file already exists the day a client calls back.

• A photo taken on site attaches to the project open that day, with its date and author, with no folder to pick.
• The handover report gets signed on site, from a tablet, and stays retrievable months later.
• Clearing a snag is photographed in the same place as the snag itself: the two read side by side.
• The day a dispute arrives, the site manager opens the project and finds the photo they need and the signed handover report in the same place, with no one to call.

What not to do#

Do not wait for a dispute to arrive to realise everything should have been kept: by then, it is too late to take the missing photo. And do not confuse a snag mentioned verbally with a written one: only the written one counts the day a client disputes it.

Construction disputes: the key takeaways#

An end-of-project dispute is almost never lost on the law: it is lost because the proof was not captured at the right moment, or can no longer be found. Fixing that costs nothing more than what the project already demanded: a photo before work, a written snag, a signed handover report.

The habit to start on the next project: name a follow-up and a clearing date for every snag in the handover notes. It is not the whole method, but it already prevents part of the files that get lost for lack of a trace, the same way a project's margin is discovered too late.