Licence Area Plan – Burnie Radio

The document uses a small set of conceptual building blocks that structure how the compilation communicates legal change and drafting anomalies to its users.

• Compilation information: Endnote 1 sets the broad scope. It frames the endnotes as a source of information "about this compilation and the compiled law." That sets the expectation that endnotes are explanatory and reference material tailored to the specific compilation rather than a reproduction of primary documents.

• Legislation history: Endnote 3 is the concept that a compilation will not only show the current text but will also summarise the sequence of amending laws. It explicitly includes three types of detail the compiler will provide: the identity of each amending law, commencement details for those amending instruments, and details of any "application, saving or transitional provisions" that are not printed in the compilation. The inclusion of "or will amend" signals that the compiler may record amending instruments that are not yet in force when the compilation itself is published.

• Amendment history: Endnote 4 brings the concept down to provision level. It promises provision-by-provision annotations showing where a provision has been amended or repealed, and it specifically accounts for misdescribed amendments. The note explains the treatment of misdescribed amendments in two possible ways: one where the compilers can give effect to the legislature’s intended change and therefore incorporate it into the compiled text (marked "(md)"), and a second where the misdescription cannot be given effect, leaving the change unincorporated and marked "(md not incorp)".

• Abbreviation key: Endnote 2 defines a small notation system for endnotes. The populated entries are "ad", "rep", "am" and "rs" with their meanings. This is a compact taxonomy the reader should use to interpret the shorthand used in endnote tables and provision annotations.

• Notation for misdescription: The text sets out a procedural convention for handling misdescribed amendments. The presence of "(md)" or "(md not incorp)" is a key concept because it signals a compiler judgement about whether a misdescribed amendment could be given effect in the compiled text.

These concepts together create a reader workflow: consult the abbreviation key, consult legislation history for instrument-level and commencement details (and for omitted savings and transitional provisions), consult amendment history for provision-level changes and special notations showing compiler treatment of problematic amending provisions.

The Endnotes are aimed at users of a compiled statute and at the professionals who rely on or produce those compilations. The document itself does not impose legal obligations; instead it affects behaviour by shaping what information readers consult and how they interpret it.

Primary affected groups are:

• Legal practitioners and in-house lawyers who read the compiled statute. The compiler tells these users to look to Endnote 3 for "commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation." That affects research practice because users must include endnotes in their due diligence to establish the application and timing of amendments.

• Legislative drafters and parliamentary counsel who prepare amending instruments. Endnote 4 specifically addresses "misdescribed amendment" and sets out how such cases are flagged in the compilation as "(md)" or "(md not incorp)". That will be relevant to anyone monitoring how the drafting of amending instruments is reflected in public-facing compilations.

• Statute compilers, publishers and legal information services. The text defines the conventions compilers should use when producing a compilation, including the abbreviation key (Endnote 2) and the approach to incorporating or flagging misdescribed amendments (Endnote 4). Compilers must decide whether to incorporate a misdescribed amendment, and if they do so they must mark it "(md)". If they cannot give effect to a misdescription, they must mark it "(md not incorp)".

• Compliance officers, accountants and corporate counsel. These users rely on properly annotated compilations to determine the state of the law at particular dates. The explicit note that Endnote 3 will record commencement and transitional provisions "not included in this compilation" warns them to check endnotes to avoid missing out-of-printed but relevant transitional or saving rules.

• Researchers and journalists. The endnotes inform secondary reporting and analysis by indicating where primary instruments or commencement details must be checked. Endnote 3’s promise to record amending laws that "will amend" implies the compilation may note future amendments, which is material for forward-looking reporting.

Less directly affected are courts and tribunals. The Endnotes do not state any binding status, they are a compilation aid. Users who rely on the compilation will bear the risk of any inaccuracy; Endnote 4’s explicit handling of misdescribed amendments recognises this risk and provides a signalling convention. In short, the primary practical effect is to shape research workflows for anyone who consults the compiled law.

The Endnotes document does not create statutory duties or confer rights. Instead it prescribes how the compiler will present certain informational features in the compiled text, and instructs users where to find particular types of information. The text uses operative phrasing such as "provide information" and "sets out abbreviations that may be used," which frames the endnotes as explanatory aids rather than as sources of legal obligations.

Key points about duties and rights that follow directly from the text:

• No new legal duties imposed: Nowhere in the endnotes text is there an instruction creating an obligation on readers, lawyers, private parties, or public officials. The Endnotes describe content and conventions. They do not purport to levy fines, alter substantive obligations under the compiled law, or create private rights.

