Television Licence Area Plan (Brisbane) 2012

The compilation’s endnotes rely on a small set of concepts and conventions that determine how the compilation records and communicates changes to the underlying instrument. Those main concepts are stated across the four endnotes and can be summarised as follows.

Endnote 1 defines the scope of the endnotes: they are information about the compilation and the compiled law. This frames the endnotes as documentary aids rather than substantive provisions. The explanatory statement is brief and categorical: “The endnotes provide information about this compilation and the compiled law.” That is the baseline concept that anchors the rest of the material.

Endnote 2 provides an abbreviation key, which is a simple controlled-vocabulary device for marking how provisions have been treated. The listed abbreviations include “ad = added or inserted”, “am = amended”, and “rep. = repealed”. A typographical anomaly appears in the supplied text where “rep. = repealedrs. = repealed and substituted” appears without a clear separator. The key is used elsewhere in the amendment history entries to convey the character of changes to provisions, for example whether a section has been amended or repealed and substituted.

Endnote 3 is the legislative-history concept. It organises metadata about each amending law or instrument that affects the compiled law. The table columns are labelled “Title”, “Date of FRLI registration”, “Date of commencement”, and “Application, saving or transitional provisions”. The entries in the table record instrument titles, registration identifiers (for example FRLI file numbers like “F2012L02495”), and commencement dates. For the entries shown, the “Application, saving or transitional provisions” column contains a dash for each row, which the compilation uses to indicate no additional application, saving or transitional provisions are recorded in those lines of the table. The legislative-history concept thereby creates a chronological and documentary trail for the instruments that have altered the compiled law.

Endnote 4 is the amendment-history concept. It lists individual provisions of the compiled law and records how those provisions were affected by amendments, using the abbreviations from Endnote 2 and the “(md)” notation explained in the endnote itself for misdescribed amendments. The amendment-history table contains rows such as “Section 5 am. No. 1 of 2017”, “Section 6 am. No. 1 of 2017”, and more complex entries for items in schedules and multiple amendments across different years. Endnote 4 also contains explanatory material on misdescribed amendments, clarifying when the editor has incorporated a misdescription and when a misdescription cannot be given effect.

Taken together, these concepts establish an editorial architecture: abbreviations to indicate amendment type, a legislative-history trail to show when and how instruments were registered and commenced, and an amendment-history index to map specific changes to provision-level identifiers. The endnotes do not present operational rules or obligations; instead they provide a taxonomy and provenance record for readers who need to trace the lifecycle of the compiled law.

The endnotes are primarily directed at users of the compilation and those who rely on the compilation for legal or administrative work. The text itself does not impose legal obligations on particular external parties; however the practical effect of the endnotes affects identifiable user groups in predictable ways, as the endnotes record the documentary trail those users rely on.

First, legal practitioners and researchers who use the compilation to identify the current form of the instrument are affected. Endnote 3’s legislative-history table supplies registration and commencement dates and a place to flag application, saving and transitional provisions not printed in the compilation. Researchers consulting the compilation will use those entries to locate the amending instruments on FRLI via the file references given, for example “see F2012L02495” and “see F2013L01905”. Endnote 4’s amendment-history entries indicate which sections and schedule items have been amended and by which instrument, which is material for anyone reconstructing the statutory text or tracing the amendment trail.

Second, publishers and compilers who prepare consolidated texts are affected because the endnotes set out the editorial conventions and the specific amendments recorded. The abbreviation key (Endnote 2) and the misdescription protocol (Endnote 4) directly govern how a publisher should interpret amendment notations within the compilation. A person maintaining an authorised compilation or an internal legal database will rely on the endnotes to know when to flag potential misdescriptions with “(md)” or “(md not incorp)”.

Third, administrative officers and policy teams responsible for managing the underlying statutory instruments are affected insofar as the endnotes provide a visible public record of amendment activity. The legislative-history table records FRLI registration dates and commencement dates, which administrative officers may use as public confirmation of when an instrument was formally registered or when a particular variation commenced operation. The endnotes therefore perform a bookkeeping and accountability function for the administrators who are responsible for registering and publishing amending instruments.

