Licence Area Plan - Hamilton Radio

The endnotes use a small set of concepts and conventions to report the state of the compiled instrument. The core concepts are: (1) the compilation as an artefact, (2) the abbreviation key for amendment actions, (3) the legislation-history entries (registration/notification and commencement), (4) the table of amendments at the provision level, and (5) flags for misdescribed amendments and for application/saving/transitional provisions that are not included in the compiled text.

The compilation concept is spelled out at the outset: "The endnotes provide information about this compilation and the compiled law" (Endnote 1). That signals that the endnotes are not the primary legislative instrument itself; they are metadata about the compilation. They are intended to accompany a compiled body of text and to document how that text came to be in its current form.

The abbreviation key in Endnote 2 is central for reading the amendment-history table in Endnote 4. The key as printed shows four items in the table: "ad = added or inserted", "am = amended", "rep. = repealedrs. = repealed and substituted". The printed line appears to conjoin "repealed" and "rs. = repealed and substituted" without an obvious separator; the document nonetheless communicates that the short codes used in the amendment table,ad, am, rep., rs.,stand respectively for various amendment actions. Those codes appear throughout the amendment table (Endnote 4) to indicate how each named provision or attachment was treated by subsequent instruments.

Endnote 3 explains the practice for legislation-history entries. Each entry in the legislation history list includes the instrument name, the Gazette registration or notification identifier, the commencement date and a field labelled "Application, saving and transitional provisions" which the endnote promises will set out any such provisions that are not in the compilation itself. That concept is important because it signals to a reader that some temporally or practically important material (application or saving clauses, transitional arrangements) may not be part of the reproduced operative text and must be examined by reference to the endnotes or the original amending instrument (Endnote 3).

Endnote 4 provides facility for provision-level amendment history and explains the use of "(md)" (misdescribed amendment that has been incorporated because it could be given effect) and "(md not incorp)" (misdescription that cannot be given legal effect). The endnote also reproduces a "Table of Amendments" (embedded HTML in the source) that lists specific provisions and how they were affected (for example, "Schedule One … am. var. Aug 2003; rs. var. No.1 of 2014"). That table is the operational record of the compilation's evolution.

Finally, the instruments listed,principal instrument, variations and a consequential-amendments instrument,illustrate two mechanisms: direct variation of the licence area plan by "variation" instruments, and consequential changes produced by later instruments that amend multiple instruments to align with, for example, new Technical Planning Guidelines (the 2017 Broadcasting Services consequential-amendments instrument). The endnotes record both types.

Readers should treat these concepts as reading rules for the compilation: use the abbreviation key to parse the amendment table; use the legislation-history entries to check Gazette registration and commencement dates; consult the endnote entries for application/saving/transitional provisions not reproduced in the compilation; and check the "(md)" flags in Endnote 4 to see where misdescriptions have been assessed.

The endnotes expressly affect anyone relying on the compilation for legal status, provenance or version control of the Licence Area Plan - Hamilton Radio. That group includes legal practitioners, compliance officers, broadcast licensees, licence applicants, policy advisers, librarians, publishers of consolidated legislation, and scholars or journalists who need to know which instrument version applied at particular dates. The endnotes are the reference layer that tells these users which instruments to consult if they need primary sources, commencement or transitional detail (Endnote 1; Endnote 3).

More concretely, the legislation history entries identify the instruments and dates that altered the licence area plan: the 2001 principal instrument, an August 2003 variation, a variation No. 1 of 2014, and a 2017 consequential-amendments instrument (Endnote 3). Any person or entity whose rights, regulatory obligations, permitted technical parameters or operational responsibilities under the licence area plan depend on temporal versioning must consult the endnotes to determine which instrument applied at a given time. For example, a broadcaster seeking to establish what Attachment 1.5 contained in 2012 would need to trace the amendment entries for Attachment 1.5 recorded in the Table of Amendments (Endnote 4) and review the Gazetteed instruments listed in Endnote 3.

The endnotes also affect those who compile or publish consolidated legislation. The compilation conventions,abbreviation key and the practice of flagging misdescribed amendments,are decisions that publishers and drafters must follow when assembling the consolidated text. The presence of "(md)" or "(md not incorp)" flags in Endnote 4 tell a compiler whether a purported amendment was given effect despite a misdescription, which is material for a correct consolidated text.

