Licence Area Plan – Cooma Radio

The endnotes centre on four main concepts: compilation metadata, abbreviation and amendment notation, legislation history and provision‑level amendment history. Each is described in the endnotes.

• Compilation metadata. Endnote 1 explains that the endnotes supply information about the compilation and the compiled law. The compilation metadata function is mechanical: it identifies the document as a compiled instrument, and explains the role of the endnotes in relation to the compiled text (Endnote 1). This tells the reader that the endnotes are not the operative statutory text but a guide to it.

• Abbreviation and amendment notation. Endnote 2 provides an "Abbreviation key" listing shorthand used in the amendment history. The table shows entries such as "ad = added or inserted", "am = amended", "rep. = repealed" and (in the supplied text) a combined string "rep. = repealedrs. = repealed and substituted" that appears to be a formatting or line‑break issue. The existence of the key indicates that the provision‑level history will use compact codes to indicate the type of amendment (Endnote 2).

• Legislation history. Endnote 3 contains a table headed "Legislation history" that lists the instrument name or variation, the Gazette registration/notification identifier, the date of commencement, and a column labelled "Application, saving and transitional provisions". The entries include the 1999 original plan, variations in 2003 and 2004, the 2011 Variation No. 1, the 2017 Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument (No. 1), and the 2019 Variation. Each row supplies a registration identifier and a commencement date (Endnote 3 table). The "Application, saving and transitional provisions" column is present but blank for the listed rows; Endnote 3's prefatory material warns that such provisions may exist but may not be included in the compilation.

• Provision‑level amendment history. Endnote 4 sets out which specific parts of the compiled instrument have been changed across amending instruments. The table lists "Provision affected" against "How affected", and records multiple entries using the abbreviations from Endnote 2. For example, the "Title pagePage 2" entry records "am. No.1 of 2011; am. No.1 of 2019.am. No.1 of 2011." and many Attachments and Schedules are recorded as "rs. No.1 of 2011; am. No.1 of 2019" or similar. Entries also indicate additions ("ad. No.1 of 2019") and at least one replacement and repeal ("Attachment 1.26.1 ad. No. 1 of 2011; am. No. 1 of 2017; am. No.1 of 2019, rep. No.1 of 2019"). The prefatory paragraph to Endnote 4 also explains the handling of misdescribed amendments with "(md)" and "(md not incorp)" flags.

These concepts are mechanical tools for a reader or practitioner who needs to track the genealogy of the licence area plan. The endnotes do not supply substantive definitions of broadcasting concepts, radio technical parameters, licence terms, rights or obligations. They exist to enable correct legal tracing of the instrument through time. Where the endnotes indicate absence , for example, the possibility that transitional or saving provisions are omitted from the compilation , that absence is itself a concept the user must account for when relying on the compilation (Endnote 3).

The endnotes themselves do not contain operative obligations targeted at named persons or classes. They are metadata about a licence area plan. Nevertheless, the content and structure of the endnotes identify categories of stakeholders who have practical reasons to use the compilation.

• Regulatory and administrative users. The endnotes list Gazette registration numbers, commencement dates and revision identifiers (Endnote 3 table). Regulators, counsel, parliamentary drafters and government records officers who must confirm the current status of the Cooma licence area plan will rely on those details to retrieve primary instruments and to verify commencement and registration. The endnotes therefore materially affect those responsible for maintaining statutory registers and preparing or responding to statutory updates.

• Legal and compliance advisors. Lawyers, compliance officers and advisers who need to advise clients about radio licences, planning parameters or rights tied to a licence area will use the endnotes to trace which attachments and schedules are in force and which have been added, replaced or amended (Endnote 4 table). The provision‑level amendment history is the primary tool for determining whether a given attachment has been superseded.

• Licence holders and prospective applicants. Although the endnotes do not list licence holders, the title and entries in Endnote 3 identify the subject matter: a licence area plan for Cooma Area (Radio). Individuals and entities holding licences or applying for radio facilities in that licence area will be affected because the plan and its attachments and schedules determine the regulatory parameters governing licences. The endnotes indicate where those parameters have been amended, and therefore affect the ability of licence holders to confirm the current technical and territorial conditions of their licences (Endnote 3; Endnote 4).

• External stakeholders needing historical change‑tracking. Journalists, researchers and industry participants seeking to map how the Cooma plan changed between 1999 and 2019 will find the endnotes directly relevant. The endnotes record not only amendments but also the instruments by which they were made and their commencement dates (Endnote 3 table).

