The Plan organises land use regulation through a combination of zoning, schedules, overlay clauses and references to State-level standards. Key concepts, and where they appear in the instrument, are:

• Zoning and Land Use Table (cl 2.1, cl 2.3 and Land Use Table): the Plan’s primary mechanism is conventional zoning. Each zone is given objectives and a Land Use Table that spells out what is permitted without consent, permitted with consent and prohibited. The consent authority must have regard to zone objectives when determining applications (cl 2.3(2)).

• Development pathways: three primary pathways are set out:

  • development requiring development consent (general rule: many uses in the Land Use Table, cl 2.3);
  • exempt development as specified in Schedule 2 and cl 3.1 (must meet Building Code and other tests, and cannot affect State heritage-listed items, cl 3.1(2)-(5));
  • complying development per cl 3.2 and Schedule 3 (requires compliance with specified development standards and conditions, cl 3.2(2)-(4)).

• Maps and overlays: the Plan relies on maps,Land Zoning Map, Lot Size Map, Natural Resources Sensitivity,Biodiversity Map, Land Reservation Acquisition Map, Heritage Map and others. Those maps are adopted instruments under the Plan and are the source of many controls (cl 1.7; cl 1.3; cl 6.1-6.4 reference Natural Resources Sensitivity maps).

• Local overlay controls and matters for consideration: the Plan contains localised development matter controls that the consent authority must consider or satisfy itself of before granting consent. Examples include biodiversity (cl 6.1), land capability and slopes (cl 6.2), waterway protection (cl 6.3), earthworks (cl 6.4), essential services availability (cl 6.5), airport noise compatibility (cl 6.7), and flood planning (cl 5.21). These controls alter the substantive and procedural test for consent beyond the Land Use Table.

• Heritage regime: Schedule 5 lists heritage items and conservation areas; demolition, alterations, excavation and new buildings on heritage/Aboriginal sites require consent (cl 5.10(2)), with specified consultation and notification steps for archaeological sites and Aboriginal places (cl 5.10(7)-(9)).

• Exceptions, thresholds and prohibitions: the Plan creates binary rules in some areas , absolute prohibitions (for example canal estate development, cl 2.9); hard ceilings for certain development types (for example signage sizes in Schedule 2); and exceptions for particular classes to be carried out without consent subject to thresholds and location tests (e.g. intensive livestock smaller-scale operations may be exempt from consent if they meet the thresholds and locational exclusions in cl 5.18(4)-(5)).

• Integration with higher-order instruments and technical standards: the Plan explicitly defers to State environmental planning policies (cl 1.9) and to technical instruments such as the Building Code of Australia (cl 3.1(3)(a)), BASIX requirements (cl 4.6(8)(b)) and the Considering Flooding guideline and Flood Risk Management Manual (cl 5.21(4)-(5)). In practice this means applicants must meet local rules and the applicable State technical/regulatory standards.

• Discretion and record-keeping: the Plan gives the consent authority discretion (for example, in using cl 4.6 to allow contraventions of development standards where justified), but requires assessment records to be kept (cl 4.6(4)). Many clauses require the consent authority to be “satisfied” of specified matters before granting consent (e.g. cl 2.8(3), cl 4.2B, cl 5.19(2)).

These concepts structure incentives: the zoning and Land Use Table channel land use choices; overlay rules increase application information and compliance costs where environmental, heritage, water, or airport noise considerations apply; exemptions and complying pathways offer lower-cost routes provided technical conditions and external approvals are met; discrete prohibitions remove certain development options entirely (for example canal estates).

The Plan allocates rights and duties across different actors and so affects several groups directly:

• Council (the local consent authority): the Council is designated as the consent authority for the Plan (cl 1.6). It makes decisions on development applications, determines if exempt or complying pathways apply, can require heritage management documents or conservation plans (cl 5.10(5)-(6)), and must be satisfied of a range of matters before granting consent (for biodiversity, flood risk, essential services, airport noise, etc.). The Plan also authorises the Council to classify or reclassify public land under the Local Government Act by listing particular parcels in Schedule 4 (cl 5.2).

