Licence Area Plan – Young Radio

The endnotes use three primary conceptual constructs to describe what has happened to the instrument: (1) a chronological register of instruments and variations (Endnote 3,Legislation history); (2) an itemised, clause‑level amendment log (Endnote 4,Amendment history); and (3) an abbreviation key that explains the editorial notation used to record how each provision was affected (Endnote 2,Abbreviation key). Each of these constructs is a different form of metadata about the compiled law.

Chronological register (Endnote 3). The register lists distinct instruments by title and records three discrete dates per entry where available: registration or Gazette notification date, statutory commencement date, and any application, saving or transitional provisions (the table includes a column for those, though many entries have that cell blank). The registration dates listed include explicit references to ComLaw/Federal Register items (for example, "see F2005B01207" is recorded in the table text for the 2001 licence area plan entry). The register therefore maps the life cycle of instruments from publication through commencement.

Provision‑level amendment log (Endnote 4). Endnote 4 is a table that maps "Provision affected" (the Title Page, introductory text, clauses (1)-(6), Schedules One-Four, and a long list of Attachments 1.1 through 4.2) to "How affected" using the abbreviations defined in Endnote 2. For instance, the Title Page is recorded as "am. var. No.1 of 2014", Clause (1) is recorded as "rs. var. No.1 of 2014" (meaning it was repealed and substituted by variation No.1 of 2014), and Clause (6) is recorded as "ad. var. No.1 of 2014" (meaning it was added by that variation). Several Attachments are recorded variously as added, amended, repealed and re‑added across the 2004 and 2014 variations and the 2017 amendment.

Abbreviation key and misdescription handling (Endnote 2 and explanatory note in Endnote 4). The key defines ad, am, rep., and rs. Endnote 4 also provides the compilation practice for misdescribed amendments: it explains that if an amendment is misdescribed but can be given effect as intended, the compilation will record it with "md"; if it cannot be given effect, the compilation records "md not incorp". The presence of that explanatory material means the compilation anticipates discrepancies between parliamentary drafting or Gazette notices and the final text and gives a method for documenting them.

Functionally, these concepts operate to tell a reader which parts of the licence area plan are current and which have been superseded. The amendment log's "rs" entries indicate that entire clauses were taken out and replaced by new text; "rep." entries indicate full repeal; "ad" entries indicate added material; and "am" entries indicate modification of existing text. Because the compilation records specific attachments and schedules individually, users are warned that maps, figures and technical attachments may have been the locus of many of the changes, not only the textual clauses.

Finally, the register records a distinct instrument titled "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)", registered 29/09/2017 and commencing 30/09/2017. Its appearance in the register signals that at least one amending instrument was framed as consequential amendments to the broadcasting technical planning guidelines, and is therefore likely to change or align technical‑planning material across multiple licence area plans or related instruments. The endnotes do not reproduce the substantive content of that 2017 instrument, but they record its registration and commencement as part of the lifecycle of the compiled plan.

The endnotes identify the instrument title "Licence Area Plan - Young Radio" and list multiple variations and consequential instruments. That identifies two immediate categories of affected parties: (1) persons and entities that hold or operate under the specific licence area plan (the licence area stakeholders for "Young Radio"); and (2) persons who rely on or administer the Broadcasting Services (Technical Planning) Guidelines, insofar as a consequential amendments instrument is recorded.

The endnotes themselves do not list named individuals or corporate entities. They do, however, show that the composition of the Licence Area Plan has changed at the Title Page, at multiple numbered clauses (1-6), through Schedules One-Four, and at a long list of attachments and attachment subsections (Attachments 1.1 through 1.13, 2.1 through 2.2, 3.1 and 3.2, 4.1 and 4.2, plus various sub‑attachments such as 1.5.1, 1.6.1, 2.1.1, 3.1.1 and so on). The granularity of the entries indicates that those who depend on particular maps, diagrams or schedule content within the plan , for example, broadcasters’ technical planners or engineers, frequency coordinators, licence applicants, and compliance officers , are the practical users most directly affected by changes to attachments and schedules.

