Licence Area Plan - Longreach (Radio) - August 1996

The endnotes centre on four doctrinal or editorial concepts: (1) a defined, small set of endnotes that accompany every compilation; (2) an abbreviation key that standardises editorial shorthand; (3) a legislation history that records registration and commencement metadata for the principal instrument and its amending instruments; and (4) an amendment history that provides a line-by-line account of what was added, amended, replaced or repealed and by which instrument. Each concept is present and described in the text you provided.

1. Endnotes included in every compilation. The document states which endnotes are included in every compilation: Endnote 1 (About the endnotes), Endnote 2 (Abbreviation key), Endnote 3 (Legislation history) and Endnote 4 (Amendment history). The text emphasises these are standard inclusions for compiled laws and are therefore part of the compilation’s metadata (Endnote 1,About the endnotes).

2. Abbreviation key. Endnote 2 contains a table of abbreviations (for example, am = amended; rep = repealed; rs = replaced and substituted; ad = added/inserted; s = section(s); Pt = Part(s); F = Federal Register of Legislation). That key is the compilation’s source of truth for interpreting the shorthand used throughout the amendment history and other endnote entries.

3. Legislation history. Endnote 3 is a compact table listing at least two instruments: the original Licence Area Plan - Longreach (Radio) - August 1996 with a registration entry of 14 April 2005 (see F2005B01110) and a Variation to Licence Area Plan - Longreach Radio - 2024 (No. 1) with registration F2024L01613, registration 23 December 2024 and commencement 24 December 2024 (Endnote 3,Legislation history table). The table explicitly provides columns for Name, Registration, Commencement and "Application, saving and transitional provisions" (the latter cells are blank for the rows shown). Readers should treat these entries as the compilation’s record of which instruments have affected the compiled material and when they came into force.

4. Amendment history mechanics. Endnote 4 is an itemised amendment history. It does two things. First, it supplies a map of "Provision affected" to "How affected" entries. Second, it uses the abbreviation key shorthand to show whether parts were repealed (rep.), amended (am.), added (ad.), or replaced/substituted (rs.). The HTML table included records an extensive set of entries showing many attachments were amended (am. F2024L01613), some replaced (rs. F2024L01613), and several added (ad. F2024L01613), as well as particular pages such as Title page and Schedule page being repealed (rep. F2024L01613).

A further editorial concept is the treatment of misdescribed amendments. The endnotes refer to the Legislation Act 2003, s 15V, as the authority under which editors may make changes to incorporate misdescribed amendments where the intended effect is clear. If incorporation is not possible, the amendment is marked “(md not incorp)”. That is an operational rule for editors and a disclosure device for users about editorial interventions.

Finally, the endnotes use instrument identifiers and gazette/Federal Register citations (for example F2024L01613, F2005B01110, gaz 11 September 1996). Those identifiers are used to locate the primary instruments; the compilation lists them but does not reproduce the full text of the amending instrument in the endnotes excerpt provided.

The endnotes principally affect the set of actors who rely on an accurate, current compilation of the Licence Area Plan - Longreach (Radio). Concretely, the affected groups include:

• Legal practitioners, drafters and counsel who must rely on the correct textual history of the instrument for advice or litigation. The endnotes provide the authoritative compilation metadata such practitioners use to confirm which version of a document is current (Endnotes 1-4).

• Compliance officers, licensees, planners and engineers who might be subject to technical rules or geographic delineations in the Licence Area Plan and its attachments. The amendment history shows Attachments 1.1-1.31 were variously amended, added or replaced by F2024L01613; anyone whose operations are governed by those attachments needs to verify the new or replaced attachments because those likely contain the technical parameters and maps (Endnote 4 entries for Attachment 1.1-1.31).

• Government publishing and parliamentary officers who compile, register and maintain instruments on the Federal Register of Legislation. The endnotes document the editor’s powers and constraints, including the use of s 15V of the Legislation Act 2003 to correct misdescribed amendments (Endnote 1 text).

