Licence Area Plan – Mudgee Radio

The endnotes rest on several discrete concepts that underpin how compiled legislation is presented to users. Those concepts are defined, used and cross-referenced in the endnotes themselves.

Compilation and compiled law

• The document treats the Licence Area Plan as a "compiled law", meaning the current consolidated form produced by combining the original instrument and subsequent amending instruments. Endnote 1 states the endnotes "provide information about this compilation and the compiled law." The compilation is therefore the product; the endnotes are the metadata about that product.

Endnotes as structured metadata

• Endnote 1-4 form the standard set of metadata in this compilation. Endnote 1 explains their purpose; Endnote 2 supplies an abbreviation key to interpret shorthand across the endnotes; Endnote 3 is a legislation history table listing instruments, registration and commencement data; Endnote 4 is the provision-level amendment history.

Abbreviation key

• The endnotes provide a formal key (Endnote 2) listing shorthand used throughout the amendment history (for example, "am = amended", "ad = added or inserted", "rs = repealed and substituted", "rep = repealed", "F = Federal Register of Legislation", "s = section(s)", "Pt = Part(s)".) That key underpins correct reading of Endnote 4’s cryptic entries.

Legislation history vs amendment history

• Endnote 3 (legislation history) records the amending instruments themselves, with registration references and commencement dates. Endnote 4 (amendment history) records how specific provisions, clauses, schedules and attachments were changed by those instruments. The two operate together: Endnote 3 answers "which amending instruments exist and when did they begin to operate", Endnote 4 answers "what did each instrument do to which clause or schedule."

Misdescribed amendments and editorial remedy

• The endnotes explain how misdescribed amendments are handled. The text defines a misdescribed amendment as one that "does not accurately describe how an amendment is to be made." It directs that "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." If it cannot be given effect, the amendment is not incorporated and "(md not incorp)" is added to the amendment history. This concept links substantive legislative drafting errors with an editorial power (s 15V LA 2003) that permits correction when the intended effect is clear.

Registration and commencement metadata

• Endnote 3 explicitly records registration and commencement data for each amending instrument, and instructs that the legislation history includes information about application, saving and transitional provisions "that are not included in this compilation." That means the compilation may not carry every legal effect of the original instruments; users must consult the original instruments listed.

Provision-level annotation practices

• Endnote 4’s table format shows that entries for particular clauses, schedules and attachments are annotated with shorthand indicating how they were affected (for example, "am. F2023L00408", "rs. var. No.1 of 2008", "rep. F2023L00408", "ad. F2023L00408"). The amendment history also shows that headings and text can be replaced or repealed and that attachments may be added, amended or repealed across different instruments.

Editorial signalling conventions

• The endnotes use specific editorial signals that carry meaning to researchers: "am." means amended, "rs." means repealed and substituted, "rep." means repealed, "ad." means added, and "(md not incorp)" flags a misdescribed amendment that was not able to be incorporated. The abbreviation key formalises those signals so readers can read the amendment history correctly.

These concepts combine to create a system where the compilation is a layered artifact: the text is primary, amendments are layered on top, and the endnotes explain the layering and provide editorial transparency. The endnotes therefore function as an interpretive and technical instrument, not as a source of substantive rule changes themselves.

The endnotes affect a discrete set of actors exposed to, or responsible for, the integrity and use of the Licence Area Plan Mudgee (Radio) compilation. The endnotes themselves are neutral metadata, but their presence, content and editorial signals shape legal research, compliance decisions and administrative record-keeping.

Primary affected groups

• Users of the compilation (lawyers, compliance officers, planners, local government authorities, broadcasters and their advisers). These users rely on compiled texts for a quick view of the current law. The endnotes instruct those users about omission risk (for example, Endnote 3 warns that application, saving and transitional provisions may not be included in the compilation) and about where to find the original amending instruments.

• The licence-holder community and industry participants associated with the Licence Area Plan Mudgee (Radio). The compilation is the publicised consolidated version of the licence area plan and its variations; operators that must comply with the licence area plan’s content are materially affected by whether the compiled text and its amendment history accurately reflect legal obligations, though the endnotes themselves do not create obligations.