• Landowners and developers: private owners proposing development are the primary regulated group. They must check zoning (cl 2.2), Lot Size Map (cl 4.1), and any overlay maps. For development to proceed they will either rely on exempt/compliant development criteria in Schedules 2 and 3 (cl 3.1-3.2) or lodge development applications subject to the Plan’s tests and the Act. Owners proposing subdivisions must meet lot-size provisions (cl 4.1, cl 4.1AA, cl 4.2C) and particular constraints for unsewered land (cl 4.2B).

• Heritage property owners and custodians: owners of items listed in Schedule 5 face additional constraints,demolition, alterations, excavations or building works on heritage items or within conservation areas require consent (cl 5.10(2)-(3)), and heritage assessments or conservation management plans may be required (cl 5.10(5)-(6)). There are consultation requirements with the Heritage Council and local Aboriginal communities for certain applications (cl 5.10(7)-(9)).

• Primary production and agriculture operators: the Plan directly addresses agricultural uses via RU zones and by including specific provisions for intensive livestock (cl 5.18), farm stay (cl 5.24), farm gate premises (cl 5.25) and aquaculture (cl 5.19 and Schedule 6). Intensive livestock has defined thresholds below which consent may not be required, but there are locational exclusions (cl 5.18(4)-(5)). Operators must comply with these thresholds and locational controls or prepare information on odour, water pollution, soil degradation and mitigation (cl 5.18(3)).

• Licensed premises and entertainment venues: cl 5.20 establishes that the consent authority must not refuse development for licensed premises on specific grounds relating to music, performance or dancing, and must not refuse on noise grounds where the authority is satisfied noise can be managed to an acceptable level. That affects owners/operators of licensed venues and the consent authority’s assessment approach.

• Applicants near Temora Airport: cl 6.7 requires consent authorities to consider aircraft noise (ANEC contours) and to satisfy themselves that development will meet relevant Australian Standards for interior noise levels for particular uses. This affects residential, educational, healthcare, and certain commercial uses near the airport.

• Public authorities and Crown bodies: the Plan preserves Crown rights and operations. It does not restrict infrastructure development or the use of existing Crown buildings where State SEPP Chapter 2 applies (cl 5.12(1)-(2)). The Plan also sets which State authority is the relevant acquisition authority for particular reserve types (cl 5.1(2)) and preserves registered instruments held by public authorities (cl 1.9A(3)).

• The public and neighbours: residents adjacent to proposed development are affected through the Plan’s amenity and environmental protection clauses (for example cl 2.8 on temporary use, cl 6.4 on earthworks, cl 5.21 on flood planning, and the heritage consultation and notification procedures cl 5.10(3), (7), (8)). Exempt development is still subject to other statutory approvals and common law rights (Schedule 2 note).

In summary, the Plan’s design concentrates decision power and discretion in the Council, operationalises State technical standards and creates a mix of permit and permit-exempt pathways that differentially affect small- and large-scale land users, agricultural operators, heritage custodians and commercial venue operators.

This section sets out the main statutory duties and rights created by the Plan text, with reference to the specific clauses.

Duties of the consent authority (Council):

• Consider zone objectives when determining applications (cl 2.3(2)). The Plan expressly requires the consent authority to have regard to the zone objectives, embedding this as a decision-making duty.
• Ensure development in sensitive overlays meets the Plan’s objectives before consent is granted, including biodiversity (cl 6.1(3)-(4)), land capability (cl 6.2(3)-(4)), water protection (cl 6.3(3)-(4)), earthworks (cl 6.4(3)), essential services availability (cl 6.5), and flood planning compatibility (cl 5.21(2)-(3)).
• Require and consider heritage assessment documents and conservation plans where relevant (cl 5.10(4)-(6)) and notify external bodies (Heritage Council, local Aboriginal communities) in specified circumstances (cl 5.10(7)-(9)).
• Keep a record of assessments under the exception to development standards clause (cl 4.6(4)).
• Be satisfied that certain local thresholds and technical standards are met prior to granting consent (e.g. aquaculture site/location and operational requirements, cl 5.19(2); airport noise compatibility, cl 6.7(2)).