• Researchers, journalists and third-party data providers who need to reconcile versions, produce timelines or track regulatory change in the Longreach radio licensing area. The registration dates and commencement dates in Endnote 3 (for example F2024L01613 registered 23 December 2024 and commenced 24 December 2024) are key timestamps for any timeline work.

• Courts and tribunal registrars to the extent they need to verify which instrument text was in force at a given date; the amendment history provides the editorial record and flagging mechanism for misdescribed amendments (Endnote 1).

The document does not itself alter substantive legal obligations, but by recording that the Variation to Licence Area Plan - Longreach Radio - 2024 (No. 1) has been registered and commenced, it signals that downstream actors with rights, licences or compliance obligations tied to the Licence Area Plan must check the amending instrument and the amended attachments for new operative content. The endnotes therefore function as a navigational and evidential tool for those whose legal or commercial position depends on the plan’s text.

The text does not list named licence-holders or agencies; it does not specify penalties or specific technical changes. It does, however, make explicit the instruments and specific attachment identifiers that were altered or added, which is the principal practical touchpoint for affected parties (Endnote 4).

The endnotes themselves do not create substantive duties or statutory rights; rather they identify where duties and rights may be set out in the primary instrument and its amending instruments. Nonetheless, they create specific informational duties and procedural rights relevant to users of the compilation:

• Duty to check amendment provenance. Users who rely on the compiled Licence Area Plan must check the legislation history (Endnote 3) and amendment history (Endnote 4) to establish which instrument(s) actually altered the plan and when those changes commenced. The endnotes record the registration identifier and commencement date for the variation (F2024L01613, reg. 23 December 2024, commenced 24 December 2024), creating an informational obligation on users to consult that amending instrument for substantive changes.

• Duty to interpret editorial shorthand correctly. The compilation imposes an interpretive duty on readers to use the abbreviation key in Endnote 2 when reading the amendment history. Misreading abbreviations such as am., rep., rs., ad. will lead to incorrect conclusions about whether a provision was amended, repealed, replaced or added.

• Right of notice about editorial corrections. The endnotes provide users the right to be informed when an amendment has been misdescribed and either incorporated editorially under s 15V of the Legislation Act 2003 or flagged as not incorporated by the notation “(md not incorp)”. That is an editorial transparency right given to users of the compilation (Endnote 1 text referring to s 15V).

• Duty on editors/publishers. The endnotes make explicit an editorial duty: where a misdescribed amendment can be given effect, editors may incorporate it by an editorial change under s 15V of the Legislation Act 2003. This places a procedural duty on the compilation’s maintainers to both correct certain misdescriptions and to declare when they cannot do so by using the defined notation (Endnote 1). The endnotes thereby record the editorial rules the publisher follows.

• Right to rely on registration/commencement metadata. Users have a documented source for registration and commencement datestamps (Endnote 3 entries). That metadata functions as a practical evidential right for users asserting what law was in force on a given date , subject, of course, to verification against the primary instruments themselves.

• No statutory penalties created by endnotes. The endnotes do not set out offences, fines or enforcement mechanisms. They merely annotate and explain the compilation’s treatment of instruments and amendments.

For legal practitioners, the key operational duty is to move from the endnotes to the underpinning instruments: the terminology and the amendment history identify which attachments and pages have been altered; establishing the substantive legal effect requires retrieving F2024L01613 and the replaced or added attachments themselves, because the endnotes do not contain the substantive text of the amendments.

The endnotes provided do not create or prescribe any penalties, offences or enforcement mechanisms. They are editorial and bibliographic materials intended to document the existence, registration and editorial treatment of instruments; they do not themselves constitute regulatory or criminal provisions. The text makes this clear by the nature of the content: Endnote 1 explains what endnotes are included and how misdescribed amendments are treated editorially, Endnote 2 supplies abbreviations, Endnote 3 records registration and commencement entries, and Endnote 4 lists the amendment history in shorthand. None of these entries mentions enforcement powers, sanctions, or penalty amounts.

