How to read a police crash report

Collision Bureau is not a law firm and this is not legal or medical advice. It is general information about what happens after a crash. For advice on your situation, talk to an attorney licensed in your state or a treating clinician.

The report is a record of the officer's work, not a verdict

The police crash report has a slightly different name in every state: traffic crash report, motor vehicle crash report, accident report, incident report, state DOT crash form. Underneath the labels, the document does the same thing. A responding officer arrives at a scene, works it, and writes a record. The record goes onto a standardized form that the state department of transportation designed and the agency uses, with some agencies adding supplemental sheets of their own. That is the whole provenance.

The provenance matters because of what it implies. The report is the officer's record of their work. It is not an adjudication. It is not a court finding. It is not binding on any insurer or any attorney, and it does not resolve any civil claim by its own authority. The report is evidence, often very good evidence, and it moves many claims in practice. It is not a verdict on who caused the crash or who owes what to whom.

That distinction keeps the rest of this guide honest. Everything in the report falls into one of two buckets. On one side sit facts the officer recorded: who was there, where, when, which vehicles, which plates, which VINs, which addresses, which drivers' licenses, which insurance policies, which weather conditions at the time, which lighting conditions, which direction each vehicle was traveling, what damage was observable, which EMS crew responded, which hospital the ambulance went to. These are facts in the ordinary sense: the officer saw them or confirmed them, and they are the officer's record of them.

On the other side sit opinions the officer formed: contributing circumstances they coded for each driver, apparent causes they noted, who they believed to be at fault if they wrote that in the narrative, and any judgment call they made about speed estimates or sequence of events. Opinions are important. They can carry weight. They are also opinions, which can be challenged, revised, and overridden by other evidence. Reading the report well means keeping the two buckets separate even when the form puts them next to each other.

The report is also a snapshot. It captures what was knowable at the scene, which is sometimes less than what gets known later. New evidence, witness statements collected after the report was filed, a second look at surveillance video, a mechanical inspection of a vehicle, all can change the picture. The report does not retroactively update to reflect new evidence. A supplemental report sometimes does, where state and agency rules allow, which is a different document rather than a revision of the first one.

The context of the writing also deserves a note of respect. Crash scenes rarely wait for perfect conditions. Officers arrive to active traffic, injured parties, wreckage, bystanders, and weather, often all at once, and their work has to produce a complete record while also preserving the scene, directing traffic, coordinating with EMS, and sometimes conducting a criminal investigation in parallel. The paperwork that emerges reflects that environment. Reading the report with awareness of how it was made, rather than as if it were drafted in a quiet office, is both fairer and more useful.

One more framing matters before the fields are decoded. The report is not written for the parties. It is written for the agency's records office, for the state's data collection, for insurers who will later request a copy, and sometimes for courts. The parties are allowed to read it, and in most states they can request a copy. Reading a document written for other audiences is a familiar discipline from reading medical records, tax forms, and other formal documents, and the same patience helps here. The form is doing a technical job, and that is why the fields look technical.

Why your report looks like every other report in your state

If you have ever compared two crash reports from the same state, they look almost identical. The reason is bureaucratic and useful. Each state's department of transportation publishes a standard crash report form, and local, county, and state law enforcement agencies within that state use it. The form has field numbers, boxes, and codes. The code manual that goes with it tells officers which codes to put in which fields. The result is a document a records office in one city can hand to an insurer in another and the format will be instantly recognizable.

Format varies between states, sometimes dramatically. One state's form may have 12 pages with a long contributing-circumstances table; another's may be a two-page form with a short code list. The federal government, through a program called the Model Minimum Uniform Crash Criteria, publishes recommended data elements that most states incorporate. The practical effect is that the fields in your state's form were chosen deliberately to answer the questions a research office, an insurer, and a court will later ask.

Reading a form means understanding what the form was built to collect. Every field exists because a question comes up for it later. Date and time exist because many deadlines run from them. Location exists because jurisdiction and legal venue depend on it. Weather, road, and lighting exist because contributing-circumstances analysis requires them. Vehicle and driver identification exist because any claim starts with them. The form is almost never arbitrary. The field is usually there because somebody needs the answer.

Each state publishes its code manual, often as a PDF, which is the key to the boxes with numbers in them. Many of the manuals are freely available online; some require a records request to obtain. Reading the manual once is a small investment that pays off every time the form uses a code the ordinary reader would otherwise skim past.

