Licence Area Plan - Innisfail (Radio) - November 1997

The endnotes work with a narrow set of documentary and editorial concepts. These concepts are explicitly named and defined, and they frame how users should read the compilation. The core concepts are compilation metadata, an abbreviation key, a legislative history for amending laws, and an amendment history at provision level (Endnotes 1-4).

Compilation metadata: Endnote 1 states the endnotes "provide information about this compilation and the compiled law." That is the principal organising concept. The endnotes are not the primary statutory text. They are descriptive material that documents the compilation process, sources, and the way the compiled law has changed over time.

Abbreviation key: Endnote 2 sets out an "Abbreviation key" that gives short codes used elsewhere in the endnotes. The key lists "ad = added or inserted", "am = amended", and "rep. = repealed" (with a typographical juxtaposition showing "rep. = repealedrs. = repealed and substituted" in the printed table; the intent is to define standard editorial shorthand). The presence of this key means the reader must translate these codes when reading amendment-history lines.

Legislation history: Endnote 3 provides a table labelled "Legislation history". The table captures, for each instrument that has amended the compiled law, these specific fields: the name of the instrument; the "Registration or Notification in Gazette" field (a Gazette reference); "Commencement" date; and a column for "Application, saving and transitional provisions". The entries in the supplied table are concrete: the original plan and four amending instruments are recorded with Gazette references and commencement dates (Endnote 3 table). The concept here is that each amending law is recorded with its formal notification and its commencement date as relevant to the compilation.

Amendment history and misdescription mechanism: Endnote 4 covers how the compilation records amendments at the provision level. It shows which clauses, attachments and schedules were amended and lists the instruments that effected those changes (for example, "am. No.1 of 1998", "am. No.1 of 2003", "rs. No 1 of 2008", "am. No 1 of 2017"). Importantly, Endnote 4 also implements a quality-control concept for "misdescribed amendments". It explains two outcomes for a misdescribed amendment: if the misdescription can still be given effect, the compiler incorporates it and annotates the entry with "(md)"; if the misdescription cannot be given effect, the entry is annotated "(md not incorp)". This is an internal classification concept that affects the reliability signal of the compilation.

The endnotes therefore embody the business rules of legal compilation: how to represent amendments, how to annotate anomalies, and how to present the provenance of each change. There are no substantive definitions of duties, offences or administrative powers in these endnotes. All concepts are administrative and documentary, designed to support a user’s understanding of the provenance and editorial status of the compiled text.

The content and structure of these endnotes affect multiple audiences involved in legal use, compilation, compliance and administration. The primary impacted groups are legal researchers and practitioners, regulatory officials and statutory compilers, compliance officers and auditors, and any party relying on the compiled instrument for legal or administrative decision making.

Legal researchers and practitioners: Lawyers and in-house counsel who consult the compiled Licence Area Plan will rely on the endnotes to trace amendment history and commencement details. Endnote 3 explicitly records commencement dates and Gazette registrations for amending laws. That means researchers depend on these endnotes to identify when particular provisions took effect and which instruments to consult for transitional rules. Endnote 4’s mechanism for labelling misdescribed amendments (md or md not incorp) is also targeted at practitioners who must decide whether a compiled provision is accurately reflected.

Regulatory officials and statutory compilers: Government drafters and regulatory staff who maintain or enforce the Licence Area Plan will use the endnotes as a quick reference to the sequence of amending instruments and their Gazette notifications. The presence of Gazette registration numbers (for example, F2008L00957 for the 2008 variation) is a bookkeeping and verification aid for officials tasked with record-keeping and retrospective compliance.

Compliance officers and auditors: Corporate compliance functions and auditors who must ensure operational conduct aligns with regulatory instruments will consult the endnotes to confirm which version of the Plan applied at specific times. Endnote 3’s "Application, saving and transitional provisions" column is intended precisely to point to transitional arrangements that could affect compliance obligations across timelines.

Parties who rely on the Plan for rights or entitlements: Broadcasters, licence holders, and technical planners that operate in the Innisfail radio licence area (the substantive subject of the compilation) will be affected indirectly. The endnotes do not create legal rights or obligations, but they influence how these parties find and interpret the operative provisions and any transitional arrangements affecting their licences.