Fourth, stakeholders whose rights or obligations derive from the primary instrument will be indirectly affected because the endnotes guide users to the authoritative amending instruments and to any application or transitional provisions that the compilation leaves unprinted. For example, the titles listed in Endnote 3 are specific to the Television Licence Area Plan (Brisbane) and its variations. Although the endnotes do not create substantive rights or duties, they affect any party that needs clarity about the instrument’s amendment history, such as licensees, broadcasters, or compliance advisers who must confirm commencement dates or the applicability of particular variations.

Finally, readers who care about legal certainty and provenance, including journalists and compliance professionals, are affected by the presence or absence of certain metadata. The endnotes’ omission of application, saving or transitional details in the rows shown, and the presence of “(md)” notations in the amendment history, are practical signals to those users that additional verification against original instruments may be necessary.

All of the above follows from the endnotes themselves: Endnote 1’s statement of purpose, Endnote 2’s abbreviation key, Endnote 3’s legislative-history table and Endnote 4’s amendment-history table and explanatory notes.

The endnotes do not, on their face, create legal duties or rights in the sense of operative statutory obligations enforceable by sanction. Instead, they impose and confer roles of information provision, editorial marking and disclosure for the benefit of users of the compilation. The key duties and rights that flow from the endnotes are therefore documentary and procedural rather than prescriptive.

Duty to disclose compilation metadata, derived from Endnote 1: The endnotes state that they provide information about the compilation and the compiled law. That establishes a documentary duty for the compiler or publisher to supply users with the information listed in Endnotes 2-4. Practically, this duty means the compiler must include an abbreviation key, a legislative-history table, and an amendment-history table where appropriate. The endnotes themselves constitute the record of that duty in the current compilation.

Duty to mark amendments using established abbreviations, derived from Endnote 2: The abbreviation key binds the compilation to a set of labelling conventions such as “ad = added or inserted”, “am = amended” and “rep. = repealed”. Those abbreviations are the agreed shorthand that the compilation uses to indicate how a provision has changed. The duty for compilers is to use those keys consistently and to make the meaning of the keys available to users.

Duty to record registration and commencement metadata, derived from Endnote 3: The legislative-history table requires recording the title of the amending instrument, the FRLI registration date, the commencement date and any application, saving or transitional provisions not printed in the compilation. Where the table shows a dash for the latter column, the compilation is indicating that, for that row, nothing additional is recorded. The duty here is one of accurate metadata recording, as the table’s entries are the primary route for users to locate amending instruments and verify commencement.

Duty to annotate or flag misdescribed amendments, derived from Endnote 4: Endnote 4 sets out the treatment of misdescribed amendments, including the use of “(md)” when a misdescription has nevertheless been incorporated into the compilation and “(md not incorp)” when it cannot be given effect. This creates a duty for the compiler to apply those flags where appropriate and to document whether the misdescription was carried into the compilation or not.

Rights of the user to provenance and verification, implicit across Endnotes 1-4: Users of the compilation have the de facto right to be informed about the amendment trail. The tables in Endnotes 3 and 4, and the abbreviation key in Endnote 2, function as the means for users to verify when changes occurred and what instruments effected those changes. That informational right is practical rather than proprietary: the compilation supplies FRLI identifiers and commencement dates to enable independent verification.

Absent duties and rights: The endnotes do not purport to grant statutory entitlements or create sanction-backed obligations. They are not written as operative sections imposing compliance requirements on external actors. There are no penalty clauses or enforcement mechanisms in the endnotes themselves. Any enforcement or legal duty arising from the underlying statute must be sought in the operative text of the primary instrument rather than in the endnotes.

In short, the “duties” are editorial duties incumbent on the compiler or publisher to record and flag amendments and registrations accurately, and the “rights” are the users’ entitlement to the provenance and metadata the compilation provides. These conclusions flow from the endnotes’ stated purposes and the contents of the tables included in Endnotes 2-4.

The supplied endnotes contain no penalty provisions and no enforcement mechanisms. They are explicitly documentary in purpose, as Endnote 1 states: “The endnotes provide information about this compilation and the compiled law.” That formulation frames the endnotes as an informational appendage to a consolidated text rather than as a locus of enforceable obligations.