The federal Fatality Analysis Reporting System and other federally supported programs pull data from state crash reports and compile national statistics. That downstream reporting is one more reason the fields on the form look technical: each field feeds a database that someone, somewhere, will later analyze for a safety research question or a policy decision. The individual report in your hand is also, invisibly, a row in a very long spreadsheet. That dual nature affects what the form looks like but does not change how a party reads it.

State forms update periodically, usually in cycles of several years, and the field numbering shifts when they do. A report from 2018 may use slightly different field numbers than a report from the same state in 2026, even on identical crashes. The code manuals carry version dates for a reason: the version that applies to a given report is the one in force on the date of the crash. For older claims that are still open or being reviewed, matching the report to the correct manual version is one of the small corrections an experienced reader makes without comment.

The header: agency, report number, date, time, location

Across the top of the report sits the identification block. The agency that produced the report, usually a city police department, a sheriff's office, or a state police district. The report or case number assigned to this incident, which is the string that will travel on every subsequent reference to this report. The date and the time of the crash, usually written separately from the date and time the report was filed. The location, which can be a street address, an intersection, a highway mile marker, or latitude and longitude for rural stretches. Sometimes the officer's badge number appears here; sometimes further along in the signatures.

Each field in this block earns a reason. The agency name tells any outside reader which records office holds the master copy. The report number is the fastest way to find it again. The date and time, often broken out to the minute, are the anchor for every deadline running from the crash: policy notice windows, repair timeline, statute of limitations, and other legal deadlines that vary by state. Location drives jurisdictional questions that are sometimes crucial in border crashes.

Illustrative example. A crash record might carry report number WRK-2026-10378 under an illustrative label, with a date of October 3, 2026, a time of 7:42 PM, and a location of the illustrative intersection of Fourth Street and Elm Avenue. Those numbers and names are invented for the example. On any real report, the field format is similar even if the specific identifiers differ. Reading them first and copying the report number into whichever claim file is being built is the small habit that saves many later confusions.

One more field often sits in or near the header: the type of crash classification. Property damage only, non-fatal injury, fatal, and a few other categories that drive which supplemental forms the officer must complete. The classification does not make the crash worse or better. It routes the paperwork, and sometimes it signals which further investigation may follow.

The header block also often prints a short list of agency contact fields: the records office phone, the records office hours, and the fee schedule for obtaining a copy. These are usually at the top or the bottom of the first page and are the first things to copy down when a party begins the request process. The lane page on how to get your crash report covers the retrieval channels in more detail.

The parties and the unit numbers

Below the header, the form shifts to the parties involved. Each vehicle in the crash gets a unit number. Unit 1, Unit 2, Unit 3, and so on. The unit number is the pointer the rest of the form uses. When later sections say driver action for Unit 1 or damage code for Unit 2, they are referring to the same vehicle. Keeping the unit numbers straight across the form is the single most useful discipline for reading an unfamiliar report.

Convention on which unit gets the number one varies by state. Some states assign Unit 1 to the vehicle the officer considers the striking vehicle; some to the vehicle the officer believes contributed most to the crash; some simply to the first vehicle recorded on scene with no further implication. The unit number is not by itself a statement about fault. Reading it that way can lead to a wrong conclusion. The code manual for your state tells you how your state's officers are instructed to assign the number.

Beyond vehicles, the form has rows for other parties. Pedestrians, bicyclists, scooter riders, and others who were involved in the crash but were not driving a motor vehicle usually get their own labeled rows, with their own identifiers. Property damaged by the crash that is not a vehicle, like a mailbox, a utility pole, a storefront window, or a fence, is often recorded in its own section with a non-motor-vehicle property label.

Nothing on the form is self-explanatory until the unit convention is clear. The first few minutes with any unfamiliar crash report should be spent finding the unit list, confirming which vehicle is Unit 1, and reading the rest of the form with that mapping in hand. Everything downstream becomes legible once that is settled.

Drivers, vehicles, and insurance fields

For each unit the form records a driver block and a vehicle block, side by side or stacked. The driver block lists the driver's name, address, date of birth, driver's license number and state of issuance, telephone number, and sometimes an employer or occupation. The vehicle block lists the year, make, model, color, body style, VIN, and license plate with state of issuance. In some states a towing company and tow destination appear if the vehicle was towed from the scene.

Below those two blocks sits the insurance information. The policy's carrier name, often abbreviated, and the policy number. Officers usually copy this from the driver's insurance card at the scene. This is one of the easiest spots on the form for a clerical error to appear, because an officer reading an unfamiliar carrier abbreviation at a roadside under weather and time pressure may transcribe a letter or number wrong. If a policy number does not match the driver's actual policy, the correction is usually a routine request to the agency, with the correct policy number documented.

