Licence Area Plan - Bourke (Radio) - December 1996

The endnotes and amendment-history table introduce three principal conceptual layers relevant to statutory compendia and to this licence area plan in particular: (1) the compiled instrument plus a history of amendments; (2) an editing and abbreviation protocol for how amendments are recorded and described in the compilation; and (3) a split between the text included in the compilation and external material or transitional provisions that the compilation does not reproduce.

1. Compiled instrument and amendment trail. The compilation is not a primary act but a collated instrument set: an original licence area plan (8 January 1997) and later amending instruments (notably 3 November 2004, 24-25 March 2011, and 29-30 September 2017). Endnote 3 provides a Table of Instruments with precise notification and commencement dates. Endnote 4 provides a provision-level table identifying which clauses, schedules and attachments were amended (am), added (ad), or replaced/substituted (rs), and by which instrument (for example, "am. No.1 of 2011" beside Clause (1)). The compilation therefore treats the licence area plan as a living document subject to discrete adjustments via variation instruments and consequential amendments from technical-guideline instruments.

2. Editorial protocol and abbreviation key. Endnote 2 supplies the abbreviation key used in the amendment table: "ad" = added or inserted; "am" = amended; "rep." = repealed; "rs." = repealed and substituted. The HTML amendment table itself uses these abbreviations to mark the fate of particular clauses and attachments. Endnote 4 further explains that where an amending provision is misdescribed in the amending instrument, the compiler will mark the amendment with "md" if it can be given effect as intended, or "md not incorp" if not. This establishes the compilation’s convention for signalling editorial uncertainty or correction, which is a conceptual device to indicate where reliance should be cross-checked against original amending instruments.

3. Division between compiled text and external materials. The endnotes explicitly state that information about commencement, application, and transitional or saving provisions that are not reproduced in the compilation is provided in the endnotes (Endnote 3). That phrase establishes a conceptual separation: the compilation includes the consolidated text but omits some transitional wording; the endnotes are the pointer to where those omissions are recorded. The Table of Instruments therefore functions as metadata that users must treat as part of the legal instrument set when determining legal effect for particular date ranges.

Operationally relevant concepts that follow from the endnotes and tables are: (a) attachments function as technical or geographical data carriers for the plan (the table lists many Attachments 1.1 through 1.17 and Attachments 2.1 to 3.3 and 4.1-4.2); (b) amendments are temporal and instrument-specific, so any compliance review must be date-sensitive (each instrument has a notification and a commencement date); and (c) consequential amendments may be produced by a different instrument (for example, the 2017 Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)) which indicates cross-linkage to the Broadcasting Services technical planning framework.

In the absence of the operative substantive text of the licence area plan within the provided material, these conceptual layers are the compilation’s primary content: they orient a reader to where substantive rules will be found (the original plan and the attachments), show how to read the amendment record, and signal how to treat potentially misdescribed changes. A practitioner should therefore use the endnotes as an index and guide to the documentary chain rather than as the sole source of rights or obligations.

The endnotes themselves are a navigation and record-keeping instrument; the entities directly affected by this endnote compilation are parties who need to know the authoritative status and amendment history of the Bourke licence area plan. At a minimum, affected parties include:

• Licence-holders in the Bourke radio licence area, both community and open narrowcasting operators, who must know which technical parameters, coverage requirements and licence conditions apply on given dates. The endnotes show that the plan and many attachments were amended in 2004, 2011 and again in 2017; operators need to trace those amendments to confirm which version applied during a specific timeframe.

• Prospective applicants and technical planners who must design transmission parameters that comply with the licence area plan and the Broadcasting Services (Technical Planning) Guidelines. The endnotes identify the Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) as an amending instrument, indicating that technical planning rules outside the plan itself may have been altered and that those changes were consequential to the plan’s text.

• Counsel, compliance teams and spectrum consultants engaged to advise on licensing, renewal or variation matters. These advisors must use the endnotes as an index to the amending instruments and to the attachments that were added or amended. The amendment table lists Attachments 1.2-1.17 as being added by No. 1 of 2011, with several of those attachments subsequently amended in 2017; a compliance adviser must check the specific attachments that apply to a given licence.