The register entries also include published registration identifiers and dates (for example, "19/12/2001 (see F2005B01207)", "18/02/2004 (see F2005B00644)", "14/08/2014 (see F2014L01093)", and "29/09/2017 (see F2017L01299)"). Those registration identifiers provide the hook for obtaining the official amending instrument in full; consequently, any person whose rights or obligations depend on the exact content of the plan will need to consult the instruments referenced by those identifiers to determine their legal position.

The appearance of the Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) in the register suggests that parties who administer or depend upon the Guidelines (for example, regulatory staff responsible for technical planning instruments, external consultants advising licensees on planning compliance, and broadcasters who must align transmitters and coverage to guideline norms) also have an interest in the recorded changes. The endnotes do not say which provisions of the Guidelines were consequentially amended; they record only the instrument title, registration and commencement dates. Practitioners should therefore treat the 2017 instrument as a pointer requiring retrieval and review.

Who pays and who decides. The endnotes do not directly specify fees, financial obligations, or explicit decision‑makers. They record the dates on which instruments were registered and commenced and mark how provisions were affected. The presence of registration numbers and Gazette dates demonstrates that an official registration process applied to these instruments; the natural reading is that an instrument‑making authority published and registered the instruments and variations, and that the instruments became effective on the recorded commencement dates. If a licence holder’s compliance costs or technical obligations changed as a result of these amendments, those costs would fall on the licence holder; the endnotes document when that shift in the compiled text occurred.

Who should read these endnotes. Lawyers advising broadcasting licensees, compliance officers checking which attachments are current, engineers mapping signal coverage against the correct version of an attachment, and documentation managers preparing transitional compliance plans should consult the endnotes to determine exactly which pieces of the compiled plan were added, amended, repealed or substituted, and on what dates those changes took effect.

The endnotes do not directly impose duties or create rights in the language of statutory obligations; they are a meta‑documentation of amendments and registration details. Nevertheless, the endnotes alter the legal content of the compiled instrument by recording that certain parts were repealed, substituted, amended or added. The legal practicalities that flow from that are the duties and rights that attach to whatever text is current in the compiled instrument.

Duties implied by the amendment entries. When a clause or attachment is recorded as "rs." (repealed and substituted), "rep." (repealed), "am." (amended), or "ad." (added), the operative version of the licence area plan as compiled will reflect those changes from the recorded commencement dates. Practitioners advising clients should therefore recognise the following mapping from the endnotes to duties and rights: the licence holder must comply with the text that is current in the compilation as at the relevant date; any compliance obligations, technical specifications, coverage obligations or schedule‑based restrictions that appear in an attachment added or amended will apply (if they are part of the operative plan) from the commencement date recorded in the register. For example, Clause (1) is recorded as "rs. var. No.1 of 2014" in Endnote 4, meaning Clause (1) was repealed and substituted by Variation No.1 of 2014; the substituted text is the one to be read as operative from the commencement date of that variation (15/08/2014 as recorded in Endnote 3).

Rights that follow from amendments. Conversely, where an amendment removes a schedule or repeals an attachment, rights or entitlements that depended on that schedule may no longer be supported by the compiled instrument. The endnotes do not set out transitional protections, saving provisions or grandfathering; the Endnote 3 table has a column for "Application, saving and transitional provisions" but most recorded cells in the extract are blank. Practitioners must therefore look up the full amending instruments (using the registration identifiers in the register) to determine whether any transitional or protective provisions were included when an item was repealed or substituted.

Practical consequence: version control of duties and rights. The endnotes provide the authoritative trail to determine which version of the plan and attachments contains the applicable duties and rights. That makes the endnotes an essential compliance checkpoint: a compliance officer or lawyer must check the compiled version and cross‑reference the endnote dates and amendment entries to establish whether an obligation, map, or technical parameter applied at a particular point in time.

No independent new obligations in the endnotes. The endnotes themselves do not create new regulatory duties or confer statutory rights; they record changes made by other instruments. The operational obligations and rights will be in the substantive text of the Licence Area Plan, its schedules and attachments, and in any consequential amendments to the Broadcasting Services (Technical Planning) Guidelines. The endnotes show which text is current and how it got there; they do not substitute for reading the substantive instruments themselves.