Each state treats registered owner differently. Some always collect it as a separate field, some only when the owner is not the driver, and some print it on the vehicle block automatically through a motor vehicle records lookup. Where the owner is different from the driver, the field matters. It routes claim correspondence and governs whose policy is primary in borrowed-vehicle scenarios, which the lane page on what happens when you crash a borrowed vehicle describes in more detail.

License plate expiration, registration status, and inspection stickers sometimes appear here or in a short vehicle condition block. These fields matter in some jurisdictions and are purely informational in others. Reading them is a one-line check: are the vehicle's basic registration facts in order on the record. Nothing more should be inferred from the field by itself.

Commercial vehicles sometimes carry additional fields on the form. A commercial driver's license endorsement, a US Department of Transportation number, a motor carrier identifier, cargo information, and hazardous materials indicators appear on crashes involving larger trucks and some other commercial vehicles. These fields are routine for the commercial side and legal shorthand for the regulatory frameworks that govern them. Where they appear, they trigger different later paperwork than a passenger-vehicle crash would. A party involved in such a crash may want an attorney licensed in your state who handles commercial vehicle crashes specifically.

Passengers and pedestrians, if any

Many forms have a dedicated section for passengers and pedestrians involved in the crash. Each row usually carries the person's name, address, date of birth, position in the vehicle for a passenger (front right, rear left, and so on), restraint use, and injury severity on a scale the state form defines. For pedestrians and bicyclists, the row records their position relative to the vehicle at impact and their actions in the moments before impact.

Restraint use is a factual field based on the officer's observation on scene. Seat belt use, child safety seat use, and occupant protection system deployment, like front airbags or side curtains, are usually listed. Officers record what they observed. The field can be contested in later proceedings if the record is wrong, but it starts life on the form as the officer's note of what they saw.

Injury severity is coded on a scale that most states adopt from the KABCO classification, which runs from no apparent injury to killed. Codes K, A, B, C, and O stand for different severity levels. The code is the officer's judgment at the scene, informed by any medical assessment from the EMS crew if present, and it does not substitute for a medical record from a hospital or clinic. The medical lane page on who pays the medical bills after a crash covers how the formal medical record is built later. The crash report captures only what was visible to the officer on scene.

Transport information often sits in this section. The ambulance company that responded, the hospital or clinic the patient was taken to, and the time of transport. These fields matter for later record retrieval, because the hospital record is the companion document to the officer's note of injury severity, and the hospital name on the form is often the fastest way to find it.

Pedestrians and bicyclists involved in a crash get fields of their own, often with a few extra entries that do not exist for vehicle passengers. Pre-crash action, position in roadway at impact, and whether the pedestrian or bicyclist was in a crosswalk, on a sidewalk, or in a bike lane are typical fields. These entries exist because pedestrian and bicycle crashes carry different legal and factual contours than vehicle-only crashes, and the extra fields capture that. For a pedestrian injury, the lane page on medical care after a collision and an attorney licensed in your state are both the right places to turn for what the report actually implies.

Injury information often sits in or beside this section. Each injured person usually has a row, with name matched back to the passenger or pedestrian section, a code for severity on the state's injury scale, a description of the injury if the officer noted one, the responding EMS unit, and the hospital or clinic the patient was taken to. The field is the officer's record of what was observable at the scene, informed by any medical assessment at the scene. The report is not a medical record. The hospital is the medical record. The report's role is to document the fact of injury as the officer saw it and to point to the medical records that follow.

Injury severity codes on crash reports often use a widely adopted scale, with letters or numbers that map to levels like no apparent injury, possible injury, non-incapacitating injury, incapacitating injury, and killed. The officer applies the scale from observation plus any medical assessment on scene. A possible injury code at the scene can become a diagnosed sprain or a diagnosed concussion in a hospital's record a few hours later. The report captures the scene reading; later records capture the medical reading. Transport information, the ambulance company name, the hospital name, and the time of transport, is often the fastest way to locate the hospital record once needed. The lane page on medical care after a collision covers the medical side of what follows.

Illustrative KABCO code	Illustrative label	What it typically describes
K	Fatal injury	A death resulting from the crash within the state's defined window
A	Suspected serious injury	Severe lacerations, broken bones, loss of consciousness, severe burns
B	Suspected minor injury	Lump on head, abrasions, bruises, minor lacerations observable at scene
C	Possible injury	Momentary unconsciousness, claim of injury, no visible injury
O	No apparent injury	No injury observable at the scene; no complaint