Agencies and advisers responsible for regulatory compliance bear practical obligations. The endnotes explicitly promise to record "details of any application, saving or transitional provisions that are not included in this compilation" (Endnote 3). That means an agency, a licence-holder or a lawyer assessing regulatory transition risk must consult the endnotes to discover whether transitional or saving arrangements exist and apply. If an enforcement action or licensing decision hinges on a transitional provision that is not reproduced in the main compilation, the endnotes are the pointer to where that provision lives.

Finally, the endnotes affect anyone using electronic or printed versions of the compilation as evidence in proceedings or administrative decision-making. Since the endnotes list Gazette identifiers and dates, they allow a party to retrieve the primary instruments (registered notifications) from the Gazette. The endnotes therefore reduce search uncertainty and provide a link between the consolidated text and the primary instruments that create substantive rights and duties.

These endnotes do not themselves create statutory duties or rights for regulated parties; instead they document where such duties and rights are created or altered in the underlying instruments and when those changes took effect. The endnotes therefore perform a legal-informational duty: they oblige the compiler to record amendment provenance, and they oblige users to consult them if they need to understand the operative legal framework at particular points in time.

The endnotes identify two concrete responsibilities for users. First, users are responsible for checking commencement and application/saving/transitional fields recorded in Endnote 3. The text says Endnote 3 "provides information about each law that has amended (or will amend) the compiled law. The information includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation" (Endnote 3). Where a licence-holder needs to know whether an amendment applied to their circumstances, they must read the entry in Endnote 3 and, if necessary, the original Gazette instrument.

Second, at provision level, the table in Endnote 4 records how specific components were altered, and the abbreviations (Endnote 2) indicate what happened to each provision: added/inserted (ad), amended (am), repealed (rep.), replaced or repealed and substituted (rs.). Users have the duty to interpret those labels correctly. For example, the Table of Amendments shows "Schedule One … am. var. Aug 2003; rs. var. No.1 of 2014", which means Schedule One was amended by the August 2003 variation and later repealed and substituted by the 2014 variation (Endnote 4). Rights and obligations that had been in Schedule One will therefore have been altered or removed by those specific actions; an affected party must trace the relevant instrument identified by the Gazette entry in Endnote 3 to obtain the operative text.

The endnotes also set out an administrative duty for the compiler to indicate whether a misdescribed amendment could be given legal effect. Endnote 4 explains that misdescribed amendments are marked "(md)" if they can be given effect as intended, or "(md not incorp)" if they cannot. That is a duty of the compilation to record the compiler's legal assessment of the effect of misdescription. Users must therefore note these flags when relying on the compiled text because they affect which amendment text is lawfully incorporated.

There is an implicit duty to rely on the endnotes for version control: the compilation is not a substitute for the primary instrument, and the endnotes make that explicit by providing the Gazette identifiers and dates for retrieval (Endnote 3). Rights that depend on the precise wording of the instrument , for example a technical planning parameter in an attachment , require a user to examine the primary instrument or the compiled text as amended, with the endnotes as the roadmap to those instruments.

In short, the endnotes allocate duties of inquiry and record-keeping: compilers must record amendment provenance and misdescription flags; users must consult the endnotes and, where necessary, the Gazetteed instruments to determine which substantive duties or rights applied at particular times.

The endnotes themselves do not prescribe penalties or enforcement mechanisms. They are descriptive metadata about the compiled instrument and its amendment history (Endnote 1). The substantive penalties and enforcement powers, if any, will appear in the principal licence area plan text or in the statute under which that plan is made; those are not reproduced in the endnotes. The endnotes do, however, have an indirect enforcement relevance because they help identify which version of the substantive rules applied at particular dates , and enforcement actions must be brought under the correct version of the law.

Mechanically, the endnotes reduce the risk of applying the wrong version of the law in an enforcement or compliance context by documenting Gazette registration/notification and commencement dates (Endnote 3) and provision-level amendment history (Endnote 4). For example, the compilation records that the Variation to Licence Area Plan - Hamilton Radio - No. 1 of 2014 was registered on 22 December 2014 and commenced on 23 December 2014 (Endnote 3). If a regulator or an affected party brought an enforcement action for conduct that occurred on 22 December 2014, the endnotes point to the relevant instrument so the applicable text can be verified. If an attachment was repealed by that 2014 variation, the endnotes record that fact in the Table of Amendments (Endnote 4), and a practitioner must use that record to determine whether the alleged contravention predated or post-dated the repeal or substitution.