Advice for drafting compliance memos. Where an advisory memo must identify present duties and rights, the endnotes mandate a three‑step workflow: (1) identify the relevant date of interest (for example, a compliance check date or an incident date); (2) consult the Endnote 3 register to establish which instrument was in effect on that date and whether any variation or consequential instrument had commenced; and (3) consult Endnote 4 to find which clauses, schedules or attachments were added, amended, repealed or substituted and then retrieve the full text of the relevant instrument(s) using the registration reference provided.

The extracted endnotes do not contain penalty provisions, enforcement mechanisms, or sanctioning regimes. They are metadata: a register and history of amendments. Therefore, they do not themselves specify monetary penalties, criminal offences, administrative sanctions, infringement notices, or enforcement procedures. No provision in the endnotes grants investigative powers or prescribes enforcement processes.

Where penalties and enforcement would be found. Penalties and enforcement provisions, if any, will be contained in the substantive instruments referenced by the endnotes , namely the Licence Area Plan - Young Radio itself, its variations (February 2004, No.1 of 2014), and the Broadcasting Services (Technical Planning) Guidelines or consequential amendments instrument of 2017. The endnotes indicate where and when the operative text changed, but they do not reproduce the operative text that may carry enforcement language. Practitioners who need to address liability exposure or enforcement risk will therefore need to retrieve the full text of the version of the plan that applies to the relevant period using the registration and commencement information in Endnote 3.

Implications for enforcement timing. The endnotes record commencement dates for each instrument. For enforcement purposes, those commencement dates are legally significant because they determine the date from which any new or altered regulatory requirements become enforceable. For example, the variation No.1 of 2014 is recorded as commencing 15/08/2014; any substantive obligations added, substituted, or repealed by that variation would be effective from that date unless a transitional or saving provision specified otherwise in the full instrument. Because the Endnote 3 table has a dedicated column for "Application, saving and transitional provisions" (which is largely blank in the extract), practitioners must check the amending instruments for any transitional relief that would affect enforcement for pre‑existing activities.

No enforcement authority named in these endnotes. The extract does not name a regulator or enforcement authority. The table’s CSS classes and text fragments such as "ACMATableText" imply that the compilation is produced using Australian Communications and Media Authority (ACMA) formatting, but the endnotes themselves do not state who enforces the provisions recorded. Do not assume an enforcement regime or enforcing agency from these endnotes alone; instead, retrieve the substantive instruments and their enabling Act to identify the enforcement framework.

Recommended compliance posture when enforcement is a concern. Where enforcement risk is material, lawyers and compliance officers should (based on the endnotes): (1) identify the applicable instrument and commencement date via Endnote 3; (2) obtain the full operative text of the instrument and any enabling statute; (3) examine the full instrument for explicit enforcement and penalty provisions and any transitional or saving clauses; and (4) map the effective compliance obligations to operational practice on and after the recorded commencement date. The endnotes are a necessary starting point for that sequence but not, alone, an enforcement manual.

The endnotes are a compilation tool that establishes the provenance and amendment history of a particular instrument and shows how that instrument has been varied across time. They do not, in themselves, create cross‑statutory obligations, but they document interactions through recorded "consequential amendments". Specifically, the register includes a distinct amending instrument entitled "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)", registered 29/09/2017 and commencing 30/09/2017. By labelling that 2017 instrument as consequential amendments to the Technical Planning Guidelines, the endnotes explicitly flag an interaction: the Licence Area Plan’s content was, at least in part, influenced by changes to or harmonisation with the Broadcasting Services (Technical Planning) Guidelines.

Consequential amendment mechanism. A consequential amendment instrument is typically used to align subordinate instruments (such as licence area plans and attachments) with primary changes in an overarching guideline or rule. The endnotes show that such a consequential instrument exists and that it was registered and commenced in September 2017. For practitioners, that indicates two things: (1) the substantive content of the licence area plan may have been changed to remain consistent with an updated guideline; and (2) the changes may therefore affect multiple instruments beyond this single licence area plan, because guidelines often have a cross‑instrument reach.