Duties of applicants and proponents:

• Demonstrate compliance with exempt or complying development criteria where applicable, including adherence to the Building Code of Australia and BASIX obligations where relevant (cl 3.1(3)(a), cl 4.6(8)(b)); provide certifying documents for contraventions of development standards as required by the Regulation (cl 4.6(3) note).
• For applications proposing to contravene a development standard, provide a document that sets out the planning grounds addressing cl 4.6(3)(a)-(b) as required by the Environmental Planning and Assessment Regulation (cl 4.6(3) note).
• Where development affects heritage items, archaeological sites or Aboriginal places, provide necessary heritage management documents and engage with consultation/notification processes (cl 5.10(5)-(9)).
• For unsewered developments seeking complying development, obtain local government approval for on-site effluent systems where required (cl 3.2(3)(c)).
• For subdivisions, respect minimum lot sizes on the Lot Size Map (cl 4.1(3), cl 4.1AA(3)) and the specific rules preventing subdivision that would separate secondary dwellings from principal dwellings (cl 2.6(2)).

Rights and entitlements:

• The Plan preserves a landholder’s right to have pre-commencement development applications determined under the prior instrument regime (cl 1.8A).
• The Plan provides applicants with defined pathways for exempt and complying development subject to meeting technical tests (cl 3.1-3.2).
• The consent authority may grant consent otherwise prohibited by the Plan if conservation incentives are satisfied for heritage items (cl 5.10(10)), providing a conditional right to approvals that facilitate conservation in return for specified works.
• Clause 1.9A gives applicants a right to proceed with development despite private covenants where necessary to enable development under the Plan, except for certain instruments listed in cl 1.9A(2). That clause also preserves public authority registered interests (cl 1.9A(3)).

Procedural constraints:

• Exempt or complying development is excluded on environmentally sensitive areas specified in cl 3.3(1), making some lower-cost pathways unavailable for environmentally constrained land.
• Certain development standards are expressly excluded from the exceptions process in cl 4.6(8) (for example BASIX commitments, clauses 5.4, 5.5, cl 5.4 types, and clauses 4.2A, 4.2C,6.1-6.3), limiting the consent authority’s ability to relax those standards.

Rights preserved for other authorities:

• The Plan recognises the primacy of State SEPPs where they prevail (cl 1.9(1)) and preserves the operation of State infrastructure provisions (cl 5.12). It identifies the State acquisition authority for specific reserved land shown on the Land Reservation Acquisition Map (cl 5.1(2)).

Collectively, these duties and rights create a framework of conditional entitlements for landowners and procedural obligations for the Council. They place emphasis on technical compliance, prescribed evidence for non-standard approvals, and targeted consultation/notification duties in heritage and Aboriginal contexts.

The Plan itself does not set out monetary fines or criminal penalties. Enforcement and penalties for unauthorised development or breaches of the Plan are matters dealt with under the Act and associated regulations, which the Plan repeatedly references (for example cl 1.6, cl 3.1 note, and cl 3.2 note). The Plan allocates regulatory effect through permit requirements and procedural checks rather than through standalone sanction clauses within its text.

What the Plan does specify that is relevant to enforcement and compliance:

• It prescribes when development consent is required, and when development may be exempt or complying (cl 2.1-2.8; cl 3.1-3.2). Non-compliance with those regimes generally places development outside the lawful pathways established by the Plan and thereby brings the enforcement mechanisms of the Act into play (for example, orders to cease work, remediation, penalties under the Act).
• It requires the consent authority to keep records of decision-making where exception to development standards is used (cl 4.6(4)). That record-keeping is a procedural obligation that supports accountability and provides an audit trail for review or enforcement.
• Heritage and Aboriginal site protections create specific procedural steps and notification obligations (cl 5.10(7)-(9)), and failure to follow heritage controls can give rise to enforcement under heritage legislation referenced (note: the Plan references the Heritage Act 1977 and matters such as the State Heritage Register).
• The Plan disallows exempt or complying development on environmentally sensitive areas (cl 3.3). Undertaking exempt/compliant works notwithstanding the exclusion is a breach of the Plan’s definition of lawful development and would attract regulatory response under the Act.

