Why Site Area Alone Doesn't Predict Parking Yield
At the very earliest stage of feasibility, it's common to see parking capacity estimated with a single division: site area ÷ average area per parking space. It's a quick number, and for a rough order-of-magnitude sense of scale, it's not useless. But treated as anything more precise than that, it can be seriously misleading — sometimes overstating what a site can hold, sometimes understating it.
Why the shortcut breaks down
The area-per-space figure baked into that calculation assumes every square metre of the site is equally usable for parking. In reality, a meaningful share of most sites is consumed by things that aren't bays at all:
- Aisles, which vehicles need to manoeuvre in and out of a space
- Circulation roads, connecting the access point to the parking areas
- Access points themselves, and the geometry needed around them
- Unusable corners and edges, created by the site's actual shape rather than a clean rectangle
None of this is a fixed percentage. It depends on the specific site — which is exactly why a single area-based ratio can't capture it.
Shape matters more than most people expect
Two sites of identical area can produce very different results purely because of their shape. A simple rectangular site is generally easier to arrange efficiently: bay rows and aisles can run cleanly from one boundary to the other with little wasted space. An irregular site — an angled boundary, a narrow frontage, a site that widens or narrows partway back — behaves differently. See our guide on testing irregular or constrained sites for a worked example of this.
Configuration choices shift the number too
Even on a fixed site shape, yield isn't a single fixed number — it moves depending on decisions made during layout:
- Parking angle changes both the bay footprint and the aisle width needed to serve it — see choosing a parking bay angle.
- Circulation design — one-way vs two-way, and how much of the site the circulation network needs to cover — changes how much space is left for bays. See circulation, aisles & access design.
- Access point location can unlock or block an efficient circulation path, with knock-on effects for the whole layout.
A single area-based number can't reflect any of these choices, because it doesn't model the layout at all — it just divides one number by another.
What a layout-based estimate adds
Rather than assuming the whole site is usable, a layout-based approach works with the site's actual geometry: its shape, its access points, and the configuration being tested. It attempts to arrange bays and circulation the way they'd actually need to sit on the site, then counts what fits. This doesn't produce a guaranteed final number — it's still an indicative estimate, not a substitute for detailed design — but it reflects the real constraints of the site rather than an average drawn from elsewhere.
When the rough shortcut is still fine
To be clear, the area-based shortcut isn't wrong to use — it has its place. For a very early, back-of-envelope sense of whether a site is in the right ballpark for a project, it can be a reasonable starting point. The issue is relying on it once real decisions — site selection, feasibility reporting, comparing alternative sites — start to depend on the number being closer to accurate.