Regulatory approval is the part of a project most often treated as an administrative afterthought and most reliably capable of costing months. The problem is almost never that a requirement was impossible. It is that it was discovered late, or that two submissions were made in an order that forced one to wait for the other.
Requirements and processes change, and they vary by authority and by project type. Treat what follows as a way of thinking about sequencing, and confirm the current requirements with the relevant authority for your specific project.
Find out what applies before you design, not after
The set of approvals a project needs depends on where it is, what it is, how big it is and what it will do. A residential building inside a city authority's jurisdiction faces a different list from an industrial facility, and a project affecting a road reserve, a wetland or a protected area adds further consents.
The first task on any project is therefore not a drawing. It is a written list of every consent that will be required, who grants each one, what each requires as input, and roughly how long each takes. That list is cheap to produce and it changes the programme more than almost anything else you will do in the first month.
Map the dependencies between them
The costly mistake is treating approvals as a parallel batch when in fact several are sequential. Some consents require evidence that another has already been granted; some require a design that cannot be finalised until an earlier condition is known.
Draw the chain. Where approval B needs the outcome of approval A, that is a serial path, and its total duration is the sum, not the maximum. Programmes that assume everything happens at once are the ones that slip quietly for a quarter.
Land and title come first
Nothing else is worth starting until land ownership and boundaries are settled. Title, survey and any encumbrance need to be clean before design money is committed, because a boundary dispute discovered after foundations are set out is the most expensive category of problem in the industry.
Environmental and utility consents have their own clocks
Environmental screening or assessment, where required, runs on a timetable driven by the assessing authority and by any public consultation. It is rarely fast and it cannot be compressed by wanting it more.
Utility connections — power, water, drainage, telecoms — are their own projects with their own lead times and, often, their own construction works. A building finished but unable to connect to power is a familiar and avoidable failure, and it comes from treating connections as a snagging item rather than a workstream with a start date.
Build approvals into the programme as real tasks
Each consent should appear on the programme with a duration, an owner and predecessors, exactly like a construction activity. Two rules make this work:
- The duration is the authority's realistic turnaround, not the best case anyone has ever heard of
- Every submission has a named owner who is accountable for chasing it
Approvals with no name against them are the ones that sit for three weeks because everyone assumed someone else had it.
Expect conditions, and plan for a second round
Approvals are frequently granted with conditions, and conditions can require design changes, further submissions or specific site measures. A programme that shows a single submission followed by a clean approval is describing the best possible case.
Allow for at least one round of comment and resubmission. If it does not happen, you have gained time. If you did not allow for it and it does happen, you have lost a month you never had.
Keep the compliance file as you go
Approvals come with obligations that continue through construction: inspections at defined stages, records to keep, notices to display. Assembling that evidence at the end, from memory, is painful and sometimes impossible.
Keep one file, updated as things happen, holding every application, approval, condition, inspection record and correspondence. It is the document that makes handover straightforward, and the one that answers questions years later when the people involved have moved on.
The habit that prevents most of the pain
Review the approvals list at the same weekly meeting where you review the programme. One line per consent: submitted, with whom, how long it has been there, what it is waiting on, who is chasing it. Five minutes a week, and approvals stop being the thing that quietly consumed a quarter.