• Users who require transitional or saving provisions. The endnotes explicitly state that the legislation history table includes "application, saving and transitional provisions" information that is not included in the compilation (Endnote 3). Practitioners who need to know whether transitional arrangements affect rights or obligations must therefore treat these endnotes as an index that signals where further inquiry is required, rather than as a self‑contained source of entitlement or obligation.

Who does not get direct treatment in the endnotes is equally important. The endnotes do not set enforcement, penalty or sanction regimes, nor do they set substantive broadcasting rules or technical parameters. They do not list specific names of licence holders, nor do they reproduce the operative clauses of the plan. For persons requiring those operative details, the endnotes point to the amending instruments and dates but do not replace the need to consult the primary instrument and the amending documents listed in Endnote 3.

The endnotes as supplied do not establish operative statutory duties or rights. They are an editorial and bibliographic apparatus for the compiled instrument. That absence is material for legal practice and compliance.

• No substantive duties or rights in the endnotes. The text of Endnotes 1 through 4 describes the role of the endnotes, the abbreviation key and the amendment history tables. The endnotes do not set licence conditions, technical planning parameters, rights of licence holders, or obligations on licence applicants, nor do they stipulate enforcement mechanisms. The absence of substantive provisions means practitioners must use the endnotes to locate the operative texts which will contain key duties and rights.

• Duties implied by the existence of amendments. The provision‑level amendment history lists numerous changes to clauses, schedules and attachments (Endnote 4 table). Where a clause or attachment is marked "rs." (replaced and substituted), "am." (amended), or "ad." (added), the practical implication is that the text that governs duties or rights has changed and that any duty or right arising under that provision will now be controlled by the current version of the provision. The endnotes therefore place a duty on users of the compilation to confirm which version is current by checking the amending instruments and commencement dates recorded in Endnote 3.

• Rights and expectations tied to commencement and transitional provisions. Endnote 3 includes a column for "Application, saving and transitional provisions", and the prefatory material warns that such provisions may not be included in the compilation. The rights or duties that flow from an amendment may be shaped by transitional rules that specify whether the amendment applies retrospectively, protects existing arrangements, or phases in change. Because these details may not be in the compilation, the endnotes create an obligation on readers to inspect the amending instruments listed in Endnote 3 to determine the scope and timing of rights or duties.

• Treatment of misdescribed amendments. Endnote 4 explains that where an amending instrument is misdescribed but can be given effect as intended, the compiler incorporates it and flags it with "(md)"; where it cannot, the compiler notes "(md not incorp)". This establishes a procedural duty for users to pay attention to "(md)" flags when relying on the compiled text because those flags indicate that the compilation treated a potentially imperfect amending instrument as effective. The absence of such flags in the supplied excerpt does not mean they do not exist elsewhere in the compilation.

In practice, this means the endnotes are a tool for identifying where substantive duties and rights will be found, but they do not themselves define those duties and rights. A practitioner must follow the cross‑references and Gazette registration identifiers in Endnote 3 and the provision‑level tags in Endnote 4 to the primary documents to determine actual legal entitlements or obligations.

The supplied endnotes do not specify any penalties, sanctions, enforcement mechanisms or prosecutorial pathways. That omission is explicit: the endnotes are descriptive and bibliographic rather than normative. They function to record amendment events and to provide an abbreviation key and a record of commencement dates (Endnotes 1-4). From the text provided, no enforcement regime, penalty schedule, infringement process or administrative enforcement procedure is contained in the endnotes themselves.

Consequences of the omission for legal practice

• No enforcement text here. Because there are no penalties recorded in the endnotes, a reader cannot rely on the compiled endnotes to determine how non‑compliance with the licence area plan would be dealt with. The enforcement provisions, if any, will be inside the operative licence area plan and the legislative framework that creates broadcasting offences or administrative sanctions. The endnotes point to the relevant instruments by registration number and date (Endnote 3 table), but they do not reproduce enforcement provisions.

• Need to consult primary instruments. Practitioners must therefore consult the primary licence area plan and any higher‑order legislation (for example, enabling broadcasting Acts or regulatory guidelines) to identify the relevant enforcement mechanisms. The endnotes provide the identifiers needed to retrieve the amending instruments from the Gazette and from the statute book, but they do not substitute for those texts.

