Presenting daylight results a committee can read

A daylight and sunlight report on a mid-sized urban scheme can run to 300 pages of window-by-window tables, and a planning committee will spend perhaps four minutes on it. The daylight results presentation problem is therefore not one of accuracy. The numbers are usually right. The problem is that nothing in the document tells a councillor which numbers matter, and in that vacuum the objector's single red plan does the work instead.

What follows is about communication rather than method. The modelling is what it is.

Why raw tables persuade nobody

A vertical sky component table lists every window on every affected property, with the existing value, the proposed value and the ratio. On a scheme affecting six neighbouring buildings that is several hundred rows.

Three problems follow. A reader cannot tell which of those windows serves a living room and which serves a bathroom, so every row appears equally important. A reader cannot tell which failures are marginal and which are severe, because a ratio of 0.79 and a ratio of 0.31 sit in adjacent rows looking similar. And a reader who wants a total has to count, which nobody does, so the conclusion becomes whatever the report's summary paragraph asserts.

The objector's answer to 300 pages is one plan with red windows on it. It is usually misleading, because it treats every affected window as equivalent and ignores the room served. It works anyway, because it is legible.

Legibility is not a presentational nicety. It is the difference between your evidence being weighed and your evidence being skipped.

Selecting the rooms that matter

The guidance assesses windows, but amenity is experienced in rooms, and the first improvement any report can make is to reorganise the results by room and by room type.

Living rooms, dining rooms and kitchens used as living space carry the most weight. Bedrooms carry less, on the reasoning in the Building Research Establishment's guidance that daylight is less critical where the room is used mainly at night. Bathrooms, halls, stores, circulation and utility rooms should be identified and set aside, with the reason stated once rather than argued repeatedly.

Where a room is served by more than one window, report the room, not each opening. A living room with three windows appears three times in a raw table and can look like three failures when the room as a whole retains reasonable daylight.

This reorganisation has to be done honestly. Reclassifying a bedroom as a store because it currently holds boxes will be spotted, and it costs the report its credibility on everything else.

State the source of the room use information, whether that is a site visit, internal layouts from a previous application, or an assumption from the external appearance. Where it is an assumption, say so.

Colour coded plans and their pitfalls

A colour coded plan is the right response to an objector's colour coded plan, but it introduces its own risks.

Red and green read as fail and pass, and the guidance does not work that way: it sets out numerical benchmarks and expects flexibility in their application, particularly in dense urban contexts. A plan that shows any departure from a benchmark in red invites a committee to count red squares and stop there.

Better practice uses a graduated scale tied to the magnitude of the change, labelled with what each band means in plain words, and accompanied by a note that the benchmarks are guidance rather than standards. Bands based on the ratio to the former value, with a separate note on absolute retained values, give a truer picture than a binary.

Two practical points. Choose colours that remain distinguishable in greyscale and to colour-blind readers, because committee packs are often printed in black and white. And put the room use on the plan, so that a reader can see at a glance that the largest changes affect a bathroom and a landing.

Explaining percentage change plainly

The two figures that matter are the absolute value retained and the proportional change, and reports routinely lead with the one that flatters the scheme.

A window dropping from 8 per cent vertical sky component to 5 per cent has lost 37 per cent of its value, which sounds severe, but it was already well below the 27 per cent benchmark and in a dense city context. A window dropping from 32 per cent to 25 per cent has lost only 22 per cent, but it has crossed the benchmark. Neither figure tells the story alone.

Report both, in the same sentence, in plain words. Something like: this living room window retains 25 per cent vertical sky component, a reduction of just over a fifth from its existing value, which is slightly below the benchmark of 27 per cent.

Avoid the temptation to describe an outcome as "compliant". The guidance is advisory, and a reader who later discovers that a benchmark was not met will treat the word as a misrepresentation. Say what the figure is and what the benchmark is, and let the comparison stand.

The same care applies to sunlight, where annual probable sunlight hours and the winter proportion both matter and quoting only the annual figure hides a scheme that removes all winter sun.

Comparing against the right baseline

Baseline choice is where most of the argument actually is, and it is often buried in a methodology paragraph.

The straightforward baseline is the existing built form. Where the site has an unimplemented permission, an assessment against the consented scheme is legitimate and is usually presented alongside, not instead of, the existing baseline. Where the existing building is low relative to its context and its surroundings, a comparison against a notional development compliant with the relevant plan policies can be informative, but it should be labelled as an additional test rather than as the primary one.

State the baseline in the summary, not in an appendix. A committee reading that a scheme causes minimal change, without being told the comparison is against a consented tower rather than against the two storey building on site today, is being misled by omission even where every number is correct.

Where the existing baseline is unusually good because the site is currently open ground, say so early. That situation is set out in daylight assessment in low baseline conditions, and it is better addressed directly than discovered by the authority's reviewer.

Handling adverse results directly

Every urban scheme of any density produces some results below the benchmarks. A report that does not acknowledge that is either about a very generous site or is not telling the whole story.

Deal with the worst affected rooms individually and by address. Say which room, in which property, retains what value, what the change is, and why the scheme nevertheless remains acceptable: the room has an alternative window, the affected window serves a deep room with limited daylight already, the context is dense and the benchmarks expect flexibility, the alternative massing tested produced a worse overall outcome.

Then stop. A long list of mitigating observations reads as defensiveness. Two solid reasons carry more weight than six.

Where an objection has already been lodged on daylight grounds, answer it in its own terms rather than repeating the main report, which is the approach set out in daylight evidence and neighbour objections. And where the loss is intermittent rather than permanent, make the distinction explicitly, since it changes the character of the harm, as covered in transient overshadowing versus permanent loss of sunlight.

The non technical summary that officers reuse

The most useful page in a Daylight and Sunlight Assessment is the one the case officer can paste into the committee report with minor edits. Write that page deliberately.

It should state the baseline, the guidance applied and its status, the number of rooms assessed and how many meet each benchmark, the worst affected rooms by address with their retained values, the reason the scheme is nevertheless acceptable, and any mitigation designed in. Two pages at most, no tables wider than the page, no jargon left unexplained on first use.

Officers are not being lazy when they reuse it. They are working to a deadline with twelve applications and a committee date, and a summary they can rely on is a summary that gets used. A report that forces the officer to write their own summary gets one written by someone with less understanding of the numbers than you have.

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. For specialist technical reports, qualified professional input may be required.

Enter your postcode on PlanScope to see which reports a scheme with neighbouring amenity issues is likely to need.