Interaction through schedules and attachments. Endnote 4 documents that Schedules One-Four and numerous attachments were amended, repealed or added across the recorded variations. Schedules and attachments often contain maps, frequency tables, coverage footprints, technical parameters and implementation rules. Where a Guideline sets technical standards, and a licence area plan contains specific parameters that flow from those standards, an amendment to the Guideline (with consequential amendments recorded in the 2017 instrument) will interact with the licence area plan by changing the plan’s attachments or schedules. The endnotes record the occurrence of these changes but do not reproduce the substantive rule language. Practitioners must retrieve the Guidelines instrument and the consequential amendments to see the exact legal interplay.

No express cross‑references reproduced. The endnotes do not reproduce statutory cross‑references or cite enabling Act provisions in this extract. To understand the vertical interaction between the licence area plan and primary legislation (for example, the Broadcasting Services Act or other enabling statute), one must consult the enabling Act and the full instruments. The endnotes function as a map of amendments and therefore as a navigational tool to find the relevant points of legal interaction.

Consequences for compliance and rights. Where a licensee’s rights or obligations are rooted in a licence area plan that incorporates or depends upon obligations from a higher‑level guideline, a consequential amendment may alter the licensee’s compliance universe without the licensee being directly named. The endnotes show where to look for those consequential changes, by identifying the amending instrument title, registration number and commencement date.

Compilation practice and statutory interplay. Endnote 4’s discussion of misdescribed amendments and the "md" and "md not incorp" flags shows that the compilation records the editorial and interpretive steps taken when parliamentary or administrative documents do not perfectly describe the text to be inserted or replaced. That matters for interaction with other laws because an amendment that is misdescribed in its Gazette notice but interpreted by the compilation may raise questions about whether the intended cross‑reference to other statutory provisions was accomplished. The compilation’s practice for flagging such misdescriptions is therefore a useful guide for practitioners seeking to understand whether an amendment was effective as intended.

Endnote 3 (Legislation history) and Endnote 4 (Amendment history) together supply the amendment timeline and the provision‑level effects. Endnote 2 provides the abbreviation key used in the amendment table. Below is a consolidated, source‑grounded chronology and provision mapping from the endnotes.

Chronology (Endnote 3):

• Licence Area Plan - Young Radio - December 2001. Registration or Gazette notification: 19/12/2001 (the table notes "see F2005B01207"). Commencement recorded 06/12/2001.
• Licence Area Plan - Young Radio - Variation - February 2004. Registration: 18/02/2004 ("see F2005B00644"). Commencement recorded 05/02/2004.
• Licence Area Plan - Young Radio - Variation No.1 of 2014. Registration: 14/08/2014 ("see F2014L01093"). Commencement recorded 15/08/2014.
• Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1). Registration: 29/09/2017 ("see F2017L01299"). Commencement recorded 30/09/2017.

Provision‑level amendment mapping (Endnote 4; abbreviations per Endnote 2):

