Site photograph schedule and how to annotate it

A site photograph schedule turns a folder of images into evidence. It is a numbered set of views, each tied to a camera position marked on a plan, with the date, direction and purpose recorded. Officers use it to understand a site without visiting twice, and inspectors use it at appeal when nobody can visit at all.

The cost of producing one properly is an hour on site and an hour at a desk. The cost of not producing one is a site visit request, a delay, and an officer forming an impression of the site from whatever they happened to photograph.

Why a schedule beats a folder of images

Twelve unlabelled JPEGs uploaded to the portal tell the reader nothing about where the camera was or which way it faced. On a rear extension that may not matter. On a scheme where the argument is about the relationship to a neighbour, or about the character of a street, it matters entirely.

A schedule does three things a folder cannot. It proves where each view was taken from. It lets a reader who visits the site stand in the same place. And it lets you control which relationships the decision maker sees, rather than leaving it to chance.

There is also a records point. Photographs taken before work starts are the only evidence of what was there, and on a site where a condition requires reinstatement or where a boundary dispute is possible, that evidence is worth having.

Camera positions on a location plan

Produce one plan, at a scale that shows the site and its immediate surroundings, with a numbered arrow at each camera position pointing in the direction of view. Use a cone rather than a line where the view is wide.

Number the views in a logical order rather than in the order you took them. Approach views first, then the street scene, then the site itself, then the views out towards neighbours and public vantage points. A reader should be able to walk the site by reading down the list.

Where a view is taken from outside the site, mark the position on the plan anyway, with the distance from the site boundary. Where it is taken from private land, say whose and note that access was given.

On a larger site, a second plan showing the wider viewpoints at a smaller scale keeps the main plan legible.

The views a householder scheme needs

For a typical extension or conversion, the schedule is short and specific.

• The front elevation of the house from the opposite side of the street, showing it in the context of its neighbours.
• The street scene in both directions from the frontage.
• The rear elevation from the far end of the garden.
• The part of the building being altered, close enough to read the materials.
• The boundary condition with each adjoining property, including the height of any existing fence or wall.
• The view from the nearest neighbouring habitable room window towards the proposed works, where overlooking or loss of light is in issue.
• A close view of the existing brick, render, tile or window detail, for the materials discussion.

That last one earns its place more often than people expect. A Design and Access Statement that says the extension will match the existing brick is far more convincing next to a photograph of the existing brick.

Where the building is listed or in a conservation area, add views of the affected fabric at a scale that shows condition and joinery detail, and cross-refer them from the Heritage Statement rather than duplicating the description.

Context views on a larger site

For anything beyond a householder scheme the purpose shifts from describing the building to describing the setting.

Cover the approaches on each road, the views from public rights of way crossing or adjoining the site, views from any nearby designated asset, and the long views where the site sits on rising ground. Where a visual assessment is being prepared, the viewpoints should be agreed with the officer first, and the schedule should use the same numbering as the Townscape and Visual Impact Assessment so that the two documents talk to each other.

Seasonality matters where screening is deciduous. A summer photograph of a site behind a hedgerow shows a site that cannot be seen. The winter photograph shows the truth, and an officer who visits in February having read the summer set will not be pleased.

Annotation that a reader can follow

Keep annotation light and consistent. The conventions that work:

1. A header on each image with the view number, a short title and the direction of view.
2. Arrows or a dashed outline marking the specific feature being discussed, in a single colour used throughout.
3. A short caption in plain text saying what the view shows and why it is included.
4. No text over the part of the image that matters.

Avoid heavy graphics. A photograph covered in coloured boxes and callouts stops being evidence and becomes a diagram, and a reader cannot tell what was there from what was added.

Where a photomontage or a wireline is produced, keep it separate from the photographic schedule and label it clearly as a visual representation, with the method stated. Mixing the two invites the objection that the record has been manipulated.

Date, time, weather and camera data

Record for each view: the date, the time, the weather and visibility, the approximate camera height, and the focal length or its 35 millimetre equivalent. Where the position is fixed by grid reference, include it.

Camera height should be around eye level, near 1.6 metres, and consistent across the set. A photograph taken at arm's length above the head of a hedge misrepresents what a person standing there would see, and an inspector will notice.

Focal length matters because a wide-angle lens makes a building look further away and smaller. For views where scale is part of the argument, use a focal length close to normal perspective and say what you used. Where wide-angle views are included for context, label them as such.

Most cameras and phones record this data in the image file, and it survives if the images are not re-exported. Keep the originals. The guided upload route on PlanScope reads coordinates from a site photograph automatically where the image carries them, which is a quick way to confirm a position after the visit.

File naming and how to submit it

Name files so they sort correctly and describe themselves: a view number with a leading zero, a short slug and the date, for example 01-front-elevation-from-north-2026-03-21.jpg. Avoid spaces and avoid the camera's own numbering.

Submit the schedule as a single PDF with the location plan first, then one or two views per page at a size that can be read on screen, with the annotation baked in. Portals impose file size limits, so export at a resolution that stays legible when printed at A4 without producing a 60 megabyte document.

Keep the unannotated originals in the project file. If anyone questions what the photographs show, the original is the answer.

Browse the 66 PlanScope report types to see which supporting documents a scheme is likely to need alongside the drawings.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.