Practical enforcement mechanism implications (as stated or implied by the Plan and its references):

• enforcement actions (in the Act) will be the principal mechanism to address breaches of the Plan’s consent requirements;
• compliance with external technical standards (Building Code of Australia, BASIX, fisheries/aquaculture licences, Local Government Act approvals for on-site effluent) is material to whether a development is exempt/compliant; noncompliance with those external approvals may attract separate enforcement actions under those instruments (the Plan notes that exempt development does not remove the need for other licences or approvals, Schedule 2 note);
• the Plan preserves registered public authority interests and excludes certain covenants from the suspension clause (cl 1.9A(2)-(3)), meaning enforcement of those superior public interests continues under other legislation.

Because penalties and enforcement powers are statutory under the Act and other referenced statutes, readers seeking precise penalty amounts, time limits for prosecutions or the procedural steps for issuing compliance notices must consult the Act, the Regulations and relevant enforcement provisions in the specific statutes referred to in the Plan. The Plan allocates permitted and prohibited pathways and triggers the enforcement architecture of those Acts when its permission regime is breached.

The Plan is an environmental planning instrument operating within the hierarchy of NSW planning law. The instrument itself cross-references, incorporates, or defers to numerous State and other statutes and policies. The Plan states these interactions explicitly and sets limits on their operation in several places:

• State Environmental Planning Policies (SEPPs): the Plan is subject to any SEPP that prevails over it as provided by s 3.28 of the Act (cl 1.9(1)). The Plan also lists several SEPPs and State instruments in notes (e.g. State Environmental Planning Policy (Housing) 2021 and SEPP (Transport and Infrastructure) 2021 in the Land Use Table note). This means a SEPP can override local provisions where it so provides.

• The Act and regulations: the Plan operates "subject to the Act" (cl 1.6) and references the Environmental Planning and Assessment Regulation 2021 procedures (cl 4.6 note), and Division 3.5 of the Act is referenced in the savings provision note (cl 1.8A note). The Plan’s procedural requirements are therefore implemented within the Act’s broader decision-making and merits review framework.

• Building Code of Australia and BASIX: exempt and complying development are conditional on compliance with the Building Code of Australia (cl 3.1(3)(a)-(b); cl 3.2(2)(b)). Clause 4.6 excludes BASIX-related development standards from the exceptions power (cl 4.6(8)(b)). In practice this ties local exempt or complying development pathways to Commonwealth/State building standards and to energy/sustainability commitments allowed under BASIX.

• Heritage Act and Aboriginal heritage law: the Plan requires notification and consultation with the Heritage Council when archaeological sites are affected (cl 5.10(7) and cl 5.10(9)) and requires consideration of Aboriginal places (cl 5.10(8)). It references the Heritage Act 1977 and the State Heritage Register explicitly.

• Crown and local government law: the Plan interacts with the Local Government Act 1993 for classification/reclassification of public land (cl 5.2); it references the Land Acquisition (Just Terms Compensation) Act 1991 when specifying the relevant State authority for owner-initiated acquisition (cl 5.1), and it preserves relevant Crown instruments and public authority interests under the suspension of covenants clause (cl 1.9A(3)).

• Natural resources and specialist statutes: the Plan invokes fisheries, marine park and biodiversity legislation in its aquaculture and environmentally sensitive area controls (cl 3.3, cl 5.19 and Schedule 6 which refer to the Fisheries Management Act 1994, Marine Estate Management Act 2014, and Biodiversity Conservation Act 2016). Intensive livestock agriculture and aquaculture provisions also incorporate State departmental guidelines and industry development plans (cl 5.18(3)(h) and cl 5.19(5)).