• Title Page: recorded as "am. var. No.1 of 2014" (the Title Page was amended by variation No.1 of 2014).
• Introductory text on page one: "am. var. No.1 of 2014".
• Clause (1): "rs. var. No.1 of 2014" (Clause (1) was repealed and substituted by Variation No.1 of 2014).
• Clause (2): "rs. var. No.1 of 2014".
• Clause (3): "rs. var. No.1 of 2014".
• Clause (4): "rs. var. No.1 of 2014".
• Clause (5): "rs. var. No.1 of 2014".
• Clause (6): "ad. var. No.1 of 2014" (Clause (6) was added by Variation No.1 of 2014).
• Introductory text on page two: "rep. var.No.1 of 2014" (introductory text on the second page was repealed by Variation No.1 of 2014).
• Schedule One: "am. var. Feb 2004; rs. var No.1 of 2014" (Schedule One was amended by the February 2004 variation and later repealed and substituted by Variation No.1 of 2014).
• Schedule Two: "rs. var. No.1 of 2014".
• Schedule Three: "rs. var. No.1 of 2014".
• Schedule Four: "rs. var. No.1 of 2014".
• Attachment 1.1: "rep. var. Feb 2004; ad. var. No.1 of 2014" (Attachment 1.1 was repealed by the February 2004 variation and then added back by Variation No.1 of 2014).
• Attachment 1.1.1: "ad. var. Feb 2004; rep. var. No.1 of 2014" (added in Feb 2004, later repealed in 2014).
• Attachment 1.2: "rs. var. No.1 of 2014, am. No.1 of 2017" (repealed and substituted by the 2014 variation and amended by No.1 of 2017).
• Attachment 1.3: "rs. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.4: "rs. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.5: "rep. var. Feb 2004; ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.5.1: "ad. var. Feb 2004; rep. var. No.1 of 2014".
• Attachment 1.6: "rep. var. Feb 2004; ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.6.1: "ad. var. Feb 2004; rep. var. No.1 of 2014".
• Attachment 1.7: "rs. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.8: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.9: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.10: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.11: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.12: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 1.13: "ad. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 2.1: "rep. var. Feb 2004; ad. var. No.1 of 2014".
• Attachment 2.1.1: "ad. var. Feb 2004, rep. var. No.1 of 2014".
• Attachment 2.2: "rs. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 3.1: "rep. var. No.1 of 2014; ad. var. No.1 of 2014" (the record shows both a repeal and an addition under the 2014 variation).
• Attachment 3.1.1: "ad. var. Feb 2004, rep. var. No.1 of 2014".
• Attachment 3.2: "rs. var. No.1 of 2014, am. No.1 of 2017".
• Attachment 4.1: "rep. var. Feb 2004; ad. var. No.1 of 2014".
• Attachment 4.2: "rs. var. No.1 of 2014, am. No.1 of 2017".

This mapping in Endnote 4 shows that the February 2004 variation and the No.1 of 2014 variation effected multiple, sometimes cyclical, changes to attachments: some attachments were repealed in 2004 and reintroduced in 2014; others were replaced by new text in 2014 and later amended again in 2017. Endnote 4 documents these editorial steps as "ad", "am", "rep" and "rs" and explicitly notes where a single attachment has been subject to multiple actions across different amending instruments.

The amendment history also contains an explanatory section about "misdescribed amendments": Endnote 4 explains that if an amendment is misdescribed but can be given effect, the compilation will annotate it "md" and incorporate it; if it cannot be given effect, the compilation will annotate "md not incorp". The visible entries in the supplied extract do not show any "md" or "md not incorp" flags, but the presence of that editorial rule in the endnotes means the compilation process anticipates and records the legal status of potentially defective amendment notices.

For a compliance timeline, the key dates to extract from the amendment history are the registration dates and commencement dates in Endnote 3 and the specific provision actions recorded in Endnote 4. Those two endnotes together identify when the compiled instrument's content was changed and how.

The supplied endnotes do not record any litigation history. The content of Endnote 3 is restricted to registration, commencement and transitional application entries for instruments. Endnote 4 is an editorial amendment log and likewise does not mention legal proceedings, court decisions, appeals, declaratory judgments, injunctions, or other forms of litigation.

Absence of litigation entries in the endnotes. Because compiled law endnotes are a record of the legislative and subordinate instrument history rather than judicial history, the absence of litigation references in these endnotes does not prove that no litigation ever touched the Licence Area Plan - Young Radio; it only indicates that the compilation's endnotes do not capture judicial decisions. Practitioners looking for litigation that might have affected the legal status or interpretation of the licence area plan must therefore search case law databases, tribunal decisions, or regulatory determinations separately.

Where to look for litigation‑relevant materials. If litigation or administrative determinations are suspected or known to exist in relation to the Licence Area Plan - Young Radio, the following steps are dictated by the structure of the endnotes: (1) use the registration identifiers and dates recorded in Endnote 3 to identify the exact versions of the instrument that were in force at relevant times; (2) search the court databases and tribunal records for decisions that reference those instrument titles, registration numbers or commencement dates; and (3) check the enabling statute and guidelines (for example, the Broadcasting Services (Technical Planning) Guidelines and any amendments) for references to dispute resolution, review rights or enforcement actions that might have produced litigation. Such searches lie outside the content of the endnotes and must be conducted in legal databases.