• Transitional and saving provisions that affect enforcement. The legislation history table includes a dedicated column for "Application, saving and transitional provisions" (Endnote 3). This indicates that enforcement consequences could be shaped by transitional arrangements introduced at the time of amendment. Because such provisions may be omitted from the compilation, a practitioner must confirm whether transitional rules alter the enforcement regime for specific periods or classes of licence holders.

• Compiler annotations relating to misdescriptions. Endnote 4's treatment of misdescribed amendments may affect enforcement if an amending instrument is misdescribed and the compilation marks it "(md)" or "(md not incorp)". Where an amendment has been incorporated despite a misdescription, a court or regulator may need to examine the underlying amending instrument to determine whether the change was validly made. The endnotes therefore flag a legal risk area in which the enforceability of particular amendments could be challenged, but they do not themselves resolve that risk.

Because the endnotes do not create or repeat enforcement provisions, any regulatory or criminal consequences for conduct in the Cooma licence area must be located in the operative licence area plan, the amending instruments identified in Endnote 3, or in the statutory scheme that gives legal effect to licence conditions. The endnotes supply the map to those documents but not the enforcement content.

The endnotes record one explicit consequential instrument that situates the licence area plan in a broader regulatory framework. The "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)" appears in the legislation history and is listed as an amending/ consequential instrument with Gazette registration 29/09/2017 and commencement 30/09/2017 (Endnote 3). This entry indicates a mechanical point of interaction: the licence area plan has been subject to consequential amendments arising from changes to technical planning guidelines, and so the plan must be read in light of those consequential amendments.

Beyond that explicit example, the endnotes convey structural interaction principles that practitioners must observe.

• Cross‑instrument consequentiality. The presence of a "Consequential Amendments" instrument in the legislation history shows that changes in one part of the broadcasting regulatory architecture (the Technical Planning Guidelines) generate amendments in administrative instruments like licence area plans. Practically, this creates a chain of dependent texts: a change in guidelines can trigger multiple technical adjustments across local licence area plans.

• Temporal interaction via commencement and transitional provisions. The legislation history table supplies commencement dates for each amending instrument (Endnote 3). Interaction across laws therefore depends on temporal sequencing. Practitioners must reconcile the dates recorded in Endnote 3 when determining which version of an instrument applies at any given time. Where transitional or saving provisions exist, they will control how the change interacts with pre‑existing rights and obligations, but the endnotes warn that such provisions may not be fully reproduced in the compilation.

• Interaction by replacement and substitution. The provision‑level amendment history shows many entries marked "rs." (replaced and substituted) and "am." (amended) across attachments and schedules (Endnote 4). That indicates that entire attachments or schedules have been replaced rather than incrementally amended, which changes the text that interacts with any higher‑order law. Where an attachment is replaced, the replaced text ceases to operate and the substituted text interacts with other instruments thereafter.

• Need to consult Gazette entries. The legislation history provides Gazette registration identifiers alongside each amending instrument (Endnote 3). Those entries are the authoritative source for exact amendment text and for any cross‑references to other laws. The endnotes thus indicate that inter‑statutory interaction must be traced back to the Gazette notices and the amending instruments themselves.

• Potential for misdescription to affect inter‑instrument consistency. Endnote 4's note about misdescribed amendments means that sometimes an amending instrument might be recorded in a way that does not accurately describe the amendment. Where the compiler has nonetheless given effect to the amendment with an "(md)" flag, the practical effect is that the compiled instrument may incorporate an amendment whose description is contested. This complicates the task of tracing interactions between instruments because users must confirm whether a supposed amendment actually has legal effect and whether it properly aligns with other laws it purports to depend on.

Overall, the endnotes show that the Cooma licence area plan has been varied over time by instruments that interact with guidelines and that any thorough analysis of inter‑statutory effects requires following the Gazette identifiers and the dates in Endnote 3 and the provision‑level tags in Endnote 4 back to the primary texts.

The supplied Endnote 3 and Endnote 4 form the primary amendment history for the compiled instrument. The history recorded in the tables covers the period from the original 1999 plan through variations up to 2019 and includes both standalone variations to the Licence Area Plan and a consequential amendments instrument tied to the Broadcasting Services (Technical Planning) Guidelines.

Summary timeline from Endnote 3 table

• 11 August 1999: Licence Area Plan Cooma Area (Radio) - July 1999, Gazette registration 11/08/1999F2005B00593, commencement 11/08/1999 (Endnote 3, first row).

• 12 November 2003: Licence Area Plan - Cooma Area (Radio) - Variation - November 2003, Gazette 12/11/2003F2005B00669, commencement 12/11/2003 (Endnote 3 second row).