• Emergency and risk statutes: bush fire hazard reduction work under the Rural Fires Act 1997 is expressly permitted without development consent (cl 5.11). Flood planning references departmental guidelines and Flood Risk Management Manual (cl 5.21(4)-(5)), embedding State guidance into local assessment thresholds.

• Planning instruments that alter private rights: Clause 1.9A suspends private covenants and agreements to the extent necessary to enable development in accordance with the Plan, subject to significant exceptions (cl 1.9A(1)-(2)). That provision interacts directly with property law instruments and creates an operational overlap between local planning permissions and private property limitations.

• External regulatory approvals: the Plan repeatedly notes that exempt development does not remove the need for other approvals (Schedule 2 note) and that complying development certificates are subject to conditions and external approvals (cl 3.2(4)-(5), Schedule 3). For unsewered development, complying development requires local government approval for on-site effluent systems under the Local Government Act (cl 3.2(3)(c)).

Overall, the Plan functions as one layer within a multi-layered legal system. It both defers to higher-order SEPPs and technical standards, and it supplements them with localised controls (maps, heritage listings, rural subdivision rules). Where conflicts arise, the Plan directs that State instruments prevail. At the same time the Plan contains provisions (for example cl 1.9A) that can affect private-law instruments, subject to specific statutory limitations and approvals noted in the text.

The Plan text includes amendment notes and insertion/repeal markers that show legislative updates recorded in the instrument. The Plan as provided incorporates multiple amendments; the instrument itself annotates several such changes. The following items extract the amendments as recorded in the text (citations are as given in the Plan):

• Clause 1.8A (Savings provision relating to development applications): appears with an amendment note "cl 1.8A: Am 2019 (621), Sch 5[1]". That indicates insertion or amendment in 2019 (instrument 621), Schedule 5[1].

• Clause 1.9A (Suspension of covenants, agreements and instruments): shows amendment notes "cl 1.9A: Am 2011 (363), Sch 23 [1]; 2019 (621), Sch 5[2]-[4]". This indicates changes made in 2011 and 2019.

• Clause 2.1 (Land use zones): annotated "cl 2.1: Am 2022 (832), Sch 1.21[1]". This indicates a 2022 amendment to the zoning clause.

• Land Use Table amendment history is noted extensively: "Land Use tbl: Am 2011 (363), Sch 23 [2]-[11]; 2018 (488), Sch 1.1 [1]; 2019 (137), Sch 6 [1]; 2019 (602), Sch 1[1]-[38]; 2019 (621), Sch 3; 2020 (71), cl 5; 2022 (314), Sch 1; 2022 (832), Sch 1.21[2]; 2023 (458), Sch 2.73." Those entries reflect multiple circuit amendments between 2011 and 2023 amending permitted uses, prohibitions and other Land Use Table content.

• Clause 4.1AA (Minimum subdivision lot size for community title schemes): marked "cl 4.1AA: Ins 2011 (363), Sch 23 [12]" showing it was inserted in 2011.

• Clause 4.2C (Minimum subdivision lot size for strata subdivision): shows "cl 4.2C: Am 2011 (363), Sch 23 [13] [14]".

• Clause 4.6 (Exceptions to development standards): shows "cl 4.6: Am 2011 (363), Sch 23 [15] [16]; 2022 (832), Sch 1.21[3]". So amendments in 2011 and 2022 affected this clause.

• Clause 5.4 (Controls relating to miscellaneous permissible uses): records multiple amendments "cl 5.4: Am 2011 (363), Sch 23 [17] [18]; 2018 (406), Sch 1.30 [1] [2]; 2023 (458), Sch 1[1]".

• Clause 5.9 (Dwelling house or secondary dwelling affected by natural disaster): contains "cl 5.9: Am 2011 (363), Sch 23 [19]" and notes one part repealed (5.9AA repealed).