• Government drafters and parliamentary counsel or the office responsible for preparing and maintaining the Federal Register of Legislation. The endnotes set the editorial rules this office follows (for example, invoking s 15V of the Legislation Act 2003 for misdescribed amendments), so they constrain, guide and document editorial discretion and workflow.

• Publishers and information services that reproduce the compilation. The abbreviation key and amendment history direct how reproductions should annotate changes and what tags to apply when an amendment could not be incorporated.

• Researchers, journalists and third-party data users. The endnotes provide provenance data (registration numbers and commencement dates) that researchers need to locate original instruments or to verify the state of the law at a particular point in time.

Who "pays" and resource consequences

• The compilation and its endnotes impose administrative costs on the compiling agency (time spent tracking, annotating and making editorial corrections under s 15V) and on professional users who must verify original amending instruments for commencement and transitional details that might not be included in the compiled text. The endnotes explicitly warn that the legislation history "provides information" about each amending law, including commencement details and "details of any application, saving or transitional provisions that are not included in this compilation." Practitioners will typically allocate time to check those originals, so the endnotes channel that compliance cost toward users rather than eliminating it.

• Where a misdescribed amendment has not been capable of incorporation, the endnotes will display "(md not incorp)". That administrative tag can generate transaction costs: parties advising clients may need to obtain and analyse the original instrument to determine the actual legal position and whether the compilation’s consolidated text fully reflects the law.

Decisionmakers and discretion

• The endnotes make explicit that an editorial power exists (s 15V of the Legislation Act 2003) to correct certain misdescribed amendments. That allocates discretion to the statutory editor to decide whether an obviously intended amendment can be implemented editorially. The decisions made under that power affect how users read the compiled law and the degree to which the compilation can be treated as authoritative for routine compliance work.

Geographical and subject-matter scope

• The immediate subject-matter is the Licence Area Plan for Mudgee (Radio). That means the compilation and its endnotes principally affect stakeholders dealing with radio licence geography and associated regulatory requirements in the Mudgee area. The endnotes’ content is specific to that instrument: the legislation history lists the June 1997 instrument and two variations in 2008 and 2023, with distinct registration numbers and commencement dates.

Conclusion on affected parties

The endnotes are targeted at those who rely on compiled legislation for operational or advisory purposes: legal and compliance professionals, industry participants regulated by the licence area plan, and the office responsible for publishing and maintaining the compilation. They create identifiable administrative burdens (verification of original instruments, handling of "(md not incorp)" flags) and allocate editorial discretion to the statutory editor under the Legislation Act 2003.

The endnotes do not themselves create novel statutory duties or rights in the substantive sense that primary legislation or the Licence Area Plan may do. Instead, they set out obligations and powers related to compilation, annotation and editorial correction. The endnotes also identify rights of access to provenance information for users.

Duties and obligations stated in the endnotes

• Duty to disclose amendment provenance. Endnote 3 requires that 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." This creates an editorial duty to disclose those categories of information in the legislation history, even if the full text of some transitional or saving provisions is not incorporated into the body of the compilation.

• Duty to annotate provision-level changes. Endnote 4 contains the "amendment history" and demonstrates the practice of annotating, at clause and schedule level, how each item has been affected (for example, "am. F2023L00408", "rs. var. No.1 of 2008", "rep. F2023L00408", "ad. var. No.1 of 2008"). The compiling office therefore has a duty, evidenced by these endnotes, to maintain a provision-level record.

• Duty to identify misdescribed amendments and record remedial action. The endnotes specify that where an amending instrument misdescribes an amendment, the compiling editor must either incorporate the intended amendment editorially under s 15V of the Legislation Act 2003 when possible, or, if not possible, mark the amendment as "(md not incorp)". That creates a documented duty to either correct or to flag misdescription errors.

Powers conferred or recorded

