Crash StepsIndependent public guide · not a law firm

Educational information only. This is not legal advice, medical advice, or an emergency service. It does not create an attorney-client relationship, and a disclaimer is not a promise that the page fits your crash. If someone may be hurt, call 911.

Records · practical playbook

A wrong detail in your crash report: a correction workflow

Find the specific discrepancy, preserve the original and ask the right agency about a correction or supplement—not a rewritten report you create yourself.

Official pages reviewed November 8, 2026.

About 4 minutes to read · 7 focused steps · reading-time estimate

Example situation · illustrative, not a real case

You open the crash report and spot the wrong vehicle detail. The insurer already has a copy. Editing your PDF would create another problem—not an official correction.

What you’ll get

  • Establish which record you have
  • Separate a factual mismatch from a disagreement
  • Use the agency route, not a public records edit request

General information only, not legal advice or medical advice. No case review, referrals or outcome predictions. For possible injury or immediate danger, call 911.

Jump to a step
  1. 1. Establish which record you have
  2. 2. Separate a factual mismatch from a disagreement
  3. 3. Use the agency route, not a public records edit request
  4. 4. Prepare a small, traceable packet
  5. 5. Track the answer without promising an outcome
  6. 6. Keep other clocks separate
  7. Before the next call: make the discrepancy readable
  8. Do this next
TxDOT published crash-report copy fees: regular six dollars; certified eight dollarsOne report. Two copy options.Regular$6Certified$8
Regular copy: $6. Certified copy: $8. These are TxDOT’s published copy fees; card or online processing charges may be additional. A copy purchase does not include other investigation records. Official fee source.

Worked example · not a real claim

A smaller correction packet

You have three disputed entries but only two supporting documents. Make three separate issue rows, link the two documents to the entries they address and leave the unsupported point explicitly unresolved. Three disagreements do not become three proven errors.

1. Establish which record you have

A Texas Peace Officer’s Crash Report, usually called a CR-3, is not the same thing as a dispatch log, an incident summary or your insurer’s claim notes. Start with the report title, investigating agency, crash date and report identifier. Keep these privately. TxDOT is the state custodian of officer crash reports; the investigating agency is the starting point for questions about what its officer recorded.

Save the received PDF untouched. If you need to make reading notes, use a separate copy. Naming a working copy “my comments” helps prevent it from being mistaken for an official amendment when you later send records to an insurer.

2. Separate a factual mismatch from a disagreement

Create a short private discrepancy table: page or field, what it currently says, what you believe is correct, and the document or direct observation supporting that belief. A vehicle-detail error and a disagreement with a narrative are different issues. Describe each precisely rather than saying the whole report is wrong.

Do not fill gaps with guesses. If you do not know the precise sequence of impacts, say so. A later recollection, a witness account and an original photo are different kinds of information; keep their origins visible instead of blending them into one confident account.

3. Use the agency route, not a public records edit request

Transportation Code §550.068 governs material changes to officer collision reports. Subsection (a) generally reserves a material-fact change to the officer who prepared the report; subsection (b) permits another person’s change through a written supplement clearly identifying its originator. That is not permission for a member of the public to overwrite the official PDF.

HPD says its Open Records Unit cannot add, change or modify reports; modifications must go through Records or the investigating division. Ask that division what correction or supplemental-information procedure applies. A records-purchase vendor is not the investigator and buying another copy does not itself fix anything.

4. Prepare a small, traceable packet

Keep your request narrow enough to follow. Identify the report, locate the specific field and supply the supporting material requested by the agency. Keep the copy you send and a record of the date and destination. Follow the agency’s current instructions rather than sending sensitive documents to every address you can find.

If the issue involves a photograph, preserve its original file and explain what it shows without editing the original. Do not add arrows to the only surviving copy. Do not include unrelated medical or financial records simply because they are in the same crash folder.

5. Track the answer without promising an outcome

Record whether the agency acknowledged the inquiry, requested more information, issued a supplement or declined to change the report. Ask where any updated version can be obtained. There is no promise that the report will be changed, that it will happen before an insurer decides a claim or that a supplement will accept your account.

Keep the original and later versions together with their received dates. If an insurer already has the earlier version, identify the later document accurately when you provide it. Do not describe your own explanatory letter as an official correction.

6. Keep other clocks separate

A correction request does not automatically extend a policy notice condition, a government notice requirement or a lawsuit limitation period. Continue preserving requested records and checking applicable deadlines through qualified advice. The existence of an error is not a reason to assume all other work can wait.

Use the document organizer for categories to gather, not for uploading the report. If you are disputing fault, a serious injury account or a deadline-sensitive matter, this workflow cannot determine legal effect. It helps you ask an organized question while keeping the underlying records intact.

Before the next call: make the discrepancy readable

Put the report identifier at the top of your private working sheet, followed by a separate row for each disputed field. Include the page, the current entry, the correction you are asking the agency to consider, the supporting record and the response received. Keep a blank space for the agency’s procedural instructions rather than presuming it accepts your proposed format. If there are several issues, separate a clerical mismatch from a disputed interpretation. At the end, ask how an approved change or supplement would be identified in a later copy. That question keeps your follow-up tied to an official version, not to your own marked-up document.

Try the next three moves

Checkmarks only are saved on this device—never your records or story. They do not certify legal compliance.

0 of 3 prompts marked.

Do this next

Turn the next question into a smaller task.

Open this guide’s companion tool →

Actual records stay in your secure files. Tool inputs are temporary; the guide checkmarks above save only step IDs on your device. A result is an organizational aid, not proof of a legal requirement.

Questions about this workflow

Can I edit the PDF before sending it?

Keep the official original intact. Put comments in a clearly separate document; an edited copy is not an official correction.

Does TxDOT correct the investigating officer’s account?

TxDOT holds crash reports. Ask the investigating agency about its correction or supplement procedure; do not assume a purchase request changes the report.

Related reading

Sources for this page