• Clause 5.13 (Eco-tourist facilities): inserted "cl 5.13: Ins 2011 (363), Sch 23 [20]".

• Schedule 1 notes record "sch 1: Am 2018 (553), cl 4 (1); 2022 (832), Sch 1.21[4]".

• Schedule 4 (Classification and reclassification of public land): "sch 4: Am 2016 (199), cl 5."

• Schedule 5 (Environmental heritage): "sch 5: Am 2020 (59), Sch 1[1]-[21]."

• Clause 6.6 is noted as repealed "cl 6.6: Rep 2021 (225), Sch 1."

• Various other insertions and substitutions: cl 5.24 and cl 5.25 are marked "Subst 2023 (458), Sch 1[4]" and "Subst 2023 (458), Sch 1[4]" respectively, indicating substitution in 2023.

Those in-text amendment markings identify the formal statutory changes recorded on the instrument. They point to a pattern of iterative local amendments across 2011, 2016, 2018, 2019, 2020, 2021, 2022 and 2023. The Plan’s notes and Sch references provide a traceable legislative history within the instrument itself.

For a complete legislative amendment history (including commencement dates of each amendment, the exact text changed and the Government Gazette references), practitioners should consult the official consolidated instrument on the NSW legislation website (the Plan’s commencement clause 1.1AA notes that the instrument commences on publication) and the primary source consolidated with marginal notes showing the amending instruments and dates.

The Plan text provided does not refer to or cite any court decisions or litigation. It contains no cases or judicial interpretations within its text and does not record any relevant litigation history or Court of Appeal/Supreme Court decisions.

Consequently, this instrument, as given, contains no named judicial authorities and does not report any litigation outcomes. Any judicial interpretation, statutory challenge or merits review arising under the Act, other SEPPs or related instruments would sit outside the Plan text and must be researched through court databases and the Act’s case law repository. The Plan itself does, however, create decision points and discretionary acts for which merits review or judicial review under the Act may be pursued; those avenues and any litigation should be explored by reference to the Act and case law rather than the Plan text.

Practitioners and applicants should pay attention to the following traps and operational nuances explicitly embedded in the Plan:

• Savings provision preserves prior DAs (cl 1.8A): a development application lodged before the Plan’s commencement and not finally determined must be determined as if the Plan had not commenced (cl 1.8A). That creates an asymmetry between pre- and post-commencement applicants and can materially affect project viability and rights. The Plan’s note points to Division 3.5 of the Act as a mechanism for development requiring changes to the instrument; the consequence is that a developer who times a lodgement before commencement can avoid the new plan’s constraints.

• Suspension of covenants (cl 1.9A): the Plan authorises that private agreements, covenants or similar instruments that restrict development do not apply to the extent necessary to enable development under the Plan (cl 1.9A(1)), but it expressly carves out covenants imposed by Council and certain Crown or conservation instruments (cl 1.9A(2)). It also preserves public authority interests in registered instruments (cl 1.9A(3)). Practically, this can allow development that would otherwise be blocked by private covenants, but only where those covenants are not listed in the exclusions. Counsel should check whether the covenant is one of the listed exceptions or a registered instrument of a public authority.

• Exempt/compliant development exclusions for environmentally sensitive areas (cl 3.3): exempt and complying development paths are unavailable on "environmentally sensitive areas" as defined in cl 3.3. This exclusion can unexpectedly remove lower-cost or expedited pathways for land identified on the Plan’s biodiversity, water or other sensitivity maps. Applicants must consult the Natural Resources Sensitivity maps before relying on exempt/compliant classifications.

• Many "must be satisfied" tests create evidentiary burden on applicants: clauses such as cl 2.8(3), cl 4.2B, cl 5.19(2) and cl 6.7(2) require the consent authority to be satisfied of particular matters. The Plan thus imposes documentation and technical evidence requirements on applicants (e.g. coastal/flood engineering, noise attenuation for airport-affected land, aquaculture site criteria, on-site sewage adequacy), increasing application costs.