• Editorial power under section 15V, Legislation Act 2003. The endnotes expressly reference s 15V of the Legislation Act 2003 as the legal basis for making editorial changes to bring misdescribed amendments into the compilation if the intended effect can be given. This is a concrete procedural power to intervene in textual presentation to reflect legislative intent.

• Signalling power via notation. The endnotes confer to the compiling authority the power to attach notational tags such as "am.", "rs.", "rep.", "ad." and "(md not incorp)". These tags are administrative instruments that carry interpretive weight for users.

Rights and entitlements for users

• Right to provenance information. Users have an entitlement (as presented by the endnotes) to see which amending instruments exist, their registration numbers, and commencement dates. Endnote 3 supplies that information for the three named instruments.

• Informational right to provision-level amendment history. Endnote 4 gives users the right to see how specific clauses, schedules and attachments were affected across amendments.

What the endnotes do not claim or grant

• The endnotes do not create substantive legal rights or civil obligations enforceable in court. They are documentation. The endnotes do not purport to change the legal effect of the substantive instrument beyond what the primary instruments effectuate; they only record, interpret or editorially implement amendments within the compilation.

• The endnotes do not set penalties or enforcement mechanisms against private parties for non-compliance with the compiled text: those are the subject of the underlying Licence Area Plan or other regulatory instruments. The endnotes are an interpretive aid, not an enforcement instrument.

Practical duties flowing to users because of the endnotes

• Duty of due diligence. The endnotes make it explicit that users should not rely exclusively on the compiled body where transitional, application or saving provisions could determine legal effect; Endnote 3 says such details are "not included in this compilation." Practitioners therefore must consult the original instruments listed in the legislation history to confirm commencement and transitional treatment, particularly where rights or liabilities depend on timing.

• Duty to notice editorial flags. Where the amendment history includes "(md not incorp)" or indicates an item was "rs." or "rep." the practitioner must interpret those flags as requiring further checking. The endnotes create an informational duty to consult the referenced instruments where the compilation signals uncertainty.

In short, the endnotes document the compiling office’s duties and powers to annotate, correct and present consolidated law, and they create contingent duties on users (principally, to verify original amending instruments and to respond to misdescription flags). The only statutory power explicitly named is section 15V of the Legislation Act 2003 as the basis for some editorial corrections.

The endnotes do not create or specify any criminal, civil or administrative penalties. They are documentary and editorial in character. The content provided expressly focuses on annotation, disclosure, editorial practice and amendment record-keeping. There is no penalties section, no fines, and no enforcement apparatus embedded in these endnotes.

What the endnotes do specify that is relevant to enforcement and legal certainty

• Editorial correction as a remedy to misdescription (s 15V). The endnotes describe an administrative remedy,editorial change under section 15V of the Legislation Act 2003,available when an amending instrument misdescribes its intended amendment but the intended effect can nevertheless be given effect. This is an internal corrective mechanism for the compilers, not a punitive sanction against drafters. The correction restores coherence to the compiled text, but it is an exercise of editorial power rather than an enforcement mechanism against the amending instrument’s author.

• Administrative tagging rather than sanction. Where a misdescribed amendment "cannot be given effect as intended, the amendment is not incorporated and '(md not incorp)' is added to the amendment history." That is a transparency measure and an editorial signal, not a penalty. It flags to users that the amending instrument’s intended effect could not be reflected editorially and that further inquiry into the original instrument is necessary.

• Signalling of repeals, substitutions and additions. The amendment history entries (examples include "am. F2023L00408", "rs. var. No.1 of 2008", "rep. F2023L00408") perform an evidentiary function: they enable an auditor, regulator or court to trace the textual history of provisions. This evidentiary use might inform enforcement actions under the substantive law, but the endnotes themselves do not initiate or adjudicate enforcement.

Enforcement implications for users

