You find the incident on the camera timeline and click download. The office now has a file, but nobody has checked whether it plays, whether the time is correct or whether it includes customers unrelated to the incident.
A useful export process covers preservation, playback and permission to share. We would keep those decisions separate. Being able to download a recording does not mean everyone with the file is authorized to send it anywhere.
Preserve the relevant window before it disappears
Follow the business's incident process promptly when relevant footage is found. Record the camera name, date, start and end time, and the displayed time zone. Note any known clock error instead of silently correcting the description as though the original time were accurate.
Include enough before and after context to understand the event. That does not mean exporting unrelated days from every camera. The authorized reviewer should define the relevant cameras and window, with further preservation directed by the appropriate legal or investigative contact where necessary.
Use supported preservation or export features before routine retention removes the footage. Some systems can reduce older footage quality as well as delete it. A bookmark or label should not be assumed to protect a recording unless the installed product's behaviour is documented and verified.
Download a real file and test it separately
Use the supported export function rather than relying on a screen recording or a link that only works while the administrator is signed in. Exact controls vary by application and version, so the handover should include a demonstration on the installed system.
Play the saved file on an approved device outside the original live session. Check the beginning, the relevant event and the end. Confirm the intended camera, time range and picture quality. A completed download notification does not prove the file contains the event or that the recipient can open it.
Some exports need a compatible player or include supporting information. Record any requirements and confirm the recipient's accepted format before converting the file. If a conversion is needed, preserve the original export and label the converted copy separately.
- Camera name, site and exact requested time window.
- Displayed time zone and any known clock discrepancy.
- Export date, operator and supported export method.
- File names and a successful playback check.
- Preservation location, access owner and any follow up needed.
Keep the original and working copies distinct
Store an unaltered original export in an approved location with restricted access. Use a separate working copy for shortening, masking or other preparation. Keep a record linking any derivative to the original and describing what changed.
For an investigation, follow the recipient's evidence handling requirements. A documented file fingerprint, often called a cryptographic hash, can help show whether a file changed after the fingerprint was recorded. It does not prove the camera clock was right or authenticate everything depicted in the footage.
Do not promise evidentiary admissibility because a clip was exported or hashed. The broader record, collection process and applicable requirements matter. Escalate those questions to the responsible adviser rather than turning an IT export checklist into a legal conclusion.
A playable file, an authorized recipient and a disclosure record are three separate checks.Review privacy before sending
Canadian overt surveillance guidance says outside disclosures should be justified and documented. It also says that when recordings are disclosed to an individual who appears in them, identifying information about other individuals should not be revealed. Masking may be needed, and the result requires review.
Verify who is asking and why. A customer, insurer, employee and police officer may present different requests and authority. Staff should route the request to the designated privacy or legal contact rather than deciding at the reception desk that any official sounding request must be fulfilled.
Do not assume the recording platform includes sufficient redaction tools. If the needed masking cannot be done reliably, pause the disclosure and obtain appropriate help. Avoid uploading raw footage to an unapproved editing or AI service just to create a quick blurred version.
Do not post incident clips publicly to identify or shame someone. Footage can include uninvolved people, and a short clip may omit context. Use the authorized incident and disclosure process instead.
Control the transfer and every retained copy
Use the approved secure transfer method and verify the recipient's address or account before sending. Apply access limits and expiry where supported and appropriate. A public link that happens to be difficult to guess is not a substitute for deliberate access control.
Record what was shared, the recipient, the reason, the authorizer, the date and the transfer method. Confirm receipt through the agreed process without resending repeatedly or creating unnecessary copies. Keep the disclosure record protected too, because it may contain sensitive incident details.
Finally, apply the appropriate retention or preservation instruction to originals, derivatives and temporary downloads. The recorder's automatic deletion settings do not manage files on every laptop or shared drive. A complete export process ends with clear custody of the copies, not merely a successful send.
Plan the next step with NeuroDesk
NeuroDesk's business camera planning can include a practical export demonstration and defined access roles. Bring the system details and your approved incident handling policy. We can check the technical process while disclosure decisions remain with the business's authorized privacy or legal contact.
See our business camera and access planning for the relevant scope.
Sources and technical scope
The technical references below describe particular equipment and software. Features and limits must be checked against the installed model and configuration; they are not promises for every system.