Television Licence Area Plan (Mount Gambier/South East) 2011

The endnotes revolve around four main concepts: the inclusion rule for endnotes, the abbreviation key, legislation history entries, and amendment history entries, plus a linked concept of editorial correction for misdescribed amendments.

Inclusion rule for endnotes. The document opens with the declarative sentence “The following endnotes are included in every compilation: Endnote 1,About the endnotes; Endnote 2,Abbreviation key; Endnote 3,Legislation history; Endnote 4,Amendment history.” That sets a structural expectation: any reader of the compilation should be able to find these four informational items consistently. The concept here is one of standardised metadata attached to each compilation rather than ad hoc notes.

Abbreviation key. Endnote 2 supplies a compact legend of the shorthand used across the compilation’s metadata tables. The key maps symbols to meanings: for example “am = amended”, “rep = repealed”, “LA = Legislation Act 2003”, “LIA = Legislative Instruments Act 2003”, “(md not incorp) = misdescribed amendment cannot be given effect”. These tokens are the compressed language by which the compilation communicates status, provenance and editorial decisions. Understanding the key is necessary to read the legislation and amendment history entries correctly.

Legislation history entries. Endnote 3 is described as providing “information about each law that has amended (or will amend) the compiled law. The information includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation.” The supplied table contains three entries, each with a title, a registration date, a commencement date and a cross-reference code (for example “see F2011L02764”). Conceptually, this is an external pointer system: the compilation records the identity and timing of amending instruments but does not necessarily reproduce their full text or the content of their transitional provisions.

Amendment history entries. Endnote 4 records “amendments at the provision (generally section or equivalent) level” and provides a compact listing of which provisions have been added, amended or repealed and by which instrument. The entries show how specific sections or schedule items have been affected (for example “Section 2.......... rep. LA 48D”). The conceptual function is to audit changes to the internal structure and text of the compiled instrument.

Misdescribed amendments and editorial correction. The document defines “misdescribed amendment” and lays out a two-step treatment: if the misdescription can be given effect as intended, compilers may make an editorial change under section 15V of the Legislation Act 2003; if not, the misdescribed amendment is left out of the compilation and annotated “(md not incorp)”. That embeds an editorial discretion and a labelling protocol into the compilation’s methodology. The concept combines legal-technical parsing (can the intended change be given effect?) with an administrative decision to correct or to flag non-incorporation.

These concepts act together to present the compilation as a curated, annotated product. The endnotes do not purport to substitute for reading the primary instruments; instead they identify, label and explain the provenance and editorial handling of amendments and amending instruments. Users must rely on the abbreviation key to decode cryptic annotations and on the legislation and amendment history tables to trace the source instruments and timing of changes. The misdescribed amendment rule shows where editorial discretion has been exercised and where the compilation diverges from primary sources.

The endnotes affect anyone who relies on the compilation for authoritative or practical information about the compiled law’s provenance, amendment history and editorial status. That includes practising lawyers, legislative drafters, compliance officers, regulators, accountants, academic researchers, journalists and any legal publisher or database that republishes the compilation.

Legal practitioners: For lawyers who cite or advise on the compiled instrument, the endnotes supply the provenance trail and amendment audit. The legislation history (Endnote 3) and amendment history (Endnote 4) list the amending instruments and the provision-level changes; practitioners need that information to verify whether an amendment was correctly captured in the compilation and to locate the original instrument for any omitted transitional or application provisions. Where the compilation records a misdescribed amendment as “(md not incorp)”, practitioners must treat the compilation as signalling a divergence and check the primary source.

Regulators and compliance officers: These readers use compilations to check whether obligations and commencement dates have changed. The endnotes’ explicit statement that the legislation history “includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation” signals that the endnotes will point to omitted transitional material. For compliance purposes, that pointer is material because transitional provisions often determine when duties become enforceable and to whom they apply.