The endnotes also carry a quality-control function relevant to enforcement evidence. By recording "(md)" or "(md not incorp)" in the amendment history, the endnotes signal whether the compiler judged a given amendment description defective and whether that defect was capable of legal effect. If a party relies on a compiled provision as the basis for enforcement, the presence of a "(md not incorp)" flag would require the enforcer to verify the primary instrument rather than to rely on the compilation.

Because endnotes supply Gazette references, they make it straightforward for enforcement agencies to retrieve the primary instruments to support an enforcement case. The endnotes therefore lower search and evidence-gathering costs for regulators and litigants. They do not, however, substitute for the primary instrument; any penalties or enforcement powers must be located in and applied under the substantive law, not in the endnotes.

Finally, the endnotes do not provide timelines for limitation periods or enforcement windows; users must check the underlying instruments or governing statute for those rules. The endnotes’ role in enforcement is therefore documentary and evidentiary: they tell you where to look for the operative text and when it commenced.

The endnotes record interactions between the Licence Area Plan - Hamilton Radio compilation and other instruments by listing consequential-amendment instruments and by annotating specific provision-level changes. The clearest recorded interaction is the 2017 instrument titled "Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1)", which is listed in Endnote 3 as having been registered on 29 September 2017 and commenced on 30 September 2017. That instrument is expressly described as consequential; the term indicates that it amended other instruments to ensure consistency with changes elsewhere, presumably the Technical Planning Guidelines themselves. The endnotes therefore document a cross-instrument alignment process: the licence area plan was adjusted to reflect changes to a broader regulatory framework (Endnote 3).

The provision-level table in Endnote 4 shows how specific Schedules and Attachments of the compilation were altered by different instruments and variations. For example, many attachments are annotated with "rs. var. No.1 of 2014" or "am. No.1 of 2017", indicating they were repealed and substituted by the 2014 variation, or amended by the 2017 consequential-amendments instrument (Endnote 4). Those annotations document the points of legal interaction: a change in the Technical Planning Guidelines produced a consequential amendment to the licence area plan's attachments; a variation in 2014 caused broader substitution or repeal of schedule material. The endnotes thus map the interdependence among instruments.

The endnotes also interact with the Gazette system. Each instrument entry records a Gazette registration/notification code (for example F2005B00809 for the 2001 instrument, F2014L01787 for the 2014 variation, F2017L01299 for the 2017 instrument). Those cross-references are the legal bridge to the primary law repository and therefore constitute the mechanism by which the compilation connects to the statutory record.

The compilation conventions themselves reflect broader publication practices for statute consolidation. The use of abbreviation keys, the recording of misdescription flags, and the explicit listing of application, saving and transitional provisions all mirror approaches used in consolidated legislation publications to manage multi-instrument interaction and to reduce the risk of misapplying an out-of-date instrument.

Where the endnotes state that Endnote 3 includes "details of any application, saving or transitional provisions that are not included in this compilation", they are indicating that interactions with other laws may be documented outside the body of the compiled text and must be consulted separately. That is an explicit acknowledgement of cross-instrument dependencies, since application/saving/transitional provisions frequently determine how a new legal rule interacts with pre-existing rights or obligations under another instrument or statute.

In short, the endnotes do not themselves change substantive cross-legal interactions; they record them. They make explicit when a licence area plan element was aligned with or changed in response to other regulatory instruments, and they provide the Gazette-based references for tracing that cross-instrument interplay.

Endnote 3 and Endnote 4 together provide the amendment chronology for the Licence Area Plan - Hamilton Radio compilation. Endnote 3 lists four principal entries by instrument name, Gazette registration/notification and commencement date. Those entries are:

• Licence Area Plan - Hamilton Radio - December 2001: registered/notified in the Gazette on 9 January 2002 (F2005B00809), and the commencement date recorded is 9 January 2002 (Endnote 3).

• Licence Area Plan - Hamilton Radio - Variation - August 2003: registered/notified in the Gazette on 27 August 2003 (F2005B00810) and commenced on 27 August 2003 (Endnote 3).

• Variation to Licence Area Plan - Hamilton Radio - No. 1 of 2014: registered/notified in the Gazette on 22 December 2014 (F2014L01787) and commenced on 23 December 2014 (Endnote 3).

• Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (No. 1): registered/notified in the Gazette on 29 September 2017 (F2017L01299) and commenced on 30 September 2017 (Endnote 3).

Endnote 4 supplies the provision-level amendment log through a "Table of Amendments". That table records, in a row-by-row fashion, which named provision or attachment was affected and how. Sample entries (as printed in the compilation) include:

• "Instrument name …………." , annotated "am. var. No. 1 of 2014" indicating the instrument name heading was amended by Variation No. 1 of 2014 (Endnote 4).

• "Heading ……………………" , annotated "am. var. No. 1 of 2014", indicating the heading was amended by that variation (Endnote 4).

• "Clause (1) …………………." , annotated "am. var. No.1 of 2014", indicating clause (1) was amended by the 2014 variation (Endnote 4).

• "Clause (4) …………………." , annotated "ad. var. No.1 of 2014", indicating clause (4) was added/inserted by the 2014 variation (Endnote 4).

• "Introductory text to Schedules …………………." , annotated "rep. var. No.1 of 2014", indicating the introductory text to the Schedules was repealed by the 2014 variation (Endnote 4).

• "Schedule One …………….." , annotated "am. var. Aug 2003; rs. var. No.1 of 2014", indicating Schedule One was amended by the August 2003 variation and later repealed and substituted by Variation No. 1 of 2014 (Endnote 4).

• "Schedule Two …………….." , annotated "rs. var. No.1 of 2014" (Endnote 4).

The table then proceeds to list numerous attachments (Attachment 1.1 through Attachment 1.18, Attachment 2.1 and sub-items, Attachment 2.2, etc.) and records their amendment status: entries like "rs. var. No.1 of 2014", "ad. var. Aug 2003; rep. var. No.1 of 2014", "rs. var. No.1 of 2014; am. No.1 of 2017", and similar appear throughout the table (Endnote 4). For example, several attachments are annotated "rs. var. No.1 of 2014; am. No.1 of 2017", signalling that the 2014 variation repealed and substituted them and that they were later amended by the 2017 consequential-amendments instrument (Endnote 4).

Endnote 4 also explains the treatment of misdescribed amendments: if an instrument's amending provision was misdescribed but nevertheless could be given effect as intended, the compiler adds the abbreviation "(md)". If the misdescription could not be given legal effect, the compiler annotates the amendment as "(md not incorp)". The endnote states that where a misdescribed amendment can be given effect, it is incorporated into the compiled law and the abbreviation "(md)" is added to the details included in the amendment history; if it cannot be given effect as intended, "(md not incorp)" is used (Endnote 4).

Taken together, the chronology shows three waves of change: the original instrument in late 2001/early 2002, a 2003 variation making amendments, a 2014 wider variation which repealed or substituted many schedule and attachment items, and a 2017 consequential-amendments instrument that made further amendments to attachments. The Gazette registration and commencement entries in Endnote 3 provide precise dates for each wave, and Endnote 4 provides granular, provision-level annotations showing which specific components were added, amended, repealed or substituted and by which instrument.

For a practitioner reconstructing the law at a given date, the amendment history as recorded here tells you which instruments to retrieve (the Gazette identifiers) and which parts of the compiled text were affected by each instrument. It also flags where the compiler has had to resolve (or has recorded the inability to resolve) misdescribed amendments.

The endnotes contain no litigation history. They do not reproduce case names, judicial interpretations, or records of disputes about the licence area plan. The source material is purely documentary metadata , details intended to assist readers in locating amending instruments and in understanding provision-level changes , and it contains no reference to judicial proceedings, appeals or tribunal decisions. The only historical material is the list of instruments, their Gazette entries and the provision-level amendment table (Endnote 3; Endnote 4).

Because no cases are named in the endnotes, there is no litigation precedent recorded within this text that would explain how courts have interpreted any provision of the compiled instrument. The endnotes do, however, provide the necessary pointers for a practitioner to assemble the primary instruments and then research any litigation that may have arisen from those instruments. The Gazette identifiers (for example F2005B00809, F2014L01787, F2017L01299) are the retrieval keys for the amending and principal instruments; once the primary instruments are retrieved, a researcher must search court and tribunal databases for any proceedings that involved those instruments or their provisions.