• Compiler conventions as practical obligations: While not statutory duties, the conventions create practical obligations for compilers and publishers of the compilation. Endnote 2 requires the compiler to "set out abbreviations that may be used in the endnotes." Endnote 4 requires compilers to indicate misdescribed amendments and to add "(md)" if they can give effect to a misdescription or "(md not incorp)" where they cannot. Those are procedural duties for whoever produces the compilation.

• Research duty on users: The text implicitly assigns a due diligence role to users. For example, Endnote 3 promises to include "commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation." That wording functions as a notice that the compiled text may omit certain transitional or saving provisions and that users must consult endnotes to obtain that information. Practically, therefore, users bear a duty to consult the endnotes when determining commencement and transitional operation of amendments.

• Rights of clarity: The inclusion of an abbreviation key and structured legislation and amendment histories confers a right of sorts to readers: a standardised means of interpreting compilation annotations. Endnote 2 is intended to promote consistent reading of shorthand such as "ad", "rep", "am", and "rs". Users have the right to expect those labels to carry the meanings set out in the key within that compilation.

• Treatment of misdescribed amendments: Endnote 4 imposes a rule for labelling. When a misdescription "can be given effect as intended, the amendment is incorporated into the compiled law and the abbreviation '(md)' added." When a misdescription cannot be given effect, the abbreviation "(md not incorp)" is added. That creates a predictable convention that affects users’ expectations.

Summarily, the Endnotes impose procedural duties on compilers about labelling and content, and impose an informational duty on users to consult endnotes for completeness. They do not create or modify substantive legal duties or confer private rights beyond supplying interpretive assistance.

The Endnotes text contains no provisions imposing penalties, sanctions, or a regulatory enforcement regime. It is exclusively explanatory and descriptive about the compilation process and conventions.

Specific observations grounded in the text:

• No criminal, civil or administrative penalties mentioned: The document does not provide any penalty clauses, monetary fines, discretionary powers to impose sanctions, or referral mechanisms to enforcement agencies. It strictly addresses the content and labelling of endnotes and an abbreviation key.

• No enforcement mechanism over compilers provided: Although Endnote 4 prescribes how misdescribed amendments should be treated in the compilation,either incorporated and marked "(md)" or left unincorporated and marked "(md not incorp)",the text does not specify who monitors compliance with that convention, nor does it prescribe consequences for a compiler that fails to follow the convention.

• Practical enforcement through reputational and professional mechanisms only: Because the text does not create penalties, the only likely enforcement pressure on compilers will be market and professional expectations. Publishers of statutory compilations are ordinarily bound by professional standards and user expectations to label and document accurately. The Endnotes create a standard; failure to adhere will produce reputational and practical consequences, not statutory sanctions.

• User risk rather than penalty: The risk to users from inaccurate or incomplete endnotes is implicit. The Endnotes themselves instruct users where to find commencement information and transitional provisions "not included in this compilation." If an endnote is incorrect or omitted, the practical consequence is legal or commercial exposure for users who rely on the compilation. The document makes no provision for remedies or relief in such circumstances.

In short, the Endnotes operate without an enforcement apparatus. Accuracy and adherence to the stated conventions are matters of compiler practice and user caution, not statutory enforcement.

This Endnotes text is meta-legal material; it describes how a statutory compilation will present information about primary law and amending instruments. Its interaction with other laws is therefore procedural and informational rather than substantive. The document explicitly instructs compilers to record aspects of amending instruments that relate to other laws and to indicate when provisions have been repealed "in accordance with a provision of the law."

Concrete interactions stated in the text:

• Recording amending instruments: Endnote 3 "provides information about each law that has amended (or will amend) the compiled law," including "commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation." That means the endnotes will cross-reference other statutes or instruments that change the compiled law and will record their commencement and transitional arrangements. This creates an explicit link between the compiled statute and the body of amending legislation.

• Provision-level amendment history and repeals: Endnote 4 "provides information about the amendments at the provision (generally section or equivalent) level and includes information about any provision of the compiled law that has been repealed in accordance with a provision of the law." This instructs compilers to link the compiled provision to the particular amending law that effected an amendment or repeal, and to note the mechanism under which a repeal or substitution occurred. In practice, that links the compiled text to other statutory instruments and may indicate the interplay between provisions across statutes.