Legislative drafters and publishers: Compilers and drafters need the abbreviation key and the misdescription protocol. The endnotes make explicit that an editorial power exists (section 15V, Legislation Act 2003) and that a label “(md not incorp)” will mark amendments that cannot be given effect as intended. Publishers republishing the compilation must preserve these endnotes so users can interpret editorial changes and cryptic annotations.

Researchers and journalists: For secondary users who are not necessarily checking primary instruments, the endnotes provide necessary context for dates and identifiers. The legislation history table includes titles and registration dates for amending instruments (for example, “Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) , 29 September 2017”), which enables targeted searches in the Federal Register or in legislative databases using the cited registration identifiers (for example “F2017L01299”).

Owners and operators of secondary databases: When incorporating the compilation into a searchable database, the endnotes are the metadata that must be indexed to allow users to trace back amendments and commencement. The inclusion of file identifiers such as “F2025L01363” requires databases to map those codes to the primary instrument entries.

Overall, the endnotes primarily affect users who must rely on the accuracy and completeness of a compilation. The document’s explicit mechanics about editorial correction and the presence of standardised endnotes are aimed at ensuring those users can locate primary documents, understand the meaning of abbreviations and identify instances where the compilation departs from source material.

The endnotes articulate duties and rights that are procedural and informational rather than substantive legal entitlements or obligations. Those duties and rights fall into two categories: duties of the compilers (what the compilation will do and how it will present changes) and informational rights of users (what the compilation gives readers the right to know).

Duties of compilers. The endnotes establish an expectation that compilers will include four standard endnotes in every compilation: information about the endnotes themselves, an abbreviation key, a legislation history and an amendment history. That is a publication duty, framed declaratively: “The following endnotes are included in every compilation.” Compilers are also bound to follow a prescribed process for misdescribed amendments: if a misdescribed amendment can be given effect, the compilers may make an editorial change under section 15V of the Legislation Act 2003; if it cannot be given effect, the amendment must be annotated as “(md not incorp)”. That sets an editorial duty-to-declare: compilers must either make a corrective editorial change or flag the non-incorporation.

Duties implied for accuracy and disclosure. By stating that the legislation history “provides information about each law that has amended (or will amend) the compiled law” including commencement details and omitted application, saving or transitional provisions, the endnotes create an informational duty to disclose where relevant material is not reproduced in the compilation but exists elsewhere. The document thereby obliges compilers to list such instruments and to include pointers (registration numbers) to the source instruments.

Informational rights of users. The endnotes give users the right to see at least four items of metadata: an explanation of the endnotes, the abbreviation key, the legislation history and the amendment history. Practically, this is a right to transparency about the lineage and editorial handling of the compilation. Users have the right to be informed where an amending instrument contains commencement, application or transitional provisions that the compilation does not include, and they have the right to see a label “(md not incorp)” where misdescribed amendments cannot be given effect.

Rights to rely and limits on reliance. While the endnotes provide metadata to assist reliance, they implicitly limit reliance by signalling when material is not included in the compilation. The endnotes’ function is to point the reader to primary instruments; the compilation’s editors retain an editorial power (s 15V) to correct misdescription where feasible, but users must check the primary sources where the endnotes indicate excluded or flagged material.

No criminal or civil penalties are created by the endnotes themselves. The document is procedural; its duties are publication and disclosure duties borne by the compiling agency. The only legal mechanism referenced is s 15V of the Legislation Act 2003, which authorises an editorial change , a statutory power that imposes a process constraint on how compilers may address misdescribed amendments. The text does not create private rights of action, nor does it set out enforcement mechanisms or sanctions for non‑compliance with its publication duties. The rights it confers are informational and procedural: users are informed of how amendments and editorial decisions have been recorded.

The supplied text does not establish penalties, offences or direct enforcement mechanisms. The endnotes are metadata for a legislative compilation and operate as descriptive and editorial annotations rather than as normative provisions that impose penalties.