• Administrators and decision-makers responsible for issuing licences or for enforcement. The compilation’s metadata, including commencement dates and Gazette citations (e.g., F2005B00659, F20101L00476, F2017L01299), are the citations officials will need to interpret which instrument is in force at a given time.

• Researchers, journalists and public-interest groups tracing regulatory change. The endnotes provide the documentary trail that will be necessary to assess how the plan changed over time and whether, for example, a change altered coverage areas or technical limits.

The endnotes do not expressly list private individuals or third parties affected by broadcast signals (such as consumers or other spectrum users). However, because the appended attachments and schedules,many of which are marked as amended or added,are typically where technical parameters, geographic coordinates and licence area boundaries are set, the practical effect is that third parties with an interest in spectrum planning, interference management or local broadcasting availability will be affected indirectly via the substantive plan documents the endnotes index.

The compilation also affects users who rely on consolidated texts for legal certainty. Endnote 3 states that application, saving or transitional provisions that are not reproduced in the compilation are nevertheless recorded in the endnotes. That means a user who relies only on the consolidated text without checking the endnotes risks missing transitional provisions that could affect rights or obligations during a period of change. The parties who therefore bear risk from incomplete checking are licence-holders, new applicants, and advisers who must ensure they have reconciled commencement dates against operational actions (for example, construction dates or licence renewals).

Finally, the amendment table shows that many attachments were "ad" (added) or "am" (amended) by No.1 of 2011 and by the Variation of October 2004, and that several were "am" again by No.1 of 2017. That pattern means parties operating in the Bourke area must be alert to layered changes: multiple instruments across years can change specific attachments while leaving others intact. For an operator, the practical consequence is that compliance is not static; it is date-dependent and attachment-specific.

The endnotes and amendment-history table themselves do not reproduce operative duties, rights, licence conditions or technical parameters. They operate as a meta-documentation layer that points to where duties and rights are established. Consequently, the endnotes identify where to find the substantive material but do not create new duties or rights. That said, they encode several practical obligations for any party seeking to know or rely on the current legal position:

1. Duty to consult the amending instruments and attachments. The endnotes list the relevant instruments and the specific clauses, schedules and attachments they changed (Endnote 3 and Endnote 4). To determine actual duties (for example, transmitter power limits, antenna coordinates, restricted content rules for narrowcasting), a party must obtain the original Bourke licence area plan and each amending instrument referenced, including the attachments. The compilation explicitly warns that application, saving or transitional provisions that are not included in the compiled text are nonetheless listed in the endnotes (Endnote 3). Therefore one duty is procedural: check the endnote entries, retrieve the Gazette instruments cited and read transitional provisions.

2. Duty to pay attention to commencement dates. The Table of Instruments provides both date of notification in the Gazette and date of commencement (Endnote 3). Some instruments commence on the same day as notification (for example, the Variation on 3 November 2004 appears to have commenced that day), while No. 1 of 2011 was notified 24 March 2011 and expressly commenced 25 March 2011. Licences and technical work are time-sensitive, so parties must align project timelines with these dates to avoid non-compliance.

3. Duty to reconcile provision-level changes and attachments. Endnote 4’s table lists which clauses and attachments were amended or added and by which instrument; for example, Clause (1) through Clause (4) are shown as "am. No.1 of 2011." Schedules One through Four and numerous attachments were either amended or added at different times. Affected parties must map which attachment(s) apply to their licence or planned facility and confirm which version (pre- or post-amendment) applies to any particular timeframe.

4. Rights are implicit and must be located in the underlying texts. Any substantive rights (for example, the right to a specific frequency, an entitlement to community narrowcasting classification, or rights to apply for variation) will be created and governed by the primary licence area plan and the licence conditions. The endnotes do not create or remove such rights; they only record the instruments that did.