Where enforcement or penalties might appear, they would be located in the substantive licence area plan, the amending instrument (F2024L01613), or in other statutory instruments referenced by those texts. The endnotes’ functional role is to point users to those instruments and to show how the compilation has incorporated amendments. The presence of the notation “(md not incorp)” in editorial practice, described in Endnote 1, is an editorial flag and not a sanctioning mechanism; it simply indicates that a particular misdescribed amendment could not be editorially incorporated.

There is one procedural mechanism with legal force mentioned indirectly: the editorial incorporation of misdescribed amendments is conducted under section 15V of the Legislation Act 2003. That section is cited as the authority for making editorial changes to give effect to misdescribed amendments. The endnotes treat this as an editorial rule, not a penalty. The text does not reproduce s 15V itself nor describe its procedural safeguards, time limits or appeal routes; it merely states that editorial incorporation can be done under that section where a misdescription can be given effect as intended. Where a user needs to understand the constraints or legal effect of an editorial incorporation, they must consult the Legislation Act 2003’s text (not reproduced here) to see whether that mechanism affects legal rights or remedies.

In practice, the enforcement implication for stakeholders is indirect and factual: if the amending instrument (F2024L01613) created or removed obligations for licensees, those obligations will be enforced under the substantive law that governs radio licensing. The endnotes themselves create no enforcement route; they are an evidentiary record that assists parties, regulators and courts to determine which instrument text was in force and whether any editorial corrections were applied to the compilation after the fact.

The endnotes explicitly reference the Legislation Act 2003 and the Legislative Instruments Act 2003 through their abbreviation key and by name, and the compilation uses the Federal Register of Legislation citation format (F-codes). Interaction points set out in the endnotes include:

• Legislation Act 2003, s 15V. Endnote 1 explains that misdescribed amendments may be incorporated through an editorial change made under s 15V of the Legislation Act 2003 where the misdescription can nonetheless be given effect as intended. This is an explicit point of interaction: the compilation’s editorial practice draws its legal authority for correcting misdescriptions from the Legislation Act. To understand the scope and limits of editorial corrections and any legal consequences, a user must consult s 15V; the endnotes do not reproduce that section but state conclusively that it is the applicable mechanism for editorial correction.

• Legislative Instruments Act 2003 (LIA). The abbreviation key includes LIA = Legislative Instruments Act 2003, establishing the compilation’s practice of using LIA shorthand. Although the endnotes do not describe substantive interaction with the LIA, the inclusion of LIA in the abbreviation key signals that the compilation’s instruments are legislative instruments and that procedural and publication requirements under the LIA may apply to those instruments.

• Federal Register of Legislation identifiers and gazette references. The legislation history lists registration numbers such as F2005B01110 and F2024L01613 and a gazettal date (gaz 11 September 1996) for the original plan entry. These identifiers are part of the Federal Register of Legislation’s system and indicate the compilation interoperates with that platform: the register provides the canonical text, metadata and retrieval paths for the instruments listed in the endnotes.

• Editorial notation conventions. The endnotes implement a standardised notation system (e.g. rep., am., rs., ad., (md not incorp)) that aligns with broader Commonwealth legislative publishing practices. Those conventions act as a bridge between the compilation and other legislative publications and datasets.

• Evidence and tribunal processes. While not stated explicitly, the endnotes are evidence about the textual history of the instrument and would be cited where courts or tribunals need to establish which version of a plan applied at a given time. The endnotes therefore intersect indirectly with processes under the Administrative Decisions (Judicial Review) Act 1977 and other legal processes that rely on accurate instrument provenance; however, the endnotes do not list those statutes.