Users who need authoritative copies: Because the endnotes are an editorial record rather than original instruments, users whose matters depend on precise legal outcomes (litigators, tribunal advocates) are affected in that they must treat the endnotes as an aide rather than as primary authority. Endnote 3 records Gazette citations and commencement dates; users must still consult the primary amending instruments and any saving or transitional provisions referenced to establish enforceable rights and obligations.

Finally, the endnotes affect anyone attempting to automate or machine-process the law. The abbreviation key in Endnote 2 sets out codes that an automated parser would need to interpret accurately. The "md" flags in Endnote 4 signal potential exceptions that any compliance system must handle differently.

The endnotes themselves do not create enforceable duties or statutory rights. Their function is descriptive and documentary. The text explicitly frames the endnotes as information about the compilation and the compiled law (Endnote 1). Consequently, there are no operative obligations, prohibitions, or rights directly established by these endnotes; rather, their value is procedural and evidentiary.

What the endnotes do create, practically, is obligations on users of the compilation: a duty to consult the primary instruments they reference when correctness matters. Endnote 3 is designed to lead users to the amending instruments by name, Gazette registration reference and commencement date. The user practice implied by the endnotes is that users should verify commencement, application, saving and transitional provisions with the original amending instruments. This follows from Endnote 3’s explicit inclusion of a column for "Application, saving and transitional provisions" and the fact that the endnotes are described as providing information about the compilation rather than as the compilation itself (Endnote 1).

Another implied duty concerns attention to annotation flags. Endnote 4 sets out a protocol for misdescribed amendments. If an amendment is misdescribed but can be given effect, it is incorporated and annotated "(md)"; if not, it is annotated "(md not incorp)". The practical duty for a user is to treat "(md)" annotations as indicating a compiler’s judgment that the amendment can be given effect despite a descriptive error, and to treat "(md not incorp)" as indicating an unresolved problem requiring reference to original instruments or legislative history. This shifts a compliance burden onto the user to examine the underlying materials where "(md not incorp)" appears.

The abbreviation key in Endnote 2 creates an interpretive duty: when reading the amendment history, the user must translate shorthand codes ("ad", "am", "rep.") into their full meanings to understand whether material has been added, amended or repealed. Failure to do so risks misreading the compilation.

There are no express rights recorded in the endnotes for third parties such as licence holders. Any rights or duties affecting broadcasters or licensees arise from the substantive Licence Area Plan and its amending instruments, not from these endnotes. The endnotes function as an index and explanatory tool to help determine those substantive rights and duties by directing users to the relevant instruments and annotation flags.

The endnotes contain no penalties, offences, civil sanctions or enforcement mechanisms. The document itself is a compilation aid and carries no enforcement regime. The source confirms this role repeatedly by describing the endnotes as providing information about the compilation and the compiled law (Endnote 1) and by listing legislative and amendment histories (Endnotes 3 and 4) rather than setting out operative or punitive provisions.

Because there are no penalties in the endnotes, enforcement capacity and sanctioning reside exclusively in the primary legislation and amending instruments that the endnotes document. Endnote 3’s purpose is to record each amending law, its Gazette notification, and its date of commencement; Endnote 4 records provision-level amendment history including flags for misdescribed amendments. Neither provision creates enforcement instruments or prescribes penalties.

The practical implication is that anyone facing a compliance question, enforcement action or alleged breach must consult the operative instrument referenced by the endnotes to determine applicable penalties and which regulator or administrative mechanism enforces them. The endnotes provide the trail to find those substantive provisions but they are not themselves enforceable law.

From a compliance-risk viewpoint, there is an enforcement-related cost: if a user relies solely on the compiled text without checking the amending instruments referenced in Endnote 3, they risk misunderstanding which version of a provision applied at a given time and thus miscalculating exposure to penalties or enforcement. Endnote 4’s "(md)" and "(md not incorp)" flags indicate where compilation reliability might be compromised, which in turn increases the need to verify with primary sources before responding to enforcement action.

Finally, the endnotes’ metadata (Gazette registration numbers and commencement dates) supports enforcement by enabling regulators and enforcement agencies to establish the timeline of legal changes. That is, while the endnotes do not enforce, they affect the evidential path by which regulators and courts identify the operative law at a given time.