5. Duty to resolve editorial uncertainty flagged by the compilation. Endnote 4 explains the compiler’s approach to misdescribed amendments and the "md" and "md not incorp" notations. Where the compiler has flagged an amendment as misdescribed,or where no such flag appears but the user suspects inconsistency,the duty is to consult the amending instrument as published in the Gazette to determine the intended legal effect.

6. Administrative obligations vis-à-vis consequential instruments. The presence of a Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) in the Table of Instruments indicates that some changes to the plan are consequential on the technical-planning framework. Hence rights and duties deriving from the plan may be affected by external instruments; parties must therefore treat downstream guideline amendments as part of their compliance universe.

Because the endnotes do not include fine-grained substantive text, the compilation shifts the duty of verification to the user: the endnotes indicate paths to the substantive law but do not relieve the user of the obligation to obtain and read the underlying instruments, their attachments, and any transitional provisions for periods straddling amendment dates.

The endnotes provided do not specify penalties, offence provisions or enforcement mechanisms. They are editorial and metadata material for the compilation and, as such, contain no enforcement clauses. The consequences for non-compliance with the Bourke licence area plan,be that licence cancellation, monetary penalties, or variation refusal,would be specified in the operative statutory framework and in licence conditions, neither of which are reproduced in the material provided here.

What the endnotes do provide that is relevant to enforcement risk is the audit trail necessary to determine which instrument was in force at any particular time. Enforcement inquiries and any penalty determinations require precise knowledge of the applicable rules on the relevant dates. The endnotes therefore function indirectly in enforcement by:

• Recording the notification and commencement dates for the original plan and its variations (Endnote 3). An enforcement action will depend on the plan as it stood at the time of the alleged non-compliance, so accurate dating from the endnotes is essential.

• Showing which clauses and attachments were amended or added by which instruments (Endnote 4). Because attachment-level technical parameters are likely to determine whether a device or operation complied, enforcement authorities and regulated parties must consult the specific attachments listed in the amendments table.

• Signalling editorial anomalies via the misdescription conventions explained in Endnote 4. Where compilers have added "md" or "md not incorp" the legal effect of an amendment may be uncertain until the original amending instrument is examined; enforcement action premised on a compilation should avoid relying on a misapplied editorial correction without checking the original Gazette.

For advisers and compliance officers, the absence of explicit penalty clauses in the endnotes requires two practical steps before assessing enforcement exposure: first, retrieve the underlying primary instrument(s) referenced by the endnotes (the plan and its variations) and search within them for offences, sanctions, or licence-condition consequences; second, check the broader statutory framework under which radio licensing and narrowcasting operate,likely the Broadcasting Services Act and related regulations,because the endnotes identify a Broadcasting Services-related instrument in 2017 (which may affect enforcement regimes by altering technical guidelines or rules that feed into licence conditions).

Finally, because the compilation explicitly notes that it does not reproduce application, saving or transitional provisions in full (Endnote 3), an enforcement timeline may be affected by transitional rules that alter whether a contravention is actionable, or by transitional relief for operators who are changing facilities because of an amendment. The user must therefore obtain and read the saving and transitional clauses of the amending instruments, as recorded by the endnotes, to understand enforcement exposure during amendment periods.

The endnotes and instrument table show direct linkages to other legal instruments and reflect standard cross-instrument interaction in regulatory compendia. The immediate interaction signalled by the compilation is between the Bourke licence area plan and the Broadcasting Services (Technical Planning) Guidelines. Specifically, the Table of Instruments lists "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)" (notified 29 September 2017, commenced 30 September 2017). The label "Consequential Amendments" indicates that the 2017 instrument amended other instruments to align them with changes made to the technical-planning guidelines. That is a common legislative technique: when a central guideline or framework is altered, consequential amendments modify dependent instruments so their provisions remain coherent.

