¶ Reports and Exports
After you have found the correct vehicle and reviewed the right recording, the next step is often to create material that can be shared internally or used in a formal follow-up.
In practice, reports and exports are used for:
- damage investigations
- incident follow-up
- internal review with operations or engineering teams
- sharing selected evidence with approved stakeholders
Some reports are generated by vehicle-side utilities and become available in OEC as reference documents.
These can include installation or system reports that help confirm:
- vehicle identity
- installed hardware
- software versions
- device test results
Screenshot placeholder: reports tab on a vehicle in OEC
The legacy manual described a simple report flow from the Web Player, and that is still the right mental model:
- Open the correct recording in the Web Player.
- Navigate to the exact time you want to document.
- Add a short description of the incident or finding.
- Create the report.
- Wait for the generated report to appear in OEC if your environment supports that flow.
Screenshot placeholder: web player report menu and report form
Keep the text practical and easy for someone else to understand later.
Include:
- vehicle id
- event date and time
- short description of what happened
- which camera views were used
- what action is expected next
Confirm:
- you selected the correct vehicle and time window
- the footage clearly shows the relevant event
- you are following your organization's process for handling recordings
- the recipient is approved to receive the material
If you expected a report but do not see it:
- refresh the vehicle page after waiting briefly
- confirm the report was actually created from the player
- check whether your account has access to the reports area
- contact Support if the report should already be visible