Administrative mechanism: editorial change under the Legislation Act. The only statutory mechanism referenced is the editorial power under section 15V of the Legislation Act 2003. The endnotes say that when an amendment is misdescribed but can be given effect as intended, compilers can incorporate it through an editorial change made under s 15V. That provision is a statutory authorisation for compilers to make editorial corrections; it is not framed here as a penalty or enforcement tool but as an administrative legal power that governs the technical process of compilation.

Labelling mechanism instead of sanction. Where a misdescribed amendment cannot be given effect as intended, the endnotes describe a labelling response: the amendment “is not incorporated and ‘(md not incorp)’ is added to the amendment history.” That label is an informational control, a transparency measure, rather than a sanction. It has the practical effect of highlighting to readers that the compilation does not reflect that specific change; it does not itself impose legal consequences on private parties. The label serves as a warning and preserves fidelity to primary sources.

Indirect consequences for users. Although the endnotes do not create penalties, their content can have compliance consequences. If a practitioner relies solely on a compilation that has failed to incorporate or has incorrectly incorporated an amendment, there is a risk of legal error in advice or in regulatory compliance. That risk is not a statutory penalty arising from the endnotes; it is a professional risk for the user. The endnotes mitigate that risk by requiring the compilation to record commencement details and to flag excluded transitional provisions, but only insofar as the compilers have included accurate entries.

No enforcement body or sanctions detailed. The endnotes do not identify an enforcement agency, enforceable sanctions, or administrative penalties for failing to provide the endnotes themselves. They describe publication practice. Any enforcement of statutory requirements concerning the preparation or publication of legislation would be governed by the parent statutes (for example, the Legislation Act 2003) and public law obligations; this endnotes extract does not set out those enforcement regimes.

Practical implication. From the user perspective, the lack of penalties in the endnotes places the onus on practitioners to verify primary instruments where the endnotes indicate amendments, commencements or editorial flags. The s 15V power is the only described instrument that affects the compilation process; it is a remedial power that allows compilers to address misdescriptions administratively rather than through court enforcement or retrospective sanctions.

The endnotes explicitly reference and interact with the Legislation Act 2003 and the Legislative Instruments Act 2003 through abbreviations and by invoking a specific editorial power. That establishes a narrow but concrete legal relationship between the compilation’s metadata practices and the architecture of federal legislative publication and editing.

Reference to the Legislation Act 2003. The endnotes cite section 15V of the Legislation Act 2003 as the statutory basis for editorial changes to correct misdescribed amendments. The text states: “If, despite the misdescription, the amendment can be given effect as intended, then the misdescribed amendment can be incorporated through an editorial change made under section 15V of the Legislation Act 2003.” That links the compilation editorial practice to a specific provision of the Legislation Act that governs how misdescriptions can be fixed through editorial amendment. The endnotes also use the abbreviation “LA = Legislation Act 2003” in Endnote 2, reinforcing that references to “LA” in the amendment history should be read as shorthand for that Act.

Reference to the Legislative Instruments Act 2003. The abbreviation key includes “LIA = Legislative Instruments Act 2003,” indicating that some of the conventions or cross-references in the compilation may rely on terminology or processes established under the Legislative Instruments Act. However, the endnotes do not cite a particular provision of the LIA; the reference functions as a decoding aid for users who encounter that abbreviation elsewhere in the compilation.

Interaction with amending instruments and register identifiers. The legislation history table in Endnote 3 lists registration codes such as “F2011L02764”, “F2017L01299” and “F2025L01363.” Those codes are identifiers likely used by the Federal Register of Legislation or similar repositories. The endnotes therefore interact with the administrative machinery of legislative registration and publication: they point readers to registration records where the text, commencement notices and any transitional provisions can be located. The endnotes thus operate as a bridge between the compiled instrument and the corpus of amending instruments registered under the relevant publication regimes.