Illustrative labels only. States adapt the KABCO scale with their own definitions, and the state's manual carries the exact wording.

Environmental conditions: light, weather, road, traffic

A block of environmental fields describes the physical conditions at the time of the crash. Light conditions (daylight, dawn, dusk, dark with street lights, dark without street lights). Weather (clear, rain, snow, sleet, fog, wind, severe crosswinds). Road surface (dry, wet, slushy, snowy, icy, oily, debris). Road character (straight, curve, grade). Traffic control (none, signal, sign, flashing light, officer directing). Each field is a short code from the state's manual.

Each field is also a factor insurers and attorneys weigh when thinking about contributing circumstances. A dry road at midday with clear weather frames one picture of a crash. A dark unlit stretch with snow on the ground frames a different picture. The report records what the officer judged the conditions to be at the time, and the record then colors how everything else on the page is read.

Where the officer and a party disagree about conditions, the officer's record is the starting point. Challenging it requires evidence, like weather service records for the hour of the crash, nearby traffic camera footage, or dispatch recordings from other units in the area at the same time. Disputed conditions in a civil claim are usually a question for an attorney, which the lane page on what to do after a weather-related crash addresses from the weather side.

Traffic control deserves its own close read. If a signal was present and whether it was functioning is a fact the officer records. If the officer coded none for traffic control, that reflects their observation at the scene and may or may not match what a party remembers from a moment under stress. The field is a short code with a specific meaning in the manual, and the manual is the right reader for what each short code implies.

Here is a quick reference showing how environmental fields usually appear on a crash form, so the short codes do not feel arbitrary when a party is reading the report for the first time. Each row below is illustrative; the actual labels and codes on your state's form sit in the manual.

Field	Illustrative code	Illustrative label in the manual
Light condition	01	Daylight
Light condition	03	Dark, no street lights
Light condition	04	Dark, street lights on
Weather	01	Clear
Weather	02	Rain
Weather	05	Fog, smoke, smog
Road surface	01	Dry
Road surface	04	Icy or snowy
Traffic control	00	None
Traffic control	07	Traffic signal, functioning

Illustrative environmental codes only. The actual code list for your state is in that state's crash form manual.

The diagram, drawn to show direction and impact

Most crash reports include a scene diagram, sometimes small and schematic, sometimes drawn to scale. The diagram places each unit on a sketched road, uses standard symbols for direction of travel, arrows to show paths before and through impact, and often an impact-point symbol like an asterisk or a filled circle at the point of first contact. The diagram is not a photograph. It is a sketch that encodes the officer's understanding of the sequence of events in a compressed visual form.

Diagram conventions vary slightly between states, but a few symbols are nearly universal. An arrow in a straight line represents a vehicle's path of travel. A hook or curved line represents a turn. A circle, star, or filled dot usually marks the impact point. The unit numbers from the earlier section label the vehicles on the diagram. Lane markings, median lines, curbs, and signal locations are drawn where they help the sketch make sense.

The useful habit is to read the diagram with the narrative. The narrative describes the sequence in prose. The diagram shows it visually. If the two disagree, that is a reading signal, not necessarily an error, but worth attention. A diagram that shows an impact in a different lane than the narrative places it in is a question an insurer will ask, and a question worth asking before the insurer does.

One honest limit about diagrams. Many are drawn without any reconstruction evidence. The officer did not survey the scene with instruments; they sketched what they understood. For a serious crash where the sequence matters, a reconstruction expert may later produce a very different diagram built from evidence like skid marks, debris field analysis, and vehicle damage mapping. The report's diagram is the officer's drawing. A reconstruction is a different document.

Agencies also handle diagrams differently when the scene is unusual. A diagram for a highway interchange may include ramps and barriers. A diagram for a parking lot may abstract parking stalls into schematic rectangles. A diagram for a crash on a private driveway or a loading dock often simplifies the environment aggressively, because the standard road symbols do not fit. None of this is a flaw. The diagram is a sketch, and sketches simplify. The key is to read the diagram alongside the narrative so that the simplification does not obscure the sequence.

One useful habit for parties reading a diagram is to physically retrace the scene mentally. Which direction were you driving. Where were the signals, signs, or markings. Where did the impact feel like it happened in the vehicle, relative to the diagram. If the mental retrace matches the diagram, the sketch did its job. If it does not match, that mismatch is not necessarily evidence of an error, but it is a question worth noting, written down for a later conversation rather than for a dispute at the records office.

Coded fields and the state code manual