Limits of interaction stated in the text: the endnotes do not themselves displace or alter substantive provisions of the principal instrument; they only record changes made by other instruments and the editorial decisions applied in the compilation. Any substantive legal interaction , for example, whether a replaced Attachment 1.1 changes licence boundaries or technical parameters , must be resolved by consulting the amending instrument F2024L01613 and the actual replacement attachments, because the endnotes record only the fact and provenance of changes, not their operative substance.

Endnote 4 supplies a granular amendment history in table format. The amendment history lists specific parts of the compilation that the Variation to Licence Area Plan - Longreach Radio - 2024 (No. 1) instrument (F2024L01613) has affected. The entries, shown as shorthand plus the amending instrument identifier, include the following notable items drawn directly from the table:

• Title page: rep. F2024L01613. The Title page of the compilation was repealed by the variation.

• Determination: am. F2024L01613. The Determination was amended.

• Determination, c 3-7: ad. F2024L01613. New clauses 3-7 were added to the Determination.

• Date after clauses: rep. F2024L01613. The "Date after clauses" page or entry was repealed.

• Schedule page: rep. F2024L01613. The schedule page that previously existed was repealed.

• Schedule One: rs. F2024L01613. Schedule One was replaced and substituted by the variation.

• Attachment 1.1: rs. F2024L01613. Attachment 1.1 was replaced and substituted.

• Attachments 1.2-1.31: a mixture of amendment (am.) and replacement (rs.) entries are recorded. For example, Attachment 1.2 is marked am. F2024L01613, Attachment 1.3 am. F2024L01613, while Attachment 1.1 is rs. F2024L01613. Specific new attachments were added, e.g. Attachment 1.22A is ad. F2024L01613 and Attachment 1.24A is ad. F2024L01613.

• Schedule-level and attachment-level changes: the table shows changes at both the schedule and attachment level, indicating structural changes to the compilation , not merely textual edits. The presence of 'rs.' (replaced and substituted) entries indicates some parts were fully replaced, not merely amended.

The amendment history is extensive and detailed in its shorthand. It records which particular elements were altered and by which instrument. It does not reproduce the text of those amendments, but it supplies the necessary pointers for locating the amending instrument and the replaced or added material.

The amendment history also records that the primary compilation was itself originally registered as "Licence Area Plan - Longreach (Radio) - August 1996" with a registration identifier F2005B01110 and a gazette date of 11 September 1996, while the variation was registered as F2024L01613 on 23 December 2024 and commenced on 24 December 2024 (Endnote 3). This shows the line of authority and the timeline for when the amendments became operative in the compiled text.

Two procedural features are important for users: first, the use of standard shorthand that must be read against the abbreviation key in Endnote 2; second, the editorial caveat in Endnote 1 about misdescribed amendments, which explains that some entries may have been subject to editorial correction under s 15V of the Legislation Act 2003. If an amendment could not be given effect as intended due to a misdescription, it is not incorporated and would be annotated “(md not incorp)”, although the particular table excerpt provided does not show any “(md not incorp)” markers for the entries listed.

Practically, the amendment history tells readers exactly where to look: if, for example, a radio licensee needs to know whether boundary maps changed, the amendment history shows Attachment 1.1 was replaced and several attachments were amended or added; the licensee must retrieve the contents of Attachment 1.1 as replaced under F2024L01613 to see the new boundaries or technical parameters.

The endnotes do not record any litigation history. There is no mention of court proceedings, judicial interpretations, appeals or disputes concerning the original Licence Area Plan - Longreach (Radio) or the Variation to Licence Area Plan - Longreach Radio - 2024 (No. 1) in the provided text. The endnotes are concerned with registration, commencement and editorial history; they do not collect or summarise litigation data.

For practitioners looking for litigation that might bear on the plan or its variation, the absence of any litigation entries in the endnotes means two things: first, the compilation’s endnotes are not a repository for case law; second, researchers should not assume there has been no litigation simply because none is recorded in the endnotes. The endnotes’ function is strictly to document amended legislative instruments and editorial actions. If litigation exists that affects interpretation or enforcement of the plan, that litigation would appear in case law databases, court registers or separate parts of statutory databases , not in this endnotes record.