Editorial methodology vis-à-vis primary sources. The endnotes describe an editorial regime (s 15V corrections and “(md not incorp)” labelling) that affects the relationship between the compilation and the primary statutory sources. Where misdescribed amendments are corrected editorially, the compilation will diverge from the literal drafting of the amending instrument to reflect what compilers judge to be the intended effect. Where misdescribed amendments cannot be corrected, the compilation will diverge by omission and will signal that divergence. That interaction raises a question of fidelity: the compilation both relies on and may modify how primary statutory text is presented to readers.

No assertion of primacy or substitution. The endnotes do not assert that the compilation replaces the original instruments or that it has legal primacy over them. Instead, it repeatedly frames the legislation history as providing information about amending laws and notes that commencement and certain transitional provisions “are not included in this compilation.” That wording preserves the conceptual priority of the original instruments and frames the compilation as an annotated secondary presentation.

Practical crosschecks required. Given these interactions, readers should use the endnotes’ registration identifiers and amendment entries to consult the underlying instruments (registered under titles and file codes cited), and where the endnotes indicate editorial correction or non-incorporation, readers should consult the Legislation Act 2003 for the exact scope of s 15V and the original amending text for any unresolved ambiguity.

The endnotes present an amendment history in Endnote 4 and a legislation history in Endnote 3. The amendment history lists provision-level modifications; the legislation history lists the amending instruments with registration and commencement information. The amendment history table supplied contains the following entries:

• Section 2.......... rep. LA 48D
• Section 5.......... am. No. 1 of 2017.
• Section 6.......... am. No. 1 of 2017.
• Section 7.......... am. No. 1 of 2017.
• Schedule 1, item 2.... am. F2025L01363
• Schedule 1, item 3.... am. F2025L01363

These entries show at least two classes of amendment markings. First, provisions marked “am.” denote that they were amended by a named instrument (for example “No. 1 of 2017”), which in turn is recorded in the legislation history. Second, provisions marked “rep.” indicate repeal (for example “Section 2.......... rep. LA 48D”), meaning that section 2 was repealed by an instrument or item identified in the amendment history with the label “LA 48D” , the abbreviation key indicates that “LA” stands for the Legislation Act 2003, but the precise meaning of “48D” is given in the amendment history without further elaboration in the supplied text.

The legislation history in Endnote 3 lists three amending instruments with registration and commencement dates and cross-references:

• Television Licence Area Plan (Mount Gambier/South East) 2011 , Date of registration: 21 December 2011(see F2011L02764); Date of commencement: 2 April 2012; Application, saving or transitional provisions: “-” (the table cell contains a dash).
• Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) , Date of registration: 29 September 2017(see F2017L01299); Date of commencement: 30 September 2017; Application, saving or transitional provisions: “-”.
• Television Licence Area Plans (South Australia) (Consolidation) Variation 2025 (No. 1) , Date of registration: 7 November 2025 (see F2025L01363); Date of commencement: 18 April 2024; Application, saving or transitional provisions: blank cell.

Taken together, the amendment history and legislation history provide a chronological and provision-level map of how the compiled instrument has been altered. A reader relying on the compilation should read these entries in tandem: the legislation history identifies the instruments (with registration identifiers) and key dates; the amendment history maps which internal provisions were amended, added or repealed and by which instrument (as indicated by the shorthand).

Two methodological points the endnotes make about amendments are critical. First, the legislation history “provides information about each law that has amended (or will amend) the compiled law. The information includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation.” That means the legislation history is the place to look for omitted transitional or application rules that may affect how an amendment operates in time. Second, the amendment history warns about misdescribed amendments: if an amendment is misdescribed and cannot be given effect, it will not be incorporated and will be marked “(md not incorp)”. That label will appear in the amendment history at the provision level, signalling to users that the compilation does not reflect that particular change.

Practically, the amendment history entries must be cross-checked against the registration entries and the primary instruments they reference. The file identifiers (for example F2017L01299) are the keys to retrieving the full text of the amending instruments and any commencement notices or transitional provisions not reproduced in the compilation. The amendment history is an index; it does not itself reproduce the operative language of the amending instruments.