Because the endnotes are limited to the compilation, other statutory or regulatory frameworks that could interact with the licence area plan,such as the Broadcasting Services Act, spectrum-management instruments, or radiocommunications licences,are not set out in the material provided. Nevertheless, the presence of a Broadcasting Services consequential-instrument in the Table of Instruments implies at least one cross-instrument pathway: technical-planning rules in the guidelines inform, and are reflected in, the licence-area plan's attachments and technical schedules. Practitioners should therefore expect that:

• Technical parameters in the licence area plan (likely contained in the attachments listed in Endnote 4) will be constrained by the Broadcasting Services (Technical Planning) Guidelines. Changes to those guidelines may necessitate changes to frequency coordination, interference protection criteria, or transmitter parameters in the plan.

• Administrative processes and decision criteria for licence variations or approvals may reflect both the licence area plan and broader Broadcasting Services policy instruments. The 2011 variation and the 2017 consequential instrument together suggest iterative policy updates in the technical planning regime that have been mapped into the Bourke plan.

The endnotes also flag the possibility of application, saving or transitional provisions that are not reproduced in the compilation (Endnote 3). Such provisions can create temporal interactions with other laws,for example, they may grandfather certain installations under an earlier standard, or they may require compliance with a different instrument for a defined period. That means a full legal analysis of interactions must include:

• The primary legislative authority for radio licensing, which typically sets overarching powers and enforcement regimes (the endnotes do not reproduce that primary act, but the Broadcasting Services connection suggests that the Broadcasting Services Act is relevant in practice).

• Any regulations, guidelines or instruments that are referenced for technical planning, because the 2017 consequential instrument demonstrates that guideline changes can ripple through dependent instruments.

• Transitional or saving clauses in the amending instruments, because they determine whether an entity remains governed by an old rule or must transition immediately to the new one.

Finally, the amendment table shows that many attachments were added in 2011 and some amended again in 2017; that sequencing implies layered interactions across instruments. Where an attachment contains coordinates, coverage maps or technical parameter tables, those details interact operationally with spectrum management and interference-mitigation frameworks administered elsewhere in the broadcasting and radiocommunications regime. The compilation endnotes do not spell out those operational interactions, but they perform the essential task of identifying which external instruments need to be consulted to understand how the licence area plan fits into that regulatory web.

The compilation’s Endnote 3 and Endnote 4 together form the amendment history for the Bourke licence area plan. Endnote 3 contains a "Table of Instruments" that lists the principal instruments and their dates of notification and commencement. Endnote 4 gives provision-level details that identify the effect of those instruments on specific clauses, schedules and attachments.

From Endnote 3 (Legislation history,Table of Instruments), the sequence recorded is:

• Community and Open Narrowcasting Radio Licence Area Plan Bourke (Radio), notified in the Gazette 8 January 1997 (Gazzette citation F2011C00225) and commenced 8 January 1997. This entry appears to be the original plan.

• Variation to Licence Area Plan Bourke (Radio), notified 3 November 2004 (F2005B00659), with commencement the same day, 3 November 2004. The entry labels this as a "Variation to Licence Area Plan" without providing the textual content of the variation in the compilation.

• Variation to the Licence Area Plan for Bourke Radio - No. 1 of 2011, notified 24 March 2011 (F20101L00476), with commencement 25 March 2011. The table records the variation number, indicating that a formal variation instrument (No. 1 of 2011) altered provisions of the plan and likely added attachments.

• Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1), notified 29 September 2017 (F2017L01299), with commencement 30 September 2017. This instrument is described as "consequential amendments" to technical planning guidelines and therefore altered the plan in consequence of changes elsewhere.

Endnote 4 provides the provision-level amendment table (rendered in the supplied HTML). The table lists the following examples (the list in the compilation is extensive; the endnotes excerpted here reproduce multiple lines):

• Clause (1) through Clause (4) are marked "am. No.1 of 2011." Clause (5) and Clause (6) are marked "ad. No.1 of 2011." That indicates that Clauses (1)-(4) were amended by No. 1 of 2011, while Clauses (5)-(6) were added by the same instrument.

• Schedule One and Schedule Two are marked "am. Variation of October 2004, rs. No.1 of 2011." That notation suggests Schedule One and Two were previously amended by the October 2004 variation and then repealed and substituted by No. 1 of 2011.