The density of a crash report comes from its coded fields. Many fields on the form are a two-digit or three-digit number, with the number pointing to a specific line in the state's code manual. Driver action, contributing circumstance, road surface, light condition, weather condition, type of collision, vehicle maneuver, defect, and others all usually appear as codes rather than words.

The reason for coding is efficiency. A box on the form holds a number faster than a sentence, and a database holds a code better than a paragraph. The downside is that an untranslated code looks like noise. The upside is that once the manual is in hand, the codes are instantly readable, and a lot of information fits in a small space on the page.

Illustrative example of how codes stand in for text. On an illustrative state's manual, driver action code 15 might stand for failed to yield right-of-way; code 24 might stand for exceeding speed limit; code 42 might stand for inattention; code 03 for rear-end damage code. The actual numbers and definitions differ by state. The pattern is identical everywhere. The form carries the number; the manual carries the meaning.

If a party disagrees with a code the officer entered, that is a dispute about an opinion, not a dispute about a fact. The code is the officer's judgment of what applies at the scene. The remedy is to engage the formal process the agency allows for revisiting a report, which the amendments section below covers, and to document the alternative view with evidence.

Illustrative field	Illustrative code	Illustrative text in a manual
Driver action	15	Failed to yield right-of-way
Driver action	24	Exceeding speed limit
Contributing circumstance	42	Inattention
Light condition	03	Dark, no street lights
Weather condition	02	Rain
Road surface	04	Icy or snowy
Type of collision	07	Rear end

Illustrative codes and labels only. Every state publishes its own code manual, and the actual numbers and definitions on your report come from your state's manual rather than this table.

If this is your week

Get the report, then read it against the manual.

One request covers the attorney, the tow, the repair, and the rental. It costs you nothing, ever.

Get help now How it works

Contributing circumstances, read as officer opinion

One of the most important sections of any crash report is the contributing circumstances field, usually filled in once for each unit. This is where the officer records what, in their assessment, contributed to the crash from each driver's side. Codes here can include things like driver inattention, failure to yield, following too closely, speed, impaired driving, defective equipment, and others defined in the state manual.

These are opinions. The officer formed them from the scene, from the drivers' statements, from the physical evidence, and from any witness accounts collected. Opinions can be well-founded, and they often are. Opinions can also be wrong, in all of the human ways opinions can be wrong. The report records them as the officer's judgment, which is what they are, and insurers and attorneys will weigh them against other evidence over the course of the claim.

How insurers weigh contributing circumstances varies. Many carriers treat the officer's coded contributing circumstances as significant evidence while reserving their own liability determination for the full file. Attorneys read the field through the same lens, with an eye on what evidence supports or contradicts the officer's codes. A code is a starting point, not a destination.

What the field never does is end a case by itself. A code of inattention on one driver is not a verdict of fault. It is a note that the officer, on scene, saw indications that attention was lacking. The civil determination of fault involves many facts, and reading the contributing circumstances line as an opinion rather than a ruling keeps the rest of the file in its proper place.

Here is one more honest aspect of the contributing-circumstance field. In some claims the officer codes a circumstance for one driver and no code for the other, which some parties read as a clear fault assignment. The reading is reasonable and sometimes correct. It is not automatic. The absence of a code for one driver does not mean the officer found that driver blameless; it means the officer did not record a specific circumstance in the field at the scene. The civil claim weighs the whole picture, including the absence, and the lane page on how fault actually gets decided describes that weighing in more detail.

The narrative, in the officer's own words

Most crash reports include a narrative section, written as a paragraph or several short paragraphs in the officer's own voice. The narrative usually describes the officer's arrival, the apparent position of the vehicles, the visible damage, the drivers' statements, witness statements if any were collected, and the actions taken. It is the officer's prose record of the scene, and it is usually the richest part of the report in detail.

Narratives vary dramatically in style. Some officers write tight, dated chronologies. Some write longer accounts that put the scene in context. Some include brief characterizations of the drivers' demeanor. The variation reflects agency conventions, officer habit, and the complexity of the scene. All of them, however, are the officer's words, which means every sentence is on the opinion side of the ledger except where the sentence states an observable fact.

The useful move is to read the narrative with a mental highlighter. Facts in one color: the officer's arrival time, the vehicles' positions, the damage descriptions, the statements each driver gave. Opinions in another color: characterizations of the sequence, judgments about which maneuver caused the collision, inferences from physical evidence. Both are present. Reading them differently keeps the record honest.

