Presenting daylight results so an officer can use them

A case officer writing a committee report needs three things from your daylight report. A statement of the criteria applied, a table showing every affected window against those criteria, and a plainly worded conclusion they can quote. Most reports supply the numbers and leave the officer to construct the other two, which is how a technically compliant scheme ends up with a weak paragraph in the officer report and an objector's summary quoted instead.

Presentation is not decoration on this kind of document. It is the difference between evidence that gets used and evidence that gets filed.

What the case officer needs from the report

Start from what the officer has to write. They need a sentence saying which properties were assessed and why, a sentence saying which standard was applied, a summary of how many windows and rooms meet it, a description of the exceptions with their magnitude, and a conclusion on whether the effect on living conditions is acceptable.

Give them those five things in that order, in the first two pages, before any methodology.

Officers are generalists working to a deadline, often with twenty other applications open. A 90-page report with the conclusion in section 8.4 and the results in appendix C will be read for ten minutes. Write the front end for those ten minutes.

Structuring results by property and window

Organise by neighbouring property first, then by floor, then by window. Number every window on a drawing and use those numbers everywhere, including in the appendices and in any objector correspondence you respond to later.

The window reference is the spine of the whole document. Where the survey drawings call it W12 and the results table calls it R3/2, nobody can follow the argument, and an officer who cannot follow it will not rely on it.

For each window, state the room it serves and how that was established. Internal access, external observation, an assumption from the floor plan, or a published plan from an earlier application. Officers and objectors both challenge room use assumptions, so declare them rather than defending them later.

Where internal access was refused, say so and state what was assumed instead. That is an ordinary limitation, not a weakness.

Showing pass, marginal and fail clearly

Use one table per property, with a consistent set of columns.

The recognised criteria come from the BRE guidance on site layout planning for daylight and sunlight, which sets a vertical sky component target of 27 per cent, treats a reduction to less than 0.8 times the former value as noticeable, and applies the same 0.8 proportion to daylight distribution within rooms and to annual probable sunlight hours. The 2022 edition is clear that these are guidelines to be applied flexibly, particularly in dense urban settings where the existing baseline is already low.

Colour or symbol coding helps, provided the key is on the same page as the table. Avoid three shades of the same colour, which print identically in a black and white committee pack.

State the number of windows assessed and the number meeting each criterion in a single sentence above the table. That sentence is what gets quoted.

Explaining exceedances without spin

Every report has some. Handle them directly.

Give the magnitude, not just the fact. A window falling from 30 per cent to 24 per cent vertical sky component is a different matter from one falling to 12 per cent, and an officer cannot weigh the harm unless the number is in front of them.

Give the context. Whether the room has other windows, whether the affected window sits under a deep balcony that already restricts light, whether the baseline is unusually high because the site has been vacant, and what the surrounding pattern of development already looks like.

Do not argue that a shortfall does not matter because the guidance is advisory. Officers hear that on every scheme and it reads as evasion. Argue instead that the residual condition is acceptable in this context, and say why.

Where the effect is clearly adverse, say so. A report that finds no harm anywhere invites the officer to commission their own review, and on a contested scheme that review will be paid for by you.

Illustrative example. A five-storey infill affects fourteen windows across two neighbouring houses. Twelve meet the vertical sky component target. Two fall to about 0.7 times their former value, both serving a rear bedroom that also has a second window facing the garden. Stating that in one sentence, with the numbers and the second aspect, gives the officer a defensible paragraph. Leaving it in an appendix gives an objector a headline. The figures are illustrative.

Cross-referencing drawings and appendices

Three cross-references carry most of the weight.

A key plan showing the site, every assessed property and the window numbering, at a scale that can be read when printed. A model view or axonometric showing the massing used, so the officer can see the modelled scheme matches the application drawings. And a short table mapping each appendix to the section that relies on it.

State the drawing numbers and revisions the model was built from. When the scheme is amended during determination, that reference is what tells everyone whether the daylight work still applies. Amendments that postdate the modelling are the most common reason a report has to be redone at the worst possible moment.

Keep the Design and Access Statement consistent with the daylight conclusions, and cross-reference between the two rather than restating results in both. Where amenity space is affected as well as windows, the shadow work belongs in a separate Overshadowing Study so that the two questions are not blurred together.

Common presentation failures

The recurring ones are easy to fix and rarely are.

• No summary table, so the officer builds one and gets it wrong.
• Window numbering that differs between the survey, the model and the results.
• Undeclared assumptions about which rooms are habitable.
• Results reported only as ratios, with no absolute values, so the reader cannot see whether a compliant ratio sits on a very low baseline.
• Mixing the existing baseline with a consented-scheme baseline without saying which is which.
• A conclusion written in the conditional, so that nobody can tell what the author actually thinks.
• Appendices that arrive as a separate file nobody uploads to the public register.

That last one costs more applications than any technical error. Check the council's website a week after submission and confirm that every appendix is there and legible.

Where the assessment is being prepared alongside the rest of the submission, keep the Daylight and Sunlight Assessment and the other amenity documents on the same drawing revisions, and check the whole supporting evidence base for consistency before anything is uploaded.

This is general guidance, not legal advice. Local policy on daylight targets varies, so 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.