The endnotes record metadata about amending instruments, such as registration dates, commencement dates and the fact of amendments to particular provisions, but they do not set out sanctions for non-compliance with any substantive legal requirement. Endnote 3’s legislative-history table lists titles, FRLI registration identifiers and commencement dates, and an “Application, saving or transitional provisions” column; in the provided rows that column contains a dash, indicating no such applications are listed there. Endnote 4’s amendment-history table catalogues which provisions were amended and by which instrument, but it offers no language that would create offences, fines or administrative penalties.

Because the endnotes do not create penalties, enforcement considerations for practitioners and administrators are limited to procedural accuracy and record-keeping. The compilation’s publisher or editor has a practical incentive to ensure the endnotes correctly reflect the state of the law, because errors in the endnotes can mislead users about commencement dates or the applicability of amendments. That incentive is professional rather than statutory. Endnote 4’s discussion of misdescribed amendments and the use of “(md)” and “(md not incorp)” is an internal control that addresses editorial risk: it instructs readers how to interpret entries where the amending instrument’s description in parliamentary or legislative drafting sources was defective. This is a quality-control mechanism, not an enforcement sanction.

For users seeking to enforce substantive provisions of the underlying statutory instrument, the endnotes are a starting point for locating the operative amending instruments and for identifying commencement dates; enforcement of substantive obligations or pursuit of remedies must be pursued under the primary legislation or associated regulatory instruments, not via the endnotes. The endnotes facilitate verification by giving FRLI file references (for example “see F2012L02495”) and by listing which sections and schedule items were affected, but they do not alter or enforce the law.

In practice, the absence of penalty provisions in the endnotes means that compliance risk lies in misinterpreting or relying on incomplete endnote information. Therefore a practical enforcement-related risk for users is that a mistaken reading of the endnotes could lead to a false view about when a substantive obligation commenced or whether a variation applies. The endnotes mitigate that risk to some extent by listing FRLI registration identifiers and by using flags for misdescribed amendments, but they do not themselves provide enforcement remedies or penalties.

The endnotes function as a cross-referencing and provenance tool, and their entire raison d’être is to document interactions between the compiled instrument and other legislative and regulatory instruments. Endnote 3 lists the titles of amending instruments and records FRLI registration file numbers and commencement dates. This is the primary structural mechanism by which the compilation captures legal interactions.

The legislative-history table in Endnote 3 identifies instruments that have modified the Television Licence Area Plan (Brisbane) 2012 and related variations. The titles listed include “Television Licence Area Plan (Brisbane) 2012”, “Television Licence Area Plan (Brisbane) Variation 2013”, “Variation 2014”, “Variation 2015 (No. 1)”, and “Variation 2016 (No. 1)”. It also lists a consequential instrument in 2017 titled “Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)”. By naming those amending instruments and recording FRLI registration numbers for some items, the endnotes provide the documentary linkages that show which other instruments affect the compiled law and when they were formally registered.

Endnote 3’s “Date of commencement” column is the mechanism that records temporal interactions between statutes. Commencement dates are crucial because they determine when amendments take legal effect and therefore how the compiled instrument and other laws interact over time. For example, the 2012 Plan is shown as commencing on 29 May 2013, whereas subsequent variations have later commencement dates. Where an amending instrument contains application, saving or transitional provisions, Endnote 3 is the place the compilation will flag them; the endnote explicitly states it provides information about such provisions that are not included in the compilation’s main body. That is the mechanism by which the compilation acknowledges that the compiled text may omit transitional rules that still govern how numbered amendments interact with existing rights and obligations.

Endnote 4’s amendment history maps the provision-level interactions. It records, for example, that “Section 5” and “Section 6” and “Section 7” were amended by “No. 1 of 2017”, and that various schedule items and clauses were amended across 2013-2016. That mapping shows precisely which parts of the underlying instrument changed because of other identified instruments. The amendment-history table is thus the interface between provision-level changes and the named amending laws.

The endnotes also supply editorial rules for dealing with misdescribed amendments. Endnote 4 explains when an amendment that was misdescribed in source materials can nevertheless “be given effect as intended”, in which case the compilation adds the abbreviation “(md)” to the amendment entry, and when a misdescription “cannot be given effect as intended”, in which case the compilation records “(md not incorp)”. This editorial convention affects how the compilation reconciles drafting or publication errors in amending laws, and therefore affects how users interpret interactions where the amending instrument’s description is defective.

