How to read a development consent

A development consent is the legal document that says your project can proceed — and on what terms. It's issued by a consent authority (usually a local council or the Department of Planning) after a development application is assessed. Every condition in that document is legally binding from the moment the consent is granted.

Most people skim the consent looking for the obvious conditions — hours of work, noise limits, tree removal. But the obligations that cause problems are the ones buried in cross-references, schedules, and management plan requirements. This guide walks through the structure of a typical consent and shows you how to find every obligation.

The anatomy of a consent document

While every consent authority formats theirs slightly differently, the structure is broadly consistent across Australian jurisdictions. Understanding the sections helps you know where to look — and what to expect.

Part A — Administrative conditions

These appear at the top and cover the basics: what's been approved, the plans it relates to, the consent's validity period, and any modifications to the original application. They feel procedural, but they contain obligations. A condition requiring you to "carry out development in accordance with the approved plans" means any deviation — even minor — is a breach.

Part B — Prior to commencement

Conditions that must be satisfied before any physical work starts. These typically include lodging bonds, obtaining construction certificates, submitting management plans (CEMP, TMP, NMP), appointing principal certifiers, and notifying neighbours. Missing one of these is a stop-work issue.

Part C — During construction

The bulk of the consent. These are your ongoing obligations: erosion controls, noise limits, working hours, dust suppression, traffic management, heritage protocols, stormwater management, and environmental monitoring. This is where most breaches occur because these conditions require continuous attention, not a one-off action.

Part D — Prior to occupation / completion

Conditions that must be met before you can get an occupation certificate or hand over the completed works. Landscaping completion, as-built surveys, compliance certificates from service authorities, final inspections, and bond releases all sit here.

Schedules and annexures

Often attached at the end, these contain the detail that the main conditions reference. A condition might say "in accordance with the Noise Management Plan at Schedule 3" — the actual limits and monitoring requirements are in the schedule, not the condition text. Always read these.

Understanding the legal language

Consent conditions use specific language that carries legal weight. Knowing the difference changes how you interpret your obligations.

"Must" and "shall" — mandatory. Non-negotiable. Failure to comply is a breach.

"Should" and "is encouraged to" — advisory. Rare in modern consents but sometimes appears. Not strictly enforceable but ignoring advisory conditions can count against you during audits or enforcement proceedings.

"To the satisfaction of" — means someone specific (usually the certifier, council, or a government agency) must approve your compliance. You don't get to self-assess.

"Prior to" / "before" — creates a timing gate. The action must be completed before the trigger event. "Prior to commencement of earthworks" means the earthworks cannot start until this condition is discharged.

"In accordance with" — binds you to an external document. If your condition says "in accordance with AS 2436", you need to know what that standard requires. The condition is only as detailed as the document it references.

Finding the hidden obligations

The numbered conditions are the obvious ones. But consents contain obligations in places people don't think to look.

Cross-referenced documents

Conditions frequently reference external documents: management plans, Australian Standards, EPA guidelines, council DCPs, and approved drawings. Each of these contains additional obligations that are legally binding through the condition that references them. A consent with 80 numbered conditions might actually impose 300+ obligations once you trace the cross-references.

Definitions section

The definitions section can change the meaning of conditions. "Construction hours" might be defined differently than you expect. "Sensitive receiver" might include commercial premises you hadn't considered. Always check definitions before interpreting conditions.

General terms of consent

Some consent authorities include boilerplate general terms that apply to all consents they issue. These are separate from your specific conditions but equally enforceable. They often cover things like site signage, complaints handling, and notification requirements.

Condition types you'll encounter

Not all conditions work the same way. Understanding the type helps you determine how to track and evidence compliance.

Hold points and triggered actions are the highest-risk types because they have hard timing requirements. Missing a hold point can stop your project. Missing a triggered action window can result in a breach notice.

Building your register from the consent

Once you understand the document, the next step is extracting every condition into a compliance register. For each condition, you need to capture:

• The reference number — exactly as it appears in the consent
• The full condition text — verbatim, including any cross-references
• A plain-English interpretation — what it actually means for your team on site
• The trigger or timing — when does this condition need to be satisfied?
• The responsible party — one person accountable for compliance
• Evidence required — what documentation proves you've complied?
• Risk level — what happens if this condition is breached?

State-specific differences

The format and naming varies across jurisdictions:

• NSW: Development consents (local), State Significant Development (SSD) conditions, and Conditions of Approval (CoA) for State Significant Infrastructure (SSI). The Independent Planning Commission may add its own conditions on appeal.
• Victoria: Planning permits issued under the Planning and Environment Act 1987. Conditions are typically shorter but reference endorsed plans extensively.
• Queensland: Development approvals under the Planning Act 2016. Conditions may be imposed by multiple referral agencies (SARA process).
• Western Australia: Development approvals under the Planning and Development Act 2005. Often includes separate conditions from the EPA for Part IV assessments.
• South Australia: Planning consents under the Planning, Development and Infrastructure Act 2016. Assessment panels and the State Commission Assessment Panel (SCAP) may impose conditions.

Regardless of the jurisdiction, the principle is the same: every condition is enforceable, every cross-reference imports additional obligations, and compliance is your responsibility from day one.

What to do after you've read it

Reading the consent is step one. The real work is turning it into a system your team can actually use. That means:

• Extract every condition into a register — including obligations from referenced documents
• Categorise by timing: pre-commencement, during construction, pre-occupation
• Assign a single responsible person to each condition
• Identify your hold points and triggered actions first — these have the tightest deadlines and highest risk
• Set up evidence collection from day one, not when the auditor asks

The gap between reading a consent and actually tracking compliance is where most projects fail. A consent sitting in a drawer is the same as not having one.