Construction AI: Liverpool got England's first Place Delivery Agreement, and Procore moved Europe's data in-region

So the housing story this week turns on a signing. On 5 October, Homes England and the Liverpool City Region Combined Authority signed what the government is calling England's first Place Delivery Agreement. The name is dull and the idea is not. What it does is pull the national agencies and the local authority into one delivery team, pointed at one place, with one set of priorities, instead of each running its own programme and hoping the three line up. Liverpool is the pilot. Homes England has said plainly it means to sign one of these with every mayoral authority as devolution spreads, so this is the template, not a one-off.

The money behind it is the government's new National Housing Bank, sitting on £16bn of debt, equity and guarantees, and the agreement names real schemes to spend it on, the North Docks and the Central Station Gateway among them. Steve Rotheram, the Liverpool City Region mayor, put it the way a mayor would: "This is what devolution should be about, giving places more control and then getting on with the job." Fair enough. The national target hanging over all of it is still 1.5 million homes this Parliament, and you'll remember I wrote on 7 October that new-home permissions had just fallen to a 14-year low. So the delivery machinery is arriving at exactly the moment the pipeline feeding it is running thin. Good timing or bad, depending on whether the machinery actually shifts the permissions number, which is the thing to watch and the thing nobody can promise yet.

Here's the bit I'd flag, and it's the reason a construction-AI brief cares about a regeneration deal at all. A joint delivery team only works if everyone is looking at the same picture. Pull three organisations into one programme and the first thing that breaks, every time, is the data: whose land record is right, which pipeline figure is current, who signed off what and when. The agreement is a promise to share accountability, and shared accountability runs on a shared, trustworthy record, or it runs on arguments in meetings. Today's action: if you work in or around one of the next authorities in line, find out who will own that shared record before the deal is signed, because the standard gets set once, early. For the delivery teams in Liverpool, and the ones in the next ten authorities to sign, the quiet first job isn't the ribbon-cutting. It's agreeing whose data is the truth. That's the job.

So the software story lands the same day, and it's about where your data sleeps at night. On 5 October Procore announced an EU Application Zone, a chunk of infrastructure that hosts and processes European customers' data inside Europe rather than shipping it across the Atlantic, sitting alongside the UK Zone the firm already runs. The detail worth reading is the list of what stays in-region: not just the files, but the metadata, the logs, the RFI text, the directory, the database records, the exhaust of a running project. That's Procore's own description, from its product announcement, so treat the specifics as the vendor's until an independent test says otherwise, and note the exact go-live and the countries covered aren't spelled out yet.

Why it counts is procurement, not performance. For a public-sector client, or a large contractor bound by data rules, where the data physically sits can decide whether a tool clears the buying process long before anyone opens the feature list. What Procore has done is remove a reason to say no. That's a shrewd, unglamorous move, and the big incumbents can afford to stand up a data-centre presence in every region a client might demand. The comparison only goes so far, but it's the app-bank question turned sideways: the challengers in construction software, the broad AI-first tools built to take the incumbent suites on, make their case on published pricing and a clean exit, your data walking out with you when you leave. Residency is the next question in that same conversation, not where you can take your data, but where it lives while you're using it. A smaller challenger has to answer that too, and the good ones already do.

What that means for whoever runs your procurement is one more line on the checklist. You've probably already got "can we get our data out" on there. Practical bit: put "where does it live while we're in" right underneath it, because a public client is going to ask, and somewhere in America is increasingly the wrong answer. For the person actually filling in the security questionnaire at eleven at night, that's one less fight to have. That's what it comes down to.

Put the two together and they rhyme, even though one is a regeneration deal and the other is a software release. Liverpool's agreement is a bet that you deliver more homes by sorting out who's accountable and getting everyone onto one shared picture. Procore's EU zone is a bet that where that picture is stored is now part of whether anyone's allowed to buy the tool at all. Different ends of the same job: the plumbing under delivery, and the record it runs on. One week the word was devolution and the next it was data residency, but the thing underneath both was the same dull, decisive question. Who owns the truth, and where does it sit.

A practical step: whatever you're signing this month, a delivery agreement, a software renewal, a framework slot, write down the two lines that will still matter in two years. Who's accountable when it goes wrong, and where's the record when you want it back. If you can answer both, carry on. If you can't, you've just found this week's work.