• Schedule Three is marked "rs. No.1 of 2011," and Schedule Four is marked "ad. No.1 of 2011." That is consistent with the 2011 instrument replacing or adding whole schedules.

• Attachment 1.1 is marked "am. Variation of October 2004, rs. No.1 of 2011." Attachments 1.2 through 1.17 are mostly marked "ad. No.1 of 2011" with many also noting "am. No. 1 of 2017." That establishes that No. 1 of 2011 added many attachments, and the 2017 instrument subsequently amended several of them.

• Attachments in Attachment 2.x and 3.x series show mixed "am" and "ad" entries and in several cases "am. No. 1 of 2017," indicating further amendment in 2017. Attachments 4.1 and 4.2 are marked "ad. No.1 of 2011" and "ad. No.1 of 2011; am. No. 1 of 2017" respectively.

The amendment table therefore documents a multi-stage amendment process: the 2004 variation made changes, the 2011 instrument made a comprehensive series of amendments including adding attachments and substituting schedules, and the 2017 consequential instrument amended certain attachments to align with updated technical guidelines.

Endnote 4 also contains editorial commentary: it explains the compilation’s practice of noting misdescribed amendments and how such instances are marked with "(md)" or "(md not incorp)" if a misdescription exists and is or is not capable of being given effect as intended. The table itself uses the standard abbreviations noted in Endnote 2: "ad" = added, "am" = amended, "rs." = repealed and substituted. The HTML table provided shows these abbreviations alongside each provision entry.

For practitioners, the amendment history recorded here establishes three important facts: (1) the plan has been revised repeatedly and at both the clause and attachment level; (2) the 2011 instrument was major in scope, adding many attachments and substituting whole schedules; and (3) the 2017 instrument implemented consequential technical-guideline changes that updated specific attachments. Any analysis of current rights or obligations must therefore reconcile the original 1997 plan, the October 2004 variation, No. 1 of 2011, and the 2017 consequential amendments, taking care to apply the correct version of attachments and schedules as they existed at the relevant date.

The compilation’s endnotes, as provided, do not contain or reference any litigation history. There are no court cases, tribunal decisions, or administrative appeals mentioned in the endnotes or in the amendment tables. Where endnotes or amendment histories include litigation notes, they typically cite cases that interpret the instrument or confirm the legal effect of particular amendments; no such citations appear in the material supplied.

The absence of litigation references in the endnotes means that, as far as the compiler recorded, either there has been no reported litigation directly concerning the Bourke licence area plan that the compiler included, or such litigation was not considered part of the compiled material being annotated. Endnote 1 explicitly frames the endnotes as providing information about the compilation and the compiled law; it does not promise to catalogue judicial decisions.

For practitioners this absence has two practical implications:

• Evidence of legal disputes will not be found in the endnotes: if litigation or administrative reviews exist that bear on the interpretation or enforceability of the licence area plan or of any of its amendments, those will need to be located by searching court databases, administrative tribunal records, or specialised reporting services. The endnotes do not perform that function.

• When advising clients about legal risk or precedent, one must therefore not rely on this compilation alone to determine whether previous litigation has established interpretations of ambiguous clauses or attachments. The absence of litigation notes in the endnotes is a gap to be filled by direct legal research.

Because the compiled materials include detailed attachment-level changes and misdescription conventions (Endnote 4), a litigation search may be particularly relevant if a client faces enforcement action or a contested technical interpretation. For example, where the compiler has used an "md" notation in other compilations it signals that amending instruments were misdescribed and that courts or tribunals might have been the forum in which disputes concerning that misdescription were resolved. No such annotations are shown explicitly in the excerpt provided, but the mechanism is recorded in Endnote 4. Therefore a prudent practitioner should check case law where a misdescription could alter the operative effect of an amendment.

In short, this compilation provides no litigation history. To establish whether any judicial or administrative authority has construed or invalidated any part of the Bourke licence area plan or its variations, a separate legal database search is required.

