Proof of evidence summaries an inspector reads first
The summary is the part of your proof the inspector reads first and the part you read aloud at the inquiry. Here is how to write one that works as the case rather than as an abstract.
The proof of evidence summary is the document the inspector reads first, reads most carefully and is most likely to have open during the round table session. Under the inquiry procedure rules, any proof longer than 1,500 words has to be accompanied by a summary, and at the inquiry your evidence in chief is normally given by reading that summary rather than the full proof. So the summary is not an abstract of the argument. It is the argument, in the form the decision maker will encounter it.
Consultants who treat it as a formality write a summary that lists the sections of the proof. Consultants who understand it write a summary that could stand alone as the case.
Why the summary carries the argument
Three things happen at an inquiry that make the summary decisive.
The inspector reads the proofs and summaries before the inquiry opens, with limited time and several sets to get through. The summary is what shapes the questions they arrive with. Then, in the session itself, the witness reads the summary aloud, which means the summary is the only part of the evidence spoken into the record in full. And in cross-examination, opposing counsel works from the summary's propositions, because that is where the case is stated in its shortest form.
A summary that hedges every proposition gives the inspector nothing to hold onto. A summary that overstates gives the other side something to dismantle. The target is a document where each paragraph states a position you can defend under cross-examination, in the order you want the inspector to think about them.
Length conventions and what to leave out
The 1,500 word threshold triggers the requirement, and it is not the target length. On a proof of 8,000 to 12,000 words, a summary of around a tenth is conventional, which means 800 to 1,200 words of tight prose.
What goes in: the conclusion, the two or three propositions that produce it, the policy provisions that matter with their edition stated, the decisive facts, and the answer to the reason for refusal. What stays out: methodology description, background history, site description beyond a sentence, quotation at length, tables, and anything the other side has already agreed in a statement of common ground.
The commonest failure is a summary that spends 300 words describing the site and the planning history before reaching an argument. The inspector has the officer report and has done a site visit. Start at the point in dispute.
Never introduce material in the summary that is not in the proof. It will be noticed, and it invites an application to adjourn.
Structuring the main proof behind it
The proof and its summary should be written as a pair, and the cleanest way to do that is to write the summary first as a skeleton, then expand each proposition into a section of the proof.
- State the issue as the inspector will frame it, using the wording of the reason for refusal or the main issues identified at the case management conference.
- State your conclusion on that issue in one paragraph.
- Set out the policy framework, with the edition of the Framework named and the local plan policies quoted only where the wording is doing work.
- Set out the facts you rely on, each tied to an appendix or an agreed document.
- Deal with the contrary case explicitly, rather than leaving the inspector to infer your answer.
- Reach the conclusion again, in the same words as at step two.
Numbered paragraphs throughout the proof, with the summary cross-referring to them, saves everyone time. "Summary paragraph 4, proof paragraphs 5.12 to 5.31" lets the inspector move between the two without hunting.
Keep to your own discipline. A planning witness who strays into highway capacity or acoustics is offering evidence they cannot defend, and the point will be taken in cross-examination rather than politely ignored.
Appendices and cross-referencing
Appendices exist to prove facts, not to bulk out the case. Every appendix should be referred to at least once in the proof text, and anything never referred to should come out.
| Material | Where it belongs |
|---|---|
| Policy extracts in dispute | Core documents list, not an appendix |
| Agreed technical data | Statement of common ground |
| Survey results you rely on | Appendix, with the methodology in the proof |
| Appeal decisions cited as indicative | Appendix, with the relevant paragraphs marked |
| Correspondence with the authority | Appendix, complete rather than extracted |
Appeal decisions need care. They are indicative of how inspectors have approached an issue, not binding precedent, and a proof that treats one as though it settles the matter reads as overreach. Mark the paragraphs you rely on and say what the factual parallel is.
Aligning with the statement of case
The statement of case sets the boundaries. It has to contain the full particulars of the case you intend to put, and evidence outside it is vulnerable.
Read the statement of case again before finalising the proof, and check three things. That every argument in the proof has a home in the statement of case. That nothing in the statement of case has been quietly abandoned without explanation, because the inspector will notice the gap. And that the documents you now rely on were listed or have since been added to the core documents by agreement.
Where the case has in fact moved, say so and explain why, ideally before the proofs are exchanged. An honest note about a changed position costs less than the same change discovered during cross-examination. The discipline of going back to the refusal reasons and working forward, set out in reading a refusal notice and turning it into a plan, applies at this stage too.
Reading the summary aloud at the inquiry
Write it to be spoken. Short sentences, one idea per paragraph, no nested subclauses, no abbreviations the inspector has not already seen spelled out.
Time it. A thousand words read aloud at a sensible pace takes around seven or eight minutes, which is roughly what an inspector expects for evidence in chief. Anything much longer and you will be asked to take it as read, which loses you the advantage the summary was meant to give.
Practise the transition to cross-examination. The last paragraph of the summary is the one sitting in the room when the first question arrives, so make it the proposition you most want to defend rather than a courtesy.
Third parties and interested persons also speak at inquiries, and their material is dealt with differently, as set out in the guide to what objectors can do once a planning appeal starts.
A drafting checklist
- Summary under about a tenth of the proof, and comfortably readable in eight minutes
- Conclusion stated in the first two paragraphs and repeated at the end in the same words
- Every proposition traceable to a numbered paragraph of the proof
- Framework edition stated wherever a policy is cited
- Nothing in the summary that is absent from the proof
- Contrary case addressed, not ignored
- Appendices all referred to in the text, and none included that are not
- Statement of case checked against the proof for gaps in both directions
- No evidence outside the witness's own discipline
- Read aloud once, out loud, before it is sent
Illustrative example: a proof of 9,400 words on a Green Belt case produces a summary of 980 words. The first paragraph states that the proposal is inappropriate development and that the other considerations clearly outweigh the harm. The next four paragraphs take each limb of that conclusion. The final paragraph returns to the balance in the same words as the first. The site description occupies one sentence. Details are illustrative.
Where a written representations appeal is the procedure, there are no proofs at all, and the appeal statement carries everything. PlanScope drafts the Planning Statement and supporting documents that sit behind an appeal case, structured to UK planning policy, with missing facts flagged rather than filled in. Browse all 66 PlanScope report types to see what an appeal pack may need.
This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
When is a summary of a proof of evidence required?
The inquiry procedure rules require a summary where the proof exceeds 1,500 words. That is a trigger rather than a target length. On a proof of 8,000 to 12,000 words a summary of around a tenth is conventional, which means roughly 800 to 1,200 words of tightly written prose.
Is the summary what gets read out at the inquiry?
Normally yes. Evidence in chief is usually given by reading the summary rather than the full proof, which is why it needs to be written for speech: short sentences, one idea per paragraph and no abbreviations the inspector has not already seen. A thousand words takes about seven or eight minutes to read.
Can the summary contain anything not in the proof?
No. Introducing new material in the summary will be noticed and can prompt an application to adjourn. The summary should state propositions that appear in the proof, ideally with cross-references to numbered paragraphs so the inspector can move between the two documents without hunting for the supporting text.
How do appeal decisions get used in a proof?
As indications of how inspectors have approached a similar issue, not as binding precedent. Include the decision as an appendix, mark the paragraphs relied on, and state the factual parallel. A proof that treats one decision as settling the matter reads as overreach and invites the point being taken in cross-examination.
What is the relationship with the statement of case?
The statement of case sets the boundaries, since it must contain full particulars of the case to be put. Check that every argument in the proof has a home there, that nothing in it has been quietly dropped, and that the documents relied on are listed or have been added to the core documents by agreement.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.