The endnotes operate as a cross-reference system linking the compiled Licence Area Plan to its amending instruments and consequential instruments. They do not in themselves interact substantively with other laws, but they provide the documentary links required to establish how the compiled text relates to the rest of the legal landscape.

Endnote 3 is structured to show the interaction points: for each amending instrument it records the instrument's name, the Gazette registration reference, the commencement date, and a field for "Application, saving and transitional provisions". Those entries are the explicit pointers to where interaction with other laws will be governed. For instance, a "Variation No.1 of 2008" recorded in Endnote 3 commenced 1 April 2008; any cross-cutting transitional rules, savings, or application provisions that determine how the Variation interacts with pre-existing licences or other regulatory instruments would be recorded in the amending instrument and should be listed in the "Application, saving and transitional provisions" column of the endnote (Endnote 3 table). The endnote therefore maps interaction by citation and by commencement.

Endnote 4 provides provision-level amendment history and flags misdescribed amendments with "(md)" or "(md not incorp)". Those flags matter where the interaction with other laws depends on precise textual amendments. For example, if an amendment purported to align an attachment of the Plan with a consequential change to Broadcasting Services (Technical Planning) Guidelines, but the amendment was misdescribed, the "(md not incorp)" flag signals that the intended cross-reference might not have been effectually made. The reader must then look to the amending instrument and possibly to related instruments to determine the actual legal interaction.

The endnotes also list consequential amendments, which is an explicit form of interaction. The Endnote 3 table includes "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)",an example of how the Plan is interconnected with regulatory guidelines. That shows a documented, reciprocal interaction: the Plan is amended in light of changes to technical planning guidelines, and the endnotes record those movements.

In terms of legal hierarchy, the endnotes do not change the ordering of laws. They are a tertiary resource pointing to primary legislation, subordinate instruments and guidelines. Where interaction is material for legal effect,such as transitional or saving provisions that determine whether older licences remain valid,the endnotes aim to summarise that linkage in the "Application, saving and transitional provisions" column, but the actual determinative text remains the original instruments.

Therefore, for legal operation, the endnotes are an interaction map: they record where, when and by which instrument the compiled law was altered. Determinations of conflict, precedence or operative effect must be made by consulting those primary instruments identified in Endnote 3 and the provision-level notes in Endnote 4.

Endnote 4 is the repository for provision-level amendment history and describes both how amendments are recorded and how anomalies are annotated. The endnote includes a table-like string that lists "Provision affected" alongside "How affected." In the supplied content, the "Provision affected" column enumerates items such as "Clause 1", "Clause 2", "Clause 3", "Schedule 1", and a list of Attachments by number (for example, Attachment 1.1, Attachment 1.2, Attachment 1.5, Attachment 1.7, Attachment 1.10, Attachment 1.11, Attachment 1.16, Attachment 1.18, Attachment 1.20, Attachment 1.21, Attachment 1.22, Attachment 1.23) (Endnote 4).

The "How affected" column records the instruments responsible for the amendments and the nature of those changes through shorthand. For instance, entries include "am. No 1 of 2008", "am. No.1 of 1998", "am. No.1 of 2003", "ad. No 1 of 2008", "rs. No 1 of 2008", and "am. No 1 of 2017." These entries indicate a mixture of additions, amendments, and repeals and substitutions across the instrument’s components. The use of the abbreviation key from Endnote 2 is necessary to translate those short forms.

Crucially, Endnote 4 also sets out a quality control procedure for misdescribed amendments. It explains that if a misdescription can nevertheless be given legal effect as intended, the compiler will incorporate it and add the annotation "(md)". If the misdescription cannot be given effect as intended, the compiler annotates "(md not incorp)". That procedural rule has two concrete consequences. First, it tells the user that some parts of the compilation may not exactly mirror the amending instrument’s text but are the compiler’s best effort to achieve the legislative outcome. Second, it provides a signalling mechanism so that users can detect where further verification is recommended.

