Automating Council Submission Forms for a Small Architecture Practice

A council submission is rarely difficult on its own. What makes it slow is the repetition: the owner’s name, the erf number, the zoning, the same consultant details, typed onto form after form, each one wanting the information laid out slightly differently. Get one field wrong or inconsistent across the pack and you risk a bounce-back that costs you weeks, not minutes. I run AB Architecture, a residential practice in Knysna and Cape Town that also works under the joint brand AB+HvD Architects, and the submission pack was one of the more obviously repetitive parts of the week — so it’s one of the things I’ve rebuilt around AI.

Where the time actually goes in a submission

A typical residential submission pack isn’t one form, it’s several: the building-plan application itself, appointment forms for the various professionals on the job, and a set of compliance forms depending on what the project involves. Each one asks for a version of the same core facts — who owns the property, what it is, who’s doing what on the job, what’s being built. None of that is hard information to produce once. The time goes into producing it five or six times over, keeping it consistent, and then re-checking that consistency before the pack goes in.

The actual municipal process itself is worth knowing in outline before any of this — the City of Cape Town’s building plan application guidance sets out what a submission needs and how it’s lodged. Automating the forms doesn’t change any of that; it just removes the retyping around it.

How the forms get filled now

The tool I use reads the project’s own documents — the project record set up when the job started, which already has the owner details, the property information and the appointed consultants — and fills each form from that single source. Once a field is filled and checked, it’s locked, so it can’t drift out of sync with the others later in the process. The tool then lists what the submission pack still needs: a missing appointment letter, an outstanding compliance certificate, whatever it is. Anything it genuinely can’t find in the project’s documents is flagged for me rather than guessed at — that’s the same rule that runs through everything else I’ve built, and it matters more here than almost anywhere else, because a guessed fact on a council form is worse than a blank one.

I’ve tested this on three real submissions so far. It’s not a large sample, and the forms and their exact requirements differ between municipalities, so I’d call this an early result from my own practice rather than a general claim about how it performs everywhere.

A checklist before you automate your own submission paperwork

If you’re weighing up whether this is worth building for your own practice, this is roughly the order I’d work through:

1. List every form your municipality actually requires, not a generic list from another region — requirements and form layouts differ between local authorities.
2. Trace where each piece of information already lives — title deed, fee proposal, project record — before you build anything. If the source data is scattered, that’s the first problem to fix, not the forms.
3. Decide what “locked” means for your own workflow. A field that’s been checked shouldn’t be able to silently change later without you noticing.
4. Test on jobs you’ve already submitted, not on the next live deadline. You want to find the gaps in the tool before council finds them in your pack.
5. Keep a clear, visible list of what’s still missing — not just what’s been filled in. A form that looks complete but has a guessed entry is more dangerous than one that honestly shows a gap.
6. Have a person check the whole pack before it goes to council, every time, no exceptions for the “easy” jobs.

Limits — what still needs a person

I want to be plain about what this doesn’t do. It doesn’t know your submission is correct — it knows the fields are filled and consistent with your project’s own documents. Whether the submission itself meets the building regulations and municipal requirements for that specific job is still a judgement call for someone who understands the submission, not something a form-filling tool can certify. Three submissions is a small track record, and different municipalities ask for different things, so treat this as a description of what’s worked in my own practice so far, not a finished, general-purpose product.

This also isn’t legal or regulatory advice, and nothing here is a guarantee that a given submission will be accepted. The forms are the mechanical part of a submission; the professional judgement about what the project actually requires sits outside what any tool fills in.

Where this fits in a bigger workflow

This only works because the project record it draws from is already good — see how a new project sets itself up for where that information actually comes from. On its own, a form-filling tool with nothing solid behind it just automates the retyping of bad data faster. I’ve written more generally about how these pieces connect in AI for architects in South Africa, and about how a build like this gets scoped for another firm at Services.

If council paperwork is eating more of your week than it should, book a free 30-minute call and I’ll tell you honestly whether automating it would actually help in your practice.