• 13 October 2004: Licence Area Plan - Cooma Area (Radio) - Variation - September 2004, Gazette 13/10/2004 F2005B00670, commencement 13/10/2004 (Endnote 3 third row).

• 17 August 2011: Variation to Licence Area Plan for Cooma Radio - No. 1 of 2011, Gazette 16/08/2011 F2011L01657, commencement 17/08/2011 (Endnote 3 fourth row).

• 30 September 2017: Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1), Gazette 29/09/2017 F2017L01299, commencement 30/09/2017 (Endnote 3 fifth row).

• 29 May 2019: Variation to Licence Area Plan - Cooma Radio - 2019 (No.1), Gazette 28/5/2019 F2019L00693, commencement 29/5/2019 (Endnote 3 sixth row).

Provision‑level detail from Endnote 4 table

The Endnote 4 table lists numerous provisions and shows how each was affected by amending instruments. The entries use abbreviations (Endnote 2) and record a pattern of substitution and amendment concentrated on attachments and schedules. Representative entries include:

• "Title pagePage 2" annotated "am. No.1 of 2011; am. No.1 of 2019.am. No.1 of 2011." This indicates the title page and page 2 were subject to amendment in 2011 and 2019.

• "Clause (1)" annotated "am. No.1 of 2011." Clauses (2) through (6) are recorded as "rs. No.1 of 2011" (replaced and substituted by the 2011 variation) and clause (6) is further recorded "rs. No.1 of 2011, rs. No.1 of 2019." This shows iterative replacement activity.

• Schedules 1 and 2 entries show multiple substitutions and amendments: "Schedule 1 rs. No.1 of 2003; rs. No. 1 of 2004; rs. No.1 of 2011; rs. No.1 of 2019." Schedule 2 mirrors this pattern. This indicates that entire schedules were successively replaced across successive variations.

• Attachments 1.1 through 1.31 and Attachments 2.1 through 2.5 have a mix of "rs." and "am." tags and later "ad." tags for some additions in 2019. For example, "Attachment 19.A ad. No.1 of 2019" and "Attachment 1.10A ad. No.1 of 2019" indicate that new attachments were added in 2019. Several other attachments are recorded as "rs. No.1 of 2011; am. No. 1 of 2017; am. No.1 of 2019." This shows that the 2011 variation was a major substitution event, with subsequent technical and minor amendments in 2017 and 2019.

• One specific entry records a replacement followed by a repeal: "Attachment 1.26.1 ad. No. 1 of 2011; am. No. 1 of 2017; am. No.1 of 2019, rep. No.1 of 2019." This indicates that Attachment 1.26.1 was added in 2011, amended twice, and then repealed in the 2019 instrument.

Treatment of misdescribed amendments

Endnote 4 includes a procedural rule for misdescribed amendments. It explains that the amendment history will note whether an amending instrument was misdescribed. If the misdescription can be given effect, the compiler will incorporate it and flag it "(md)"; if it cannot be given effect as intended, it will be flagged "(md not incorp)". That practice affects how users read the amendment history: the presence of an "(md)" flag means the compiler has resolved a drafting error in favour of effecting the amendment, while "(md not incorp)" warns that the amending instrument could not be reconciled and the compilation therefore does not incorporate it (Endnote 4 prefatory paragraph).

Practical reading of the history

The overall pattern in the amendment history is significant: the 2011 Variation No. 1 appears to have been a comprehensive replacement episode affecting clauses, schedules and many attachments. The 2017 Consequential Amendments instrument appears to have introduced technical amendments, while the 2019 Variation added new attachments and adjusted several items, including repealing at least one attachment. The endnotes give the Gazette identifiers needed to retrieve each amending instrument for the exact amendment text and any transitional rules.

Users should use the abbreviation key in Endnote 2 to read the "How affected" column entries correctly. Given the density of substitutions and amendments across attachments and schedules, careful comparison of versions by date is necessary to determine the operative text at any point in time.

The supplied endnotes do not reference any litigation, case law, or judicial determinations relating to the Licence Area Plan Cooma Area (Radio) or its amendments. There are no named cases, no citations to judicial decisions, and no indication that the compilation has been the subject of litigation or judicial correction. The only law‑history material in the supplied text is administrative: registration numbers, commencement dates and provision‑level amendment notes (Endnotes 3 and 4).

Implications for practitioners

