An expert witness report is written for a court, not a client. This guide sets out a workflow that takes an automotive engineering practice from instruction to a signed, compliant report, and keeps it consistent across engineers and defensible years later.
Under Part 35 of the Civil Procedure Rules an expert's duty is to help the court on matters within their expertise, and that duty overrides any obligation to the person who instructed or is paying them. Practice Direction 35 sets out what the report must contain: the expert's qualifications, the literature relied on, the facts and instructions material to the opinions, who carried out any tests and under whose supervision, the range of opinion where one exists and the reasons for the expert's own, a summary of conclusions, a statement that the expert understands and has complied with their duty, and a statement of truth in the prescribed form.
An automotive engineer is instructed on collision mechanics, low-speed impact disputes, repair quality, vehicle condition, pre-accident value and whether a repair estimate was reasonable. The instructing solicitor, the opposing expert, and eventually a judge will read the report looking for exactly the things PD 35 lists, and a report that is expert in its engineering but loose in its structure loses on the structure.
The operational problem is volume. A practice handling hundreds of instructions a year has engineers inspecting in different places, writing in different styles, and holding evidence on different devices. Without a process, the report that reaches the court depends on which engineer happened to take the instruction, and when a report is challenged the practice has to reconstruct how it was produced.
Treat each instruction as a case that moves through fixed stages: instruction and conflict check, documents in, inspection, analysis, draft, review, signature and issue, then questions and any joint statement. The letter of instruction, the documents disclosed, the inspection findings, the photographs and the calculations attach to the case as the work is done, so the report is written from the case rather than from memory.
The report itself is generated from the case in the structure PD 35 requires, from one template the practice owns. The engineer's qualifications come from their record, the instructions and material facts from what was recorded at intake, the tests and who performed them from the inspection stage, the photographs from the evidence on the case. The engineer writes the opinion; they do not rebuild the scaffolding every time.
Review is a named stage with a checklist drawn from the Practice Direction, and a report cannot issue without it. Issue records who received the report and when. Written questions under CPR 35.6, requests for a joint statement and any supplementary report attach to the same case, so the whole history of the instruction is in one place when the practice is asked about it.
Follow these steps to run every instruction the same way, from the first letter to the signed report and whatever follows it.
Record the instructing party, the parties to the dispute, the vehicle, the issues the expert is asked to address, whether the appointment is single joint or party-appointed, the deadlines and the fee basis. Run the conflict check against the practice's previous instructions before anything else happens, and record the result.
Disclosed documents, repair estimates, photographs from the parties, engineer's reports already served, police reports and vehicle history arrive in every format. Read them into the case with document extraction so the key facts, dates, figures and vehicle identifiers are fields rather than PDFs, and the engineer can see what was disclosed and when.
Whether the inspection is physical or desktop, record it against a form that mirrors the report: identification, condition, damage by area, measurements, tests performed and by whom, and photographs attached to each observation. The facts the report relies on are then recorded at the moment they were observed.
The draft is produced from the case: qualifications, instructions, material facts, documents relied on, inspection findings, tests, analysis, the range of opinion and the expert's reasons, conclusions, the duty statement and the statement of truth. The engineer writes and edits the opinion and the reasoning within that structure.
A second engineer or a reviewer checks the report against the Practice Direction: every required element present, the instructions stated accurately, each opinion reasoned, the range of opinion acknowledged where it exists, photographs and documents cited correctly, and the statements in the prescribed form. The review is recorded with the reviewer's name and what changed.
The engineer signs; the report issues to the instructing party with the date and recipient recorded. The case then holds the issued version as the version of record, separate from drafts, so there is never doubt about what was served.
Written questions under CPR 35.6, the discussion between experts and the joint statement, and any supplementary report are stages on the original case, with their deadlines and their own review. The practice can see what is outstanding on every instruction and the engineer has the whole history in front of them.
The judge and the solicitors are the audience. Explain the mechanism, define the terms, and put the conclusion where it can be found. Technical precision and plain language are not in tension.
Record what was observed, what was told, and what was concluded as distinct things. The report must make the distinction, and a case that holds them separately makes the report honest by construction.
Qualifications, memberships, CPD and the categories of dispute each engineer is competent to address belong on a record the report draws from, so the qualifications section is never out of date and the instruction goes to someone competent for it.
Each photograph on the case has a reference, a timestamp and the observation it supports. The report cites the reference. A folder of images with no link to the findings is a weakness the other side will find.
Where competent engineers could differ, say so, and give the reasons for the expert's own view. A report that admits no range is less credible, not more.
Drafts, the issued version, questions, answers and the joint statement, with dates, on one case. When a report is questioned years later, the history is the defence.
Set turnaround targets by instruction type and client.
Every assessment is a number somebody will argue with. This guide sets out a workflow that gets a practice from instruction to an estimate it can stand behind, consistently across assessors and at volume.
automotive assessmentMost of what a vehicle assessment relies on is a photograph. This guide sets out what to capture, how an image becomes evidence rather than illustration, how to treat images other people supply, and how to keep them so they still prove something years later.
automotive assessmentA practice with engineers in the field lives or dies by who gets which job and how fast it comes back. This guide sets out how to allocate by competence, location and capacity, set turnaround targets that mean something, and see the whole network at once.
Bring us a live instruction and we will show you what it looks like as a case: the documents in, the inspection form, the draft in the Practice Direction structure, the review and the issued report.