Occasionally the narrative is the first place a dispute is visible. If a driver gave the officer a statement at the scene, the narrative records what the officer wrote down. If the driver remembers saying something different, that is a discrepancy worth noting, with the understanding that discrepancies between on-scene statements and later memory are extremely common, and that resolving them is a legal question rather than a documentary one. An attorney licensed in your state is the right reader for that question.

Narrative length is often a signal of complexity rather than quality. A short narrative on a straightforward rear-end crash in daylight on a dry road may be entirely appropriate. A longer narrative on a multi-vehicle crash at an intersection with contested right-of-way reflects a scene that required more words to describe. Comparing narrative length between two reports is rarely informative. Comparing the narrative against the coded fields in the same report usually is: a long narrative with coded fields that match tells one story, and a long narrative with codes that seem to pull in a different direction tells another.

Witness statements and the officer's handling of them

Where there were witnesses, the report usually records their names, addresses, telephone numbers, and short statements. Some agencies have the officer summarize what each witness said; some include the witnesses' own written statements as attachments. Either way, the record creates a trail that insurers and attorneys can follow later to speak with the witness directly.

Witnesses are decisive in many claims and absent in many others. The officer records who was there and spoke, within the limits of the scene time and conditions. A witness who left the scene before the officer arrived usually will not appear on the report unless a party documents their contact information and provides it later. A witness who stayed and spoke to the officer appears in the narrative or the witness block, with the detail the officer captured.

What a witness said at the scene is one piece of evidence. What they will say in a formal statement later is another. The gap between the two is a normal fact of memory and process rather than evidence of deception. The report captures the first version, and later proceedings may capture more polished and considered versions. All of them belong to the case file in whatever role the law gives them.

Collecting witness information yourself at the scene, if conditions allow, is one of the simpler habits the lane page on the first 48 hours after a crash recommends. Even a name, phone number, and short note of where someone stood during the crash can be useful if the officer did not record it, or recorded it in less detail than the facts of the claim later require.

A short note about witness statements and nothing more. The officer's record of what a witness said is a near-contemporaneous record, which carries weight because of how quickly it was created. The witness's own later written statement, provided through a party's attorney or an insurer, is a separate document with its own evidentiary role. Both can exist in the same claim, both can be useful, and the differences between them are a legal question an attorney licensed in your state is positioned to answer.

Citations, charges, and what each one means

A crash report lists any citations issued at the scene, usually in a dedicated field or in the narrative. Each citation names the driver, the statute cited, and the offense. Some citations are for traffic infractions, some for criminal offenses, some for equipment violations, some for license and insurance verification issues.

A citation is evidence in a civil claim, not a verdict. It records that the officer, at the scene, believed probable cause existed to charge the driver with the named offense. A court may later find the driver responsible for the offense, and the proceedings that follow can produce a conviction, a plea, a dismissal, or an acquittal. Each of those outcomes carries different weight in a civil claim, and the lane page on how fault actually gets decided addresses the overall picture.

What a citation never does, on its own, is resolve a civil claim. Even a citation that is later paid or admitted is one piece of evidence toward fault, not a complete determination. On the other side, the absence of a citation does not resolve a claim in a driver's favor, either. Officers decline to cite for many reasons, including evidentiary limits, departmental practice, and judgment calls about what the scene supported.

How a conviction, plea, dismissal, or acquittal of a cited offense is used in a later civil claim is a legal question that varies by state. In some jurisdictions, certain outcomes may be admitted as evidence in the civil proceeding. In others, specific evidentiary rules limit how a cited offense can be referenced. The report records the citation. The policy and the state law decide what the citation means in the civil claim. That is one more reason an attorney licensed in your state is the right reader when a citation is in play.

If an officer at a scene with a criminal element made an arrest, as in a crash involving suspected impaired driving, the report will usually note it. The downstream criminal proceeding is a separate matter from the civil claim. The lane page on what to do if the other driver was DUI covers how the criminal and civil tracks run alongside each other without conflating them.

Reading citations against the rest of the report is where the officer-opinion versus factual-record discipline earns its keep again. A citation records that the officer, with the authority to do so, believed probable cause existed. It is a specific professional act with legal consequences for the cited driver. It is not a civil fault determination, and it is not the end of the matter even for the specific offense cited.

Officer opinion versus factual record, in one page

Everything above compresses into one honest discipline. The report mixes record and opinion, and reading well means separating them in your head as you read. Here is a short checklist that makes the split visible.

