Planning is not delivery: reading data-centre consent properly

Consent, reserved matters, condition approvals and physical works answer different questions. Two Slough applications show why planning progress is not delivered capacity.

“Planning approved” is an important statement. It is not a delivery date.

For someone assessing future data-centre supply, the useful question is not simply whether a site has permission. It is what that permission covers, which phase it applies to and what still has to happen before that phase can be built and used.

Our earlier analysis explained why a single project-status label can mislead. Planning deserves a closer look because its records contain several different kinds of progress. A decision to grant, approval of particular details, lawful implementation and physical completion are not interchangeable milestones.

1. A resolution to grant is not the issued permission

A favourable resolution may still be subject to requirements before a formal permission is issued. Where a resolution depends on a Section 106 planning agreement, an analyst should not quietly remove that qualification when summarising the project.

The distinction is visible at 188–216 Bath Road. An earlier council summary described a resolution to grant application P/20367/001, subject to a Section 106 agreement. The later direct register records “Withdrawn by Applicant”, dated 20 August 2026. [1] [2]

The earlier positive resolution is therefore not a sound basis for describing this application as a live, issued consent awaiting construction. The supported statement is that the application was recorded as withdrawn. Our reviewed evidence did not establish the reason.

Nor does the withdrawal establish that the site has been abandoned. Another proposal, a different permission or a changed development strategy would each need its own evidence. The unit of analysis here is the application, not every possible future use of the land.

2. Outline permission can leave important details for later

The former AkzoNobel site on Wexham Road illustrates a different position. Application P/00072/152 received conditional outline planning permission on 30 July 2026, corroborated by the signed decision notice. That supersedes the earlier “under consideration” description. [1] [3]

The notice does more than announce an approval. Its first page describes a phased development and reserves matters including layout, scale, appearance, landscaping and certain additional access points for subsequent approval. Condition 1 requires the relevant reserved matters for a phase to be submitted and approved in writing before that phase begins.

That wording makes the phase boundary important. An approval relating to one part of the scheme should not automatically be attributed to the whole campus. Equally, the absence of evidence about a later phase should not be used to deny progress that is properly established for an earlier one.

Outline permission is real planning progress. The mistake is treating it as evidence that every detail needed for every phase has already been settled. Full permissions and other consent routes need to be read on their own terms; not every scheme follows the same outline-and-reserved-matters sequence.

3. Submitting details is not the same as having them approved

A planning file can continue to grow after permission is granted. It may contain applications for approval of details, revised drawings, reports or requests concerning individual conditions. The presence of a submission establishes that something was filed. It does not, by itself, establish that the authority approved it.

At Wexham Road, the relevant distinction is already explicit in the first condition: details must be both submitted and approved. Counting documents, or counting applications associated with the site, cannot answer whether that requirement has been met for a particular phase.

Nor does a decision approving one set of details clear every other requirement. Conditions can concern different stages or continuing obligations. The question is which requirement has been satisfied, for which permission and phase, and what the wording requires next. “All conditions discharged” is a much broader claim than “these details were approved”.

Match the document to the claim
Resolution to grant
Read the qualifications. Look for the subsequent formal decision rather than assuming it was issued.
Issued permission
Identify the authorised proposal, conditions, reserved matters and phase boundaries.
Details submitted
Find the authority’s determination. A filing is not its approval.
Details approved
Keep the conclusion tied to the particular requirement and phase.
Works reported
Establish what happened, where and when; assess legal implementation separately.
Operation claimed
Identify the facility, capacity boundary and actual operational evidence.

A guide to reading evidence, not a universal sequence or a forecast of successful delivery.

4. Procedural deadlines are not construction forecasts

The Akzo notice’s first condition gives different windows for submitting reserved-matters applications for the first and subsequent phases. Those are procedural deadlines. They are not promises that a data centre will open at the end of either window. [3]

This matters when turning a planning pipeline into an estimate of future supply. A permission date, a deadline for submitting details and a developer’s construction programme answer different questions. None should silently replace another in a spreadsheet’s “completion year” column.

A reliable delivery forecast needs separate evidence about programme, dependencies and the milestone being forecast. Shell completion, energisation, customer fit-out and IT operation are different endpoints, even if they appear under the same project name.

5. Physical activity and lawful implementation are different questions

Reports of clearance, demolition or enabling works can be useful physical evidence. But they do not, without further examination, establish that a particular permission has been lawfully implemented. The activity may need to be matched to the relevant permission, phase and applicable requirements.

This is not a suggestion that either of these sites has acted unlawfully. It is a limit on what a researcher can infer. A planning decision does not demonstrate works on the ground, while a photograph of works does not settle every legal question about the consent being relied upon.

The same restraint applies further along the programme. Construction evidence is not evidence that a facility has an energised supply, completed customer fit-out or live IT capacity. Those claims require their own support.

Describe the permission, then describe the remaining questions

The practical improvement is modest: replace the bare label “approved” with a statement that names the application, decision date, consent type and relevant phase. Then distinguish the next planning requirement from the next physical or commercial milestone.

For Akzo, the reviewed evidence establishes a conditional outline grant and phase-specific reserved-matters requirements. It does not establish complete clearance of those requirements or delivered capacity. For Bath Road, it establishes withdrawal of the specified application, not abandonment of the entire site.

Those conclusions are narrower than a headline, but more useful. They preserve genuine progress without turning permission into an assurance of delivery, and preserve uncertainty without turning it into a negative verdict.

Sources and scope

This article develops two examples from public material retained in our 1 October 2026 research snapshot. No new site observation or source refresh was performed for publication. It is an analytical reading framework, not legal advice or a site-specific opinion on lawful implementation.

  1. Slough Borough Council, data-centre planning-consents appendix (PDF): historical entries for Wexham Road and 188–216 Bath Road. A summary’s title does not establish that every listed proposal has an issued permission; the later direct records below supersede the relevant historical descriptions.
  2. Slough planning register, P/20367/001: specific decision entry “Withdrawn by Applicant”, dated 20 August 2026. The generic portal status label was not used to override the specific decision.
  3. Slough planning register, P/00072/152, Documents: signed decision notice dated 30 July 2026, first page, including the proposal description and Condition 1 on reserved matters. The full notice, subsequent decisions and legal position were not comprehensively audited.

Council portals may require their ordinary access acknowledgement. The analysis does not reproduce the underlying report files or release the internal evidence register.