Endnote 4’s misdescription policy and litigation risk. Endnote 4’s procedure for marking misdescribed amendments ("md" vs "md not incorp") is useful in assessing litigation risk linked to drafting errors. If an amending instrument was poorly described in its Gazette notice but the compilation indicates it could be given effect by the drafters' intention (marked "md"), a prospective litigant could still challenge the amendment on formal notice grounds. Because no "md" entries are visible in the extract provided, no such specific risk is flagged, but practitioners should be alert to the possibility and verify whether the full amending instruments include any contested drafting anomalies in the registration notices.

Treat the endnotes as metadata, not as substitute for operative text. The primary practical "gotcha" is to assume that the endnotes set out substantive obligations. They do not. The endnotes record when an instrument or specific provision was added, amended, repealed or substituted; they do not reproduce the replacement text or the content of affected attachments, clauses or schedules. Using the endnotes as a shortcut to compliance obligations without retrieving the full operative instruments will lead to error.

Abbreviation decoding is mandatory. The endnotes rely on shorthand (ad, am, rep., rs.) defined in Endnote 2. Misreading these abbreviations or ignoring them can lead to incorrect conclusions. For example, misreading "rs." (repealed and substituted) as merely "am." would obscure whether an earlier version persists in part; likewise, conflating "rep." (repealed) with "rs." can mask whether a clause was replaced with new text or removed entirely. Always consult Endnote 2 for the canonical meaning of the notation.

Watch for multiple, overlapping edits. Endnote 4 shows that single Attachments and Schedules underwent multiple actions across different amending instruments: an attachment might be "rep." in Feb 2004 and "ad." in 2014 and then "am." in 2017. This cyclical editing means that a practitioner must look at the compilation's final assembled text plus the endnotes’ dates to determine which version was effective at any given time. Relying on an intermediate PDF or a cached version of an attachment without cross‑checking the endnotes can produce mistakes.

Expect blank transitional columns. The Endnote 3 table includes a column headed "Application, saving and transitional provisions". In the provided extract most of those cells are blank. Do not infer that absence of a note means absence of transitional relief; the transitional provisions may be present in the full amending instrument but not reproduced in the brief line in the endnote. Always retrieve the full text of the amending instrument to see whether the drafters included application, saving or transitional rules.

Don't assume registration equals commencement date alignment. Endnote 3 lists both registration/Gazette dates and separate commencement dates. The registration notice date and the formal commencement date can differ (for example, an instrument may be registered on a later date than its listed commencement or vice versa). For example, the 2001 Licence Area Plan was registered on 19/12/2001 with a commencement date recorded as 06/12/2001. Practitioners must use the commencement date recorded in the register (and verify against the full instrument) when determining which text applied at a specific earlier date.

Beware of presumed regulator identity. The compilation table uses class names like "ACMATableText", which suggest that the Australian Communications and Media Authority formatted the material. The endnotes, however, do not explicitly name the regulator as the decision maker or enforcer. Avoid assuming enforcement responsibilities or procedural rules solely from the presence of formatting class names; instead, confirm the responsible authority from the enabling legislation and the text of the instruments.

Misdescribed amendment traps. Endnote 4 explains how the compilation handles misdescribed amendments (the "md" and "md not incorp" flags). Even if the compilation shows an amendment as given effect under "md", a court could still find a procedural defect in the amending notice. If a regeneration or reinterpretation of an amendment was required in the compilation, there may be legal arguments that the amendment was not validly made. The endnotes flag the issue but do not resolve it substantively for practitioners.

Rely on registration identifiers to retrieve amending instruments. The endnotes provide registration references like "F2014L01093" and "F2017L01299". If those references are unavailable or incorrectly transcribed, retrieving the amending instrument will be slower and may lead to reliance on an incorrect version. Always copy the registration reference precisely and confirm that the instrument you retrieve matches the registration date and commencement date recorded.

Because the endnotes are a map of changes, compliance is a versioning exercise plus a substance exercise. Use this endnotes‑driven workflow:

1. Establish the relevant timeframe. Decide the date for your compliance assessment: the date of an alleged contravention, the date of an application, or the current compliance date. The commencement dates recorded in Endnote 3 determine which version of the Licence Area Plan applied at that time.

2. Use the register to retrieve instruments. Take the registration identifiers and dates from Endnote 3 (for example, "see F2014L01093" for the 2014 variation and "see F2017L01299" for the 2017 consequential amendments) and retrieve the full text of each relevant instrument from the official register or Gazette. Do not rely on the endnotes alone.

3. Cross‑check provision effects. Consult Endnote 4 to identify which clauses, schedules and attachments were added, amended, repealed or substituted by each instrument. Use the "ad", "am", "rep.", "rs" codes from Endnote 2 to determine the legal operation (added vs amended vs repealed and substituted). Map those changes to the full text you retrieved: confirm that the clause you are reading corresponds to the action recorded in the amendment log.

4. Look for transitional or saving provisions. Even if Endnote 3's "Application, saving and transitional provisions" column is blank in the extract, the full amending instrument may include transitional measures. Search the full text for sections titled "application", "transitional", "savings", or similar language. These provisions can materially alter who must comply, when enforcement begins, or whether prior authorisations remain valid.

5. Identify technical attachments and maps. The amendment history shows heavy editing of attachments (for example, Attachment 1.2 through 1.13, Attachment 2.1 and 2.2, Attachment 3.1 and 3.2, and Attachment 4.1 and 4.2). These are likely to contain technical parameters (maps, frequency listings, diagrams). Obtain the attachments as separate files if necessary and confirm which version is incorporated by reference in the operative text.

6. Confirm the applicable enforcement and remedy regime. Retrieve the enabling Act or policy instrument that identifies enforcement powers and penalty provisions. The endnotes do not reproduce enforcement material. For any risk assessment or compliance remediation plan, identify the statutory basis for enforcement and whether administrative processes, criminal sanctions or civil penalties apply.

7. Document version control in compliance files. Maintain a compliance register that records: the instrument title, registration number, Gazette date, commencement date, provision(s) affected, and a snapshot of the operative text for the date of interest. Use Endnote 4 as the index for which provisions changed so your compliance file identifies which attachment or schedule you relied on.

8. If in doubt, obtain regulatory confirmation. Where a change in an attachment could impose new technical obligations (for example, frequency or coverage obligations) that would require capital or operational modifications, consider submitting a formal technical clarification request to the relevant authority or a compliance notice seeking guidance on application timelines, enforcement posture and transitional relief.

9. Watch for further consequential instruments. The record shows that after 2014 there was a 2017 consequential amendment instrument. Regulators often implement consolidated changes incrementally. After making any compliance decisions, check whether later amending instruments have been registered that further change schedules or attachments.

10. Seek legal advisement for contested changes. If a misdescribed amendment is suspected, or if there is a substantial compliance cost arising from an amendment where transitional relief is absent, discuss litigation or administrative review options with counsel. The endnotes’ misdescription policy (Endnote 4) flags the possibility that an amendment could be defective in form, which may give rise to challenge in appropriate circumstances.

Practical checklist for licensees and advisers:

• Pull the full texts of: Licence Area Plan - Young Radio (Dec 2001), Variation (Feb 2004), Variation No.1 of 2014, and Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1) using the registration references in Endnote 3.
• Confirm the operative commencement date for each relevant piece of text.
• Review clause (1)-(6) and Schedules One-Four in the versions that apply to your date of interest; use Endnote 4 to identify which version applies.
• Retrieve and store the exact version of each Attachment that applies (Attachments 1.1-1.13, 2.1-2.2, 3.1-3.2, 4.1-4.2, and sub‑attachments).
• Document any differences between prior and current versions that affect technical operations, and prepare an action plan for any required modifications.
• If enforcement risk or financial exposure is material, obtain written confirmation from the regulator or consider legal proceedings only after evaluating transitional provisions and misdescription risks.

Following the endnotes as a navigational tool will ensure that compliance work targets the operative text rather than an obsolete or superseded version of the licence area plan.