• Risk of relying on incomplete compilation. Because Endnote 3 records that the legislation history may include commencement and transitional details "that are not included in this compilation", there is an enforcement risk if a user relies on the compiled text without checking the original amending instruments. If rights, exemptions or obligations hinge on commencement or transitional terms not included in the compilation, a party could face enforcement action under the substantive law despite believing the compiled text showed compliance. The endnotes therefore function as a warning that reliance without checking original instruments carries legal risk.

• No listed remedies for errors in compilation. The endnotes set out the editorial practice but do not specify a remedy for a user who suffers loss because of an erroneous compilation. The endnotes’ public transparency (for example, "(md not incorp)") mitigates some risk by flagging unresolved issues, but the document does not describe compensation, correction timelines, or dispute mechanisms arising from compilation errors.

Institutional enforcement architecture implicit in the endnotes

• The Federal Register of Legislation references (F codes) and registration numbers recorded in Endnote 3 and Endnote 4 identify the primary instruments by reference to the official registry. That registry and the relevant statutory frameworks (Legislation Act 2003, Legislative Instruments Act 2003) provide the institutional architecture supporting the compilation. Enforcement and penalty regimes for substantive non-compliance remain matters for the primary legal instrument and the agencies entrusted with regulatory oversight, not the endnotes.

Summary statement

The endnotes supply editorial powers and administrative signals to maintain and explain the compilation. They do not specify penalties or enforcement measures. The only corrective mechanism described is an editorial one (s 15V Legislation Act 2003) and the only enforcement risk they themselves create is the possibility that a user who fails to check original amending instruments might be exposed to adverse enforcement action under the substantive law.

The endnotes function as a bridge between the compiled instrument and the broader statutory and regulatory framework that governs legislative instruments, publication and amendment. The text explicitly references and interacts with specific legal instruments and administrative systems.

Referenced statutes and administrative instruments

• Legislation Act 2003 (section 15V). The endnotes explicitly identify s 15V of the Legislation Act 2003 as the legal basis for making editorial changes to correct misdescribed amendments. That means the compilation process and the editorial choices made by the compiler are governed by the Legislation Act’s provisions on compilation, editorial powers and formal correction. The endnotes therefore place compilation practice within the statutory framework that controls how legislative instruments are to be presented and amended.

• Legislative Instruments Act 2003 (LIA) and the Federal Register of Legislation conventions. Although the endnotes do not quote specific provisions of the LIA, the abbreviation key includes "LIA = Legislative Instruments Act 2003" and identifies "F = Federal Register of Legislation". The compilation’s references to registration numbers such as "F2023L00408" imply a reliance on the Federal Register’s registration and publication system. The endnotes therefore interact with the administrative systems and statutory regimes that determine instrument registration, publication and retrieval.

• The underlying substantive instrument (Licence Area Plan Mudgee (Radio)) and its amending instruments. Endnote 3 lists named amending instruments including the original June 1997 instrument and two variations (2008 and 2023). The endnotes do not alter the substantive effect of those instruments but record their registration and commencement metadata, and they record, in Endnote 4, provision-level effects such as repeal, substitution and addition. This interaction is one of record: the endnotes show how the compiled text is to be read in light of the amending instruments.

Interplay with commencement, application, saving and transitional provisions

• The endnotes emphasise that the legislation history includes "details of any application, saving or transitional provisions that are not included in this compilation." That instructs users that some legal effects generated by the primary and amending instruments may not be captured by the compiled text and that these aspects may require consulting the original instruments listed in Endnote 3. Practically, the compilation interacts with the rest of the statutory framework by being a distilled public record rather than a complete repository of every legal effect.

Editorial practice and statutory amendment rules

• The endnotes’ description of misdescribed amendments shows a direct interaction between drafting errors in primary/amending instruments and the editorial corrective power conferred under the Legislation Act 2003. The editorial correction acts as an interaction point where the administrative practice of publishing consolidated law meets statutory rules about formal amendment. The endnotes therefore function as the procedural interface for implementing that interaction.

Evidence and administrative record-keeping

