Reading the limitations page of a consultant's report

Read the limitations page first. On a specialist report it usually sits at the front or the back in smaller type, and it tells you what the author did not do, what they assumed and who may rely on the conclusion. A consultant report limitations section is where the risk you thought you had transferred comes back to you, and on a planning submission that matters because the council reads the conclusion while the condition is drafted against the scope.

A conclusion is only as good as the scope that produced it. The limitations page is the scope.

Why the limitations page decides how useful the report is

Take a Phase 1 desk study for land contamination. The conclusion may read that no unacceptable risk to future residential end users has been identified. The limitations will say that no intrusive investigation was carried out, that ground conditions were inferred from published geological and historical sources, and that actual conditions may differ.

Those two statements are consistent with each other. But the second one means the report cannot discharge a condition requiring a site investigation, because the condition is asking for exactly the work the limitation excludes. Submitting it to discharge that condition wastes a fee and six weeks.

The pattern repeats across disciplines. The conclusion answers the question the consultant was asked. The limitations tell you whether that was the question the council is asking.

Common exclusions and what they shift back onto you

Six exclusions turn up again and again, and each one moves a risk.

• Desk-based only, with no intrusive investigation, inspection of concealed fabric or opening up
• Visual inspection from ground level, with no access to roofs, voids, basements or climbing inspection of trees
• Reliance on information provided by the client or by third parties without verification
• Assessment against the policy or standard current at the date of the report
• Survey undertaken outside the optimal season for the receptor in question
• Exclusion of matters outside the author's discipline, such as structural adequacy in an arboricultural report

The fifth of those is the one that ruins programmes. A preliminary ecological appraisal carried out in January cannot rule out roosting bats, because the activity surveys that would do so run in the warmer months, with emergence surveys generally from May to September. The appraisal will say so in the limitations and recommend further survey. If you submitted on the strength of the conclusion without reading that, you have a validation problem and a season to wait.

The sixth is quieter and more dangerous. An arboricultural report that excludes structural matters, next to a structural report that excludes ground conditions, next to a geotechnical report that excludes tree influence, leaves a gap between three appointments with nobody in it.

Desk study against intrusive work

Make the distinction explicit in your own project file, because councils do not.

A desk study produces a conceptual model from sources: historical maps, geological memoirs, published datasets, previous reports and a walkover. It identifies potential sources, pathways and receptors and says whether further work is needed. Under the relevant British Standard for the investigation of potentially contaminated sites, that is a legitimate first stage and not a conclusion about ground conditions.

Intrusive work tests the model. Trial pits, boreholes, gas monitoring over a period, laboratory analysis against generic or site-specific assessment criteria. Only that produces data a remediation strategy can be built on.

Where a condition says "site investigation", it means the second. Where it says "preliminary risk assessment", it means the first. Read the condition and the limitations side by side before you commission anything, which is the discipline our note on briefing a specialist so the fee stays fixed sets out in more detail.

Data currency and the survey date

Every report has a shelf life, and the limitations page usually hints at it without stating it.

Watch four dates. The survey date, which tells you the season and the conditions. The date the published datasets were downloaded, because flood mapping, protected site boundaries and designation layers change. The policy edition cited, which matters now that the national Framework has been reissued and renumbered more than once, so a report citing older paragraph numbers was written against a superseded edition. And the report date itself, because councils and consultees apply their own currency expectations.

Tree surveys are commonly treated as current for about a year, ecological surveys for a season or two depending on the receptor, and traffic counts need to come from a neutral month rather than August or late December. None of those is a statutory rule. They are the expectations consultees apply, and the limitations page is where a careful author tells you which one applies to their work.

If a report is close to the edge of its currency, ask the author for a short validity letter rather than paying for a repeat survey. Most will write one if the conditions have not changed.

Third party reliance wording

The standard wording restricts use of the report to the named client for the stated purpose, and excludes reliance by anyone else. That is reasonable from the consultant's side and inconvenient from yours.

It becomes a live problem in three situations. When the client sells the site and the buyer wants to rely on the reports. When a funder's solicitor asks for a collateral warranty. And when the local planning authority is being asked to approve a remediation strategy on the strength of a report it cannot rely on.

Check three things in the wording. Whether reliance can be extended by a reliance letter and on what terms. Whether liability is capped, and at what figure against the professional indemnity limit. And whether a net contribution clause limits recovery to the consultant's share where several parties are at fault.

Professional indemnity cover is usually written on a claims-made basis, so the cover that matters is the policy in force when the claim is made rather than when the work was done. A consultant who has retired or gone out of business may have no cover at all. Our piece on reliance letters and collateral warranties for planning reports goes through what is reasonable to ask for and when.

Where a caveat undermines the conclusion

The test is simple. Does the exclusion cover the risk the report is being used to address?

A noise assessment concluding that internal levels are achievable, with a limitation that glazing performance was assumed rather than specified, cannot support a condition requiring a glazing schedule. A daylight assessment concluding compliance, with a limitation that neighbouring window positions were taken from aerial imagery rather than survey, is vulnerable to an objector who measures them. A flood risk assessment concluding that finished floor levels are safe, with a limitation that no topographic survey was undertaken, has not established the levels at all.

In each case the conclusion is not wrong. It is conditional on something nobody has checked, and the condition sits in the limitations rather than in the conclusion where a reader would find it.

Where the exclusion covers the very point in dispute, the report is a scoping document rather than evidence, and it should be described that way in the planning submission. Overstating it is worse than acknowledging it, because a consultee who spots the gap stops trusting the rest of the pack.

Questions to put back to the author

Four questions, in writing, before you submit anything.

1. Which of these limitations could change your conclusion, and in which direction?
2. What further work would remove that limitation, what would it cost and how long would it take?
3. Does this report, as scoped, allow the authority to discharge the specific condition quoted here?
4. On what terms will you extend reliance to a purchaser or a funder?

The answers belong on the file. They are also the fastest way to find out whether the person who signed the report understands the planning use it is being put to, which is a different competence from the technical work itself. Our note on what suitably qualified means for a heritage statement applies the same reasoning to heritage work.

PlanScope drafts the planning narrative that sits around specialist reports, structured to UK planning policy, with placeholders where the specialist findings belong and flags where facts are missing. You can send a draft for review through the professional directory before it goes to the council. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.

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