The amendment-history table as supplied shows that the instrument underwent successive changes across several years: variations in 1998 and 2003, a notable Variation No.1 of 2008 with a commencement of 1 April 2008, and consequential amendments in 2017 relating to the Broadcasting Services (Technical Planning) Guidelines. The recorded Gazette references in Endnote 3 give a parallel trail to the Amendment History: for instance, F2008L00957 is the Gazette registration for Variation No.1 of 2008, which appears in both endnote tables as the instrument responsible for multiple "am." and "rs." entries.

For practitioners, the amendment history is therefore twofold: Endnote 3 identifies the amending instruments and their commencement, while Endnote 4 maps those instruments to specific clauses, schedules and attachments and flags any drafting anomalies. Both endnotes together constitute the compilation’s audit trail for amendments, and the explicit "(md)" regime identifies where a user should be cautious and consult the original amending instrument.

The supplied endnotes do not record any litigation history. There are no case citations, reported decisions, tribunal determinations, or references to litigation outcomes in the material provided. The endnotes are limited to compilation metadata, an abbreviation key, legislative history and amendment history (Endnotes 1-4). They do not purport to be a research digest of case law or to list judicial interpretations of the compiled provisions.

The absence of litigation material in the endnotes has practical implications for users who need to understand the legal meaning of particular provisions or to assess enforcement risk. While Endnote 3 supplies Gazette registration and commencement dates for amending instruments, and Endnote 4 supplies provision-level amendment records, neither offers interpretive guidance or examples of judicial application. Consequently, users who require authoritative interpretation must search case law databases, tribunal records, or administrative rulings outside the compilation.

The endnotes do include a mechanism for flagging misdescribed amendments (Endnote 4), but that mechanism is editorial and does not substitute for judicial or administrative interpretation. A "(md)" annotation indicates an incorporated misdescription the compiler believes can be given effect; a "(md not incorp)" annotation indicates the compiler could not implement the misdescription. Neither annotation resolves how a court would construe the instrument; it only records the compiler’s approach to presenting the text in the compilation.

For matters where litigation outcomes might affect compliance, licensing rights, or technical planning obligations, the endnotes should be treated as an index to the primary instruments rather than a substitute for legal research. The user should consult the amending instruments cited in Endnote 3 and then conduct case-law research to discover any reported decisions that construe those instruments or their provisions. The endnotes’ lack of litigation history is therefore a limitation a practitioner must address when preparing for adjudication or enforcement matters.

The endnotes include several features and limitations that can catch users unprepared. These "gotchas" flow directly from the endnotes’ stated function as informational and from the compiler’s annotation approach. They are set out below with the relevant endnote references.

1. Endnotes are not substantive law (Endnote 1). Users who treat the compilation as the primary legal instrument risk missing operational provisions contained in the amending instruments. The endnotes signal provenance but do not substitute for the operative text in force.

2. Abbreviation ambiguity (Endnote 2). The abbreviation key lists "ad", "am", "rep.", but the printed line also contains "rep. = repealedrs. = repealed and substituted" which is typographically fused. Practitioners relying on automated parsing or quick reading may misread the codes. Users must manually verify the meanings in the context of the amendment history.

3. Potential misdescription issues (Endnote 4). The compiler flags misdescribed amendments with "(md)" or "(md not incorp)". A "(md)" indicates the amendment was misdescribed but could be given effect and was incorporated. A "(md not incorp)" indicates the misdescription could not be implemented. The gotcha is that the compilation may therefore present a text that differs from the amending instrument’s literal wording where the compiler has exercised discretion. Users must check original instruments where "(md)" or "(md not incorp)" appear.

4. Omitted transitional or saving details (Endnote 3). The legislative history column claims to include "details of any application, saving or transitional provisions that are not included in this compilation." The gotcha is that where such provisions are not included in the compilation, the compiled text alone will not reveal transitional arrangements; users must pursue the original amends to find out how transitions were handled.

5. Gazette reference is a pointer, not a full record (Endnote 3). The registration or notification in Gazette is recorded, but that is a reference to official publication, not a replacement for the full instrument text. Assuming the Gazette citation supplies the entire legal content would be an error.

6. Scope of amendment-history entries (Endnote 4). The amendment-history entries aggregate multiple attachments and clauses into a single line with multiple instruments referenced. That economy of presentation can obscure the precise textual change and may require a line-by-line check with the amending instruments.

