7 October 2026
How to tell a data centre shell from a big-box warehouse shell
From the road, or from a satellite pass, a windowless concrete shell on a greenfield plot could be either. Both are tilt-up or precast boxes going up fast on a flat pad outside a motorway junction. Both show up on imagery months before anyone's filed a name with the local authority. What separates them is what's built around the box: the yard, the parking count, and the power infeed.
Start with the loading face
A distribution shed is built around its dock wall. Walk the footprint in imagery and you'll find one long elevation lined with dock doors, dozens of them on a big-box unit, each with a leveler pad and a trailer queuing lane running the full length of the building. That apron is often as wide as the building is deep, because the whole site exists to get trailers in and out.
A data centre shell has almost none of that. One or two roller doors handle plant delivery, tucked at a gable end rather than along a full wall. There's no queuing lane because there's no fleet of trailers coming and going. If the long wall is blank concrete with no dock line at all, that's your first flag.
Check what's parked next to it, not what's parked on it
Warehouse sites carry a car park sized for shift changeovers, sometimes 200 to 400 spaces for a mid-size distribution unit, because the building runs on labour. A data centre shell on the same footprint carries a car park you could count on two hands. The building runs on power and cooling, not people, and the site plan says so before a single rack goes in.
That's also where the real tell sits: the yard. A warehouse roof carries scattered rooftop units for office and ambient HVAC, nothing more. A data centre site has a dedicated plant yard, often fenced off separately from the shell itself, holding chiller banks or cooling towers sized for the load, standby generators lined up in enclosures, and fuel storage sitting next to them. Look for a second structure or a walled compound close to the shell that's clearly not office space and doesn't match the building's own roofline. On a warehouse plot, there's nothing there to match it against.
Power infeed is the other giveaway. A distribution shed draws what any commercial unit draws, so there's rarely a substation footprint of its own on site. A data centre build brings its own switchgear and transformer pads, sometimes a full substation compound, connected back to the grid by a corridor you can trace in the imagery before the main building is even topped out. If you're seeing pad-mounted transformers and switchgear in numbers that look disproportionate to the building size, that's not a warehouse.
Fencing and phasing
Distribution sheds go up as a single pour and a single structure. Hyperscale campuses tend to phase, two or three shells of similar footprint going up close together with gaps between them reserved for future cooling plant or a second power run. Perimeter security also tends to be heavier and earlier on a data centre plot, double fencing and a gatehouse appearing at groundworks stage rather than after fit-out, because the operator's security requirement starts before the roof does.
None of these tells work in isolation. A shed can have a small car park if it's an automated fulfilment unit. A data centre build can sit on a shared plot with other light industrial. What holds up is the combination: blank loading face, minimal parking, a disproportionate power and cooling yard, and phased fencing going in ahead of the shell. Read for all four together and the box stops looking ambiguous.
That reading is exactly what gets missed when the first signal you get is a tender notice landing in your inbox, because by then the shell's framed and the packages are already out to quote. Data Centre Build Watch turns a monthly pad-to-roof read on sites like these into something you can act on while the groundworks are still being poured.
If your team is still relying on planning-portal alerts to find out a hyperscale site exists, you're finding out after the people who read the shell already knew.