The supplied endnotes do not record any litigation history. There are no case names, judicial decisions, appeals or court orders listed in the endnotes extract. The document is confined to editorial, publishing and amendment-tracking matters and does not purport to summarise or reproduce litigation about the compiled instrument.

Absence as information. The omission of litigation information is itself a relevant datum for users: the endnotes should not be read as providing a comprehensive legal history that includes judicial interpretation, challenges to validity, or orders affecting the operation of the instrument. Instead, the endnotes provide a publication and amendment trail. If litigation or judicial commentary potentially affects the meaning or operation of provisions in the compiled instrument, that material will not be captured by these endnotes unless the compilers separately choose to include a litigation note , and no such note is present here.

Implication for practitioners. Practitioners seeking to advise on how courts have interpreted the compiled instrument must therefore search case law databases and not rely on the endnotes for litigation history. Where an amending instrument or a transitional provision has been the subject of a court decision, that decision would not appear here unless the compilers included an express litigation endnote, which this compilation does not.

Editorial and evidential caution. Because the endnotes may be used as an audit trail, the absence of litigation entries underscores the need to check primary sources and case law separately. For example, an amendment listed as commencing on a given date could have been the subject of judicial review, injunction or stayed operation, which would materially affect reliance , such outcomes will not be evident from the endnotes alone.

In short, the endnotes contain no litigation history; users who require judicial context must consult court records and legal databases external to the compilation.

The endnotes expose a number of practical pitfalls and sources of user error. These are not speculative concerns; they follow from the processes and conventions the endnotes themselves describe.

1. Misdescribed amendments and editorial correction. The compilation permits editorial correction of misdescribed amendments under section 15V of the Legislation Act 2003. The “gotcha” is that the compilation may not verbatim reproduce the amending instrument where compilers have corrected a misdescription. If a user assumes literal fidelity between the compilation and the amending text without checking the cited instrument, they may rely on text that reflects an editorial correction rather than the amending instrument’s literal wording. Conversely, if a misdescribed amendment cannot be given effect and is omitted with the label “(md not incorp)”, the compilation will not show the intended amendment at all. In both scenarios, reliance without checking the primary source can mislead.

2. Cryptic shorthand and file identifiers. The abbreviation key contains many short tokens (for example “am”, “rep”, “F2025L01363”, “LA”, “LIA”). Users unfamiliar with the key might misread the amendment history. The file identifiers are necessary to retrieve the full text of amending instruments; failure to use them will slow or prevent verification. The endnotes direct readers to these identifiers but do not explain how or where to retrieve the referenced files , that retrieval step is left to the reader.

3. Omitted commencement/saving/transitional text. The legislation history states it “includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation.” That indicates the compilation may omit transitional or saving provisions. The “gotcha” is that transitional provisions often determine who is bound and when; relying on the compiled text without checking for omitted transitional rules can lead to incorrect conclusions about the timing or applicability of an amendment.

4. Inconsistent or confusing dates. The legislation history table contains an entry with a registration date (7 November 2025) and a commencement date (18 April 2024) that precedes the registration date. The endnotes include these dates as reported; readers must not assume the compilation has resolved any apparent chronological inconsistencies. The “gotcha” is to accept presented dates without cross-checking the primary instruments and any explanatory notes or commencement notices.

5. Limited scope of the endnotes. The endnotes do not record litigation history, ministerial explanatory memoranda, policy papers, or subsidiary instruments beyond those listed. Users who need interpretative or contextual materials must seek them elsewhere. The compilation’s endnotes are a publication tool, not a comprehensive legal research apparatus.

6. Labelling conventions indicate absence, not remedy. The label “(md not incorp)” signals a misdescribed amendment cannot be given effect and thus is not incorporated. The “gotcha” is that this label is an index entry of omission: it does not itself fix substantive gaps or provide a method to implement the intended change. Practitioners must follow the pointer to the primary instrument to determine how the issue should be operationally handled.