7. No litigation or interpretive guidance. As noted earlier, there is no litigation history or interpretive annotation. Users who need interpretive certainty must seek case law or regulator guidance externally.

8. Reliance on compilation dates. The Endnote 3 commencement dates are authoritative for the amending instruments’ commencement as recorded by the compiler. However, if an instrument’s application is subject to specific saving or commencement provisions that differ from the recorded date, the compilation’s single-date presentation could be misleading. Users should verify any staggered or partial commencements in the primary amending instrument.

9. Machine-readability and data-cleanliness. The supplied tables and abbreviation lines show formatting irregularities (for example, fused cell data and missing separators). Users automating extraction must validate parse results against the human-readable endnotes.

10. Editorial changes by subsequent compilers. The endnotes reflect the compiler’s judgement at the time of compilation. Later editions of the compilation might alter annotations or include previously omitted transitional provisions. Users must check the version and date of the compilation.

Each of the above gotchas follows directly from the endnotes’ stated content and structure (Endnotes 1-4). They do not allege errors in the primary law; rather they emphasise how the endnotes' editorial mechanics can affect research, compliance and enforcement tasks.

Compliance in relation to these endnotes has two strands: procedural compliance when using the compilation for legal work, and practical steps for ensuring accurate reliance on the compiled text. The endnotes themselves impose no statutory duties, but they embed signals and annotations that users must respect. The checklist below follows directly from the endnotes’ stated contents (Endnotes 1-4).

1. Use the endnotes as an index, not as substitute law. The endnotes explicitly provide information about the compilation and compiled law (Endnote 1). Always obtain and read the primary instrument(s) cited in Endnote 3 before advising, deciding or acting on a matter that depends on legal effect.

2. Translate abbreviations. When reading the amendment history, convert the codes from the Endnote 2 key into full terms: "ad = added or inserted", "am = amended", "rep. = repealed". Be alert to typographical irregularities in the key. If the compiled text shows "rs." interpret that in context (for example, "rs." is used in the amendment table).

3. Check the Gazette references and commencement dates. Endnote 3 supplies Gazette registration numbers and commencement dates (for example, F2008L00957 and 1 April 2008). To confirm effect, obtain the Gazette notice and the full text of the amending instrument. Confirm whether any special commencement provisions apply that might alter the effective date.

4. Investigate "Application, saving and transitional provisions." Endnote 3 includes a column for these provisions. If the compilation indicates that such provisions exist but does not include them, retrieve them from the amending instruments. Transitional and saving provisions often determine the rights or obligations during changeovers.

5. Review "(md)" and "(md not incorp)" flags. Endnote 4 instructs users to treat "(md)" as an incorporated misdescription and "(md not incorp)" as a misdescription that could not be given effect. Where these flags appear, reconcile the compiled text with the original instrument and, if necessary, verify legislative intent through parliamentary materials or legal advice.

6. Cross-check provision-level amendments. Use Endnote 4 to map which clauses, schedules and attachments were affected by each amendment. For precise compliance, compare the compiled provision against the amending instrument’s text to ensure there are no transcription or editorial differences.

7. Confirm version and currency of the compilation. The endnotes record amendments up to 2017 in the supplied material. If compliance depends on the current law, verify whether further amendments or subsequent compilations have been published.

8. Do not rely on the compilation for litigation posture. Because the endnotes contain no litigation history and because "(md not incorp)" may indicate residual uncertainty, obtain original instruments and conduct case-law research before litigating or advising on enforcement issues.

9. Document reliance steps. Where a compliance decision depends on the compiled instrument, record the steps taken to verify the text: which Gazette notices were consulted, which amending instruments were obtained, whether "(md)" flags were present, and what conclusions were reached about commencement and transitional rules.

10. For automated systems, validate parsing. The endnotes show formatting irregularities that can mislead automated parsers. Build validation checks to compare parsed Gazette references and dates with official Gazette databases to ensure accuracy.

Following this compliance checklist aligns with the role the endnotes perform as explained in Endnotes 1-4. The core practical rule is to treat the endnotes as a curated pointer system and to verify critical legal facts with the primary amending instruments and official Gazette publications before taking legal, contractual or regulatory action.