• The endnotes reference the Federal Register of Legislation ("F") registration numbers and dates for each amending instrument in Endnote 3. That creates an evidentiary trail: researchers and decision-makers can follow the registration identifier to the published instrument on the Federal Register and read its full text, including any commencement and transitional provisions. The endnotes thus interact with the administrative evidence record used to prove the existence and terms of amending instruments.

Limitations and non-interaction

• The endnotes do not change substantive law and therefore do not directly interact with substantive enforcement provisions in the instrument they annotate. They are a meta-layer. Any obligations, penalties or rights that exist are derived from the Licence Area Plan and its amending instruments themselves; the endnotes simply document and annotate.

In practice, then, the endnotes are an administrative node in the network of legislation management: they operate under the Legislation Act 2003 editorial powers, they make use of Federal Register registration identifiers for traceability, and they direct users to original instruments for aspects that cannot be included in the compilation, such as certain application, saving and transitional provisions.

Endnote 4 is the amendment history and it records provision-level editorial actions for the Licence Area Plan Mudgee (Radio). The amendment history is presented as a table and lists how specific parts of the instrument were affected by later instruments, particularly by Variation No.1 of 2008 and the 2023 variation registered F2023L00408. The amendment history entries use the abbreviations defined in Endnote 2; the table entries repeatedly cite "am. F2023L00408", "rs. var. No.1 of 2008", "rep. F2023L00408", "ad. var. No.1 of 2008", and other shorthand.

Key recorded changes (as expressed in the amendment history)

• Instrument-level annotation. The amendment history shows an entry that the document was "am. F2023L00408". That indicates that the 2023 instrument (registration F2023L00408) amended aspects of the compiled law.

• Headings before clauses. The table records "Headings before clauses" with the annotation "am. F2023L00408", indicating the 2023 instrument amended headings prior to clauses.

• Clauses (1)-(6) and subsequent text. The amendment history entries for "Clause (1)" through "Clause (6)" show a mixture of annotations: for Clause (1),"am. var. No.1 of 2008, rs. F2023L00408"; for Clause (2),"am. var. No.1 of 2008, rs. F2023L00408"; for Clause (3),"am. var. No.1 of 2008, rep. F2023L00408"; for Clause (4),"am. var. No.1 of 2008, am. F2023L00408"; for Clause (5),"ad. var. No.1 of 2008, am. F2023L00408"; for Clause (6),"ad. var. No 1 of 2008, rs. F2023L00408". There is also a line "Text after Clause (6)" annotated "rep. F2023L00408."

• Schedules and attachments. The amendment history records multiple changes to schedules and attachments. For example:

  • "Schedules" heading and text annotated "rep. var. No.1 of 2008".
  • "Schedule One" annotated "rs. var. No.1 of 2008, rs. F2023L00408".
  • "Schedule Two" annotated "rep. F2023L00408".
  • "Schedule Three" annotated "rs. F2023L00408".
  • "Schedule Four" annotated "ad. var. No.1 of 2008, am. F2023L00408".
  • Various "Attachment 1.1" through "Attachment 4.3" lines with annotations such as "rs. var. No.1 of 2008, am. F2023L00408", "am. F2023L00408", "rep. var. No.1 of 2008, ad. F2023L00408", "rep. var. No.1 of 2008, rs. F2023L00408", and many "ad." or "am." entries.

• Repetitive pattern of actions. The entries show a consistent pattern: Variation No.1 of 2008 effected a set of changes; the 2023 instrument F2023L00408 then further amended, repealed, substituted or added text and attachments. The amendment history therefore records a sequential layering of change: original instrument (1997), variation 2008 changing many clauses and schedules, and 2023 changes that sometimes replaced or repealed the 2008 changes.

Editorial signal examples in the amendment history

• "am." entries indicate text was amended by the identifying instrument. Example: numerous clauses and attachments are marked "am. F2023L00408" or "am. var. No.1 of 2008".

• "rs." entries indicate repeal and substitution. Several items show "rs. var. No.1 of 2008, rs. F2023L00408", indicating that a clause or schedule was repealed and substituted first by the 2008 variation and later by the 2023 instrument.