• Exceptions to development standards have explicit limits (cl 4.6): while cl 4.6 allows flexibility to contravene standards in limited circumstances, it excludes certain standards and topics from its operation (e.g. BASIX commitments and several specific clauses listed in cl 4.6(8)). Also, cl 4.6(6) prohibits using the exceptions power to subdivide to create multiple subminimum rural lots or lots below 90% of the minimum, which limits creative subdivision strategies.

• Intensive livestock thresholds with locational exclusions (cl 5.18): some small-scale livestock operations may proceed without consent if they meet numeric thresholds and are not located within sensitive areas or minimum proximity distances to other farms or dwellings (cl 5.18(4)-(5)). Practitioners must confirm both footprint and location conditions; a project that meets the size threshold may still require consent because of proximity or environmental exclusion.

• Heritage and Aboriginal consultation requirements can add delay and conditions (cl 5.10): the consent authority may require heritage management documents or conservation plans, and must notify the Heritage Council and local Aboriginal communities in some cases (cl 5.10(5)-(9)). Failure to budget for these steps can generate delay or additional conditions.

• Exempt development does not remove other approvals (Schedule 2 note): even if a development qualifies as exempt under the Plan, other statutory approvals and common law property rights still apply. Practitioners should not assume that a lack of development consent requirement cures all other regulatory or civil constraints.

• Airport noise requirements (cl 6.7) include technical standards: development near Temora Airport must meet AS/NZS-style noise siting and interior noise standards. Applicants must check ANEC/ANEC contour mapping (cl 6.7(2)-(3)) and provide evidence of compliance, which adds a technical compliance component not always obvious from a zoning table.

• Canal estate prohibition (cl 2.9): the Plan expressly bans canal estate development (cl 2.9(1)-(2)). Proposals involving constructed waterways with residential development that involve fill or excavation to comply with flood planning are precluded.

• Signage and specific local thresholds: Schedule 2 sets detailed size and locational limits for temporary community event signage, real estate signage and moveable advertising signage. These localised numeric limits can be stricter than broader State rules and require attention to avoid infractions.

These "gotchas" are not covert , they are explicit in the Plan , but they create practical traps when combined with State standards, the requirement for external approvals (BASIX, Building Code), and the Plan’s overlay maps. Practitioners should cross-check the Plan maps and schedules and confirm whether any relevant State policy prevails.

The Plan creates a multi-step compliance pathway. Below is a practical checklist, grounded in the Plan, for applicants, owners, and advising practitioners.

1. Identify the land and authoritative maps

• Confirm the land to which the Plan applies using the Land Application Map (cl 1.3).
• Check the Land Zoning Map for the applicable zone and the Lot Size Map for minimum lot sizes (cl 2.2; cl 4.1).
• Inspect overlay maps referenced in the Plan: Heritage Map, Natural Resources Sensitivity,Biodiversity Map, Natural Resources Sensitivity,Land Map, Natural Resources Sensitivity,Water Map, Land Reservation Acquisition Map and the Temora Airport ANEC/ANEF map where relevant (cl 1.7; cl 6.1-6.4; cl 5.1; cl 6.7).

2. Establish the permissible pathway

• Consult the Land Use Table (cl 2.3 and Land Use Table) to determine whether the proposed use is permitted without consent, permitted with consent, or prohibited in the relevant zone.
• If the use is listed as exempt development in Schedule 2 and meets the Schedule’s standards, confirm exemption under cl 3.1. Remember exempt development must meet Building Code of Australia requirements and not affect State heritage items or environmentally sensitive areas (cl 3.1(2)-(5); cl 3.3).
• If the use is complying development in Schedule 3, verify compliance with the conditions and the requirement that the development is permissible with consent in the zone, meets Building Code and, where applicable, on-site effluent approvals for unsewered land (cl 3.2(2)-(4)).

3. Check overlay and technical constraints

