Incident response · Free Excel template

IVMS data-retrieval checklist after a crash

Many recorders overwrite old video. Work through 26 steps in the first hours, save the data and the video, and record who did what and when.

Free: enter your name and email and we send you the file. Works in Excel, Microsoft 365, Google Sheets and LibreOffice Calc. No macros.
  • Targets counted from the incident time
  • 26 steps in 4 phases
  • Data-source sheet for your own devices
  • Coordinator told, incident time written downDone
  • Recording locked, or card removed and baggedDone
  • Hash written for each exported fileCheck
  • Photos of the scene and the camera positions
What's inside

What is inside the checklist?

Five working sheets, plus Start here and the drop-down Lists. The status of each step is worked out from the incident time and your target.

  1. 01

    Incident details

    Incident time, review time, device IDs, data window and deadlines. Every target counts from the incident time.

  2. 02

    Checklist

    26 steps with who, a target in hours, a result, the time done and a calculated status.

  3. 03

    Data sources

    12 sources to pull. You write the exact steps for your own devices from their documentation.

  4. 04

    Worked example

    Made-up times that show all six statuses.

  5. 05

    Summary

    Steps by phase and status, the first-hour verdict and the hours to protect and export.

Status of a step

DoneDone lateOpenOverdueNot possibleNot applicable
The four phases

From the first hour to the close-out

Each phase has its own typical targets, counted from the incident time.

  1. First hour: protect the data

    Tell the coordinator, identify every device, find out when the MDVR will overwrite, then lock the recording or remove the card as your documentation says. Record the device clock.

    7 steps
  2. First day: pull the data

    Pull the detailed log, the impact event, the driver identity and the alarms. Export video from every channel in its original format. Calculate a hash and open custody entries.

    10 steps
  3. Within three days: document

    Photograph the scene and the device. Take statements. Compare the data with the photos and statements, complete the report and note the deadline.

    5 steps
  4. Close out: access and retention

    Decide who may see the footage and log every request. Share outside the company only as your legal team approves. Set the delete-by date and review the case.

    4 steps
Target hours after the incident (typical values)
PhaseTarget
First hour steps1 to 2htypical
First day steps4 to 24htypical
Three-day steps24 to 72htypical
Close-out steps72 to 168htypical

Typical values. Replace them with your policy, contract or client requirement.

Why does the first hour matter?

After a crash, the vehicle may keep running, the recorder may keep writing, and people may move or repair things. Each of these can destroy data you will want later. The checklist puts the protective steps first and gives each a target counted from the incident time.

Overwriting and the storage card

Many recorders record in a loop and overwrite the oldest footage when storage fills. How long that takes depends on the number of cameras, the quality and the card size. Work out the time left first, then lock the recording or remove the card as your device documentation says. Do not format the card.

The device clock

Compare the device time with real time while you are at the vehicle and write the difference in seconds. Do not change the clock. A clock that is a few seconds out can matter when you line up video with GPS data.

Hash and custody

Calculate a hash for each exported file and write it down. Keep one locked original and work from copies. Every handover goes into a custody log, so you can show later who held what and when.

References to verify

Verify against the current official text

Some operator standards ask for a rolling record of the minutes before an event. A copy of the PDO road safety standard SP-2000 is reported to mention a 5-minute second-by-second record. We could not confirm this or its clause number against the current edition. Some operators also set short deadlines for investigation reports on serious cases. Read the current official text of your client's requirement, and check what your own device records. This checklist does not say that any Tracom device meets a requirement. iogp.org

Limits of this checklist

It reminds you of the steps and times them. It does not describe device menus, and it does not replace your investigation procedure. Sharing footage outside the company needs legal review.

Related Tracom solution

Ask how your devices protect video and data

Tracom M1N is a mobile DVR (MDVR). Camera options such as DSM/ADAS are confirmed with the Tracom team. Bring this checklist and we write the steps for your model with you.

  • Tracom M1N MDVR. Camera options such as DSM/ADAS are confirmed with the Tracom team.
  • Second-by-second data. A detailed record to line up with the video.
  • Advanced configuration files. Settings you can write down and repeat across vehicles.
  • SCMS portal. Manage devices and configuration files in one place.
Questions

Data-retrieval questions, answered

Need the pull steps for your Tracom model? Talk to Tracom.

Does an MDVR really overwrite old video?

Many do. Most recorders record in a loop and replace the oldest footage when storage is full. Check how yours behaves in its documentation, and work out the time left.

Should I remove the storage card?

Only if your device documentation says so. Locking the recording is safer when the device allows it. If you remove a card, label it, bag it and log who took it and when.

Does the checklist show how to export from a Tracom device?

No. Steps differ by device and platform. The Data sources sheet has a column where you write your exact steps from the device documentation or the SCMS portal. Contact Tracom if you need the steps for your model.

Are the target hours a requirement?

No. They are typical values you can change. Some clients set their own deadlines, so read your contract and the current official text.

Why record a hash for each file?

A hash is a practical way to show later that a copy has the same content as the original. This file asks for it as good practice. Whether it is required depends on your client, insurer or authority.

What is Tracom's role here?

Tracom makes the devices. This checklist is a neutral tool for any fleet and any device. It makes no claim about approvals or about meeting an operator standard.

Next step

Write the pull steps for your devices

Bring the checklist. We go through the Data sources sheet with you and fill in the steps for your Tracom model.

Related tools and templates

Keep going after a crash

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Scroll to Top