• "rep." entries indicate repeal. For example, Clause (3) has "rep. F2023L00408", and "Text after Clause (6)" is marked "rep. F2023L00408".

• "ad." entries indicate addition or insertion. The amendment history shows "ad. var. No.1 of 2008" and "ad. F2023L00408" for certain clauses and attachments, indicating new material was added by the 2008 or 2023 instruments.

• Mixed annotations. Some entries show that an item was added by one instrument and later amended by another (for example, "ad. var. No.1 of 2008, am. F2023L00408"). That indicates iterative change where a 2008 addition was later amended in 2023.

Use of "(md not incorp)"

• Endnote 4 also explains the handling of misdescribed amendments: if a misdescription can be given effect, the editorial change is made under s 15V Legislation Act 2003; if not, the amendment is not incorporated and "(md not incorp)" is added. The amendment history table itself does not display a conspicuous "(md not incorp)" entry in the excerpt, but the rule is stated in the endnote. Practitioners must therefore check for that tag in the full amendment history for any provision where a misdescription occurred.

Implications for reading the compiled law

• The amendment history makes it technically possible to trace, at clause, schedule and attachment level, the successive amending steps that led to the current compiled text. However, Endnote 3 cautions that application, saving and transitional provisions may not be included in the compilation, so the amendment history alone may not be sufficient to reconstruct the full legal implications without consulting the original instruments cited by registration number.

• The dense and repetitive entries suggest that schedules and attachments have been heavily reworked across the 2008 and 2023 instruments. Users needing authoritative current content for a particular schedule or attachment should consult the text of the instrument responsible for the most recent annotation in the amendment history (for example, F2023L00408 for items marked "am. F2023L00408").

In sum, Endnote 4 provides the granular record of textual change that a practitioner needs to determine which instrument changed what. The amendment history repeatedly records that the 2008 variation and the 2023 instrument effected a broad set of amendments, replacements and repeals across clauses, schedules and attachments.

The endnotes provided contain no entries or references to litigation concerning the Licence Area Plan Mudgee (Radio) or the compilation. There is no "Litigation history" endnote, no court citations, and no mention of judicial proceedings in the text presented. The compilation’s endnotes are limited to editorial, amendment and registration metadata.

What the absence of litigation references implies for practitioners

• No recorded cases in the compilation’s endnotes. Because the endnotes do not record judicial decisions, there is no compilation-level evidence here that any dispute about the plan’s content, interpretation, validity or application has been judicially resolved. This absence in the endnotes does not prove there was no litigation, but it does mean the endnotes do not provide guidance on disputes or case law.

• If litigation status matters, consult other sources. Practitioners needing to know whether the Licence Area Plan or an amending instrument has been subject to legal challenge must search court databases, jurisdictional registries, news archives and legal reporting services. The compilation’s endnotes do not nullify or substitute for that research.

• Be alert to judicial treatment of misdescribed amendments. While the endnotes describe an administrative mechanism for dealing with misdescribed amendments (editorial correction under s 15V), the compilation does not report whether courts have considered or approved that editorial practice in particular disputes. If a party plans litigation that hinges on whether an editorial correction properly reflects legislative intent, the absence of litigation references in the endnotes means this question is unresolved by the compilation itself.

Contextual note about administrative vs judicial correction

• The endnotes set out an administrative route for correcting misdescribed amendments (s 15V Legislation Act 2003), but whether that administrative correction would be decisive in litigation is a matter for the courts. The endnotes do not provide any commentary or record of judicial acceptance or rejection of such corrections.

In short, the endnotes contain no litigation history. Where litigation history is a material consideration for advising clients or assessing legal risk, the endnotes point to the need for separate, discipline-specific litigation research.

The endnotes flag several technical traps and practical risks that a practitioner must be alert to. These "gotchas" derive from the endnotes’ own warnings, the amendment history’s dense shorthand, and the way compilations can omit material that is legally significant.

1. Misdescribed amendments and the "(md not incorp)" tag

