In brief: retrieve footage quickly, export it carefully, and check who’s entitled to it before you hand it over.
Three common failures
Footage that’s hard to retrieve when it’s needed. Exports done so carelessly that the key detail is lost. And footage released without understanding the operator’s obligations.
Retrieving it quickly
Modern systems allow footage to be downloaded remotely over broadband, so nobody needs to visit site with a USB stick. Specify this from the start.
Exporting it correctly
- Identify the camera, date and time.
- Review enough footage either side to capture the whole incident, not just the moment itself.
- Export in a format that keeps timestamps, camera details and other metadata.
- Check the file plays on a separate computer before treating the job as done.
Common mistakes:
- Waiting until footage has been overwritten
- Choosing the wrong camera, or relying on a recorder clock that has drifted
- Cutting the clip too tight and losing the context
- Screen-recording or converting files in ways that strip out quality or metadata
- Proprietary formats that need a special player nobody has
Who gets the footage
Different requests follow different rules:
- A person asking for footage of themselves is making a subject access request (see Topic 1).
- The police may ask for footage to investigate a crime. Data protection law allows you to disclose it for that purpose, but it doesn’t oblige you to. Record every request and what you released.
- Other third parties, such as insurers or neighbours, need careful thought before you release anything.
Treating every request the same way is a common and avoidable mistake.
Three parts of one well-run system
Quick retrieval, careful export and caution about who receives footage aren’t in conflict. A well-run system gets all three right.
This article gives practical guidance. It is not legal advice.
Electronic security for over a decade, after an early career in IT networks.