Construction AI: England scraps the consultation rule that added a year to big projects, and Washington asks for a 30-day key to the frontier

The government confirmed on Friday 3 July that mandatory pre-application consultation requirements for Nationally Significant Infrastructure Projects will be scrapped, with the change taking effect on 24 July through the Planning and Infrastructure Act. New Civil Engineer carried it on the day, and the Register followed on 7 July with the angle everyone was thinking: the projects that gain most are the data centres the government wants built quickly. Ministers claim the reform cuts up to 12 months from the planning process and saves industry £1bn over this Parliament. Both figures come from the government's own press notice, so hold them at arm's length, but the mechanism is real enough. The statutory duty to consult before submitting a Development Consent Order application goes, and in its place developers get earlier technical support and what MHCLG calls meaningful advice from the Planning Inspectorate before submission.

So, the part that matters more than the headline. Consultation isn't dead, it's discretionary, and the government's own response says fresh statutory guidance will make clear that applications are unlikely to progress to examination if pre-application engagement was inadequate. What that means in practice is the risk moves rather than disappears. Under the old regime, a thin consultation was a procedural defect you could point at; under the new one, it's a judgement call the Examining Authority makes about whether your application is ready, and a gift to any objector building a judicial review case on fairness grounds. The developers who treat the freed-up year as a reason to engage earlier and better will bank the time saving. The ones who treat it as permission to skip the conversation with the parish council will find the year again at examination, with interest.

For contractors and consultants the change lands in the order book before it lands anywhere else. NSIPs now include data centres, and the consenting stage has been the slowest part of every energy, water and transport scheme in the pipeline. I've sat through enough pre-application rounds to say the statutory version had become a performance, three rounds of exhibition boards nobody read, so I won't mourn the duty. But the discipline behind it, knowing what the community objection actually is before you design past it, was always worth the fee. That's what it's about.

The tender-desk view: If you support DCO applications, your pre-application offer needs rewriting this month. The sell is no longer "we'll get you through the statutory stages"; it's "we'll do the engagement that keeps your examination short, now that nobody's forcing you to".

Monday's brief mentioned in passing that a Kent data centre had been routed around local councillors. Here's the detail, because the scheme deserves more than a clause. Clearstone Energy, the UK renewables developer, announced the Ebbsfleet AI Data Centre Campus on 2 July: a 300MW campus on 145 acres off New Barn Road between Northfleet and Southfleet, 2km south of Ebbsfleet International, with up to 180,000 sqm of data centre space across four buildings and a direct connection to National Grid's transmission network. KentOnline puts the build cost at around £3bn. Data Centre Dynamics and Property Week both carried the announcement the same week. The first facility is targeted to come online in 2030, community design workshops start this autumn, and the full public consultation runs in 2027.

The planning route is the story inside the story. The Secretary of State has agreed to treat the scheme as a development of national significance, which lifts the decision out of the local committee room, and from 24 July the scheme also benefits from the consultation reform in the item above. Put the two together and you have the clearest example yet of the government's data centre delivery model: national designation, streamlined consenting, grid connection dealt with at transmission level. I'm not sure the residents of Southfleet will experience "meaningful advice from the Planning Inspectorate" as an upgrade on a statutory right to be consulted, and the local reporting suggests the village has noticed. But the direction of travel is unmistakable, and it's the same one the Loughton letters pointed to on Monday.

For the supply chain this is the practical bit: 1.9 million sq ft across four buildings with a 2030 first energisation is a multi-year civils, MEP and commissioning programme, and the pre-construction services work, ground investigation, utilities diversion, logistics planning, starts long before 2027's consultation closes. The M25-east corridor now has this, the approved Kent scheme from March, and whatever follows the NSIP change. The site teams that did a data hall in the last cycle are about to be the most borrowed CVs in the south east.

Worth doing: If data centre work is anywhere near your plan, map the named schemes within an hour of your office and note which planning route each one is on. The route tells you the programme risk, and the programme risk tells you when the tender actually lands.

The Hill reported this week that the White House is in the final stretch of negotiations with OpenAI, Google and Anthropic on voluntary AI release standards, with an announcement possible as early as this week. The framework grows out of June's executive order on advanced AI, and the core of it is access: developers of covered frontier models would give the federal government up to 30 days with a new model before public release, to review national security implications, and would work with government to select trusted partners for early access. Voluntary is the operative word, though the recent past shows how much weight it carries. Washington has already applied export restrictions to Anthropic models and asked OpenAI to delay releases, and the confusion around those interventions is, per the Hill's reporting, part of why the labs want a written framework at all.

Regular readers will connect this to the Fable 5 story from last Friday's brief: a frontier model disappeared for 19 days and took a set of production workflows with it. What we've found this year is that model availability has stopped being a pure engineering question, it moves with export rules, review windows and now a pre-release protocol negotiated between three companies and one government. I'll hedge honestly here: a 30-day review on a model you haven't got yet costs you nothing today, and a predictable framework beats the ad-hoc interventions we've had since June. But the precedent, that release timing is now a matter for government, will outlast this administration and this framework, and buyers everywhere should price that in.

The construction read is short. If your tools sit on top of Claude, GPT or Gemini, and increasingly they do, then your vendor's roadmap dates now have a review window in front of them that neither you nor the vendor controls. The person doing the paperwork doesn't care whose signature the delay carries; they care whether the document check runs on Tuesday. Keep the fallback arrangements you built during the Fable outage alive rather than filing them under crisis-over.

Today's action: Ask your main AI vendor one question: which model each critical feature runs on, and what the tested fallback is. If the answer to the second half is a shrug, that's your risk register entry written for you.

One thread runs through all three items: government has moved from commentator to participant, at both ends of the stack. In England it's rewriting how the biggest schemes get consent, and the data centre pipeline your order book wants a piece of is the intended beneficiary. In Washington it's negotiating a seat at the release desk of the models your tools depend on. Neither is a reason to slow down. Both are reasons to underwrite differently: consent risk and model availability risk are now named lines, not background noise.

The response fits on a page. A pre-application offer worth paying for after 24 July. A map of the data centre schemes near you with their planning routes marked. A fallback model answer from your vendor in writing. Small, checkable, done this month.

The takeaway: The firms that treat policy shifts as programme inputs, rather than news, keep their margins when the rules move again. They always move again.