Legalnaut

CASE PREPARATION 2026-10-05 6 MIN READ

How to prepare cross-examination from the case file

A cross-examination preparation checklist built from the documents, and why the inconsistencies have to be lined up before the witness gives evidence.

The witness gives evidence tomorrow and the inconsistencies sit in forty documents nobody has lined up. What a cross-examination file needs, why fairness demands it, and where manual prep fails.

The witness gives evidence tomorrow at ten. Their statement runs to nineteen pages. Somewhere in the forty documents behind it are the email that puts them in a different city on the day of the meeting, the board minute that records a figure they now say was never discussed, and an attendance note from your own side that half supports them. Nobody has lined these up against the paragraphs of the statement. That is the job tonight.

This post covers what a cross-examination file needs to contain when you build it from the documents, and where the manual version breaks down. The practice is broadly the same wherever witnesses are questioned by counsel, but the rules on how and when you may confront a witness differ between courts. Check the rules of the court or tribunal you appear before. This is general information, not legal advice on any particular trial.

Why the documents carry the weight

In many systems the witness's written statement or affidavit now does most of the work of evidence in chief, so the witness will say little at the hearing that you have not already read. Your time with them is questioning, and courts and tribunals increasingly cap it. You will rarely get to cover everything, so the choice of points matters as much as the points themselves.

The documents also tend to decide the facts. Memory drifts, gets rebuilt in the retelling and is shaped by the process of preparing a statement. A contemporaneous email was written before anyone knew there would be a dispute. When the two conflict, most tribunals give real weight to the paper, and the most useful questions are usually the ones that take the witness to a document and ask them to deal with it.

Fairness: put your case before you rely on it

Across very different systems, one idea recurs: if you intend to ask the tribunal to disbelieve a witness on a point, the witness should have had a fair chance to answer it. The procedural form varies. Two labelled examples show the range:

  • Common-law courts (England and Wales, Australia and others). The rule in Browne v Dunn (House of Lords, 1893) requires a cross-examiner who will rely on contradictory evidence to put it to the witness, so they can explain it. The UK Supreme Court restated it in TUI UK Ltd v Griffiths [2023] UKSC 48 (November 2023), treating it as a matter of overall fairness rather than a rigid rule.
  • US federal courts. Federal Rule of Evidence 613(b) generally bars extrinsic evidence of a prior inconsistent statement until the witness has had an opportunity to explain or deny it, although the judge has discretion (FRE 613, as amended December 2024).

Where the judge leads the questioning, as in many civil-law systems, you may not cross-examine in this form at all, but you will still need to point the court to the inconsistencies and the documents that show them, usually in writing and in advance. Whatever the local form, the practical consequence is the same: you need the full list of inconsistencies before the hearing, not after the witness has left.

What the file has to give you before you write a question

A cross-examination checklist built from the case file needs, at minimum:

  • Everything the witness has said, in every form: statement, exhibits, pleadings they verified, correspondence they wrote, interview notes, earlier affidavits.
  • Everything said about them by other witnesses and in other documents.
  • The events they took part in, in date order, so a timing problem is visible. The chronology does much of this work if you have one; see how to build a case chronology from 900 emails.
  • Each inconsistency as a pair: the passage in the statement and the passage in the document that conflicts with it, each with document and page.
  • A judgement on each pair: is it a real conflict, a difference of wording, or something the witness can explain away in one sentence?
  • The points that help you, which you may want the witness to confirm before you challenge anything.
  • The questions the file cannot answer, so you know where you are exposed.

The fifth item is where preparation usually goes wrong. Plenty of apparent contradictions dissolve on inspection: a different date format, a draft superseded by a later version, a translation that shifted a word, two people describing the same meeting from different ends of the table. The method for testing a candidate pair is covered in how to find contradictions in witness statements. For cross-examination the question sharpens: would you be content for the judge to watch the witness answer this one?

Why doing it by hand is slow and risky

Illustration only, not a real matter. Take a contractor's project manager whose statement says the variation was agreed orally on 14 March. The file holds his own email of 16 March asking for "sign-off on the variation we discussed", a site diary entry for 14 March recording him off site, and a later letter from his lawyers describing the agreement as made "in or around March". Three documents, each saying something slightly different, filed under three custodians. Found separately, each looks minor. Put side by side against paragraph 22 of his statement, they are a line of questioning.

The manual version of this means reading every document for every witness, keeping a running table, and carrying the page references by hand. Three things go wrong under time pressure:

  1. Coverage. The document you did not reread is the one with the answer in it. Scanned bundles make this worse, because a scan without a text layer does not show up in a keyword search at all; see why your served bundle is invisible to search.
  2. Pin-cites. At the hearing you need to take the witness, or the judge, to a page. A note that says "somewhere in the March emails" costs you the moment.
  3. Verification. A contradiction you have not checked against the original can turn in the witness's favour when they give the obvious explanation you missed.

From inconsistencies to an outline

With the pairs confirmed, the outline has a familiar shape: background you want to lock in, facts that help, facts that hurt, then the inconsistencies, each with its own sequence. The order you put them in and how you close each one off is a matter of advocacy, of the particular witness and of what your court allows, so this post leaves it there.

Two points about the outline matter whatever your style or system. Every question should point to a line in the file, so that when the witness asks "where does it say that?" you can answer with a page. And the pairs you have not confirmed belong on a separate list as risks, so you decide consciously whether to raise them rather than drifting into them.

This is the part Legalnaut is built for. It assembles a witness dossier for one person (their statements, what others said about them, the documents they wrote, the events they took part in, and the statements the records contradict), each line with document, page and quotation. From the dossier it drafts an examination outline with an impeachment sequence for each inconsistency, and lists the unverified ones as risks. Legalnaut suggests the contradictions, but only a lawyer confirms them.

Create your account and build a witness dossier for your next cross-examination on a real matter. No card needed.

Legalnaut does this to your own case file: a chronology built from the documents, every finding showing the source it came from. See the plans.