The endnotes do not, however, substitute for consultation of the primary amending instruments where interactions may be complex. The compilation’s tables provide pointers to FRLI registration numbers and commencement dates, but they do not reproduce application, saving or transitional provisions that might be the decisive element in how the compiled instrument interacts with other laws. The “Application, saving or transitional provisions” column in Endnote 3 is explicitly the place where such details would be flagged if they are not printed in the compilation, which is an important caveat for users reconstructing the legal effect of multiple instruments.

In summary, the endnotes’ interaction mechanisms are metadata-based. They connect the compiled text to its amending instruments by title, registration identifier, commencement date and amendment mapping; they signal the existence of application, saving and transitional provisions not printed in the compilation; and they apply editorial flags for misdescribed amendments. All these mechanisms are documented in the endnotes themselves.

Endnote 4 contains the compilation’s amendment-history index and a short explanation of how misdescribed amendments are treated. The amendment-history table in the supplied text lists specific provisions of the compiled law and states how each was affected. The entries included in the supplied excerpt are:

• Section 5: amended by “No. 1 of 2017” (recorded as “am. No. 1 of 2017”).
• Section 6: amended by “No. 1 of 2017” (recorded as “am. No. 1 of 2017”).
• Section 7: amended by “No. 1 of 2017” (recorded as “am. No. 1 of 2017”).
• Schedule 1: listed as affected; the table does not show a simple single-line amendment entry but indicates changes to multiple schedule clauses across several instruments.
• A complex row listing multiple items: “Clause 1Clause 2Clause 3Schedule 2Clause 1Clause 2Schedule 3Clause 1Clause 2Attachment 1” is recorded as having been amended by a set of instruments across 2013-2016, with the annotation “am. No .1 of 2014am. No .1 of 2014am. No .1 of 2014am. No .1 of 2014am. No .1 of 2014am. No .1 of 2014am. No. 1 of 2013; am. No .1 of 2014; am. No. 1 of 2015; am. No. 1 of 2016rs. No .1 of 2014” in the supplied text. This combined entry appears to record multiple, possibly overlapping amendments to various schedule clauses and an attachment across several variation instruments.

The amendment-history endnote also carries an explanatory paragraph on misdescribed amendments. It explains that the amendment history 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.” The note goes on to explain the editorial treatment of misdescribed amendments: if a misdescription nonetheless allows the intended amendment to be given effect, the compilation puts the abbreviation “(md)” in the amendment history entry; if a misdescription cannot be given effect, the compilation marks the entry “(md not incorp)”.

The amendment-history table as supplied contains typographical and formatting irregularities in the combined row mentioned above, and several entries compress multiple amendment histories into a single table cell. That pattern indicates that the compilation covers a number of variation instruments across multiple years and that the amendment history for schedule and clause items is aggregated in the printed endnote, rather than individually itemised in the supplied excerpt.

Practical implications for users include the need to consult the named amending instruments for text-level details. The amendment-history table identifies which provisions were affected and by which instrument, but not the precise text of the amendments. Where the endnote flags a misdescription with “(md)” or “(md not incorp)”, users should be alerted to the fact that the compilation has exercised an editorial choice about whether to give effect to the intended amendment. The amendment-history endnote therefore operates as a navigational and explanatory index, rather than a substitute for the amending instruments themselves.

All items above are taken from Endnote 4 as provided in the compilation extract.

The supplied endnotes contain no entries depicting litigation history. They are confined to editorial metadata about the compilation, including an abbreviation key, legislative history and amendment history. None of the endnotes provides case citations, summaries of judicial interpretation, or references to litigation that has affected the construction or application of the compiled law.

Endnote 1 explicitly describes the function of the endnotes as informational about the compilation and compiled law. Endnotes 3 and 4 are respectively legislative-history and amendment-history tools, listing amending instruments, FRLI registration dates, commencement dates, and provision-level amendment annotations. There is no section, table or note in the supplied endnotes that addresses litigation, judicial review, proceedings, or case citations. The absence of litigation data in the endnotes is itself the relevant fact for researchers: if a user requires judicial decisions that interpret, apply or invalidate parts of the compiled law, the endnotes do not provide that record.