Practitioners should note two procedural implications flowing from the absence of litigation references in the endnotes. First, absence of litigation references in the compilation does not mean there has been no litigation about the licence area plan; it only means the endnotes do not record such litigation. The compiler's task is to map instrument provenance and amendments, not to summarise case law. Second, because the endnotes do not provide interpretation, a litigant or adviser must consult primary instruments and then search case law for interpretive guidance on ambiguous provisions or on the effect of transitional or saving provisions that the endnotes record exist but do not reproduce (Endnote 3).

If a party needs to know how particular terms, attachments or technical parameters have been judicially interpreted, the proper workflow is: (1) use the endnotes' legislation-history and Table of Amendments to identify the primary instrument and the precise historical version; (2) retrieve that text from the Gazette or an official repository; and (3) search for litigation citing that instrument and those provisions. The endnotes are the map; the case law is found by following the map.

The endnotes and the amendment table include a number of concrete pitfalls that can mislead users if they are not read carefully.

1. Compilation is metadata, not law. The endnotes repeatedly state they provide information about the compilation and the compiled law (Endnote 1). The endnotes do not themselves carry operative policy or create rights. Relying on the endnotes alone, without inspecting the primary instruments identified by the Gazette references in Endnote 3, risks misapplying the law.

2. Commencement versus registration/notification dates. The legislation history entries in Endnote 3 show both a "Registration or Notification in Gazette" and a separate "Commencement" date (Endnote 3). Those dates are not always identical: for example, the Variation No. 1 of 2014 is recorded as registered on 22 December 2014 and as commencing on 23 December 2014 (Endnote 3). Failing to observe the commencement date can produce temporal misalignment when assessing which instrument applied at a particular time.

3. Application, saving and transitional provisions may be omitted from the compiled text. Endnote 3 expressly records that it "includes commencement details for amending laws and details of any application, saving or transitional provisions that are not included in this compilation" (Endnote 3). The gotcha is that the operative transitional arrangements may not be reproduced in the body of the compilation; a user must read the endnotes and, where necessary, the primary instrument to discover these provisions.

4. Abbreviation-key parsing. The abbreviation key in Endnote 2 is essential to read Endnote 4's table. The printed key contains the line "rep. = repealedrs. = repealed and substituted", which is run together in the source. Practitioners should therefore be cautious and confirm the intended meaning of "rep." and "rs." when reading the Table of Amendments. The table uses the codes "ad", "am", "rep.", and "rs." to indicate added/inserted, amended, repealed, and repealed-and-substituted actions respectively (Endnote 2; Endnote 4).

5. Misdescribed amendments. Endnote 4 explains the compiler's practice of marking misdescribed amendments "(md)" or "(md not incorp)". The presence of "(md not incorp)" means the compiler judged the description of the amendment incapable of legal effect; the entry will therefore not have been incorporated into the compiled law. Users should look for these flags in the provision-level amendment history and, if present, retrieve the primary instrument to confirm what, if anything, was legally effective.

6. Multiple amendment waves can create complex provenance. The Table of Amendments shows many attachments being repealed, substituted and later amended. For example, several attachments are annotated "rs. var. No.1 of 2014; am. No.1 of 2017" (Endnote 4). That means a user reconstructing a historical version must apply both steps in the correct chronological order. Failing to apply amendments in sequence is a common source of error.

7. HTML/table rendering issues. The Table of Amendments is included in the source as an embedded HTML table block. This is structural metadata for the compilation; in some reproductions the formatting may collapse or the rows may be truncated. Practitioners should confirm entries against the original consolidated source or the Gazetteed instruments if the table appears damaged or incomplete.

8. "Replaced" and "repealed and substituted" distinctions. The table uses "rep." and "rs." to indicate different outcomes. Repeal without substitution removes text; repeal and substitution replaces it with new text. This distinction matters for transitional operation and for any references that rely on a prior attachment or schedule. The endnotes show, for example, that the "Introductory text to Schedules" was "rep. var. No.1 of 2014", which suggests the introductory text was removed by the 2014 variation (Endnote 4).

9. Attachments and schedules are frequently the locus of technical detail. The table shows most changes occurred in attachments and schedules rather than in the instrument's front matter (Endnote 4). Because attachments typically contain technical parameters or maps, a user looking for substantive regulatory detail must pay close attention to the amendment annotations for those items.