• Treatment of misdescribed amendments: Endnote 4’s policy for "(md)" or "(md not incorp)" interacts with the operation of amending laws when their drafting errors or misdescriptions affect the compilation. The stated approach aligns the compilation with the legislature’s intended change where possible, or with the primary text where incorporation is impossible. This creates a pragmatic interaction between the compiled presentation and the actual wording and legal effect of amending instruments.

• Abbreviation key as cross-compilation standard: Endnote 2 defines abbreviations such as "ad", "rep", "am", "rs". These abbreviations are shorthand for substantive actions taken by other laws (e.g., "rep = repealed"). By standardising these notations, the compilation facilitates cross-referencing across a corpus of statutes and amending instruments.

Limitations on interaction:

• No legal effect claimed for endnotes: The text nowhere asserts that the endnotes alter the legal operation of acts or subordinate instruments. They are presentation and informational devices. Consequently, endnotes should be read as aids to understanding the interrelations among laws rather than as legal instruments themselves.

• Omitted application, saving or transitional provisions: The document specifically acknowledges that some application, saving or transitional provisions may not be printed in the compilation and that details of these will be recorded in Endnote 3. Users must therefore consult the original amending instruments to determine their full interaction with other laws.

Overall, the interaction is a descriptive mapping between the compiled statute and the body of amending legislation, providing cross-references and commencement details but not changing substantive legal relationships.

Endnote 4 is devoted to amendment history and sets out the compiler’s conventions for describing and handling amendments at the provision level. The Endnotes explain two core elements of amendment history: the scope of provision-level annotations and the handling of misdescribed amendments.

Scope and content

• Provision-level annotations: Endnote 4 "provides information about the amendments at the provision (generally section or equivalent) level." That means the compilation will show which sections have been added, amended, repealed, or substituted, usually with an entry against each affected section explaining the amending instrument and the nature and date of the change.

• Repeals in accordance with a provision of the law: Endnote 4 explicitly covers "any provision of the compiled law that has been repealed in accordance with a provision of the law." This indicates that the amendment history will not only list amending instruments but will show the legal mechanism and authority under which a repeal or substitution occurred.

Treatment of misdescribed amendments

• Misdescribed amendment defined and signalled: Endnote 4 recognises that some amending instruments may be misdescribed , that is, the instrument’s text or notation does not accurately describe the amendment intended. The endnote prescribes how compilers should represent these cases in the compilation.

• "(md)" and "(md not incorp)" conventions: The text sets out two possible compiler responses where a misdescribed amendment is encountered. If "despite the misdescription, the amendment can be given effect as intended, the amendment is incorporated into the compiled law and the abbreviation '(md)' added to the details of the amendment included in the amendment history." If a misdescription "cannot be given effect as intended, the abbreviation '(md not incorp)' is added to the details of the amendment included in the amendment history." These labels therefore act as a direct signal in the amendment history to users that a compiler judgement was required and the nature of that judgement.

Relation to Endnote 3 and commencement details

• Link to broader legislative history: Endnote 3 addresses instrument-level history including commencement and transitional provisions not printed in the compilation. Endnote 4 then supplies the granular, provision-level account. Both notes together constitute the compilation’s entire amendment-history apparatus; Endnote 3 tells the reader which instruments to look at and their commencement; Endnote 4 tells the reader how individual sections were changed and whether the compiler has exercised discretion in incorporating or marking misdescribed amendments.

Practical implications for amendment history readers

• Expect explicit labelling where compilers have exercised judgement: The presence of "(md)" or "(md not incorp)" in an amendment history entry is a concrete indicator that the amending instrument had drafting or description issues; the entry will thus signal potential areas where users should consult the original instrument or legislative history.

• Expect cross-references to unprinted transitional or saving provisions: Because Endnote 3 records commencement and any application, saving or transitional provisions "that are not included in this compilation," amendment history entries may refer you to those instrument-level endnotes for full operational detail.

In sum, Endnote 4 sets out the compiler’s method for constructing a provision-level amendment history and for signalling where compiler judgment has been applied.

The Endnotes document does not include any litigation history. There are no case names, citations, or summaries of judicial decisions in the text. The content is purely explanatory about compilation practice and annotation conventions.

Consequences of that absence and what the document does indicate

• No direct reports of judicial treatment: Because the Endnotes contain no reference to litigation, they do not record how courts have interpreted particular provisions, whether any judicial decisions have affected the compiled text, or whether any case law has influenced how amendments should be read or incorporated. Users seeking litigation history must therefore consult other sources.

