Checking a technical report before it is submitted

Read the conclusions against the method before you read anything else. A specialist report goes wrong in one of three ways: the method does not support the conclusion, the report describes a different scheme from the one being submitted, or the data behind it has expired. All three are visible in about twenty minutes if you read in the right order, and all three are invisible if you start at the executive summary and nod along.

This is a review routine for the person assembling the application, not a substitute for the specialist's own quality control or for professional sign-off by a competent person.

Start with the conclusion, then the method

Turn to the conclusions and write down, in your own words, what the report says the effect is and what it says should happen about it. Then go to the methodology section and ask whether that method could have produced that finding.

The mismatches are usually simple once you look. A noise report that concludes plant is acceptable but ran the measurement in the middle of a weekday, when the background level is at its highest, has not tested the condition that matters. A daylight assessment that concludes no material harm but modelled only the two nearest windows has not tested the receptors the objectors will raise. An ecology report that recommends no further survey while recording moderate roost potential has skipped the step its own scoring system requires.

Where the method is set by a standard, check the report says which version it used. A Noise Impact Assessment should name BS 4142:2014+A1:2019 and state the rating penalties applied, and a tree survey should name BS 5837:2012 and give the categorisation for each tree. A report that cites a standard without saying how it applied it is asserting compliance, not showing it.

Drawing references and revision numbers

This is the dullest check on the list and the one that most often prevents a refusal. Build a single table of every drawing referred to anywhere in the submission, with the number, the revision letter and the date, and reconcile it against the drawing schedule you intend to submit.

What you are looking for:

• a technical report assessing revision B while revision D is being submitted
• a report that references a drawing number which no longer exists after a renumbering
• site area or red line boundary described differently in two documents
• floor areas quoted as gross internal in one report and gross external in another
• the access arrangement shown on the transport drawing not matching the general arrangement

The red line is worth its own moment. If the Planning Statement describes a site of 0.48 hectares and the location plan measures 0.52, one of them is wrong, and on a major development threshold that difference decides whether the application is major.

Survey dates and whether the data is still current

Ecological data ages. The professional guidance from CIEEM on the lifespan of ecological reports sets out when survey information should be reviewed or repeated, and councils and their ecology advisers apply it, so a report built on survey visits from three seasons ago will attract a request for an update rather than a decision. Check the current advice note version rather than working from memory.

The same logic applies elsewhere with different clocks. Traffic counts should come from a neutral month, which in practice means avoiding August and the fortnight either side of Christmas, and a count taken during a road closure nearby is not a baseline. Parking surveys under the Lambeth methodology need overnight midweek and weekend visits outside school holidays. Contamination desk studies rely on historical mapping that does not age, but the site walkover behind them does.

Write the survey date, not just the report date, into your review note. Reports get reissued with a new cover date and the same fieldwork behind them.

Assumptions that have quietly changed

Every technical report rests on assumptions about the scheme. Unit numbers, mix, floor areas, parking provision, hours of operation, plant selection, construction sequence. Those assumptions were fixed at the moment the specialist was briefed, and the design has moved since.

Keep a short assumptions register for the project and reconcile each report against it before submission. Ask the specialist directly whether the change you made matters. Two extra flats will not usually alter a landscape assessment and will alter a foul drainage calculation, a child yield figure and a habitats catchment contribution.

The assumptions that cause the worst problems are the ones nobody wrote down. Whether the existing building is in lawful use, whether the neighbouring land is in the applicant's control, whether the plant deck is enclosed. Ask about those explicitly.

Cross-checking figures between documents

Pick the four or five numbers that appear in more than one document and check them everywhere they appear. On a typical residential application those are site area, unit count, gross internal floorspace, parking spaces and the existing floorspace being retained or demolished.

Existing floorspace deserves particular attention because it drives the levy calculation. Under the Community Infrastructure Levy Regulations 2010 a building can only be deducted from the chargeable amount if it has been in lawful use for a continuous period of at least six months within the three years ending on the day permission first permits development. If your Design and Access Statement describes the unit as vacant for years while the levy form claims the deduction, the council will notice, and the correction arrives as a demand notice long after the decision.

Check the ownership certificate too. Certificate A is signed far more often than it is true, and a wrong certificate can invalidate a permission years later.

What to send back, and how to word it

Send one consolidated note per report, numbered, with the page or paragraph reference and a specific question. Not "please review section 5". Something closer to "section 5.3 concludes no further survey is required, but table 4 records the building as having moderate roost potential, which under the guidance you cite would normally trigger emergence surveys. Please confirm the reasoning or amend."

Separate the points that change the conclusion from the points that only change the presentation, and say which is which. Specialists work to fees, and a note that mixes a typographical error in with a methodological gap gets the same weight given to both.

If the answer to a substantive question is unconvincing, do not paper over it in the covering letter. An assessment you could not defend at appeal is a liability at validation and a worse one at committee. Where the report needs an author with specific competence, the honest route is a review and sign-off by a qualified professional through a professional directory rather than an editorial tidy.

Log the version you submitted, with its revision and date, on the day you submit it. Six months later, when the officer refers to figure 3, you will want to know which figure 3.

This is general guidance rather than legal advice. Check the position with your local planning authority or a qualified professional before relying on it.