Parking survey report outline and its data tables

A parking survey report is judged on three things: whether the survey area is defensible, whether the capacity measurement is reproducible, and whether the counts were taken on nights that represent normal conditions. Get those right and the tables almost write themselves. Get the survey area wrong and a highways officer will discount the whole document, because a boundary drawn to include a quiet mews two streets away is the oldest trick in the trade and officers read these reports every week. What follows is the reporting structure that survives that scrutiny, section by section, with the tables that belong in each.

Survey area and why it has to be justified

Open with the site, the proposal, the parking provision proposed, and the adopted standard you are measuring against. Then define the survey area and justify it in the same breath.

The convention drawn from the London Borough of Lambeth methodology is a catchment of 200 m walking distance from the site boundary, measured along walkable routes rather than as the crow flies. Say which streets are in, which are out, and why. Severances matter: a railway line, a river, a dual carriageway with no crossing, or a gated estate all cut a street out of the catchment even when it is 120 m away on a plan.

State the restrictions on every street in the area, because a controlled parking zone changes the meaning of every number that follows. Where the zone operates Monday to Friday 9am to 5pm and your survey is an overnight count, the kerb is unrestricted at the time of counting and the capacity figure must reflect that.

Include a survey area plan at a legible scale with each street labelled and the 200 m contour drawn. Number the streets, or number sections where a street is long, and use those numbers consistently through every table.

Measuring capacity

Capacity is the number of vehicles that could park legally on each length of kerb. It is measured, not estimated from memory, and the method has to be stated so that a reviewer can repeat it.

For marked bays, count the bays. For unrestricted kerb, the Lambeth approach allocates a nominal length per vehicle, commonly 5 m, applied to the measured length of usable kerb. Deduct everything that cannot be parked on:

• Dropped kerbs and vehicle crossovers, including the splay each side.
• Junction protection markings and the statutory clearance at junctions.
• Bus stops, cages, taxi ranks and loading bays with a restriction at the survey time.
• Disabled bays, car club bays, electric vehicle charging bays and motorcycle bays, counted separately.
• Hydrant and access points, skips, build-outs, trees in the carriageway and formal crossings.

Record the measurement method itself: a measuring wheel, a laser, or scaled aerial imagery verified on site. Aerial measurement alone is not enough where crossovers are new, and a reviewer will ask when the imagery was captured.

Occupancy counts and their timing

The purpose of an overnight count is to catch the residential population at home with vehicles parked. That is why the standard window sits between 00:30 and 05:30, and why a single count at 8pm proves nothing.

Two nights is the normal minimum: one midweek night, usually Tuesday to Thursday, and one weekend night. Both counts should be taken in the same week where possible, and both avoid school holidays, bank holidays, the Christmas and Easter periods, and any local event that pulls vehicles into the area.

Record for each count: the date, the day of the week, the start and finish times of the walk, the weather, the surveyor's initials, and any local abnormality noted on site. Count every parked vehicle, including those parked unlawfully, and record unlawful parking separately, because a street at 92 per cent measured occupancy where a fifth of vehicles sit on the footway is telling you something the headline number hides.

Exclusions and nights you should discard

Be explicit about what you removed from the dataset and why. A report that quietly drops a night invites the question of what else was dropped.

Legitimate exclusions include a street closed for utility works on one of the two nights, a count interrupted by weather severe enough to change parking behaviour, and a night coinciding with an event at a nearby stadium or venue. In each case, state the exclusion, keep the raw sheet in the appendix, and re-survey rather than proceed on one night.

An exclusion that officers reject: removing a street because it was full. Capacity constraint is the finding, not a data problem.

The data tables and how to lay them out

Three tables carry the analysis. Keep them in this order, with the same street numbering throughout.

Table 1, capacity by street:

Table 2, occupancy by street and night, with the derived stress figure:

Table 3, the area summary: total capacity, total parked on each night, area stress on each night, spare capacity in vehicles, and the same figures with the proposal's expected demand added.

Round stress to whole percentages and show the arithmetic once so the reader can check it. Put the raw survey sheets, the plan, the photographs and the measurement notes in appendices, numbered and referenced from the text. A Parking Survey that hides its raw data reads as a conclusion in search of evidence.

Reading the result against the standard

Stress is parked vehicles divided by capacity. The figure commonly treated as the point where a street is under pressure is 80 per cent, because above that drivers start circulating to find the last spaces. Below it there is usable slack.

Two comparisons belong in the interpretation. First, the existing area stress against that benchmark, on both nights, at street level and area level. Second, the stress after your proposal, using a demand assumption you state and justify: census travel-to-work data for car ownership in the area, the parking provision on site, and any car-free or permit-free condition offered.

Where the proposal is permit-free, say what secures it, whether a condition, a section 106 obligation or a traffic order, and accept that officers weigh an unsecured promise at nothing. Where the area is already above 80 per cent on both nights, argue the case on accessibility and controls rather than pretending the slack exists. A Transport Statement is the right home for the wider access argument, with the survey as its appendix.

Illustrative example: a four-bedroom house converted to a six-bedroom HMO in a street with 16 spaces of capacity, 13 parked midweek and 12 at the weekend. Adding two vehicles takes midweek stress from 81 to 94 per cent. The route through is a permit-free obligation and cycle storage, not a claim that the street can absorb the demand.

Limitations stated honestly

Every survey has limits, and a report that names them is more persuasive than one that does not.

The count is a snapshot of two nights. Car ownership in the area may be changing. Charging points and car club bays alter capacity between survey and determination. New crossovers remove kerb length. Where a nearby site is under construction, parking patterns during the survey may not be the pattern after completion.

State each limitation in a single sentence, say how it might affect the conclusion, and stop. Do not use the limitations section to soften a finding you do not like.

One further point that saves work later: if you expect to go to appeal, the survey has to stand on its own without you present to explain it, which is the same standard set out in the guidance on an appeal statement of case. Label everything. Date everything. Keep the sheets.

Browse the 66 report types on PlanScope to see how a parking survey sits alongside the transport and amenity documents a conversion application usually needs.

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.