• Absence of litigation references in the compilation. Because the endnotes make no mention of cases, any judicial interpretation, dispute or declaratory relief involving the licence area plan is not recorded here. Practitioners seeking case law should therefore search external legal databases and court records, rather than relying on the supplied compilation.

• Potential for unrecorded litigation. The endnotes are not a litigation repository. The absence of litigation entries in these endnotes does not prove that no litigation has occurred; it only confirms that the compilation as supplied contains no litigation history entries. Users must perform independent research to identify any judicial authority that addresses the plan or its amendments.

• Misdescribed amendments and potential legal challenge. Endnote 4’s procedure for misdescribed amendments may be of practical relevance if, in practice, an amending instrument was poorly drafted and a party challenged its validity. The compiler’s decision to mark an amendment "(md)" or "(md not incorp)" may itself become relevant evidence in litigation about what the law was intended to be and whether an amendment was validly enacted. Again, this is not litigation recorded in the endnotes; it is a procedural note about how the compiler treated drafting errors.

In summary, the supplied compilation contains no litigation history entries. Where litigation is material to the legal advice required, practitioners must consult court databases and the primary texts referenced by the Gazette registration numbers in Endnote 3.

The endnotes contain several features and small anomalies that can mislead or trap unwary users. These are concrete technical issues stemming from the nature of the compilation and from the text of the endnotes themselves.

1. The endnotes are not the operative law. This is the single most important "gotcha". Endnote 1 makes clear that the endnotes provide information about the compilation and the compiled law, not the operative statutory provisions themselves. Users cannot treat these endnotes as setting duties, rights, technical parameters or enforcement mechanisms. Always retrieve the primary instrument and the amending instruments listed in Endnote 3.

2. Transitional and saving provisions may be omitted. The legislation history table contains a column labelled "Application, saving and transitional provisions" but the table entries in the supplied text do not reproduce such provisions. Endnote 3 explicitly states that the information includes commencement details and details of any application, saving or transitional provisions that are not included in the compilation. Practically, this means rights or obligations may be governed by transitional rules that are not present in the compilation and can change outcomes materially.

3. Abbreviation key formatting issue. Endnote 2, which provides the abbreviation key, contains a formatting or text issue where "rep. = repealedrs. = repealed and substituted" appears on a single line, merging two distinct abbreviations without a line break or clear separator. This can cause misreading of the provision‑level annotations in Endnote 4 unless the reader recognises the intended abbreviations. Verify the intended meaning when an entry uses "rep." or "rs.".

4. Dense and iterative substitutions. The provision‑level history shows many parts of the instrument were "rs." (replaced and substituted) in 2011 and then further amended in 2017 and 2019. When entire schedules or attachments have been replaced, an earlier version ceases to apply. If your inquiry requires comparing historical provisions for a specific date, you must obtain the exact version in force at that date using the Gazette and registration identifiers recorded in Endnote 3.

5. Additions and repeals in the same year. The entry for "Attachment 1.26.1" shows it was added in 2011, amended in 2017 and 2019, and then repealed in 2019. Users might assume that an amendment in the same year as a repeal leaves an effective text, but the net effect is repeal; you must confirm the repeal date and any transitional schedule that preserved rights during the interim. The endnote flags the sequence but does not provide the operative repeal text or any savings.

6. Reliance on Gazette identifiers. The endnote table records Gazette registration or notification identifiers such as "F2011L01657" or "F2019L00693". These are necessary to retrieve the authoritative amending instruments. Failing to check the Gazette entry or relying on the compiled note alone can cause error, particularly where misdescribed amendments have been corrected or where commencement dates differ from publication dates.

7. Compound and repetitive annotations can be confusing. Several entries in the provision‑level table repeat the same amending instrument multiple times in a single cell (for example "am. No.1 of 2011; am. No.1 of 2019.am. No.1 of 2011.") which appears redundant or a typographical artifact. Treat these as indicating multiple amendment events rather than as an authoritative sequence without cross‑checking the original amending instruments.

8. The compilation’s scope may not be comprehensive. The endnotes imply the compilation covers the plan and attachments, but they do not guarantee completeness of ancillary administrative material such as ministerial directions, regulator determinations, or informal technical guidance. Use the Gazette identifiers and the amending instrument titles as the retrieval keys.

Practically, each of these gotchas points to the same mitigation: do not treat the endnotes as a substitute for the primary texts and the Gazette notices; use the endnotes as an index and then confirm the operative wording, commencement timing and transitional arrangements by consulting the amending instruments themselves.

