NSW standard and model conditions of consent: what the proposed SEPP means for your register

Who this is forEnvironmental and compliance staff on NSW construction and infrastructure projects, and anyone who keeps a conditions register and wants to know what the proposed SEPP would change before it is made.

NSW is part way through replacing the way conditions of consent are written. Standard-format conditions have applied since 30 June 2023. The next step, a statewide State Environmental Planning Policy that would fix the wording of some conditions and supply editable templates for others, has been through public exhibition and had not been made at 4 September 2026. This guide sets out what has been proposed, what is already in force, and what a compliance register should do about it now. Everything about the SEPP below is a description of a proposal, not of the law.

Where things stand

• Standard-format conditions are already required. Since 30 June 2023 consent authorities in NSW have issued conditions in a standard format and order, grouped by the stage of the development they attach to. This is about structure, not content. A council can still write whatever condition it considers appropriate, but it has to sit in the standard place with the standard headings.
• The legal basis for standard and model conditions exists. The Environmental Planning and Assessment Amendment (Planning System Reforms) Act 2025 amended the Environmental Planning and Assessment Act 1979 to allow an environmental planning instrument to prescribe conditions that must, or may, be imposed on a consent. That is the hook the SEPP would hang on.
• The SEPP itself has been exhibited, not made. The Department of Planning, Housing and Infrastructure exhibited an Explanation of Intended Effect for a statewide standard and model conditions of consent SEPP, with submissions closing on 30 July 2026. At 4 September 2026 the SEPP had not been made and no commencement date had been set. Check the DPHI conditions of consent page for the current position and the exhibition page for the Explanation of Intended Effect.

What is proposed

The Explanation of Intended Effect describes two kinds of prescribed condition.

• Standard conditions would be fixed. The consent authority would have to impose them as written and could not amend them. The intent is that the same obligation reads the same way on every consent in the state.
• Model conditions would be templates. The consent authority could edit them to suit the site, or leave them out where they do not apply. They set a starting point rather than a rule.

The proposal covers all residential development, with one set of conditions for low-rise housing and another for mid-rise and high-rise residential, shop-top housing and State significant development. The two sets are built differently. Conditions for low-rise development would be scaled to the impact of the work and written as outcomes: the result that must be achieved rather than the method. Conditions for mid-rise, high-rise, shop-top and State significant development would be management-plan based: the consent would require a plan (construction management, traffic, noise and vibration, erosion and sediment control, waste and so on), the plan would be prepared and approved, and the approved plan would then carry the detailed commitments.

Two things follow. First, if the SEPP is made in the exhibited form, a lot of what is currently negotiated condition by condition would become either fixed or templated. Second, for the larger projects that most construction contractors work on, the centre of gravity moves from the consent to the management plans it calls up.

What that means for a compliance register

Numbering becomes consistent, and worth keeping

Today a register built from three consents from three councils has three numbering schemes, three sets of headings and three ways of saying "prior to the issue of a construction certificate". If standard conditions carry a fixed number and fixed wording, a register can index on that number. The same condition would have the same identity across every project, which makes it possible to reuse a plain-English interpretation, a checklist and an evidence expectation rather than rewriting them each time. The practical move now is to stop numbering rows by position in the register and start recording the condition number exactly as it appears in the instrument, with the instrument named beside it. The register template is set up that way.

Management-plan conditions spawn sub-commitments

A management-plan condition is one row on the consent and many rows on the ground. "Prepare a Construction Noise and Vibration Management Plan" is a single deliverable due before commencement. The approved plan then commits the project to noise management levels at named receivers, attended monitoring on a cadence, respite periods, a complaints procedure and a response time for exceedances. None of those appear on the consent. All of them are conditions of the consent in effect, because the consent requires the plan to be complied with.

