Getting Site and Zoning Data Into Revit Before You Draw a Line

The first hours of most residential projects go somewhere unglamorous: working out exactly what a site allows before you can draw anything that matters. Plot boundary, building lines, setbacks, height limits, how much has already been built, what the zoning scheme actually permits — none of it is difficult to find on its own, but pulling it together and then setting it up correctly in your drawing software takes real time, every single project, before a design decision has been made. I run AB Architecture, a residential practice in Knysna and Cape Town, and this was one of the first things I rebuilt — not because it’s the most interesting part of the job, but because it repeated on every job, unchanged.

Why site data usually arrives late, and badly

The normal order of things is: read the zoning scheme, work out the numbers by hand, set up a base plan in Revit or CAD from that, and only then start designing on top of it. Each step is a manual translation from one format to another, and each translation is a place for a number to drift — a setback read slightly wrong, a coverage figure that doesn’t match the actual erf, a building line copied from an old survey rather than the current one. None of that shows up as a dramatic error. It shows up later, as a design that has to be reworked once the real numbers are checked properly.

What I built instead

I built Zonely, a web app that turns a Cape Town property’s zoning into a plain-English answer — the zoning, the plot size, what you’re allowed to build — in seconds rather than a long by-law read. That’s useful on its own for a quick check. What actually saves the hours, though, is what happens next: the same site data — plot boundary, existing building footprints, building lines, setbacks, height limits, coverage from the zoning scheme, ground levels — comes straight into Revit, already set up, before I draw anything. See the Zonely case study for how that connection works in practice.

Zonely itself currently covers residential properties in the City of Cape Town, so the tool is regional. The underlying idea isn’t — get accurate site data into your drawing software before you draw a line, rather than translating it by hand partway through the project — and that applies wherever you practise. Where a property sits inside an estate or HOA, there’s usually a second layer of rules on top of the municipal zoning too; Zonely’s sister blog has a good explanation of how that private layer works alongside the City’s rules, which is worth reading before you assume the zoning number is the only constraint on a site.

The same accurate site plan also matters once you’re working from an existing building rather than a blank site — I go into that connection, and the honest limits of it, in the post on laser scan to Revit as-built drawings.

A checklist for getting site data into your own workflow

Whether or not you build something automated, this is roughly what I’d check before trusting a base plan enough to design on top of it:

1. Confirm the zoning against the current scheme, not a remembered figure from a similar site down the road. Overlay zones and site-specific conditions change the answer more often than people expect.
2. Check existing coverage against what’s actually built, not just what old plans claim — old plans and current reality drift apart more than you’d think.
3. Bring building lines and setbacks in as real geometry, not a note on a drawing that someone has to remember to check later.
4. Confirm ground levels before you rely on them. A base plan that’s wrong on levels causes far more rework than one that’s wrong on boundaries.
5. Keep the source data linked back to where it came from, so if the zoning scheme or a survey is updated, you know what in your model needs rechecking.
6. Have a person confirm the numbers before a design decision is made on top of them — this is where an early mistake gets expensive, not where it gets caught.

Limits — what still needs checking

Zonely is a Cape Town tool right now, covering residential zoning specifically — it doesn’t cover every municipality or every property type, and it isn’t a substitute for reading the actual zoning scheme and any title deed conditions on a specific site. The data flowing into Revit is only as current as the underlying zoning data and survey information it draws from, so it’s still worth a person’s sense-check against the site itself, particularly on anything unusual: a site-specific departure, an old consent use, a condition buried in a title deed rather than the zoning scheme. None of this replaces judgement about a site that doesn’t fit the standard pattern.

Where this fits in a bigger workflow

Getting the site right before you draw is one piece of a wider pattern — gather the information once, get it into the right place automatically, keep a person checking before a design decision relies on it. I describe the rest of that pattern, including project setup and scan-to-drawings, in AI for architects in South Africa, and how a version of this could be built for another firm is at Services.

If site and zoning research is eating time you’d rather spend designing, book a free 30-minute call and I’ll tell you honestly what would actually help in your workflow.