• A misdescribed amendment is one that "does not accurately describe how an amendment is to be made." The endnotes permit an editorial correction under s 15V if the intended effect can be given effect. If not, the amendment is left out of the compilation and "(md not incorp)" is added to the amendment history. The practical trap: a practitioner might assume an amendment was incorporated into the consolidated text when it has not been. Always search the amendment history for "(md not incorp)" and consult the original amending instrument for the authoritative text.

2. Omitted commencement, application, saving and transitional provisions

• Endnote 3 explicitly warns that the legislation history "provides information … including commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation." The gotcha here is timing: a provision that appears to apply in the compiled text may have had a deferred commencement or a transitional arrangement that limits its current effect. Check the original instruments listed in the legislation history for the full legal effect, especially where regulatory obligations or liabilities depend on timing.

3. Abbreviation-based ambiguity

• The amendment history uses compact abbreviations; misreading "rs.", "rep.", "am." or "ad." can lead to incorrect conclusions about whether a provision was substituted, repealed or merely amended. Use Endnote 2’s abbreviation key to decode entries. For example, "rs." means "repealed and substituted", a materially different action from "am." which simply amends text.

4. Multiple-amendment layering

• The table shows iterative changes where a provision may have been added by one instrument and then amended or repealed by another. For example, several items show "ad. var. No.1 of 2008, am. F2023L00408." Practitioners must trace the chain of amendments through both the 2008 variation and the 2023 instrument to understand the current law.

5. Schedule and attachment volatility

• The amendment history records substantial change to schedules and attachments (for example, Schedule One: "rs. var. No.1 of 2008, rs. F2023L00408"; Attachment entries show add/amend/repeal actions). Schedules and attachments frequently contain technical data (maps, coordinates, tables) crucial to compliance. The gotcha: a practitioner might rely on an attachment in the compiled text that was later replaced or repealed; always confirm the status of attachments via the amendment history and the original instruments.

6. Registration and reference confusion

• The legislation history lists registration identifiers (for example, "16/07/1997F2005B00622", "02/09/2008F2008L03234", "03/04/2023F2023L00408"). Errors in transcribing or searching these identifiers can lead to retrieving the wrong instrument. Always copy registration numbers exactly as given in the endnotes and verify against the Federal Register of Legislation.

7. Editorial corrections vs substantive intent

• The editor’s power under s 15V is invoked where a misdescribed amendment can be given effect. But the boundary between "can be given effect" and "cannot be given effect" is sometimes judgemental. The gotcha: an editorial correction could be made that an interested party considers reflects an editorial policy choice rather than legislative intent. Where the precise legal effect is material, obtain copies of the original instrument and, if necessary, advice on the likely judicial treatment of editorial corrections.

8. Silence on litigation

• The absence of litigation references in the endnotes is not proof of absence of judicial treatment. If the legal status of a clause or amendment is contested in practice, the endnotes will not necessarily record it. Do not treat silence as clearance of legal risk.

9. Differences between "amended" and "repealed and substituted"

• Substitution can change structure and meaning more substantially than amendment. The amendment history marks substitutions ("rs.") that may alter cross-references and internal numbering. Verify any cross-references in the compiled text against the substitution instrument to ensure internal coherence.

10. Expectation management for clients

• Clients may assume the compilation is a complete, authoritative source. The gotcha is expectation mismatch: the endnotes exist precisely because the compilation may be incomplete in critical respects. Use the endnotes to qualify client advice and build checking steps into workflows.

In practice these gotchas translate into concrete steps: check for "(md not incorp)", verify commencement and transitional provisions in the original instruments, confirm the status of schedules and attachments, and do not rely on the compilation alone where exact legal effect matters.

If you are advising a client or maintaining regulatory compliance with reference to the Licence Area Plan Mudgee (Radio) compilation, the endnotes prescribe a practical workflow and a set of documentation checks. The endnotes themselves do not impose compliance obligations under the substantive plan, but they do set out what must be done to rely on the compiled text safely.

Step 1 , Treat the endnotes as mandatory research checkpoints

