Drone footage as evidence in construction disputes (what stands up and what does not)

This article is written for owner’s representatives, employer’s agents, contract administrators, and the commercial teams in main contractors and developers who deal with disputes when they arise. It is not legal advice. It is operational guidance on what makes the difference between footage that holds up under scrutiny and footage that does not.

The general principle is this. A drone visit produces video and stills. Adjudicators, arbitrators and judges treat that material as evidence if and only if its authenticity, provenance and integrity can be established. The footage is not the evidence. The package around the footage is the evidence. Getting the package right, before the dispute, is the work.

The two types of dispute drone footage gets used in

Programme disputes. A claim under JCT or NEC for an extension of time, a delay damages claim, a contested progress valuation, or a disputed practical completion certificate. The footage is reached for to demonstrate what was actually done by what date. The contested question is the state of the works on a specific date. The footage is the answer if it can be relied on.

Condition disputes. A defects claim, a claim arising from damage to adjacent property, a claim relating to site condition before or after a specific event (a storm, a flood, a strike, an act of God), or a contested handover snagging list. The contested question is the physical state of a specific element of the works. Footage from the relevant date is the answer if it can be located, dated, and verified.

In both types of dispute the same evidential standard applies. The footage must be capable of being trusted by a third party who has every reason to test it. The third party will be a competent expert, often a chartered surveyor or a forensic engineer, instructed by the opposing side. Their job is to find reasons to dismiss the footage. Anticipate that.

What makes footage admissible

Five things, in order of importance.

1. Date and time. Embedded, not overlaid.

The date the footage was captured needs to be embedded in the file metadata, not painted onto the frame in post. Embedded metadata sits in the file’s EXIF or XMP block, written by the camera at the moment of capture, immutable without specialist forensic tools that leave a detectable signature.

Date overlays added in post can be created retrospectively. Adjudicators know this. A frame burn that says “12 March 2026” in the corner is not, on its own, evidence that the footage was captured on that date. The metadata behind the file is.

The first thing a competent expert will do with contested footage is open the file and inspect the metadata. If the embedded capture date matches the claimed date, the footage clears the first hurdle. If it does not, the footage is treated with extreme caution from that point on.

Frame burns are still useful. They make the date readable on the screen during a hearing without forcing the tribunal to inspect metadata. The frame burn is the user-friendly presentation. The metadata is the proof.

2. GPS coordinates. Embedded.

The same principle applies to location. The GPS coordinates of every shot should be embedded in the file metadata. A drone with a working GPS module writes positional data to the file at the moment of capture. The metadata establishes that the shot was taken from the place it claims to have been taken from.

This matters in two specific scenarios. The first, in a programme dispute, is when the contested question is the state of a specific elevation of the works. Embedded GPS confirms that the shot is of the elevation in question, not a different one that happens to look similar in a still. The second, in a condition dispute, is when the contested question is whether a specific defect was visible from the position the footage was taken from. The embedded GPS lets the expert reconstruct the geometry.

3. Chain of custody. Documented.

The chain of custody is the documented record of who held the footage, when, and what they did with it. From the moment the file leaves the drone’s memory card to the moment it is presented in evidence, the chain should be unbroken and documented.

A workable chain of custody for a monthly aerial monitoring programme:

• The pilot downloads the SD card on the day of the flight, into a named project folder on a UK-resident cloud storage account. The download log is timestamped automatically by the cloud provider.
• The original raw files are retained, untouched, in a “raw” subfolder.
• Working copies are made into an “edit” subfolder. All editing is done on the working copies. The raw files are never overwritten.
• The delivered files (stills, edited video) are exported into a “delivered” subfolder, with a date-stamped delivery log issued to the client.
• Every access to the files is logged by the cloud provider’s audit trail.
• On request, the operator can produce a written chain-of-custody statement listing every file’s path from capture to delivery.

This is the procedure that survives the question “how do you know this is the file you captured on the day”. The answer is “because the raw file is in the cloud, untouched, with a download log that puts it there on the date of the flight, and the audit trail shows no access to it between then and now”.

Operators that do not run this procedure cannot produce the statement. Their footage is admissible only on the operator’s word, which a competent opposing expert will challenge.

4. Operator authorisation. Verified.

The operator’s CAA Operational Authorisation should be verifiable on the public CAA register. The pilot’s GVC reference should be on file. The CAA permission for any restricted airspace flight should be on file with the date of the flight matching the date on the footage.

This matters because evidence obtained unlawfully is treated very differently from evidence obtained lawfully. A drone flight in Central London Restricted Zone airspace without a NATS Non-Standard Flight Permission is unlawful. Footage from that flight, even if the footage itself shows what it claims to show, may be excluded from evidence on the grounds that the operator’s authority to capture it cannot be established. At minimum, the footage will be treated with suspicion. At worst, the party relying on it is exposed to the same enforcement action the operator is exposed to.

