How to build a compliance register from a DA consent

A Development Approval (DA) consent typically contains between 20 and 300+ conditions. Some are straightforward ("work hours: 7am to 6pm Monday to Friday"). Others are buried in schedules and reference external documents. Building a compliance register that captures every obligation — and makes them trackable — is the foundation of project compliance.

What is a compliance register?

A compliance register is a structured record of every condition, obligation, or requirement from your project's approval documents. For each condition, it typically tracks:

• The condition reference (e.g. B5, E12, Schedule 3 Condition 8)
• The original condition text
• A plain-English interpretation
• Risk level and category
• Evidence required to demonstrate compliance
• Responsible party
• Current status and verification history

Think of it as the single source of truth for "what do we need to do, and have we done it?"

Step 1: Read the entire consent end-to-end

This sounds obvious but it's the step most people skip. DA consents are long, repetitive, and written in regulatory language. The temptation is to skim for the "important" conditions and move on. The problem is that the condition you skip is usually the one that causes the stop-work order. Our guide on how to read a development consent breaks down the structure section by section.

Read every page. Read the schedules. Read the referenced documents. If the consent says "in accordance with the approved Environmental Management Plan," you need to read that plan too — its requirements become de facto conditions.

Step 2: Extract every condition

Go through the consent methodically and list every condition. This includes:

• Numbered conditions — the obvious ones (Condition 1, Condition 2, etc.)
• Schedule conditions — often buried in appendices or schedules. These are just as enforceable as the main conditions.
• Referenced document requirements — if the consent says "in accordance with the Traffic Management Plan submitted on [date]," the requirements of that plan are now conditions.
• Standard conditions — many consent authorities include standard conditions by reference. Check if your consent references a "Standard Conditions of Consent" document.

Step 3: Categorise conditions

Group conditions by discipline to make them manageable:

Step 4: Assess risk

Not every condition carries equal risk. A condition about signage placement is low risk. A condition about water discharge into a sensitive waterway is high risk. Rate each condition based on:

• Penalty exposure — what's the maximum fine if breached? See our POEO Act penalties guide for NSW specifics.
• Stop-work potential — could this trigger a stop-work order?
• Reputation risk — could this generate media attention or community backlash?
• Difficulty of compliance — how hard is it to maintain compliance over time?

Step 5: Assign responsibility

Every condition needs one accountable person. Not a team, not a department — a named individual who is responsible for ensuring compliance with that specific condition. This doesn't mean they do all the work, but they own the status.

Step 6: Track and verify

The register is only useful if it's maintained. This means:

• Regular status updates (at minimum weekly during active construction)
• Evidence attached to each condition (not stored separately)
• Verification records — who confirmed compliance, when, and based on what evidence
• Event logs for triggered conditions (e.g. rainfall inspections)