10. No litigation pointers in the compilation. The endnotes include no citations to cases. If interpretive uncertainty exists, the endnotes will not direct you to any judicial exposition; you must conduct a separate case-law search.

These "gotchas" are concrete reading hazards embedded in the compilation metadata. They mostly relate to version control, sequencing of amendments, and the need to triangulate the compiled text against Gazetteed instruments when precise legal effect matters.

Compliance in this context means ensuring that any legal or operational conclusions about the Licence Area Plan - Hamilton Radio are based on the correct historical and current text. The endnotes are a tool to achieve that, but they must be used with discipline. Below is a practical compliance checklist that follows directly from the endnotes' own contents and conventions.

1. Start with the endnotes. Open Endnote 3 and identify all instruments that have amended the compiled law. For this compilation the relevant instruments are the original Licence Area Plan (Dec 2001 , Gazette 9 Jan 2002), the Aug 2003 variation (Gazette 27 Aug 2003), Variation No.1 of 2014 (Gazette 22 Dec 2014, commencement 23 Dec 2014) and the Broadcasting Services (Technical Planning) Guidelines (Consequential Amendments) Instrument 2017 (Gazette 29 Sep 2017, commencement 30 Sep 2017) (Endnote 3).

2. Note the Gazette registration/notification identifiers. Use the identifiers provided in Endnote 3 (for example F2005B00809, F2014L01787, F2017L01299) to retrieve the full text of each instrument from the official Gazette repository. The endnotes are a roadmap; the Gazette documents are the source law.

3. Check commencement dates. Do not assume registration/notification equals commencement. Endnote 3 lists both the Gazette entry and the commencement date. For Variation No.1 of 2014 the commencement date is 23 December 2014, one day after registration (Endnote 3). Use the commencement date to determine which version applied on a particular day.

4. Parse the provision-level Table of Amendments using the abbreviation key in Endnote 2. The table uses codes such as ad (added/inserted), am (amended), rep. (repealed) and rs. (repealed and substituted). Read each attachment or schedule annotation in the table to determine whether the component was amended, repealed or replaced and by which instrument (Endnote 2; Endnote 4).

5. Watch for "(md)" or "(md not incorp)". Endnote 4 instructs that misdescribed amendments are flagged. If an amendment entry contains "(md not incorp)" do not rely on the compiled text for that change; instead consult the primary instrument and legal advice to determine whether the amendment was legally effective (Endnote 4).

6. Reconstruct the operative text chronologically. If you need the law as it stood on a specific date, apply amendments in chronological order using the instruments identified in Endnote 3 and guided by the provision annotations in Endnote 4. For example, to get the text applicable on 1 January 2015 you would apply the 2001 instrument, the 2003 variation, and the 2014 variation (commencing 23 December 2014) in sequence.

7. Check application, saving and transitional provisions. The endnotes state that Endnote 3 provides details of any such provisions that are not included in the compilation (Endnote 3). These provisions often determine retrospective effect or grandfathering of prior rights. If transitional rules are recorded in Endnote 3, retrieve the primary instrument to read them in full and assess compliance implications.

8. Use an authoritative consolidated source for operational use, but confirm against the Gazette. If you rely on a consolidated or annotated version of the licence area plan, cross-check the consolidated text against the Gazette instruments identified in the endnotes. The endnotes exist to make that cross-checking possible.

9. Document version-control steps in advice. When advising a client, include the specific Gazette identifiers, registration and commencement dates, and a clear timeline of which attachments/schedules were in force on key dates. Cite the endnotes where they provide the relevant provenance (Endnote 3; Endnote 4).

10. If in doubt, retrieve and quote the primary instrument. Because the endnotes are descriptive, do not treat them as a substitute for the operative text. For formal filings, enforcement, or compliance checks, quote the primary Gazetteed instrument and annex a copy if necessary.

11. Monitor consequential instruments. The 2017 Broadcasting Services consequential-amendments instrument is an example of a cross-cutting change that may have amended multiple instruments (Endnote 3). If the broader regulatory framework changes (for example, Technical Planning Guidelines), check for consequential amendments to the licence area plan compilation.

12. Keep a record of the compilation metadata. Store the endnotes and the primary instruments together with your compliance files. The endnotes are the canonical map to prior and subsequent changes and are necessary for audit trails.

Applying this procedure will align practical compliance steps with the mechanical structure of the endnotes as recorded in the compilation.