How to use site documentation to win legal disputes

Disputes in construction and estate management rarely start with someone shouting in a meeting room. They usually start months earlier when somebody didn’t document something properly.

We’ve seen it again and again in façade inspection work. A developer thinks a defect is “obvious” and should be covered. A contractor says it is “wear and tear.” The MCST gets stuck in the middle. Everyone has opinions, but only one thing consistently wins legal disputes: clean, time-stamped, defensible documentation.

And yes, drones from companies like AerialPS make that a lot easier, but only if you treat drone outputs like evidence, not marketing photos.

Why site documentation wins 

In a dispute, the argument is rarely about what could have happened. It’s about what you can prove happened, when it happened, and whether you followed the required process.

Most documentation fails because it’s missing one of these: clear location context, a consistent inspection method, proof of date and continuity, or proof the inspection was done legally and competently. A folder full of random site photos with no orientation is not “records.” It’s vibes.

A proper façade inspection report, especially one supported with drone imagery from AerialPS, can lock down defect location, extent, and progression. That matters when you’re trying to prove whether cracks propagated after a certain event, whether water ingress was pre-existing, or whether repairs were performed to spec.

Start with the boring part: Compliance and Timelines 

If you manage buildings in Singapore, you already know the Periodic Façade Inspection (PFI) requirement is not optional. Missing a BCA inspection notice can lead to fines of up to S$20,000. That number is painful, but the hidden cost is worse: once timelines slip, everyone starts rushing, shortcuts happen, and your documentation quality collapses right when you need it most.

So when we plan documentation for dispute-proofing, we treat compliance as part of the evidence chain. Keep the notice, keep the schedule, keep the inspection plan, keep the approvals, and keep proof of who did what.

Build an “evidence-ready” façade inspection report

A façade inspection report that stands up under scrutiny is structured, repeatable, and specific. It should not read like a brochure.

We typically anchor it around four pillars: defect mapping, high-resolution visuals, measurement context, and traceable metadata. The goal is simple: if an independent party reads it six months later, they should be able to find the same defect again without guessing.

Include clear reference points, gridlines or façade zones, and annotated defect IDs. If the building has multiple blocks and elevations, label them consistently. You’d be surprised how many disputes devolve into “which wall are we even talking about?”

Also, keep the raw image set. The report is the summary. The raw set is your backup when someone claims the report “cherry-picked” angles.

Thermal façade inspection: Useful, but only if you document conditions properly

Thermal façade inspection can be extremely persuasive in water ingress disputes, insulation issues, or areas with suspected delamination. But thermal imagery is also easy to misinterpret if you don’t document the conditions.

If you want thermal data to help you in a dispute, record the inspection timing, approximate ambient conditions, and the rationale for the method. Thermal anomalies are relative. Morning vs afternoon, wet vs dry surfaces, and sun loading can all change what the camera “sees.”

The practical takeaway is this: thermal should complement visual findings, not replace them. When the thermal result supports the visual defect mapping, it strengthens the story. When it contradicts, you need to explain why, not hide it.

Why drones change the dispute equation (and why competitors avoid the messy parts)

Gondolas and rope access are slower, more expensive, and riskier than drones. That’s not a “drone company” opinion, it’s what you see on site: more manpower, more setup time, higher working-at-height exposure, and limited angles.

But here’s what many vendors won’t say clearly: drones are not automatically faster if you didn’t plan permits, flight paths, and access properly.

Singapore’s no-fly zones continue to expand, catching many clients off guard. And airport-adjacent projects often require additional approvals. If you only discover that after awarding the job, your schedule can slip fast.

Worse, hiring drone companies without the right permits or equipment can delay projects by months. That is not hypothetical. If an operator turns up and then realises the airspace constraints, the building geometry, or the required standoff distances make the planned capture impossible, you don’t just lose time. You lose continuity, and continuity is what makes documentation defensible.

Inspection planning and permit requirements 

When documentation is meant to support legal or contractual positions, we plan like we’re going to be questioned later, because you might be.

At minimum, keep records of:

• The inspection plan and method statement (what areas, what resolution targets, what angles)
• The flight logs and date/time of capture
• The operator and platform details used (so capability is clear)
• Any airspace approvals, especially near controlled or sensitive areas

This is also where CPs and PMs can protect themselves. If you can show you appointed a compliant operator and allowed enough lead time for approvals, it becomes much harder for a counterparty to claim you were negligent or reckless in planning.

Make your documentation hard to attack

If you want documentation that survives disputes, aim for consistency over cleverness. Use the same vantage logic each cycle so you can show progression. Record what you could not access and why. If a section is blocked by ongoing works, document it. Silence looks like omission.

Either way, the point is not to create perfect records. It’s to create records that are honest, repeatable, and legally usable.

The simple rule

Most disputes are not won by the person who talks the best. They’re won by the person who can calmly point to a timestamped record and say, “This is what was there, this is when we saw it, and this is the method we used.”

If you’re managing Periodic Façade Inspection (BCA), planning a thermal façade inspection, or trying to avoid the usual delays around drone regulations and approvals, we can help you set up the inspection workflow so the documentation does its job when it matters most.