Because the supplied endnotes are metadata rather than operative regulatory text, "compliance" has two distinct trackable steps. First, as a user of the compilation, follow the endnote‑driven retrieval process outlined below. Second, once you have the primary texts, follow the normal compliance steps appropriate to licence area plans and any higher‑order broadcasting statute or guidelines. The endnotes themselves require procedural compliance for accurate legal work.

Step 1: Use the endnotes to retrieve and confirm the operative text

• Start with the legislation history table. Use the Gazette registration numbers and dates in Endnote 3 to locate the original instrument and each amending instrument. The table lists the original plan (11/08/1999F2005B00593) and subsequent amending instruments with their Gazette identifiers and commencement dates (Endnote 3). Retrieve each Gazette entry to obtain the full text and any schedules, attachments and transitional provisions.

• Read the provision‑level amendment history. Use Endnote 4 to identify which clauses, schedules and attachments were added, replaced, amended or repealed by each instrument. Pay attention to entries marked "rs." (replaced and substituted), "ad." (added), "am." (amended) and "rep." (repealed). Use the abbreviation key in Endnote 2 to interpret these markers.

• Check for "(md)" flags. Where an amendment is misdescribed but incorporated, the compilation will flag it with "(md)"; if it could not be incorporated it will be flagged "(md not incorp)". If any such flags appear in the full compilation you retrieve, scrutinise the underlying Gazette instrument to confirm the intended legal effect.

• Confirm commencement and transitional details. Do not infer operative effect from the date of Gazette publication alone. Confirm commencement dates recorded in Endnote 3 and examine amending instruments for any application, saving or transitional provisions that modify effect for existing licence holders or pending applications.

Step 2: Determine the current operative text and compliance obligations

• Assemble the chain of versions. Where a provision was replaced, locate the substituted text and confirm its commencement date so you can identify which version governs current compliance. For provisions with multiple amendments, confirm the order in which they took effect.

• Locate enforcement and penalty provisions in the primary instruments. The endnotes do not contain penalties or enforcement mechanisms; identify those provisions in the operative licence area plan and any enabling statute or subordinate instrument.

• Review attachments and schedules thoroughly. The provision‑level history shows extensive amendment activity focused on attachments and schedules. Because these often contain technical parameters, frequency allocations, transmitter locations or contour maps (not reproduced in the endnotes), ensure you review the full text of each attachment that is recorded as current.

• For licence holders, audit operations against the current attachments. If an attachment contains technical planning parameters relevant to your transmitter, antenna or service area, compare your operational settings and spectrum use to the current attachment text. Confirm whether any transitional provisions permit legacy operations that differ from the new text.

Step 3: Document and record compliance actions

• Keep dated copies of the operative versions you relied on. Save the Gazette entries and the text of the primary instruments and attachments with the commencement dates clearly noted. This is especially important where amendments occurred close in time or where a later instrument repealed a recently amended attachment.

• Maintain an issues log for misdescribed amendments. If the compilation includes "(md)" annotations or you encounter ambiguous Gazette notices, keep a record of your analysis and correspondence with the regulator or legal advisers showing how you resolved any ambiguity.

• Reconcile regulatory guidance. Because the 2017 Consequential Amendments instrument indicates an interaction with the Technical Planning Guidelines, check the relevant guidelines and any regulator publications or technical guidance that interpret how the licence area plan interacts with those guidelines.

Step 4: When in doubt, seek authoritative confirmation

• Contact the registry or regulator for confirmation of the current operative text if the compilation or Gazette entry is unclear. The endnotes supply registration identifiers that are the proper references for any such inquiry.

• If compliance involves significant capital expenditure, consult counsel or a technical adviser who can map the attachment parameters to your physical infrastructure and confirm compliance timelines given any transitional provisions.

Checklist summary drawn from the endnotes

• Use Endnote 3 to obtain Gazette registration numbers and commencement dates for the original plan and each amendment.

• Use Endnote 4 and the abbreviation key in Endnote 2 to identify which provisions were added, amended, replaced or repealed.

• Retrieve the full text of each amending instrument from the Gazette and confirm the presence and text of any application, saving or transitional provisions.

• Identify and extract enforcement and penalty provisions from the primary instrument and any higher‑order statutes or guidelines.

• Archive copies of the specific versions you rely on, with dates, for evidentiary and audit purposes.

Following these steps aligns practice with the procedural structure the endnotes supply. The endnotes are an index and audit trail; effective compliance requires retrieving and applying the operative texts they point to.