{"id":"F2017L00934","name":"Telecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2017","slug":"f2017l00934","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":439275,"registerId":"F2017L00934-fast-fetch-1775955365934","compilationNumber":null,"startDate":"2026-04-12","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"1","sectionType":"section","heading":"Telecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2017","content":"---\nmeta-content-style-type: text/css\nmeta-content-type: application/xhtml+xml; charset=utf-8\n---\n\n?xml version=\"1.0\" encoding=\"utf-8\" standalone=\"no\"?>\n\n![](image.001.jpeg)\n\n \n\nTelecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2017\n\n \n\n \n\n \n\nI, MITCH FIFIELD, Minister for Communications make the following instrument.\n\nDated 18 July 2017    \n\nMITCH FIFIELD\n\nMinister for Communications\n\n \n\n \n\n \n\nContents\n\n1  Name\n\n2  Commencement\n\n3  Authority\n\n4  Definitions\n\n5  Schedules\n\n6  Specification\n\nSchedule 1—Repeals\n\nTelecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2007 (No. 1)\n\n \n\n \n\n1  Name\n\n  This instrument is the Telecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2017.\n\n2  Commencement\n\n  This instrument commences on the day after this instrument is registered.\n\n3  Authority\n\n  This instrument is made under subsection 285(5) of the Telecommunications Act 1997.\n\n4  Definitions\n\nAct means the Telecommunications Act 1997.\n\ncarriage service provider has the meaning given by section 87 of the Act.\n\nclassified business directory means a public number directory that does not contain information about residential telephone subscribers unless a residential telephone subscriber has agreed with the public number directory publisher that information about the subscriber will be included in the directory (for example, where the public number of the residential telephone subscriber is also used for business purposes).\n\nNote:  Examples of classified business directories include the Yellow Pages® and specialist trade directories.\n\ncustomer includes the nominee of a customer.\n\nintegrated public number database has the meaning given by subsection 285(2) of the Act.\n\nintegrated public number database scheme means the scheme in force under section 295A of the Act.\n\nlisted number means a public number that the customer of a carriage service provider and the provider have agreed to have included in a public number directory, as indicated by the ‘List Code’ in the integrated public number database.\n\npublic number has the meaning given by subsection 285(2) of the Act.\n\npublic number directory has the meaning given by subsection 285(2) of the Act.\n\npublic number directory authorisation has the same meaning as in the Telecommunications (Integrated Public Number Database Scheme – Conditions for Authorisations) Determination 2017.\n\npublic number directory publisher means a holder of a public number directory authorisation issued under the integrated public number database scheme.\n\n5  Schedules\n\n  Each instrument that is specified in Schedule 1 to this instrument is repealed as set out in the Schedule.\n\n6  Specification\n\n  For the purposes of paragraph (e) of the definition of public number directory in subsection 285(2) of the Act, the following requirements are specified:\n\n (a) a public number directory must contain no fewer than 1000 entries;\n\n (b) the entries in a public number directory must not be disaggregated to a level below postcode;\n\n (c) if the public number directory is not a classified business directory, the directory must contain all listed numbers in the relevant geographical area covered by the directory;\n\n (d) if the public number directory is not a classified business directory, the directory must be organised alphabetically by name, according to standard industry practice;\n\n (e) no more than 20 entries may be transferred from a public number directory in a single action;\n\n (f) no more than 100 entries may be generated from a single search of a public number directory that is in electronic form; and\n\n (g) a public number directory that is in electronic form must be encrypted or otherwise electronically protected.\n\nNote:  An example of a way a record may be transferred is the cutting or copying, and pasting of information from a public number directory.\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\nSchedule 1—Repeals\n\nTelecommunications (Integrated Public Number Database – Public Number Directory Requirements) Instrument 2007 (No. 1)\n\n1  The whole of the instrument\n\nRepeal the instrument.\n\n \n","sortOrder":0}],"analysis":{"flash_summary":{"complexity_score":4,"scope_assessment":{"changed":true,"description":"This instrument expressly repeals the 2007 Instrument (Schedule 1) and replaces the specified public number directory requirements by setting new quantitative, organisational and security rules (see Schedule 1; Specification). The practical scope therefore shifts to the new minimum-entry, disaggregation, inclusion, transfer/search limits and encryption requirements laid out in section 6."},"complexity_factors":["Cross-references to the Telecommunications Act 1997 (defined terms rely on subsection 285(2) and authority under subsection 285(5)) introduce dependency on primary legislation for scope and meaning (see Definitions and Authority).","Numeric and operational prescriptions (minimum 1,000 entries; max 20 entries transferable per action; max 100 entries per electronic search) require directory publishers to adapt data structures and UI/export controls (see Specification, paragraph (a), (e), (f)).","Security requirement for electronic directories to be encrypted or otherwise protected is specified without technical standards, creating implementation discretion and potential compliance ambiguity (Specification, paragraph (g)).","Interaction between 'classified business directory' carve-out and obligations to include 'all listed numbers' raises compliance questions for mixed-use numbers and carriage service providers (Definitions; Specification paragraphs (b)–(d)).","Terminology and scope depend on defined terms (public number, listed number, public number directory authorisation), so legal effect hinges on how those definitions in this instrument and related determinations are read (Definitions).","Repeal of the 2007 instrument (Schedule 1) means prior practices may need updating; transitional or enforcement mechanisms are not addressed here, increasing implementation risk for affected publishers (Schedule 1)."],"plain_english_summary":"This instrument sets the rules for what counts as a public number directory under subsection 285(2) of the Telecommunications Act 1997: minimum 1,000 entries; no disaggregation below postcode; non‑classified directories must include all listed numbers and be organised alphabetically; limits on transfers (20 entries per action) and electronic search returns (100 entries); and electronic directories must be encrypted. It applies to public number directory publishers and affects carriage service providers' listed numbers and customers (including nominees), changing how directory data may be copied, searched and published."},"flash_summary_failed":{"failed":true,"reason":"A positive credit balance is required for all requests, including BYOK, so fallback providers remain available. Add credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up to continue.","source":"analysis-cron"},"kimi_summary":{"content_quality":"ok","complexity_score":2,"scope_assessment":{"changed":false,"description":"The instrument maintains its original narrow scope: setting technical specifications for public number directories under the Integrated Public Number Database scheme. It updates the 2007 version but does not expand beyond the original purpose of defining what constitutes a legitimate public number directory."},"complexity_factors":["Short instrument: only 6 operative sections plus a schedule","Minimal defined terms: 9 definitions, mostly referencing existing definitions in the parent Act rather than creating new ones","No nested conditional logic or exceptions to exceptions","Simple structure: definitions, one specification section with 7 straightforward requirements, and a repeal schedule","No cross-referencing maze — primarily refers to section 285(2) of the Telecommunications Act 1997 for core concepts","Plain English drafting with helpful examples (e.g., Yellow Pages as classified business directory, explanation of 'transferring' entries)"],"plain_english_summary":"This instrument defines what counts as a public number directory in Australia and sets minimum standards for publishers, telcos supplying customer data, and users' privacy protections under the Telecommunications Act 1997.  \n\nIt tightens rules for modern (including electronic) directories — size and aggregation limits, encryption/protection, and restrictions on bulk extraction — to prevent mass scraping and highly targeted lists while allowing legitimate directory services to operate."}},"importantCases":[],"_links":{"self":"/api/acts/f2017l00934","history":"/api/acts/f2017l00934/history","analysis":"/api/acts/f2017l00934/analysis","conflicts":"/api/acts/f2017l00934/conflicts","importantCases":"/api/acts/f2017l00934/important-cases","documents":"/api/acts/f2017l00934/documents"}}