Users requiring litigation history should therefore take these steps: consult legal databases (for example AustLII, or official court registers), search for proceedings that reference the Licence Area Plan - Longreach (Radio) or the amending instrument identifier F2024L01613, and check tribunal decisions where administrative law questions about radio licensing or plan variation may have been litigated. The endnotes provide authoritative instrument identifiers and dates which are useful search keys for that external litigation research (for example, use F2024L01613 and the commencement date 24 December 2024 as search parameters in case databases).

The endnotes do show the exact amending instrument identifier and commencement timestamp that a litigant would rely on when pleading which version of an instrument was in force at a particular time; that evidential function is useful in litigation even though litigation itself is not recorded here.

The endnotes present several practical pitfalls and traps for those relying on the compilation. The following are concrete items drawn from the endnotes and the amendment history table:

• Do not assume the endnotes are substantive law. The endnotes record metadata and editorial decisions; they do not themselves create or change substantive legal obligations. Users who need the operative text must retrieve the primary instruments referenced by the endnotes, notably the variation F2024L01613 and any attachments replaced or added (Endnotes 3 and 4).

• Abbreviation misreading risk. The amendment history uses shorthand heavily. Misinterpreting am. (amended), rs. (replaced and substituted), rep. (repealed), ad. (added) will lead to wrong conclusions about whether a provision exists or has been removed. Always cross-check against Endnote 2’s abbreviation key before acting on the amendment history.

• Editorial incorporation can mask misdescription. Endnote 1 explains that if a misdescribed amendment can be given effect, editors will incorporate it under s 15V of the Legislation Act 2003. That means the compiled text may include editorial corrections that are not literal reproductions of the amending instrument’s description. If precise original drafting is material (for litigation or historical analysis), users must obtain the original instrument(s) and any recorder of “(md not incorp)” markers to see what was editorially changed.

• Absence of the substantive amending text in the compilation excerpt. The amendment history shows many attachments were amended or replaced, but the endnotes excerpt provided does not include the replacement texts. Parties affected by the plan must retrieve the new attachments and not rely solely on the endnote shorthand to know what changed in substance.

• Timing and registration details require verification. The legislation history lists registration and commencement dates, but users should verify these dates by consulting the Federal Register of Legislation entry for F2024L01613. For example, the table shows the original plan has registration 14 April 2005 (F2005B01110) with gazette 11 September 1996. That apparent diachrony suggests the compiled metadata records the original gazette date as 11 September 1996 while the registration identifier is dated 2005; users must not assume continuity without verifying the actual historical instruments.

• Many attachments amended or added. The sheer number of attachments listed as amended (Attachments 1.2 through 1.31 repeatedly marked am. F2024L01613) means a large body of technical material may have changed. Missing an amended attachment could have operational consequences for licensees. Practitioners should check each attachment cited in the amendment history relevant to their area.

• No transitional or savings clauses recorded. The legislation history table’s "Application, saving and transitional provisions" column is blank for the variation row. That does not mean there are no transitional provisions in the amending instrument , it means none are recorded in this excerpt. Users should check F2024L01613 for any transitional arrangements that might affect rights or compliance obligations during the changeover.

• Notation “(md not incorp)” may appear elsewhere. Although not shown in the provided table excerpt, the endnote text explains the compilation will append “(md not incorp)” where a misdescribed amendment cannot be given effect. Users need to look for this notation because it indicates there remains some discrepancy between the amending instrument’s descriptive text and what can be given effect in the compiled text.

• Reliance on the compilation alone is insufficient. The endnotes are a navigational tool. Where the substantive content of an attachment is critical (for example maps or technical radio parameters), relying on the endnote’s shorthand without inspecting the actual attachment may leave a client exposed to non-compliance.

