The clip is not ready to hand over just because an export button worked. Check that the intended recipient can open it and understand where and when it came from.
The idea in view · Planning diagram
A usable handover is more than a download
- Authorized request
- Correct selection
- Supported retrieval
- Playback checked
- Controlled transfer
- Receipt and retention
Specify the request
Record the purpose, authorized requester, view aliases, interval and time zone. Use the minimum relevant footage. Ask the responsible team to review any privacy, preservation or disclosure obligations before sharing.
Check the exported result
Verify playback, start and end points, timestamps and any required player. Keep the original export unchanged. If a redacted or converted copy is needed, identify it as a derivative and retain the relationship to the original through the approved procedure.
Record custody and access
Log who exported, where the file is stored and which authorized party received it. Avoid emailing an unrestricted public link. Confirm the recipient can retrieve the permitted file before the source recording expires.
Test retrieval before an urgent request
Choose a harmless staged event and have an authorized user find it with the account and equipment they normally use. Record the camera alias, interval, time zone, export format and playback result. NIST’s video-exchange work exists because interoperability is a real retrieval issue; a working recorder screen does not establish that another system can read the export.
GOV.UK’s retrieval guidance addresses native video and preservation of evidential context. Keep the original unchanged under the approved procedure. If a redacted or converted copy is needed for an authorized purpose, record how it relates to the original. Do not widen access simply to make sharing convenient, and do not assume an export automatically satisfies a formal disclosure requirement.
Agree what the receiving person needs
Before exporting, confirm the authorized request, relevant cameras, time period and intended receiving system. A short clip for an internal review may serve a different purpose from material requested through a formal evidential process. Use the organization's procedure and appropriate expertise for the latter. The worksheet helps prepare and track the task; it does not certify forensic admissibility or replace local requirements.
Identify the original recording system and any time discrepancy before choosing the period. Include relevant context rather than assuming one dramatic frame is enough. Keep the request proportionate and authorized. Exporting every camera for an entire day merely because it is easy can create unnecessary data-handling work and expose information unrelated to the purpose. Record what was selected and why.
Reference context: GOV.UK: Recovery and Acquisition of Video Evidence v3.0 (2022)
Preserve the original and check the export format
Use the system's supported retrieval process. A native export may preserve information or require a particular player, while another format may be easier for a recipient to view. Do not assume that converting to a familiar file type preserves every relevant feature. Retain the original material and record any derivative or conversion according to the approved evidence process.
Check playback on an authorized receiving device before the source becomes unavailable. Confirm the intended cameras, period, visible detail and time context. A file that downloads successfully can still be incomplete, corrupt or dependent on missing software. If a player is required, arrange its approved use with the receiving organization. Do not bypass its security controls or send an unknown executable as an informal workaround.
Reference context: NIST: digital video exchange standards
Make the transfer traceable and controlled
Record the export operator, source reference, selection, format, creation time and authorized recipient or role. Use the organization's approved transfer method and verification controls. Any integrity checks or chain-of-custody requirements must follow that process; the presence of a checksum field alone does not establish a complete evidential procedure.
Keep footage and access links out of general planning sheets and unsecured messages. The worksheet can record a restricted reference and transfer status. Confirm receipt and usability where the process requires it, then apply the approved retention and deletion decision to temporary copies. A successful send is not necessarily a completed handover, and retaining copies indefinitely is not a substitute for deciding who owns the record.
A fictional export that fails at the recipient
A site exports a requested time period from a recorder and sends it through the approved channel. The authorized recipient reports that only one of the intended views is present and the required player has not been arranged. The transfer succeeded technically, but the requested task is incomplete.
The export owner returns to the source while it is still available, checks the selection and follows the supported process for a complete usable export. The record identifies the original attempt, correction and confirmed receiving result without overwriting the history. If the missing material can no longer be obtained, the report states the limit. This is more reliable than marking every downloaded file complete regardless of playback and coverage.
Make the call
Which export problem remains?
| Situation | Decision to make | What to ask for |
|---|---|---|
| The file needs a proprietary player | Whether the approved recipient can use it | The supported player and a playback test |
| A converted file loses source context | Which copy is the original | A retained native export and documented derivative |
| The system clock is offset | How the recipient interprets event time | An observed time-reference note |
Before you move on
- Approve the request and relevant interval.
- Export and test playback through authorized tools.
- Log storage, recipient and any derivative copy.
A worksheet you can actually use
Start with the blank sheet. Add one row per item, assign an owner and mark anything unresolved as pending. The completed example shows the level of detail to aim for.
Keep completed security plans private. Use aliases; keep passwords, access codes, personal contacts and footage links in your approved systems.
How to fill the worksheet
- Request reference
- Identify the authorized request and purpose, keeping the selection proportionate to the actual task and applicable procedure.
- Views
- List the relevant aliases and check that every requested view is present before treating the export as complete.
- Interval and zone
- Record the chosen period and time context, including any known camera discrepancy or historical uncertainty.
- Format
- Use the supported retrieval format and identify required player or derivative handling through the approved evidence process.
- Playback tested
- Verify the relevant material on an authorized receiving system; a successful download does not establish usable playback.
- Authorized destination
- Reference the approved recipient and transfer channel without placing private footage or unrestricted access links in the worksheet.
A worked example
Fictional test: a recorder exports a proprietary file that needs a vendor player. The team verifies that the approved recipient can use it before accepting the retrieval process.
| Request reference | Views | Interval and zone | Format | Playback tested | Authorized destination |
|---|---|---|---|---|---|
| TEST-EXPORT | GATE-01 | To specify UTC | Vendor export | Pending | Restricted repository |
Questions readers bring to this task
What else should you know?
Should every export be MP4?
No universal format is appropriate for every system and evidential purpose. Preserve the supported native export where required and test the receiving workflow. A convenient viewing copy may be a derivative; identify it as such rather than replacing the original without a record.
Link to this answer ↗Is a screen recording an adequate evidence export?
Do not assume it is equivalent to a supported native retrieval. It may omit metadata, quality or context needed for the purpose. Follow the organization's procedure and the receiving authority's requirements, retaining original material and documenting any derivative where appropriate.
Link to this answer ↗Should exports include a video player?
Some formats require a specific supported player. Confirm that need early and arrange approved playback with the recipient. A file extension alone does not prove compatibility. Do not ask the recipient to bypass security restrictions to run unfamiliar software.
Link to this answer ↗When is an export complete?
When the authorized selection has been retrieved, checked, transferred and acknowledged as required by the applicable process, with retention and remaining work assigned. The exact requirements depend on purpose and local procedure. A progress bar reaching one hundred percent is only one technical event.
Link to this answer ↗Notes & sources
Admissibility and disclosure rules vary. This is an operational export test, not legal or forensic certification.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- GOV.UK: Recovery and Acquisition of Video Evidence v3.0 (2022)
Native retrieval, playback and source context. A formal forensic procedure requires appropriate expertise.
- ICO: surveillance data protection principles
UK surveillance guidance on purpose, retention, secure access and transparency. Guidance is under review; check it when making a decision.
- NIST: digital video exchange standards
Video export interoperability research, not a certification of this website or a customer system.