The Deposition as a Discovery Tool

Building the House

Apr 23, 2026

THE FORENSIC ENGINEER'S FIELD MANUAL | Post 5 of 13

Facts Build the House. Logic Defends It. The Jury Decides Whether They Believe It.

Act I — Building the House

In the last post we covered chain of custody and why the first photographs taken at a scene control the evidentiary record from that point forward. Today: the deposition — what it demands of the expert giving one, and what it reveals to the expert reading one. Next Thursday: What Are They Saying — reading between the lines of an opposing expert's testimony.

The Deposition as a Discovery Tool

Three people in the room. Three different stories. One of them is yours.

The Friendly Room

The deposition your own counsel takes is conducted under friendly conditions. Your law firm arranged it. They will ask questions that support their case. The atmosphere is professional and calm. Nobody is trying to destroy you.

And none of that means you are safe.

There are three parties to every litigation — the defendant, the plaintiff, and the expert. They never fully share the same story. The defendant has what happened to them. The plaintiff has what happened to them. The expert has what the evidence shows.

Those three stories overlap. They are never identical.

Your job in a deposition is not to reconcile the other two stories. It is to tell yours — the engineering story — cleanly, completely, and without letting either side pull it off its axis. Including your own side.

When Your Own Counsel Asks the Wrong Question

You may see the questions ahead of time. That is standard practice and it serves a legitimate purpose — you are not there to be surprised, you are there to give accurate testimony that supports the case as the engineering evidence supports it.

But sometimes a question tries to bridge a hole.

The attorney has a gap in their case. The forensic data does not fully close it. And the question — carefully worded, professionally delivered in that friendly room — is designed to stretch the engineering truth just far enough to fill the space. And your name gets hung on the bridge.

This is the hardest moment in a forensic engagement. Not the opposing cross-examination. Not the hostile double negative at trial. This moment — in the friendly room, with your own counsel waiting for an answer that helps their case.

Your credibility is not the attorney's asset to spend. It is yours. And it is the only thing that makes your testimony worth anything to anyone in that courtroom.

If the question stretches beyond what the evidence supports, you answer what the evidence supports. Precisely. In the language of the engineering. Nothing more.

What a Correction Costs You

A lawyer does not hear a correction as a clarification.

They hear it as a full rebuttal.

The moment you say — in any deposition, on any question, under any condition — "what I meant was" or "to clarify my earlier answer" — you have just told every person in that room that your prior testimony cannot be fully trusted. Not partially. Fully. Every answer you gave before that moment is now available for challenge.

This is why consistency of framework is not a preference. It is the discipline that protects everything you have said and everything you are about to say. Answer in the same terms. Use the same language. Stay inside the same boundaries every time.

Because the engineer who answers consistently — even under questions designed to stretch the forensic truth — never gives the correction that unravels the whole testimony.

No corrections. No clarifications. No edits.

Answer what was asked. In your framework. Then stop.

Reading the Opposing Deposition

Now you are back at your desk. The opposing expert has given their deposition and you have the transcript.

Most people read a deposition looking for the wrong answer. The answer that is factually incorrect, technically unsupportable, demonstrably at odds with the physical evidence. Those mistakes exist. They are not where the most useful information lives.

The gap never appears in the first sentence.

Watch the third and fourth questions. Watch where the attorney circles back — where they return to something they asked earlier, slightly reframed. That pattern is not accidental. The attorney is working around something. A weakness in the opposing expert's analysis. A finding that doesn't hold under a different line of questioning. A conclusion that required the expert to step outside their own evidence.

The gap shows in the pattern of the questions, not in any single question. The attorney who designed those questions knows exactly where the weakness is. Your job is to find it in the same place they found it — and hand it to your counsel as a fact, not a suspicion.

The Engineering Story Is the Only Story You Tell

Three people. Three stories. One of them is yours.

The defendant's story is about what happened to them. The plaintiff's story is about what happened to them. Your story is about what the evidence shows — what physically occurred, in what sequence, for what reason, to what effect.

Your story does not require the other two to be right or wrong. It requires the evidence to be followed wherever it leads. It requires the language to stay inside the engineering. It requires the framework to hold from the first answer to the last.

That consistency is not stubbornness. It is the thing that makes your testimony worth believing.

And it is the thing that makes the opposing deposition readable — because the expert who drifted from their framework, who answered outside their evidence, who accepted a question's premise when the premise wasn't supported — left a pattern in the transcript that a prepared forensic engineer can find.

Read the pattern. Tell your story. Make no corrections.

Next Thursday: What Are They Saying — reading between the lines of an opposing expert's testimony, and what the questions they chose to ask reveal about the gaps in their analysis.

The Inventor's Mind Blog's Substack

Discussion about this post

Ready for more?