If the footage was captured by a properly authorised operator on a lawfully cleared flight, none of this is an issue. If it was captured by an operator who could not produce the authorisation on demand, the evidence is at risk before any other consideration.

5. Original file integrity. Hash-verified.

For high-stakes disputes, the operator should be able to produce a cryptographic hash of every original file at the point of capture. The hash is a fingerprint that confirms the file has not been modified since the hash was generated. If the file presented in evidence produces the same hash, the file is provably unmodified. If the hash differs, the file has been altered.

Hash verification is not standard practice across the industry. It should be on programmes where the contract value is high enough to warrant the discipline. Embassy Gardens, Canary Wharf, large infrastructure schemes. Hashing adds about thirty seconds per file to the post-flight workflow. The protection is significant if a dispute does arise.

What does not stand up

Three patterns that get footage challenged or excluded.

Footage with no embedded metadata. A video file with the metadata stripped, or with a generic capture date that does not match the claimed flight date, fails the first test. This happens when footage is exported through a video editing programme that strips metadata by default, or when the file has been re-encoded for delivery without preserving the original.

The fix is to retain the original raw file, exactly as captured, alongside the delivered version. The expert can then inspect the original. The delivered version is the user-friendly copy. The raw original is the evidence.

Footage from an operator who cannot produce the CAA Operational Authorisation reference. The first thing the opposing expert will check. If the operator is not on the CAA register, or if the flight was conducted in restricted airspace without the relevant permission, the footage’s admissibility is in question.

The fix is to commission only operators who can produce verifiable authorisation, on every flight, in writing, before mobilisation.

Footage that has been “enhanced” in post. Colour grading, exposure correction, sharpening, and cropping all change the file. If the changes have been made to the only available copy, the footage is no longer the original. The opposing expert will challenge it.

The fix is the chain-of-custody procedure above. The original raw file is retained untouched. The edited version is a separate file, clearly labelled as the working copy. The expert is shown both. The original is the evidence. The edit is the presentation.

What contract administrators should specify when commissioning

A short list to write into the contract or the brief.

1. All footage shall be captured by an operator holding a current CAA Operational Authorisation, verifiable on the CAA register.
2. All footage shall be captured under any necessary restricted airspace permissions, with the relevant references provided to the contract administrator before the flight.
3. All raw original files shall be retained on UK-resident infrastructure, untouched, for the duration of the contract plus twelve months.
4. Embedded metadata (date, time, GPS coordinates, camera settings) shall be present in every original file.
5. A written chain-of-custody statement shall be issued at handover, listing every file’s path from capture to delivery.
6. For high-value programmes, cryptographic hashes of every original file shall be generated at the point of capture and held in a separate log.

This is six clauses. They add nothing to the cost of the programme if the operator already runs to a serious standard. They add a significant amount if the operator is running on convenience and has to set up the procedure to match. The latter is the operator you do not want on a project that may end in dispute.

How JCT and NEC frame this

Neither standard form contract sets out what counts as drone footage evidence. The general principle is that any material adduced as evidence must be capable of being relied on. The five-point standard above is what “capable of being relied on” looks like in practice for drone footage.

Under JCT, the contract administrator’s certificate is the working document on programme and progress. Drone footage is supporting evidence behind the certificate. Contested certificates can be referred to adjudication. Adjudicators reach for the underlying evidence. If the drone footage is solid, the certificate is supported.

Under NEC, the project manager’s instructions and the early warning system rely on a shared visual understanding of the works. Frame-accurate monthly aerial monitoring, with the chain of custody intact, gives the project manager a defensible factual base. Disputes referred to the senior representative or to adjudication start from a stronger position when the visual record is solid.

In both contract families, the principle is the same. The contract administrator’s authority is supported by the quality of the underlying evidence. Investing in the discipline of the monitoring programme is investing in the contract administrator’s hand when it matters.

What this looks like in practice

The aerial monitoring programmes Over & Above runs are built to this standard from day one. Every flight is run by a CAA-authorised operator, with the airspace clearance on file, with the original raw files retained on UK cloud infrastructure, with embedded metadata in every file, and with a chain-of-custody log issued at handover. Hashing is available on request for high-value contracts.

The reason is simple. The cost of running the discipline once it is set up is negligible. The cost of not having the discipline, when a dispute arises, is the entire value of the footage as evidence. There is no halfway position. The discipline is either there from the start, or it is not.

If you are commissioning aerial monitoring on a project where a dispute is plausible, the discipline is what to specify in the brief. It is the difference between footage you have and evidence you can rely on.

---

If your project is at high risk of dispute and you want aerial monitoring built to evidence-grade standard, request the capability deck or call 0207 458 4997. The deck includes the chain-of-custody specification, the metadata standard, and the hashing protocol.