Record side. Names, addresses, dates of birth, license numbers, vehicle identifiers, policy numbers, time and date of the crash, location, agency, officer badge, weather and lighting as observed, road surface as observed, visible damage, EMS and hospital transport, citations issued, charges filed, witness names and contact details. Each of these is a fact the officer recorded or confirmed from a source, and each is on the record side even if some specific values might later be challenged for accuracy.

Opinion side. Contributing-circumstance codes, driver-action codes beyond the mechanical description, inferences about speed where no reconstruction was done, inferences about sequence of events in the narrative, characterizations of driver demeanor, and judgments about who was at fault. Each of these is the officer's reading of the scene. Each carries weight. Each is still an opinion.

The middle sometimes exists. A field like direction of travel is a record where the officer observed it or saw a definitive sign; it is an opinion where it was reconstructed from damage patterns and witness statements. The code manual tells officers how to decide, and the resulting entry is as reliable as the inputs the officer had. Reading these middle fields with awareness of how they were formed is the honest way to use them.

Amendments, supplemental reports, and the errors that show up most often

Crash reports can be revised. The channels differ by agency and by state, but the common patterns are two: a correction to a clerical error, and a supplemental report that adds information that was not available when the original was filed. Both are informational processes rather than fault determinations. Neither is a trial by paper.

Clerical corrections handle things like a transposed VIN, a misspelled name, a wrong policy number, a date typo. Most agencies accept a written request with supporting documentation and either reissue the report with the correction or add a short addendum. The threshold is factual verifiability, not debate. The correct policy number is the correct policy number.

Supplemental reports handle things like a witness who contacted the agency after the original was filed, additional evidence like a surveillance video that surfaced later, or a mechanical inspection of a vehicle that identified a defect. The supplemental report is a separate document that adds to the record without replacing the original. It carries its own date, its own author, and its own narrative, and it joins the file.

What amendment processes almost never do is retroactively change the officer's opinions on contributing circumstances or driver action. An opinion recorded in good faith at the scene remains the opinion recorded, even if additional evidence later shifts how the claim gets resolved. A party who believes an opinion was wrong usually works through the civil claim process rather than through an amendment to the report, which is why the lane page on how fault actually gets decided describes the broader process rather than treating the report as the final word.

Each state defines who can request an amendment and how. For a party in a crash, an attorney licensed in your state can walk through what your state and agency allow. This guide stops short of describing a specific amendment procedure because the differences across jurisdictions are too wide to generalize responsibly.

A short catalog of the common clerical mistakes helps readers spot them in their own reports. VIN transposition: one or two characters in the 17-character string swapped or wrong. License plate transposition: similar, in the shorter plate string. Policy number transposition: the easiest kind to produce when the officer is reading an unfamiliar carrier abbreviation. Date typos: a 03 that should be 30, usually from quick typing. Name misspellings: common when the officer heard the name once and did not confirm the spelling. Address misreads: common on older driver's licenses where the address has been updated by sticker.

Each of these is a clerical error with a clean amendment path. Finding them is a matter of comparing the fields on the report against the primary documents: the driver's license, the registration, the insurance card. A ten-minute pass through those three documents catches most of what the officer may have transcribed slightly wrong at the scene.

Non-clerical mistakes are harder. A diagram that places an impact in the wrong lane, a narrative that misstates which driver spoke first, a contributing-circumstance code that the recipient disagrees with: these are not simple typos. The amendment process for them is narrower, the burden of evidence is higher, and the practical path often runs through the civil claim rather than through a report revision. The honest advice remains the same here: an attorney licensed in your state is the right reader for how your jurisdiction handles the difference between a clerical error and a disputed opinion.

One mistake that is not actually a mistake is a report that leaves the fault determination open. Many officers decline to characterize fault on the face of the report, writing a factual record and letting the contributing-circumstance codes speak for themselves. This is not an omission. It is often a professional choice to limit the opinion content on the record. The absence of an explicit fault statement is not evidence of incomplete work.

Common clerical error	Where to spot it	Clean fix path
VIN transposition	Vehicle block, 17 characters, compare to door jamb or dash	Short written request, supporting photo of the VIN plate
License plate transposition	Vehicle block, compare to the plate itself	Short written request, supporting photo of the plate
Policy number transposition	Insurance block, compare to the declarations page	Short written request, declarations page attached
Date typo	Header block, cross-check against calendar	Short written request, no supporting document often needed
Name misspelling	Driver block, compare to driver's license	Short written request, driver's license copy attached
Address misread	Driver block, compare to current license or utility bill	Short written request, supporting document attached

Common clerical errors and the clean amendment path. Non-clerical disputes travel a narrower route and may belong in the civil claim rather than in a report amendment.