• Indirect signalling to check primary sources: The Endnotes’ emphasis on recording commencement details and unprinted transitional provisions, and on flagging misdescribed amendments, acts as a reminder to consult primary instruments and any relevant legislative history. In the absence of litigation history in the endnotes, practitioners should verify whether courts have made pronouncements affecting interpretation or operation of provisions whose amendment history or commencement status is unclear.

• Where litigation history would normally appear: In some statutory compilations, endnotes or editorial notes sometimes include references to cases that interpret or affect provisions. This document, however, confines itself to amending and provision history and to an abbreviation key. The absence of litigation history in the endnotes therefore reduces the completeness of the compilation for users who need to understand judicial construction as part of legal research.

Practical steps implied for users

• Do not rely on the compilation for case law: Because the Endnotes do not report litigation history, researchers must consult case law databases, law reports and other secondary sources to assemble the litigation context for any statutory provision.

• Use the amendment and legislation histories as pointers: Where the endnotes flag "(md)" or list commencement and transitional provisions, those flags may identify provisions that have been contested or ambiguously drafted. That can guide further searches for litigation addressing those issues.

In essence, the Endnotes document provides no litigation history. It implicitly instructs users to treat the endnotes as an instrument and amendment guide and to supplement that with separate legal research for judicial treatment where required.

The Endnotes text contains several potential pitfalls that users and compilers need to be alert to. These stem from both the substantive content of the endnotes and from the formatting and limited scope of the provided abbreviation key.

1. Misdescribed amendments and the two-label convention

• What the text says: Endnote 4 explains that misdescribed amendments are either incorporated and labelled "(md)" if they "can be given effect as intended", or labelled "(md not incorp)" if they "cannot be given effect as intended."

• Practical consequence: Where a provision carries either label, the user must investigate what the underlying misdescription was and why the compiler chose to incorporate or not. The label flags a defect in the amending instrument that may bear on statutory interpretation or on reliance.

• Risk: Users who see the compiled text without the labels, or who fail to consult the endnotes, may be misled into thinking the compiled text is an unambiguous reflection of primary law. The "(md)" label does not itself explain the legal effect; it simply signals that an editing judgement was made.

2. Abbreviation key coverage and formatting

• What the text provides: Endnote 2 supplies an HTML table where only four abbreviations are explicitly defined: "ad = added or inserted"; "rep = repealed"; "am = amended"; and "rs = repealed and substituted."

• Practical consequence: Other abbreviations commonly used in statutory compilations may not be present. The key uses the wording "abbreviations that may be used in the endnotes," which implies it is not exhaustive. Users should not assume that the compilation will not use abbreviations outside this list.

• Formatting risk: The HTML table contains numerous empty rows and cells, and a final row showing numeric widths. That formatting could lead to confusion about whether entries are missing or whether the table was truncated. Compilers and users should be cautious in relying on the table’s apparent completeness.

3. "Will amend" language signals prospective amendments

• What the text says: Endnote 3 "provides information about each law that has amended (or will amend) the compiled law."

• Practical consequence: The compilation may record amending instruments that are not yet in force. Users must check commencement details in Endnote 3 to determine whether a recorded instrument is prospective, conditional, or already in force. Relying on an annotation without verifying commencement could produce incorrect legal advice or compliance decisions.

4. Omitted application, saving or transitional provisions

• What the text says: Endnote 3 includes "details of any application, saving or transitional provisions that are not included in this compilation."

• Practical consequence: Transitional or saving provisions may not be printed in the compiled statute itself. Users who do not read the endnotes can miss critical rules that determine when or how amendments apply.

5. No litigation history

• What the text lacks: The endnotes do not contain litigation history or case annotations.

• Practical consequence: Users seeking interpretive guidance or precedent must look beyond the compilation. Particularly where a misdescription is flagged, there may be litigation or parliamentary history that affects the legal position; none of that appears in these endnotes.

6. Limited express guidance on compilers’ decision criteria

• What the text provides: A binary outcome is stated for misdescribed amendments , they are either incorporated or not, with labelling.

• Practical consequence: The document does not set out the detailed principles compilers will follow in deciding whether a misdescription "can be given effect as intended." That creates potential inconsistency across compilations and means users cannot assume a uniform standard without consulting the particular compiler’s methodology.

7. Ambiguity about legal status of the endnotes

• What the text does not state: There is no assertion that the endnotes have legal force or amendment effect.