• Read Endnotes 1-4. Endnote 1 explains the role of the endnotes. Endnote 2 decodes the abbreviation key. Endnote 3 lists amending instruments and their commencement dates. Endnote 4 gives the provision-level amendment history. As the endnotes state, the legislation history provides "information about each law that has amended (or will amend) the compiled law." Do not skip these endnotes when the legal effect of a provision matters.

Step 2 , Verify the provenance identifiers and obtain original instruments

• Use the registration numbers listed in Endnote 3 (for example, 16/07/1997F2005B00622; 02/09/2008F2008L03234; 03/04/2023F2023L00408) to retrieve the original instruments from the Federal Register of Legislation. Confirm commencement dates listed in the endnotes against the original instruments and note any application, saving or transitional provisions not incorporated in the compilation.

Step 3 , Trace the provision-level history for any clause, schedule or attachment of interest

• Consult Endnote 4 for the clause or attachment you need to rely on. If the amendment history shows multiple actions (for example, "ad. var. No.1 of 2008, am. F2023L00408"), obtain the amending instruments in the sequence recorded and read the relevant provisions in full to confirm how the text should be read now.

Step 4 , Check for "(md not incorp)" and editorial corrections

• Look for the explicit "(md not incorp)" tag in the amendment history for any provision you rely on. If present, the compilation has not incorporated the misdescribed amendment. The endnotes state that if the misdescription "cannot be given effect as intended, the amendment is not incorporated and '(md not incorp)' is added." In such cases you must treat the original amending instrument as the primary source for what was attempted and consider contacting the office that maintains the Federal Register if ambiguity persists.

Step 5 , Investigate commencement and transitional provisions that may affect enforceability

• The endnotes warn that application, saving and transitional provisions may not be included in the compilation. Those provisions frequently determine whether and how the amendments apply to particular persons or activities. Read original instruments for any conditions or staged commencements that might limit immediate effect.

Step 6 , Verify attachments and schedules for technical compliance

• Many regulatory obligations in licence area plans depend on the text of schedules and attachments (for example, maps, coordinates, technical parameters). Endnote 4 records numerous changes to Schedules One-Four and Attachments 1.1-4.3. For compliance purposes, obtain and compare the most recent versions of those attachments in the amending instruments.

Step 7 , Maintain version control and record searches

• Record the date you accessed the compilation and the original instruments. Keep copies of the Federal Register pages for the amending instruments and any relevant gazette notices. This reduces the risk of later disputes over whether a provision applied at a relevant time.

Step 8 , Where ambiguity affects legal rights, seek formal clarification

• If an editor’s correction under s 15V is relied on in the compilation and the legal effect is material to client decision-making, consider seeking formal clarification from the agency responsible for the instrument or professional legal advice. The endnotes state the editorial power exists, but do not provide interpretive guidance on edge cases.

Step 9 , Advise clients about risk and reliance

• Explain to clients that compiled texts are convenient but not infallible: the endnotes exist because details such as commencement and transitional provisions may be omitted or because misdescribed amendments require editorial correction or flagging. Build into client instructions a certainty check: if action depends on a provision, verify the original instrument and the amendment history before relying.

Step 10 , For publishers and compliance officers: implement automated checks

• If you are a publisher or maintain compliance systems that draw on the compiled text, implement automated checks to flag any items annotated "rep.", "rs.", "ad.", or "(md not incorp)". Where a compiled attachment or schedule is replaced, ensure systems refresh those items from the official Federal Register source, not cached compiled text.

Closing operational note

The endnotes are an operational tool to ensure legal accuracy and transparency in the presentation of the Licence Area Plan Mudgee (Radio). Complying with the guidance they provide requires an attentive, document-driven research workflow: decode abbreviations, check the amendment history, retrieve original amending instruments via the Federal Register registration numbers, confirm commencement and transitional provisions, and treat "(md not incorp)" as a red flag requiring further inquiry. Following these steps will align professional practice with the processes and limitations the endnotes themselves describe.