Skip to content
Got the discovery packet? What a careful reader checks in the report, the video, and the breath logs
Kinzua Walleye

Got the discovery packet? What a careful reader checks in the report, the video, and the breath logs

A plain walk through the documents that arrive in a Washington DUI discovery packet, and what an experienced reader looks for in each one.

One person's working-out of how impaired driving charges move through Washington courts, written down so the next person can ask better questions before hiring anyone.

01

Two records of the same night

The written report and the recorded video are separate accounts of the same events, produced hours apart. Comparing them line by line is the first useful task in any discovery review.

02

CAD dispatch timestamps

Computer-aided dispatch entries fix the time a stop was called in, when backup arrived, and when transport began. They are the closest thing in the file to an independent clock.

03

Late camera activation

Body cameras are sometimes switched on after a contact has already begun, leaving the initial exchange unrecorded. Whether that gap was policy, error, or ordinary lag is a fair question to put in writing.

Discovery in a Washington impaired driving case arrives as a stack, sometimes paper, more often a download link with a password taped to a letter, and the first thing worth understanding is that nothing in it is neutral. It was written or recorded by people building a case, and it will read that way. That does not make it useless to the defense. It makes it a record that can be checked against itself, one document against another, and the checking is where most of the useful work in a misdemeanor DUI actually happens.

The narrative report, read against the timestamps

The officer's report is a story told after the fact, usually hours after, and it follows a shape: the reason for the stop, the observations at the window, the decision to ask for field tests, the arrest, the transport, the breath test. A careful reader does not argue with the adjectives. Instead the report gets laid alongside the computer-aided dispatch log, the arrest paperwork, and the video timestamps, and the question is whether the sequence holds. When the report says the driver was asked to step out at a certain point, and the dispatch entry puts the stop three minutes later, that gap is worth understanding before anyone calls it a discrepancy.

Dash and body camera footage, watched more than once

Video is the part of the file that most often changes how a case is valued, in either direction, and it needs to be watched at full length rather than skimmed at the interesting moments. The audio matters as much as the picture: what the driver was actually asked, in what words, and whether the answer was a slur or a wind-buffeted microphone. Camera angles rarely show the feet during the walk-and-turn. That absence is itself a fact about the record. Missing footage, a camera activated late, a unit whose recording was not preserved, all of it gets noted and asked about in writing rather than assumed away.

Breath test instrument logs and calibration records

The breath result is a number, and the number depends on a chain of maintenance that has its own paperwork: the instrument's certification, the quality assurance procedures, the simulator solution batch, the thermometer records, and the log of tests run on that machine around the same date. The National Institute of Standards and Technology is responsible for the measurement standards and reference materials that sit underneath forensic breath alcohol testing generally, which is why the paper trail exists at all. A careful reader checks whether the records supplied actually cover the date of the test, whether the solution batch was within its certified period, and whether the printed ticket matches the log.

The conditions the field tests were given in

Field sobriety tests are standardized procedures, and standardization is the whole argument: the tests mean something only when administered the way they were validated. So the file gets read for conditions. Surface slope and texture, footwear, the driver's weight and age and any injury mentioned at the scene, traffic passing at speed, headlights aimed at the subject, rain, a shoulder that slopes toward a ditch. Also whether the instructions were given in full, demonstrated, and confirmed as understood. None of this makes the tests disappear. It changes how much weight anyone should place on them.

How the checking turns into motions or leverage

A defect found in discovery becomes one of three things, and honest counsel will tell you which. It becomes a suppression motion, argued under Washington's criminal rules, asking a judge to keep evidence out because the stop, the arrest, or the test was defective. It becomes leverage, a problem the prosecutor would rather not litigate, which is discussed in negotiation and sometimes moves a charge to a lesser offense. Or it becomes nothing much, a wrinkle noted and set aside. What it never becomes, before a judge has ruled, is a promised outcome, and a quote that comes bundled with one is telling you something about the person quoting.

The practical thing a client can do is read the file too. Not to second-guess the lawyer, but because you were there and no one else in the room was, and the detail that explains a strange three minutes on the video is usually sitting in your memory rather than in the paperwork.