The question
An investigator receives an interpreted EDR report. A reviewer asks for the underlying data. Does “raw data” mean the original scan responses, decoded event tables, or the report’s analysis?
Identify the requested layer
The request needs a clear definition. Original scan responses may be supplied as hexadecimal data. A decoded data report presents recorded values in readable fields and tables, with definitions and limitations. A contextual report adds explanation and analysis. These serve different review needs.
Keep the documents connected
Confirm that the supplied documents relate to the same vehicle, scan and event records. Preserve the original acquisition and record the report version used. A shorter appendix should remain traceable to its source; it should not silently replace the complete record.
Match the scope to the assignment
A reviewer may need a compact source-data appendix, decoded tables for independent technical review, or contextual explanation for an investigative question. State which material has been supplied and what has been omitted. Request the fuller documentation when the assignment requires it.
Practical takeaway
Define “raw data” before choosing a report. Hexadecimal scan responses are not a decoded event table, and neither is a substitute for explaining how an opinion was reached. Use the applicable field definitions and limitations, and keep recorded values separate from interpretation.
About this example
This is an original illustrative workflow informed by customer reporting questions. It is not a published customer case, report extract, validation study or claim of a legal outcome. Document availability and scope should be confirmed for the assignment.