• Practical consequence: Users must treat the endnotes as guide material only. Where the compilation departs from primary sources, the absence of a stated legal status requires users to confirm from the original instruments.

These gotchas converge on a single operational caution: the endnotes are a helpful roadmap but not a substitute for verifying primary instruments, commencement dates, transitional rules and, where necessary, case law. The labels and abbreviation key are useful signals but not full explanations.

This section translates the endnotes’ content into a practical checklist for compilers, lawyers, compliance officers and researchers who must rely on the compiled statute. The Endnotes themselves prescribe a few explicit conventions; compliance means following those conventions and applying accompanying verification steps.

For compilers and publishers

1. Provide the three endnote types

• Ensure Endnote 1, Endnote 3 and Endnote 4 are present and accurately populated. The compilation should state that the endnotes "provide information about this compilation and the compiled law" (Endnote 1), list amending laws and commencement details (Endnote 3), and provide provision-level amendment history including repeals and misdescription flags (Endnote 4).

2. Publish an abbreviation key

• Include an Abbreviation key as described in Endnote 2. At minimum, define "ad = added or inserted", "rep = repealed", "am = amended", and "rs = repealed and substituted." If the compilation uses additional abbreviations, add them to the key to avoid ambiguity.

3. Apply the "(md)" and "(md not incorp)" conventions

• Where an amending instrument is misdescribed, determine whether the intended amendment "can be given effect." If yes, incorporate the amendment into the compiled text and add "(md)" to the amendment history entry. If it cannot be given effect, do not incorporate and add "(md not incorp)." Record the reason for the decision in internal editorial notes so the choice can be justified to users if queried.

4. Record commencement and transitional provisions

• For each amending instrument, record commencement details and any "application, saving or transitional provisions that are not included in this compilation" in Endnote 3. If you omit the text of such provisions from the printed compilation, provide clear references to where users can find the unprinted provisions.

5. Quality control and provenance

• Maintain provenance records linking each endnote entry to the primary amending instrument, including the gazette or instrument identifier and evidence of commencement. This is essential where "(md)" labels mean an editorial judgement altered the compiled text.

For legal practitioners, compliance officers and researchers

1. Always consult the endnotes

• Treat the endnotes as an integral part of the compilation. Follow the document’s instruction that Endnote 3 contains "commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation." Do not rely solely on the printed text when determining whether an amendment is in force or how it applies.

2. Check for "(md)" or "(md not incorp)" flags

• If you see "(md)" or "(md not incorp)" in the amendment history, inspect the referenced amending instrument to understand the nature of the misdescription and the real-world legal effect. The compilation marks the issue but does not necessarily explain the substantive legal consequences.

3. Cross-check primary sources for accuracy

• Use the endnotes to identify the relevant amending instruments and then check the original texts and official commencement notices. The endnotes are a research tool, not primary authority. This is especially important where the endnotes indicate unprinted transitional provisions.

4. Do not assume completeness

• The Abbreviation key provided is limited. If you encounter annotations or abbreviations not covered by Endnote 2, seek clarification from the publisher or consult the primary instruments. The presence of blank cells and formatting oddities in the provided abbreviation table suggests you should not assume the key is exhaustive.

5. Supplement with case law research

• Because the endnotes do not include litigation history, run separate case-law searches where interpretation risk is material, and particularly where a misdescribed amendment is present or a commencement question is flagged.

6. Document reliance and verification steps

• Where advice or compliance action turns on compiled-text readings, record that you checked the endnotes, examined the relevant amending instruments and verified commencement. The compiler’s marks are useful but a documented verification trail mitigates reliance-risk.

Practical sequence for a user checking a compiled provision

1. Read the compiled provision. Note any annotations or shorthand such as "ad", "am", "rep" or "rs."

2. Consult the Abbreviation key in Endnote 2 to interpret shorthand.

3. Go to Endnote 4 for provision-level amendment history, and note any "(md)" or "(md not incorp)" flags.

4. Go to Endnote 3 for instrument-level detail: identify the amending law, check the commencement date and look for references to application, saving or transitional provisions that may not be printed.

5. Retrieve the primary amending instrument and the official commencement or proclamation details from the government gazette or official legislative register.

6. If interpretation remains contested or risk is high, conduct case law searches for judicial consideration of the provision or the amending instrument.

By following these steps you align practice with the conventions the Endnotes set out and reduce the risk that omissions or misdescriptions will produce a mistaken reliance on the compiled text.