The endnotes themselves flag several editorial and practical pitfalls that can cause missteps if users treat the compilation as a self-contained source of law. Important "gotchas" that the endnotes reveal or imply are:

1. The compilation omits application, saving or transitional provisions in full. Endnote 3 explicitly states that the endnotes provide information about each amending law’s commencement and "details of any application, saving or transitional provisions that are not included in this compilation." The gotcha is that transitional arrangements can materially affect whether an amendment applies immediately, is phased in, or is trumped by a saving provision. Relying solely on the consolidated text without checking the endnotes and the original amending instruments risks applying the wrong rule to a fact pattern that straddles a commencement date.

2. Misdescribed amendments may be an issue. Endnote 4 explains the compiler’s approach to misdescribed amendments and the use of the "md" and "md not incorp" flags. The gotcha is that a practical legal effect may diverge from the plain words of an amending instrument if the instrument’s internal cross-references or clause numbering are wrong. The compiler may have corrected the description (placing "md") or may have noted that the misdescription could not be incorporated. Users must check the original amending instrument in the Gazette to resolve such discrepancies rather than rely solely on the compendium.

3. Attachments and schedules are heavily amended and can be numerous. The amendment table lists a long set of attachments (for example Attachments 1.1-1.17, Attachments 2.1-2.6, Attachments 3.1-3.3, Attachment 4.1-4.2). The gotcha here is that technical details tend to reside in attachments; an operator may be compliant with a core clause but non-compliant with an attached technical table. Because many attachments were added in 2011 and some amended in 2017, determining which attachment version applies is essential and non-trivial.

4. Gazette and commencement citations matter. The Table of Instruments shows both notification and commencement dates as separate fields. For example, the 2011 variation was notified 24 March 2011 and commenced 25 March 2011. A gotcha is failing to check the commencement date; action taken on 24 March 2011 might be governed by the pre-variation rules even though the variation had been notified. Always reconcile the exact commencement date.

5. “Consequential” amendments indicate cross-references to other instruments. The 2017 instrument is described as "Consequential Amendments" tied to Broadcasting Services (Technical Planning) Guidelines. The gotcha is that an amendment may not change the plan text directly but may alter the operation of the plan via modifications to an external guideline. Failure to track those guideline changes could lead to an incorrect conclusion about compliance.

6. The amendment table has formatting and content-density issues. The provided amendment table is rendered as HTML and shows repetitive entries; there is a risk of misreading which instrument effected which change if the user does not carefully parse the table. The gotcha is a human error in mapping the "am", "ad" and "rs." notations to the correct instrument entry. Cross-checking the Gazette entries with the attachments is necessary.

7. Absence of substantive provisions in the endnotes. The endnotes give the amendment trail but not the operative content. The gotcha is assuming duties, rights or penalties from the endnotes. A user must obtain the full text of the plan and attachments before concluding on substantive legal positions.

8. Reference codes (Gazette citations) are essential. The Table of Instruments lists Gazette references such as F2011C00225, F2005B00659, F20101L00476 and F2017L01299. The gotcha is failing to use these identifiers when retrieving original instruments. Searching by instrument title alone may return multiple similarly named instruments; the Gazette citation ensures the correct document is retrieved.

9. Potential for overlapping amendments. The amendment history shows that some items were amended in 2004, amended again or replaced in 2011, and again amended in 2017. The gotcha is assuming that an earlier amendment survives later amendments; provision-level substitution (rs.) means earlier text can be entirely replaced. Map the timeline to avoid misapplication.

10. No litigation or interpretive guidance in the endnotes. The endnotes do not record judicial interpretation. The gotcha is assuming that the compiled language has a single settled meaning; ambiguous clauses or coordinates can be contested, and the endnotes do not flag such disputes.

These practical pitfalls underline that the endnotes are a tool for verification rather than a substitute for primary-source reading. The safe practice is to treat the endnotes as the index and then retrieve the original Gazetteed instruments, the full attachments and any transitional clauses, and to cross-reference with any relevant guideline instruments in the Broadcasting Services framework.