• For biodiversity and sensitive land, follow cl 6.1-6.3: identify any adverse impacts and prepare mitigation/restoration measures. The consent authority must be satisfied the development is consistent with the clause objectives (cl 6.1(3)-(4); cl 6.2(3)-(4); cl 6.3(3)-(4)).
• For earthworks, ensure the work does not alter ground level by more than 600 mm unless it is ancillary to approved development or exempt (cl 6.4(2)-(3)).
• For flood-prone land, apply cl 5.21: demonstrate compatibility with flood function, evacuation, and environmental protection and use the Considering Flooding guideline and Flood Risk Management Manual as technical references (cl 5.21(2)-(5)).
• For Temora Airport-affected land, check ANEC contours and satisfy AS 2021,2000/ANEC-based standards as required by cl 6.7(2)-(3).

4. Prepare required assessments and documents

• Where heritage items or conservation areas are relevant, prepare heritage management documents or conservation management plans as the consent authority may require, and comply with consultation/notification obligations (cl 5.10(4)-(6), (7)-(9)).
• For proposals contravening a development standard, prepare the statutory document required by the EP&A Regulation setting out planning grounds under cl 4.6(3), and be aware the consent authority must keep a record of its assessment (cl 4.6(4)).
• For aquaculture or intensive livestock proposals, prepare site suitability and operational plans that address cl 5.19 and cl 5.18 matters (water quality, odour, soil impact, compliance with industry codes, Schedule 6 requirements).

5. Engage statutory consultation and approvals

• Where the Plan requires notification (Heritage Council, local Aboriginal communities, other agencies), build the consultation and timeframes into the project timeline (cl 5.10(7)-(9)).
• For exempt/compliant works that nonetheless require other statutory licences (fisheries, marine park, Crown approvals, on-site effluent approvals), lodge those applications in parallel, noting Schedule 2 warns that exempt development is not exempt from other Acts (Schedule 2 note).

6. Consider covenant and title constraints

• Review private covenants and registered instruments. If a private covenant might constrain development, consider cl 1.9A: the Plan may render such covenants inoperative to the extent necessary to permit development, but covenants imposed by Council and certain Crown/conservation instruments are excluded (cl 1.9A(1)-(3)). Confirm whether the covenant is one of the listed exceptions.

7. Subdivision and lot-size issues

• For subdivisions, apply the Lot Size Map rules (cl 4.1), and for community title or strata subdivisions consult cl 4.1AA and cl 4.2C (community title minimums; strata subdivision minimums for specified zones).
• Be aware cl 4.6 prevents using the exceptions power to create multiple subminimum rural lots or lots below 90% of minimum area in specified rural and conservation zones (cl 4.6(6)).

8. Timing, fees and decision-making

• Recognise that pre-commencement DAs may be determined under the prior instrument (cl 1.8A). If timing is critical, document lodgement dates and check transitional provisions.
• Plan for the Council’s discretion: many clauses require the consent authority to be “satisfied” of matters. This imposes an evidentiary burden on applicants and can increase application time and cost (see cl 2.8, cl 5.19, cl 6.7, and other "must be satisfied" clauses).

9. Maintain records and anticipate conditions

• For approvals involving variations under cl 4.6, expect the consent authority to keep records (cl 4.6(4)). For complying development certificates, expect standardised conditions per Schedule 3 and potential time-of-day conditions for specified work (see cl 5.8(4) for fire alarm conversion examples).

10. Seek specialist input

• Where the Plan references industry development plans, ANEC mapping, flood and bushfire guidelines, and technical Australian Standards, secure appropriate expert reports (acoustic engineers for airport noise, geotechnical/flood engineers, heritage consultants, ecological assessments) so that the consent authority can be satisfied of the required matters.

In short, compliance requires a mapped-first approach (zone, lot size, overlays), confirming the development pathway (exempt/compliant/consent), preparing the technical and statutory material required by the Plan (heritage, biodiversity, flood, on-site effluent, noise), and coordinating any required external licences. The Plan repeatedly ties local permissions to State technical regimes and external approvals, so practitioners should treat the Plan as one element within a broader compliance matrix.