A register that lists only the consent conditions will show that project as one row, Complete, with the approved plan attached. An auditor sampling that row will open the plan and ask for the monitoring results. This is already the pattern on State significant projects and it is the pattern the proposed SEPP would extend to mid-rise and high-rise residential work. The register needs a parent row for the plan condition and child rows for every commitment in the approved plan, each with its own trigger, owner, cadence and evidence. Our guide to CEMP inspection schedules covers how those commitments turn into a schedule crews can actually follow.

Hold points move into the plans

The staged structure of standard-format conditions already makes the hold points visible: prior to commencement, prior to the construction certificate, prior to the occupation certificate. Management-plan conditions add a second layer. The plan itself often sets hold points that the consent never mentions, such as a sediment basin commissioned and certified before bulk earthworks, or a pre-clearance survey signed off before any vegetation is removed. Those are the ones that get missed, because they are inside a document rather than on the consent. Pull them out into the register as milestone gates so the site programme can see them. The distinction between a hold point and a witness point matters here, and it is explained in hold points vs witness points.

Outcome-based conditions need an evidence expectation written down

An outcome-based condition on a low-rise consent says what must be achieved, not how. "Sediment must not leave the site" is easy to agree with and hard to evidence. Where the condition does not specify a method, the register needs to: what the project will do, how often, and what record will show it was done. Write that down at the start, in the plain-English column, so the team and any auditor are testing the same thing.

What to prepare now

• Record conditions by instrument and by the instrument's own number. When standard numbering arrives, a register built this way maps onto it. One built on row numbers does not.
• Break management plans into commitments now. Every approved plan on a live project should already be reflected as rows in the register with a trigger and an owner. If the plan is 80 pages and the register has one row for it, that is the gap to close first.
• Give each condition a type. Deliverable, one-off action, milestone gate, ongoing monitoring, reporting obligation, KPI target or continuous compliance. The proposal separates conditions by stage and by whether they are outcome or plan based. A typed register can be sorted the same way, which is how the claused. register and field app are organised.
• Write the evidence expectation before the work starts. For each row, the record that will demonstrate compliance. Photos with time and location, a signed checklist, a lab result, a docket, a letter. This is the column that decides how an audit goes, and it is explained in the guide to the condition evidence pack.
• Keep a copy of each instrument with the register. When consents move to standard wording, older consents will not be rewritten. A project running under a 2025 consent will still be audited against the 2025 wording.
• Watch the DPHI page, not the news. The SEPP will be made, or changed, or not, on the department's timetable. The conditions of consent page is where that will be recorded.

What this does not change

It is worth being plain about the limits. Standardising the words of a condition does not change what compliance with it requires. A rainfall inspection is still due after the rain. A monthly report is still due on the day. An exceedance still has to be recorded, actioned and closed. The evidence that shows those things happened is the same evidence whether the condition was written by a council officer or drawn from a state template, and an auditor will still ask for it one condition at a time. Deadlines remain deadlines. Existing consents keep their existing wording. Environment protection licence conditions, EPBC approval conditions and the commitments inside management plans are outside the SEPP entirely and continue as they are.

The proposal changes how conditions are written. It does not change how they are kept. The register, the triggers, the owners and the evidence trail are the same work either way, and the projects that have that work in order will find the transition easy. That is the whole of the practical advice.

The short version

Standard-format conditions have applied in NSW since 30 June 2023. The 2025 reforms created the power to prescribe standard and model conditions. A statewide SEPP to do that was exhibited to 30 July 2026 and had not been made at 4 September 2026. If it is made as proposed, standard conditions would be fixed, model conditions editable, low-rise residential conditions outcome-based and mid-rise, high-rise, shop-top and State significant conditions management-plan based. For a register, that means indexing by instrument and condition number, breaking every management plan into its commitments and hold points, and writing the evidence expectation down before the work starts. None of that waits for the SEPP. It is good practice now.

This guide is general information about a proposed instrument, not legal advice. The conditions that bind a project are the ones written in its own consent, licence and approved plans.