This instrument contains a number of practical and interpretative pitfalls that are visible from the text itself. If you will rely on the plan for licensing, engineering, acquisition, or regulatory compliance, bear in mind the following concrete issues.
Conflicting licence counts (two Table 2s). The document contains two distinct Table 2 entries that give different numbers for Category 1 licences. The first "Table 2 Number of licences to be issued" (positioned after Table 1) states Category 1: 2 licences, Category 3: 1 licence. A later "Table 2 Type and number of licences to be issued" states Category 1: 1 licence, Category 3: 1 licence. The document does not label the second table as applying to a different geographic area or as an amendment. This is a primary ambiguity: do 2 Category 1 licences exist (first table) or 1 (second table)? Practically, that affects the number of multiplex licences available and any prospective applicant’s assessment of supply. The tables in the file must be reconciled with the issuing authority before relying on licence counts.
Column 8 informational status. Table 1 includes a "General area served" column (Column 8) listing "Sydney" and "Penrith" but the table contains a note that "Column 8 is included for information only." That means the "General area served" entries are descriptive and not normative; parties should not assume that the terms translate into binding geographic rights or exclusive service areas. The practical risk is that parties may act as if those entries confer normative territorial rights, when the document explicitly treats them as informational.
Reserved frequency block vs other assignments. Table 1 marks frequency block 9C for Sydney 3 as "Yes" under "Reserved frequency block", while 9A and 9B are "No." The document does not explain the nature of the reservation, who benefits from it, or the criteria for unreserving. A reserved designation can materially affect allocation outcomes; operators should not assume reservation equals availability or unavailability without confirmation from the licensing authority.
Transmitter siting outside the BSA. Attachments 1.4-1.6 include an "Advisory Note" that the technical specification is included because the transmission site is outside the Sydney RA1 licence area. That creates practical complications: an operator assigned a licence for Sydney RA1 may be required to host transmitters outside RA1, which raises questions about planning approvals, co-ordination with other regulatory jurisdictions, and the precise legal status of transmissions that originate outside the BSA. The document gives no procedural guidance on how those cross-boundary arrangements are to be authorised.
Site tolerance and external guidance. Attachment 1.2 states "Site Tolerance , Refer to technical planning guidelines." That cross-reference means the attachments are not self-contained. Engineers and applicants must obtain and comply with the referenced technical planning guidelines; failure to do so will risk non-conformance. The text does not include the planning guidelines, so users who proceed without fetching them will lack essential constraints, particularly on permissible deviations from the nominal coordinates.
Highly varied ERP and pattern detail. The Willoughby attachments (TS1132983/2984/2985) contain very detailed sector-by-sector ERP maxima, depression angle constraints and dividing-line distinctions (e.g. "At or above dividing line", "Below dividing line", distinct limits for narrow bearings such as 10°T-40°T with 0.3° depression angle). Engineers must carefully implement these detailed constraints. A practical gotcha is mis-application of a high-level ERP cap (for example seeing 50 kW in many cells) without respecting the specified lower caps for particular narrow sectors and depression angles.
No enforcement or procedural text. The instrument contains no explicit enforcement or procedural provisions. Parties that assume that the technical specification automatically creates enforceable licence conditions and enforcement procedures will be mistaken. Enforcement, penalties and procedural processes must be sourced in the broader licensing framework not included in the document.
TS numbers without dates or versions. Each technical specification is referenced by a TS number, for example TS1132983, TS12000069. The TS numbers have no date, version or amendment suffix in the supplied text. That absence complicates version control: it is unclear whether later or earlier TS documents exist, or whether a TS number has been superseded. Practitioners should verify the current status of a TS number with the issuing body.
Multiple geographic groupings in one file. The file contains both Sydney RA1 data and Canberra attachments (TS12000069/71). The mapping of the later Table 2 to the relevant BSA is not explicit. A reader might mistakenly apply the licence counts or technical parameters for Sydney to Canberra (or vice versa). Do not assume the second Table 2 applies to the same area as the first; verify with the issuing authority.
Nominal coordinates vs practical siting. The attachments use the term "Nominal Location" and list specific GDA94 coordinates. Where attachments also specify site tolerance is "Refer to technical planning guidelines", the nominal coordinates may not be absolute. Operators must confirm allowable deviations. Misreading "nominal" as absolute consent to build at any nearby site is a practical risk.
In summary, the primary "gotchas" are internal inconsistencies in licence counts, the informational-only status of some geographic fields, reserved-block status without procedural explanation, cross-boundary siting advisory notes, reliance on external technical planning guidelines, and absence of enforcement or amendment metadata. Each of these is visible within the document text and merits confirmation with the issuing/licensing authority and with the referenced technical planning guidelines before operational or commercial decisions are taken.