The practical consequence for legal research is clear from the endnotes’ content and omissions. To locate any litigation that has engaged with the Television Licence Area Plan (Brisbane) or its variations, researchers must consult court databases, law reports, tribunal records or other secondary sources, because the compilation’s endnotes do not perform that function. The endnotes do provide FRLI registration numbers and commencement dates that can assist in constructing a chronology of amendments, which can be used as the basis for targeted searches for litigation that occurred after specific amendment commencement dates. But the endnotes do not themselves report litigation outcomes or judicial commentary.

Because the endnotes include an explicit editorial protocol for misdescribed amendments in Endnote 4, researchers should be cautious: where the compilation has applied an “(md)” flag and incorporated an intended amendment despite a misdescription, the textual form shown in the compilation may reflect an editorial construction rather than a verbatim reproduction of the amending instrument. In such circumstances, a litigant or researcher would want to check the original instrument and any parliamentary materials as part of litigation history research, because judicial treatment may hinge on the precise wording of an instrument as enacted and on how courts treat editorial corrections in compilations.

In summary, the supplied endnotes do not document litigation history. The endnotes are metadata for the statute’s amendment lifecycle and point users to the instruments that must be examined for text-level and litigation-relevant detail.

The endnotes contain several practical features and small editorial anomalies that users should treat as potential pitfalls when relying on the compilation. These are matters of provenance, completeness, labelling and interpretation, all of which are directly evident from the endnotes themselves.

1. Absence of application, saving or transitional provisions in the compilation rows shown. The legislative-history table in Endnote 3 contains an explicit column for “Application, saving or transitional provisions”, and in the rows provided that column contains a dash. That dash is the compilation’s way of indicating no such provisions are recorded in that entry. The gotcha is that the compilation warns that such provisions might exist but are not printed in the body of the compilation, and users must verify whether an amending instrument contains transitional or saving rules that affect rights during the period of change.

2. FRLI registration references require follow-up. The table lists FRLI file identifiers such as “see F2012L02495”, but it does not reproduce the amending instrument’s text. Users must consult the FRLI entry using the given identifiers to obtain the full text and confirm commencement, application, and any explanatory notes. Treat the FRLI references as pointers rather than as substitutes for original instruments.

3. Misdescribed amendment flags. Endnote 4 explains the use of “(md)” and “(md not incorp)”. A compilation annotating an amendment with “(md)” indicates the editor has treated a misdescription as capable of being given effect; “(md not incorp)” indicates the misdescription could not be given effect. The gotcha is that where a compilation has applied “(md)”, the text in the compilation may incorporate an editorially corrected form rather than a literal reproduction. Practitioners should check the source amending instrument and any parliamentary materials to understand whether the correction is consistent with the enacting intent and whether courts might treat the correction as authoritative.

4. Compressed and potentially misformatted amendment entries. The supplied amendment-history table contains a complex compressed row that strings together many clause identifiers and a concatenation of amendment source identifiers with minimal separators. For example, the combined cell “Clause 1Clause 2Clause 3Schedule 2Clause 1Clause 2Schedule 3Clause 1Clause 2Attachment 1” paired with a long sequence of amendment citations appears in the supplied text. This formatting makes it difficult to parse which amendment corresponds to which clause or attachment. The practical outcome is that users must exercise care in relying on the printed amendment history and should cross-check the mapping against the source instruments to avoid misattributing changes.

5. Typographical anomalies in the abbreviation key. Endnote 2 contains a line where “rep. = repealedrs. = repealed and substituted” appears without a clear separator between entries. While the intended meaning is inferable, the gotcha is that typographical issues can create ambiguity in automated parsing or in human reading. Users relying on programmatic extraction or textual search should not assume that all abbreviation lines are error-free.

6. Aggregation obscures detail. The endnotes list titles and high-level amendment mappings, but they do not reproduce the original amending text. That aggregation is purposeful, but it means that the granular substantive effect of an amendment, such as an inserted paragraph or a substituted definition, is not visible in the endnotes. When precise operative wording matters, users must retrieve the original amending instrument.

7. Dates in the legislative-history table are the authoritative markers in the compilation, but any error in those dates in the compilation would materially mislead users about commencement. The endnotes provide commencement dates,e.g. “29 May 2013” for the 2012 Plan and “8 November 2013” for the 2013 variation,but users should confirm with the original instrument or FRLI entry if critical deadlines, filing windows or regulatory regimes depend on exact commencement timing.