How insurers and attorneys actually read it

Insurers and attorneys read crash reports differently than first-time readers do, and knowing their reading changes what the document is useful for. An adjuster typically reads the report once for identification and factual record, confirming the parties, the vehicles, and the policies against the claim as filed. Then they read it again for liability signals: diagram, contributing circumstances, citations, witness statements. Then a third time, more selectively, when a specific point in the claim turns on a specific fact.

Attorneys follow a similar pattern with a different emphasis. The first read establishes who the parties are and whether the identifications match the attorney's existing information. The second read looks for every fact the report records that supports or contradicts the client's account. The third read, often with the file opened to specific pages, looks for the places where officer opinion and physical evidence may diverge, and where a reconstruction or an expert witness could be useful.

Both readers treat the officer's work with respect and with specificity. Officers do their work in weather, under time pressure, with information that is sometimes incomplete at the scene. Their records are usually careful. Their opinions are usually reasonable. Taking both seriously, without treating either as the final word, is how experienced readers get the most out of the document.

What experienced readers do not do is argue with the report by posting on forums. The report is the record. The claim is the forum where the record gets weighed. A citizen's dispute with an officer's opinion, if it has merit, is weighed in the claim process or in formal review channels, not in correspondence attached to the report itself. The lane page on what happens when you talk to a collision attorney describes how an attorney walks a client through the pieces of a claim, including the report.

One habit worth borrowing from experienced readers. They read the report twice before writing anything in response. The first pass is for identification: parties, vehicles, policies, dates. The second pass is for substance: what the officer saw and what the officer concluded. Only after the second pass do they start a response, a question, or a comparison against the client's account. That short discipline avoids most of the overreactions that first-time readers can have in the week after a crash.

What the report does, and does not, decide

Everything above returns to one question. What does the report decide? Narrowly, it decides nothing by itself. It records. It carries opinions. It becomes evidence. It moves claims. In a civil lawsuit, parts of it may be admitted and parts of it may be excluded under state rules of evidence. Attorneys brief these questions in motions. The lane page the timeline maps the moments where the report lands in the broader process.

What the report does well is anchor the facts of the crash in a document written near the time of the crash by someone with no stake in either driver's claim. That alone is valuable. A record created at or near the time of the event by a neutral party carries weight that a party's own later memory often cannot. The report is also the fastest way for an insurer to identify the vehicles, the drivers, and the policies, which is why obtaining it early matters.

What the report also does well is provide a stable reference across the many conversations a claim produces. Insurers, attorneys, body shops, towing companies, rental agencies, and medical providers each handle one piece of the aftermath, and each one of them can ask for the report's identifying details to confirm which crash is being discussed. Having the report in hand, and knowing the fields in it, means the party can answer each of those identification questions with the same accuracy every time. Small discipline, surprising payoff.

What the report does imperfectly, honestly, is capture the human part. The fright of the collision, the physical response of a passenger who was uninjured but is now shaken, the uncertainty of a driver who cannot remember the moment of impact: none of these have a code on the form. They are left to the narrative, where some officers capture them and some do not. The absence of these details from the report is not evidence they did not happen. The medical record, the party's own documentation, and the attorney's intake interview are where those details get captured and preserved for a claim.

What the report does not do is substitute for a complete investigation when a claim is serious. Serious claims involve additional work: witness interviews, scene photographs, expert reconstructions, vehicle inspections, cell phone records where permitted, surveillance video from nearby businesses, and medical records that build the injury picture. The report is a starting point. The file is the destination.

And what the report never does is write the policy that pays. Coverage comes from a declarations page, from the policy packet behind it, and from the state law that governs the contract. The report describes the crash. The policy decides what the crash means for coverage. Reading both together, with an attorney where the claim warrants, is how the two documents answer most of the first few weeks' questions, and reading them in that order is how most experienced readers handle a new claim file as it opens.

One final discipline. The report is a snapshot taken within hours of a crash by someone whose job that day was to write it. Treat it with the respect that document deserves, and treat the people in it, including the officer who wrote it, as professionals doing a demanding job in difficult conditions. The report moves claims because it is often careful, consistent work. The report does not resolve claims because the full picture requires more documents, more time, and sometimes a court. Both of those statements fit in the same reading, and holding them together is what a professional reader does.

If this is your week

Get the report. Read it carefully. Then talk to a professional.

One request covers the attorney, the tow, the repair, and the rental. It costs you nothing, ever.

Get help now How it works

Questions people actually ask