7. Assumed universality of the four endnotes. The statement that the four endnotes “are included in every compilation” creates an expectation of uniformity. The practical risk is assuming that those endnotes are exhaustive: they are not a substitute for other possible notes or for consultation of the primary instruments and registers.

8. Reliance risk for professional users. Because the endnotes supply metadata and editorial signals rather than the full content and interpretative apparatus of the primary sources, using the compilation as the sole source for compliance or litigation advice is risky.

Each of these gotchas flows directly from the endnotes’ content and method. They are operational issues for users who rely on the compilation to determine the law’s current form and timing.

The endnotes themselves are procedural and informational; compliance here means correctly using the endnotes to ensure accurate legal and regulatory advice, and following the compilation’s own protocols when preparing or updating a copy of the compiled instrument. The following steps are grounded in the endnotes’ text.

1. Always consult the relevant endnotes. The document begins by stating that Endnotes 1-4 are included in every compilation. Verify that these are present in the copy you are using: Endnote 1 (About the endnotes), Endnote 2 (Abbreviation key), Endnote 3 (Legislation history) and Endnote 4 (Amendment history). These are the minimum metadata items the compilation includes.

2. Use the abbreviation key to decode annotations. Before relying on amendment markings or provision status, consult Endnote 2. The key maps abbreviations in the amendment and legislation histories (for example “am” = amended; “rep” = repealed; “(md not incorp)” = misdescribed amendment cannot be given effect). Treat these abbreviations as authoritative within the compilation.

3. Cross-check amendment entries against the legislation history. The amendment history gives provision-level changes and the legislation history identifies the instruments that effected those changes with registration identifiers and dates. For each amendment you rely on, use the legislation history entry to retrieve the full text of the relevant amending instrument (using the file code cited, for example “F2017L01299”).

4. Verify commencement and transitional provisions in the primary instruments. The endnotes explicitly state that the legislation history includes commencement details and details of application, saving or transitional provisions that are not included in the compilation. That means compliance requires reading the primary amending instrument to find omitted transitional or savings rules that determine real-world application dates or carve-outs.

5. Pay special attention to “(md not incorp)” flags. If an amendment is labelled “(md not incorp)” in the amendment history, the compilation has not incorporated that change. Do not assume the compilation’s omission means the intended change does not exist in law; instead, consult the primary instrument to understand why the amendment is misdescribed and how the law should be read in practice.

6. Where an editorial correction is noted, compare texts. The endnotes permit editorial change under section 15V of the Legislation Act 2003. If you encounter an editorial correction, compare the compilation’s consolidated text with the original amending instrument to confirm the scope and nature of the editorial change and to ensure you understand whether the compiler’s correction aligns with the intended legal effect.

7. Investigate any chronological anomalies. If dates in the legislation history appear inconsistent (for example a commencement date before a registration date, as appears in the table provided), do not assume the compilation has resolved the anomaly. Check the primary instruments, commencement notices and the Federal Register records for definitive dates and explanatory material.

8. Do not treat the compilation as exhaustively authoritative for litigation or policy history. The endnotes do not include litigation history or policy papers. For interpretative issues, judicial treatment, or the legislative intent context, consult case law databases, explanatory memoranda and ministerial materials.

9. Index and archive the cited registration identifiers. When relying on a compilation as part of compliance systems, store and index the registration identifiers (for example F2011L02764) and the full text of the cited amending instruments. That preserves an audit trail and enables verification if questions arise about which version of the law applied at a given time.

10. For publishers or compilers: preserve endnote labelling and make editorial decisions transparent. If you are producing or republishing a compilation, ensure the four endnotes are present, implement the s 15V editorial corrections only where permitted by the Legislation Act 2003, and annotate any non-incorporated misdescribed amendments with “(md not incorp)” so readers can identify gaps.

Following these steps aligns directly with the practices described in the endnotes and reduces the operational risks the endnotes identify. The key compliance theme is verification: the endnotes are an index and editorial log, not a substitute for primary documentation.