Workflow
How to Structure a Legal Case Report: A Step-by-Step Framework
Most case reports are rewritten not because the analysis was wrong, but because the structure was decided while writing. Here is a framework that settles it beforehand.
A case report has one job: let a reader who has not seen the file reach a reliable view of it, and check that view against the source. Everything about the structure follows from that. Sections are not decoration; each one answers a question the reader will otherwise have to ask.
The framework below is deliberately generic. It works for a dispute analysis, an internal case assessment, an expert's factual section, or a handover memo — because the underlying questions do not change much even when the format does. Adapt the headings to your house style and your tribunal's expectations; keep the order.
Key takeaways
- Decide the structure before you read, not while you write.
- Separate what happened (chronology) from what each side says about it (positions). Merging them is the most common structural failure.
- Every factual assertion carries a source reference. No exceptions, including in the executive summary.
- Keep facts and evaluation in different sections, clearly labelled.
The eight-part framework
Scope and instructions
What you were asked to do, by whom, and as of what date. State the documents reviewed, the period covered, and — critically — what you were not asked to address. A reader who knows the boundary stops treating a gap as an oversight. Also record any limitation: documents not provided, access not granted, a witness not available.
Executive summary
Written last, read first. Three to eight findings, each stated as a conclusion rather than a topic. “The variation was instructed orally on 4 March and confirmed in writing on 19 March” is a finding; “Variation instructions” is a heading. Cross-reference each to the section where it is supported.
Parties and relationships
Who is involved, in what capacity, and under which contractual instrument. Include corporate relationships, changes of name, assignments, and the roles of individuals who appear repeatedly in correspondence. Written once here, this saves the reader from re-deriving it on every page.
Chronology of events
A single, neutral, dated sequence of what happened, with a source reference on every entry. Neutral means it contains events, not characterisations: an email was sent on a date; whether it constituted notice belongs in the issues section. Build it from the documents rather than from either side's narrative, and it becomes the backbone the rest of the report hangs on.
Positions of the parties
Each side's case, set out in its own terms and separately from the chronology. Give each position its pleading or correspondence reference. The discipline here is to state the other side's case well enough that they would recognise it — a report that only steelmans one party is not usable for decision-making.
Evidence and documents
An index of what supports what: the document, its date, its provenance, and the assertions it bears on. Flag the three states that matter — supported, unsupported, and contradicted — and note documents that are referred to but were never produced. That last category is often the most valuable page in the report.
Issues in dispute
The list of questions the decision-maker actually has to answer, each with the competing positions and the evidence bearing on it. This is where the report earns its keep, because it converts a pile of material into a finite set of decisions. Keep issues genuinely separable; if two collapse into one, merge them.
Quantum
Where money is claimed: the heads of claim, the amounts, the basis of calculation, and the evidential support for each. Present the claimed figure, any admitted or agreed figure, and the difference, with the reason for the difference. Keep the arithmetic reproducible — a reader should be able to rebuild the total from the components.
Note
If a section would be empty, keep the heading and write one line explaining why. “No quantum claim has been advanced as at the date of this report” tells the reader something. A missing section tells them nothing, and they will wonder.
The rules that make the structure hold
One assertion, one source
Every factual statement carries a reference to where it came from — document, page, and where relevant paragraph or timestamp. This is not formality. It is what makes the report checkable, and checkability is the difference between a document a tribunal or client can rely on and one they have to verify from scratch. It also protects you: eighteen months later, the reference is the only thing that reconstructs your reasoning.
Facts and evaluation live in different rooms
Keep the chronology, the positions, and the evidence index descriptive. Put assessment in the issues section, or in a clearly marked commentary block. Reports that interleave the two are hard to reuse, hard to update when a new document lands, and easy to attack — because a single contested evaluative sentence casts doubt on the factual sentences around it.
Write the chronology from documents, not from submissions
It is much faster to lift the sequence from a party's statement of case, and it is the shortcut that most often has to be undone. Submissions are argument with dates attached; they omit what does not help. Build from the primary material and the omissions become visible — which is frequently the finding.
Make the report updatable
Case reports are rarely written once. Number sections and paragraphs, keep the evidence index in a form you can add rows to, and avoid prose that has to be rewritten wholesale when a late document arrives. A structure that absorbs new material is worth more than an elegant one that does not.
Common structural failures
- Chronology merged into positions. The reader can no longer tell what is agreed from what is asserted, and neither can you on the second pass.
- An executive summary of topics rather than findings. If it survives unchanged when the conclusions reverse, it is a table of contents.
- Evidence discussed inline and never indexed. Fine while you hold the file in your head; unusable to anyone else, including yourself later.
- Silent gaps. A document referenced but never produced is a finding. Left unmentioned, it reads as an oversight.
- Quantum without a reconstructable calculation. A total nobody can rebuild from its components will be challenged, and you will rebuild it under time pressure.
- Undated versions. Every report needs an as-at date, because the underlying file keeps moving.
Where the time actually goes
Ask anyone who writes these regularly and the answer is consistent: the writing is not the bottleneck. The bottleneck is everything before it — reading several thousand pages, building the chronology, mapping which document supports which assertion, and reconciling what a witness said in a hearing against what the correspondence shows.
That pre-writing phase is structured, repetitive work, and it is the part that benefits most from being done systematically rather than by memory. If the chronology, the parties table, the evidence index, and the issues list already exist when you sit down, the report largely writes itself — because the framework above is really a description of those four artefacts, arranged for a reader.
For the practical mechanics of compressing that pre-writing phase, see five ways to cut case file review time without cutting corners. And before routing any of it through an AI tool, check what the confidentiality rules require.
Keep reading
Workflow
5 Ways Paralegals Can Cut Case File Review Time Without Cutting Corners
Speed in file review comes from doing fewer passes over the same pages, not from reading faster. Five techniques that hold up when the file is 4,000 pages.
AI & Data Privacy
Why Pasting Case Files Into ChatGPT Could Violate Client Confidentiality
A general-purpose chatbot is a third party. The moment a client document goes into one, you have made a disclosure decision — whether or not you thought of it that way.