Given that the endnotes and amendment table function as an index rather than as the operative regulatory text, compliance requires a procedural, document-centric approach. The steps below are practical, source-grounded actions for licence-holders, advisers, technical planners and administrators operating under the Bourke licence area plan as indicated by the compilation.

1. Retrieve primary instruments using Gazette citations. Endnote 3 lists exact Gazette citations and commencement dates for the original plan (8 January 1997, F2011C00225), the 2004 variation (3 November 2004, F2005B00659), Variation No. 1 of 2011 (notified 24 March 2011, commenced 25 March 2011, F20101L00476) and the Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (notified 29 September 2017, commenced 30 September 2017, F2017L01299). Use those citations to obtain certified copies of the instruments in force and any attachments or schedules they reference.

2. Map the amendment timeline to your operational dates. Use the commencement dates in Endnote 3 to determine which version of the plan, schedules and attachments applied during any relevant period (construction, testing, operation, licence application, or enforcement incident). Because some instruments have notification and commencement dates that differ, align project activities with the applicable commencement date.

3. Identify relevant attachments and schedules. Endnote 4’s table lists numerous attachments (for example, Attachments 1.1 through 1.17, Attachments 2.1-2.6, Attachments 3.1-3.3, Attachments 4.1-4.2) and specifies which were added or amended by the 2011 and 2017 instruments. For compliance, identify which attachment(s) applies to your licence or facility and ensure you have the correct version (pre- or post-amendment).

4. Check for application, saving and transitional provisions. Endnote 3 warns that such provisions may not be reproduced in the compilation but are recorded in the endnotes. Retrieve and read any transitional or saving clauses in the amending instruments to see whether they affect obligations during a migration period (for example, phased changes to power limits or grandfathered operations).

5. Resolve any editorial anomalies. If the compilation or the amendment table signals an "md" or "md not incorp" situation (Endnote 4), consult the original amending instrument in the Gazette. If the amending instrument’s cross-references are mistaken, a legal construction may be required to determine how the amendment was intended to operate. If ambiguity remains, consider seeking an administrative ruling before committing to costly technical changes.

6. Align technical planning with Broadcasting Services guidelines. The 2017 instrument in the Table of Instruments is a Broadcasting Services consequential-instrument. This indicates that technical-planning guidelines feed into the plan. Ensure that your engineering and spectrum coordination work reflects any updated technical criteria, interference matrices or coordination protocols published in the Broadcasting Services (Technical Planning) Guidelines and in the consequential amendments.

7. Document compliance and version control. Maintain a compliance register that records which instrument and which attachment version governs each transmitter or licence. That register should include the Gazette citation, notification date, commencement date, and a scanned copy of the relevant attachment so that auditors or enforcement agencies can be shown the law you relied on.

8. Coordinate with licensing authority processes. Before undertaking any variation, construction or transmitter relocation, confirm with the licensing authority which documentation they require, which version of the plan they apply, and whether any new licence applications need to reference the updated attachments. Provide the authority with the Gazette citation for the version you rely on.

9. When in doubt, seek legal or technical advice. Because the endnotes do not include penalties, rights or substantive clauses, interpretive issues (for example, conflicting attachment coordinates, ambiguous clause text after an amendment, or the effect of consequential guideline changes) should be referred to counsel or an accredited technical planner. This is especially important where an investment decision or enforcement risk is involved.

10. Retain the amendment trail as evidentiary material. If you face scrutiny or a dispute, the amendment history recorded in the endnotes will be useful evidence. Keep the original Gazette notices and a dated record of which version of the attachment was in effect when you built or operated a facility.

These compliance steps are procedural because the compilation does not contain operative rules. The core compliance principle is to treat the endnotes as an authoritative index and to use the Gazette citations they provide to obtain the primary instruments and attachments, confirm commencement and transitional details, and align technical and licensing actions with the specific versions of the plan that apply to your facts.