8. No litigation or interpretive history included. As explained above, there is no litigation history in the endnotes. If the legal effect of an amendment has been considered by courts or tribunals, the endnotes will not reflect that development. Users should not assume that the absence of litigation entries implies the absence of interpretive issues.

These gotchas are directly visible in the supplied endnotes and should prompt users to treat the endnotes as a navigational and editorial tool that is necessary but not sufficient for definitive legal conclusions. Verification against source instruments is the recommended follow-up, precisely because the endnotes both point to and summarise amending material.

“Compliance” with the endnotes’ regime is primarily a matter of using the endnotes correctly when preparing, publishing or relying on consolidated legal material. The endnotes do not impose substantive statutory obligations on external parties, so the practical compliance steps concern due diligence, verification and editorial practice. Below are concrete steps, drawn from the endnotes themselves, that a practitioner, publisher or compliance officer should follow.

1. Treat Endnote 1 as the starting rule. The endnotes exist to provide information about the compilation and the compiled law. Compliance, in this context, means that when you use the compilation as an authoritative source you must also consult the endnotes for the compilation’s editorial and provenance statements. Do not rely on the consolidated text in isolation.

2. Use the abbreviation key in Endnote 2 accurately. The abbreviations “ad”, “am”, and “rep.” are the shorthand used in the amendment entries. When preparing your own consolidation or cross-referencing extracts, use these same abbreviations to maintain consistency with the compilation’s conventions. Where the abbreviation key shows typographical ambiguity, resolve the ambiguity by consulting the rest of the compilation or the amending instrument.

3. Verify FRLI registration references in Endnote 3. For any amending instrument you plan to rely on, use the FRLI identifiers given (for example “see F2012L02495”) to retrieve the official register entry and the full text of the amending instrument. Confirm the registration date shown in the endnote against the FRLI entry, and record the official commencement date as stated in the original instrument.

4. Check application, saving and transitional provisions. Endnote 3 has an explicit column for these provisions, and the endnotes state they will note such provisions that are not included in the compilation. Compliance requires you to follow up where the endnote flags an entry in that column, and to obtain the original instrument where transitional rules may alter the effect of amendments.

5. Cross-reference amendment-history entries in Endnote 4 to source instruments. The amendment-history table identifies which sections and schedule items were amended and by which instrument. For precise drafting, statutory interpretation or litigation purposes, obtain the amending instrument and confirm the exact amendment text. Where the compilation uses “(md)” or “(md not incorp)”, check the primary materials to understand the nature of the misdescription and whether the compilation’s treatment is justified.

6. Where you rely on an “(md)” flagged entry, document your verification steps. Because “(md)” signals that the editor has incorporated a misdescribed amendment, keep a record of the FRLI entry, the original amending text and any parliamentary materials you used to confirm the intended effect. This audit trail is useful if a dispute arises about textual accuracy.

7. Avoid automated reliance on the endnotes without human review. The supplied text shows compressed and potentially misformatted entries in the amendment-history table and a typographical anomaly in the abbreviation key. If you use the compilation for database ingestion or legal-tech workflows, implement a validation step that cross-checks parsed entries against FRLI entries to catch formatting or OCR errors.

8. Use the endnotes as a pointer not a substitute. The compilation’s endnotes give you the titles, registration identifiers, and commencement dates, but they do not replace the amending instruments. For any compliance action, regulatory filing, or litigation position that depends on precise timing or wording, retrieve and rely on the original instrument.

9. Maintain a versioning log. When the compiled instrument is subject to multiple variations across years, keep an internal record of which consolidated text you used and when. The endnotes provide the chronology that should anchor your versioning records, for example the 2012 Plan and its 2013-2016 variations and the 2017 consequential instrument listed in Endnote 3.

10. If in doubt, escalate to primary-source retrieval. The most robust compliance practice is to treat each FRLI reference and each amendment-history citation as an instruction to retrieve the primary legislative instrument. The endnotes perform the indexing task; compliance requires retrieval and verification.

These steps are directly derived from the content and structure of Endnotes 1-4 as provided. They are practical measures for anyone using the compilation for legal work, publication, regulatory compliance or advisory purposes.