Each of these “gotchas” is grounded in the endnotes’ mechanics: the heavy use of shorthand in Endnote 4, the editorial incorporation rule in Endnote 1, and the limited scope of information provided in the legislation history in Endnote 3. They translate into operational risks for lawyers and compliance professionals who must ensure they retrieve and check the primary amending instrument and any replaced or added attachments.

Compliance, in the context of these endnotes, means taking the documented steps to ensure a client’s actions, licences or regulatory practices align with the actual operative text of the Licence Area Plan and its variations. The endnotes give a clear checklist and record identifiers to support compliance work. Practical compliance steps, grounded in the endnotes, are as follows:

1. Retrieve the amending instrument(s) by identifier. Use the registration identifier F2024L01613 (listed in Endnote 3) to download the full text of the Variation to Licence Area Plan - Longreach Radio - 2024 (No. 1) from the Federal Register of Legislation. Do not rely solely on the endnote summary to determine substantive obligations.

2. Verify commencement. The legislation history shows F2024L01613 was registered 23 December 2024 and commenced 24 December 2024 (Endnote 3). Confirm these timestamps in the amending instrument and, where timing affects compliance (for example, licence renewal windows or transitionary compliance dates), plan action around the actual commencement date.

3. Map attachments to operational responsibilities. The amendment history lists which attachments were replaced, amended or added (Endnote 4). Identify which attachments (for example Attachment 1.1, 1.2, 1.22A, 1.24A etc.) pertain to your client’s licences or technical operations. Retrieve each replaced or amended attachment and read them in full to determine any change to parameters, boundaries, frequencies, or other operational constraints.

4. Watch for editorial corrections and misdescribed amendments. The endnotes explain editorial incorporation under s 15V of the Legislation Act 2003 (Endnote 1). Where a compilation includes incorporated corrections, document this in your compliance file and, if necessary, obtain the original instrument(s) to cross‑check whether the text has been editorially corrected. If the amendment is annotated “(md not incorp)” in the compilation, treat the matter as unresolved until you inspect the underlying instrument.

5. Check for transitional provisions. The legislation history table has a column for "Application, saving and transitional provisions" but no entries are shown in the extract. Search F2024L01613 for any transitional or savings clauses which might postpone obligations or preserve rights during the changeover.

6. Use the abbreviation key. When interpreting the amendment history, use Endnote 2’s abbreviation key to ensure accurate reading of shorthand such as am., ad., rs., rep. Misreading these will cause incorrect compliance conclusions.

7. Update compliance documentation and notifications. If the substantive attachments change technical parameters (which they likely do when attachments are amended or replaced), update internal compliance manuals, technical specifications, licence condition trackers, and any notices you must give to stakeholders or third parties. Record the Federal Register identifiers and the dates of retrieval in your file.

8. Consider regulatory reporting. If your client is a licensee, check whether the changes require you to notify the regulator, update licence conditions, or apply for variations. The endnotes do not state any regulator’s reporting obligations; consult the substantive instrument and the regulatory framework governing radio licences.

9. Maintain version control. Keep copies of pre-amendment and post-amendment attachments, and document the amendment history shown in Endnote 4 in your compliance audit trail. If any disputes arise about which text applied at a given time, the compiled amendment history plus the archived primary instruments will be essential evidence.

10. Where necessary, escalate to specialist counsel. If the amended attachments produce material operational or commercial impacts (for example changes to licence areas, interference protections, or technical standards), instruct specialist regulatory counsel or technical consultants to advise on implications and risk mitigation.

These steps derive directly from the endnotes’ content: use the Federal Register identifiers from Endnote 3, interpret amendment entries using Endnote 2, and follow editorial caveats in Endnote 1. The endnotes give you the route map; compliance requires following those pointers to the primary instruments and applying the substantive legal and regulatory rules that govern radio licensing.