Business Names Registration (Availability of Names) Determination 2015

The Determination relies on a small set of legal concepts and implements them by concrete heuristics. Those concepts are availability (as referenced in the Act), identity or near‑identity, undesirability, restricted words and the allocation of decision‑making to named Ministers or agencies.

Availability and identity: The Determination tells ASIC how to decide whether a proposed business name is "identical or nearly identical" to another name. For non‑company names, that determination is made by first disregarding matters listed in s 5 (articles, corporate suffixes, punctuation, order of words, domain prefixes and so on), then applying the sameness rules in s 6 and Schedule 1, and finally considering whether the post‑disregard names are the same or whether they may be pronounced the same (s 5A). For company names, s 7 imports the comparison rules of Part 1 of Schedule 6 to the Corporations Regulations 2001, aligning business name comparisons with the longer‑standing company name rules in corporate regulation.

Words taken to be the same: Schedule 1 lists items of commonly used trade, descriptive and stylistic words that are treated as equivalent for identity comparisons. Examples include numeric‑word equivalences (eg 100 and one hundred), symbol‑word equivalences (eg % and percent, @ and at), common service descriptors (eg cafe/caffe/cafe bar listed at item 149), and many sectoral synonyms (eg solicitor/law/legal at item 189). Section 6 declares that words and expressions in the same Schedule 1 item are to be taken as the same, and it also treats pronunciation as a ground for sameness (s 6(2)).

Undesirable names: Section 8 sets out categories of undesirable names, where ASIC's opinion that a name is likely offensive or falsely suggests a connection to particular persons or institutions (from the Crown to named historical figures and the United Nations) can make a name undesired. Section 8 includes a geographical‑use safeguard for "Commonwealth" and "Federal" where used as place names.

Restricted words and consent: Part 4 and Schedule 2 create a two‑tier set of restrictions. Schedule 2 Part 1 contains words that are restricted unless the Minister has given written consent (s 9); Part 2 lists words that need the consent of a specifically named Minister for that word (s 10(1) and Schedule 2 Part 2); Part 3 lists financial and related terms that require consent of the relevant public authority or agency, principally APRA (s 10(3) and Schedule 2 Part 3). The Determination extends these restrictions to similar‑meaning words, abbreviations and non‑English equivalents (ss 9(2) and 10(4)-(5)), and records a narrow exception: letters "ADI" are not restricted when they appear as part of another word (s 10(6)(b)).

Decision‑makers and subjectivity: ASIC is given a role where the Determination expressly defers to "the opinion of ASIC" for offensiveness and contextual connection questions (s 8(1)). Ministerial and agency consents are required for a subset of restricted words, and s 10(7) specifies a procedural detail: written consent need not expressly name the word or refer to business names, which expands administrative discretion over what counts as consent.

Terminology linkage: The Determination refers back to definitions in s 3 of the Act for terms such as ASIC, available, business name and entity (s 3 note). It defines certain terms itself, including APRA, company name and character (s 3). The instrument therefore operates as a rulebook that interprets statutory phrases into operational comparisons and approval processes.

Directly affected parties are applicants seeking to register a business name, current business name holders and intermediaries who advise or file registrations. The Determination governs whether ASIC may accept a business name application under the Business Names Registration Act 2011 by specifying what counts as identity, undesirability and restricted wording.

Applicants: Any person or entity proposing to register a business name must test proposed names against the Determination. This includes sole traders, partnerships, companies, trusts and other entities that register trade or service names under the Act. The rules in Part 2 apply to comparisons with other business names and with company names (s 4(1) and s 7). Applicants using stylised branding, symbols, numerals, slang spellings or domain aspects must account for s 5 and s 6, which treat punctuation, capitals, spaces and pronunciation as potentially non‑distinctive.

Existing name holders and competitors: The Determination affects competitive dynamics because Schedule 1 equivalences and the disregarded matters in s 5 materially expand the set of names treated as identical or nearly identical. An existing holder may be able to block a later applicant on grounds of near‑identity created by the Schedule 1 mappings or pronunciation rules (s 6(2)). Conversely, existing holders who rely on minor typographical or domain‑level differences to distinguish themselves may discover that those differences are disregarded.

Public authorities and Ministers: The Determination assigns specific consent powers. Certain words in Schedule 2 Part 2 require written consent of named Ministers (eg "Anzac" requires consent of the Minister for Veterans’ Affairs, Schedule 2 Part 2 item 201). Words in Schedule 2 Part 3 require consent of named public authorities or agencies,APRA is the named authority for financial terms including "bank" and "authorised deposit‑taking institution" (Schedule 2 Part 3 items 301-309). The Determination therefore obliges Ministers and agencies to have internal consent processes and to respond to requests, which creates an administrative interface between applicants and particular portfolio holders.

Regulatory administrators: ASIC is the primary decision‑maker for availability and for undesirability assessments (s 8(1) uses the phrase "in the opinion of ASIC"). APRA and the specified Ministers are gatekeepers for restricted terms. The Determination thereby divides responsibility: ASIC enforces the availability rules, while named Ministers and agencies supply or withhold the consents that render some restricted words permissible.

Indirectly affected groups: Businesses that brand with names evoking government, charities, royal patronage, or named cultural figures must consider s 8 because a proposed use that suggests a non‑existent connection can render a name undesirable. Likewise, overseas entities or foreign companies seeking to register Australian business names must be aware that comparisons with company names are made by applying corporate regulations (s 7), and that several Schedule 2 items relate to foreign company descriptors.

Costs and burdens fall to applicants and to the public authorities that must respond to consent requests. Applicants face search, documentation and processing time costs; Ministers and agencies must develop and adhere to consent procedures. ASIC bears the administrative burden of applying the Determination’s tests and exercising judgement where the Determination permits opinion‑based decisions.

The Determination does not create freestanding criminal obligations; it prescribes tests that ASIC must apply under the Business Names Registration Act 2011. Nevertheless, it creates clear duties for decision‑makers and practical rights for applicants and other consent‑holders.

ASIC’s duties and discretions:

• When determining availability under s 26 of the Act, ASIC must apply the comparison rules set out in Part 2. For non‑company name comparisons, that means applying s 5 to disregard certain features, then treating Schedule 1 items as the same under s 6, and applying s 5A to decide identity or near‑identity.
• ASIC must determine whether a name is "undesirable" by reference to the characteristics listed in s 8. That provision explicitly accords ASIC an evaluative role: s 8(1) frames the first characteristic as "In the opinion of ASIC, it is likely to be offensive to" certain groups.
• For company‑name comparisons, ASIC is obliged to apply the rules in Part 1 of Schedule 6 to the Corporations Regulations 2001, as if those rules had been made for subparagraph 25(a)(ii) of the Act (s 7).

Ministerial and agency duties and rights:

• Ministers named in Schedule 2 Part 2 have the right to give written consent that authorises use of specified words. For example, the Minister for Veterans’ Affairs is the consenting Minister for "Anzac" (Schedule 2 Part 2 item 201).
• APRA has the right to give consent for the use of banking and deposit‑taking terms listed in Schedule 2 Part 3 (items 301-309). Section 10(3) obliges applicants to obtain the written consent of the identified public authority for those terms.
• Section 10(7) gives a practical procedural liberty to consenting authorities: a written consent "does not need to refer specifically to the use of the word or expression in the name, or in business names generally." That enlarges what counts as valid consent, though it also creates evidentiary questions for applicants.

Applicants’ obligations and entitlements:

• Applicants must ensure that a proposed name is not identical or nearly identical to another name, and not undesirable, and that it does not include restricted words without the necessary written consent. The Determination explains what constitutes "the same" (s 5A, s 6 and Schedule 1), and what requires consent (s 9 and s 10).
• Applicants have a right to seek consent from the relevant Minister or agency where a word is restricted. The Determination does not preclude an applicant from seeking judicial review of refusal decisions under the Act, but it does not itself set appeal routes or remedies.

Specific interpretative duties:

• Under s 5(1)(f), ASIC must disregard a host name such as "www" and domain extensions such as "net", "org" and "com" when comparing names. That duty prevents applicants from relying on domain suffixes to create distinctiveness in the business name register.
• Section 6(2) requires ASIC to consider phonetic equivalence. A proposed stylised spelling that sounds the same as an existing name may be treated as identical even when the characters differ, as the illustrative examples demonstrate.

Rights to non‑application:

• Section 9(4) creates an entitlement for entities that, by reason of their incorporation or registration under a particular Act, must include certain words in their business name. Where a business must include a word because the law of its incorporation requires it, that word is not treated as restricted under items 113, 117, 123, 135, 141, 142 or 143 of Schedule 2. The Determination therefore recognises prevailing legal obligations that could otherwise clash with the restricted‑words regime.

Procedural implications:

• Section 10(6)(a) and s 8(2) provide narrow exceptions for geographical usage of restricted words; for example, "Commonwealth" or "Federal" used in a geographical context is not undesirable under s 8(2). These clauses impose an interpretative obligation on ASIC to consider context.

In short, the Determination imposes duties on ASIC to apply precise comparisons and to exercise opinion in some contexts, grants Ministers and agencies authority to grant or withhold consents for certain restricted words, and requires applicants to secure those consents where relevant before a name will be treated as available.

The Determination does not itself create or specify penalties; it is an availability and interpretative instrument that informs the operation of the Business Names Registration Act 2011. Enforcement mechanisms and sanctions for misuse of business names, fraudulent registration, or other contraventions are matters for the primary Act and any other applicable legislation. The Determination repeatedly cross‑refers to the Act for substantive consequences: s 4 situates the Determination as the rules for ss 26-28 of the Act, which are the provisions governing availability, undesirability and restricted words.

What the Determination does affect for enforcement purposes:

• It defines the operational tests ASIC must apply to decide whether to accept a registration. If ASIC refuses an application under the Act on the basis that the name is identical or nearly identical (as assessed under Part 2), or undesirable (as characterised in s 8), that refusal is an administrative action based on the Determination. Any statutory enforcement or remedial process for such refusal follows the Act and general administrative law principles rather than penalties contained in the Determination itself.
• The Determination sets the prerequisites for written consent that make a restricted word permissible. If a person uses a restricted word in a business name without the necessary consent, the Act prescribes ASIC's powers and potential consequences. The Determination clarifies when consent is needed by listing the relevant words and specifying the consenting authority (ss 9-10 and Schedule 2). The Act governs the legal effect of registering without consent and any potential liability.

Administrative compliance and remedies:

• Wrongful registration that contravenes the Act, as interpreted via the Determination, may lead to ASIC deregistering or refusing to accept a name, but where sanctions or remedies apply those derive from the Act. For example, where a name falsely suggests government connection (s 8(1)(2) categories), ASIC may refuse registration under s 27 of the Act; remedies and offences for fraudulent or misleading conduct are handled under the relevant primary legislation and general law.

Practical enforcement risk:

• Because the Determination makes several assessment points subjective (notably "in the opinion of ASIC" in s 8(1)), enforcement outcomes may depend on ASIC's discretionary assessment. This creates a litigation risk for applicants who dispute ASIC's view; however, the Determination itself does not list appeal or penalty processes. Applicants challenging ASIC decisions would need to turn to the administrative law framework and the remedies available under the Business Names Registration Act 2011.

Consent evidentiation:

• Section 10(7) states a written consent does not need to refer specifically to the use of the word in business names. That affects enforcement and evidentiary practice because an applicant relying on a purportedly valid consent may have to demonstrate that the consent, while not specific, nonetheless authorised the use in a registration context. The Determination therefore influences how ASIC and consenting authorities document and treat grants of permission.

In short, enforcement actions and penalties are exercised under the Act using the Determination as the authoritative interpretative guide. The Determination creates the substantive gates and criteria that ASIC enforces, while sanctions and remedies remain within primary legislation and general administrative law.

The Determination explicitly cross‑references and imports rules from other instruments and statutes. Its operation is therefore interdependent with the Business Names Registration Act 2011, the Corporations Regulations 2001 and consent regimes administered by other Commonwealth authorities, principally APRA and relevant Ministers.

Primary statute interaction:

• The Determination is made under, and for the purposes of, the Business Names Registration Act 2011. Section 4 links the Determination to specific provisions of that Act: determining identity/near‑identity for s 26, kinds of undesirable name for s 27, and restricted words for s 28. Consequently, the Determination has legal effect only insofar as it operationalises those statutory provisions; any enforcement, penalties or appeals remain governed by the Act.

Corporate regulation interaction:

• Section 7 imports Part 1 of Schedule 6 to the Corporations Regulations 2001 for comparisons involving company names. That Part sets out matters to be disregarded when comparing company names for purposes of paragraph 147(1)(a) or (b) or 601DC(1)(a) or (b) of the Corporations Act 2001. By instructing ASIC to apply those rules "as if they had been made for subparagraph 25(a)(ii) of the Act", the Determination aligns business name/company name comparison methodology with corporate name rules, thus avoiding inconsistent treatments between company and business‑name registers.

Administrative law and consent regimes:

• The Determination makes a list of words that are restricted unless written consent is given by a Minister (s 9 and Schedule 2 Part 2) or a specified public authority or agency (s 10 and Schedule 2 Part 3). This creates a procedural overlap between corporate name registration and portfolio‑specific regulatory consent regimes. For example, use of "bank" or "authorised deposit‑taking institution" triggers APRA's consent under Schedule 2 Part 3 (items 301-309). Use of "University" triggers the consent of the Minister for Tertiary Education, Skills, Jobs and Workplace Relations (Schedule 2 Part 2 item 204). Those Ministerial or agency consents are separate administrative acts under other statutory responsibilities; the Determination requires applicants to obtain them for business name availability but does not substitute ASIC for those bodies.

Other Commonwealth, State and Territory laws:

• The Determination includes a note that other Commonwealth, State or Territory laws may limit trading under names containing specified words or expressions and that such limits do not make a word restricted under this Determination unless it appears in Schedule 2 (s 9 note). That indicates the Determination accepts parallel regulation and does not seek to preclude local licensing or naming restrictions; businesses may need to comply with additional naming or trade restrictions beyond what this Determination enforces.

Interpretation and evidence law:

• Section 6 treats pronunciation as a criterion for sameness. Pronunciation as a legal test interacts with evidence rules, hearsay issues and contested factual inquiries in administrative review or litigation. Similarly, s 10(7) (that written consent need not mention business name use specifically) interacts with administrative evidentiary practice, because what qualifies as consent will be an interpretative question under administrative law.

Regulatory perimeter and incorporated entities:

• Section 9(4) establishes that certain words in Schedule 2 are not restricted if, by virtue of the Act under which an entity is incorporated or registered, the word must be included in the business name. This cross‑references corporate and incorporation statutes and ensures that mandatory descriptors required by other Acts are not blocked by this Determination.

In sum, the Determination is an interpretative and procedural bridge between the Business Names Registration Act and other statutes and administrative regimes. It prescribes how ASIC should translate statutory phrases into operational decisions and how third‑party consents under other laws interact with registering business names under the Act.

The compilation and endnotes attached to the Determination summarise its amendment history. The instrument was originally registered as the Business Names Registration (Availability of Names) Determination 2015 and commenced on 18 July 2015 (Endnote 3). Two subsequent instruments amended the Determination: the Treasury Laws Amendment (Miscellaneous Amendments) Instrument 2020, registered 27 November 2020 and commenced 28 November 2020; and the Treasury Laws Amendment (Miscellaneous Amendments No. 1) Instrument 2022, registered 25 November 2022 and commenced 26 November 2022 (Endnote 3). The compilation date for the version provided is 26 November 2022.

Endnote 4 records provision‑level amendment history. It shows:

• that section 2 was affected (noted as "rep s48D LA" in the amendment history), which indicates an editorial or technical replacement arising from the Legislation Act 2003 machinery;
• that specific items in Schedule 1 and Schedule 2 were amended: the entry "Schedule 1 table item 190 Schedule 2 Part 1 | am F2022L01520 am F2020L01485" indicates that Schedule 1 item 190 and the corresponding Schedule 2 Part 1 item were amended by the 2020 and 2022 Treasury Laws Amendment Instruments. The endnotes do not describe the textual nature of those amendments in this compilation; they record the amending instruments and their commencement dates.

The Determination itself notes in its preliminary section that the compilation includes amendments up to the Treasury Laws Amendment (Miscellaneous Amendments No. 1) Instrument 2022 and that uncommenced amendments, if any, are identified in the endnotes. The endnotes further explain that misdescribed amendments may be incorporated editorially where appropriate under s 15V of the Legislation Act 2003, and they provide an abbreviation key for reading the amendment notes.

Practitioner consequences of the amendment history:

• Users of the Determination must be attentive to the amendment record because the list of taken‑to‑be‑same words (Schedule 1) and the list of restricted words (Schedule 2) have been updated since 2015. The Endnote entries identify the amending instruments and dates, which gives rise to a duty for practitioners to check the version history when advising clients on name availability, particularly for items that were amended in 2020 and 2022.
• The 2020 and 2022 amendments imply that the instrument is responsive to policy adjustments, but the endnotes do not provide policy rationales. For precise textual changes to particular Schedule items (for example item 190 in Schedule 1), practitioners must consult the consolidated legislation text on the Federal Register of Legislation or the specific amending instruments cited in Endnote 3 to see the exact alterations.

In short, the Determination has a clear amendment trail: original instrument in 2015, amendments in 2020 and 2022, and an up‑to‑date compilation as at 26 November 2022. The endnotes supply the primary references to the amending instruments and their commencement dates.

The Determination itself does not include a litigation history section and does not cite any cases. Its endnotes (Endnotes 1-4) record compilation and amendment history only; they do not record any judicial decisions that have interpreted the Determination. The instrument contains no references to court or tribunal decisions.

Implications for practitioners:

• Because the Determination is an administrative rulebook that operationalises ss 26-28 of the Business Names Registration Act 2011, legal disputes about name availability, undesirability or consent will commonly arise under the Act and be litigated, if at all, in administrative law contexts. Any judicial interpretations of the Determination would be found in decisions addressing ASIC decisions under the Act, and that material is not recorded in the Determination itself.
• Where applicants or name holders have contested ASIC refusals or consent denials, case law may develop that interprets the Determination’s provisions such as the pronunciation rule in s 6(2), the set of disregarded matters in s 5(1), the Ministerial consent clauses in ss 9-10, or the scope of the "in the opinion of ASIC" tests in s 8. The compilation provided does not capture such litigation.

Recommended practitioner steps:

• In advising clients, check contemporary case law and administrative decisions that interpret the Determination, because the instrument’s tests are fact‑sensitive and administrative outcomes may be shaped by judicial interpretation. The absence of litigation history in the instrument requires practitioners to look beyond the Determination to the Business Names Register decisions, tribunal reviews and court judgments, if available, to understand how subjective or borderline cases have been resolved in practice.

Because the instrument itself is silent on litigation, the compilation cannot identify precedent or disputes; practitioners must supplement the Determination with searches of administrative and judicial databases for any cases applying or construing its provisions.

The Determination contains a number of rules that can produce counter‑intuitive outcomes. Close attention to the textual tests and schedules will avoid common traps.

1. Stylised and symbolic branding is risky. Section 5(1)(d) requires disregarding the size, type, case, accents, spaces and punctuation marks; s 5(1)(f) disregards host names and domain extensions. Combined with s 6(2) (pronunciation equivalence) and Schedule 1 mappings, a stylised mark such as "Creative@Work" may be treated as the same as "Kre8tive at Work" (example in s 6). Don’t assume that atypical characters, punctuation, caps or domain suffixes protect distinctiveness.

2. Pronunciation is a legal test. Section 6(2) states that a name may be identical or nearly identical if it may be pronounced the same as another name. The Determination gives examples such as "100% Cats" and "100 percent Kats". That creates evidentiary risk: a client’s intentionally unusual spelling may lose on oral‑based equivalence.

3. Order of words and plurals do not help. Section 5(1)(e) disregards the order of words, and s 5(1)(c) disregards plural vs singular. The register treats "A B" and "B A" as the same and "Lawn Care" as the same as "Lawn Cares" in the relevant contexts.

4. Large lists of equivalences. Schedule 1 contains hundreds of mappings that equate common trade descriptors and synonyms. For example, "coffee shop", "coffee bar", "coffee house" are grouped (item 159), and "lawyers", "legal", "legal services", "solicitors" are in item 189. A name containing any equivalent may be blocked as identical or nearly identical to an established name.

5. Domain and internet differences are ignored. Section 5(1)(f) explicitly removes domain extensions from consideration. Registering "example.com" as a business name variation is not a reliable differentiator.

6. Ministerial and agency consent is not mechanical and may be slow. Schedule 2 lists words that need written consent from Ministers (Schedule 2 Part 2) or APRA (Part 3). Section 10(7) allows consents that do not expressly refer to business name use, but that increases the administrative ambiguity of what counts as adequate consent. Applicants should expect procedural delays and should obtain documented consents before relying on availability.

7. Narrow exceptions that may not cover intended use. Section 8(2) and s 10(6)(a) provide that "Commonwealth" or "Federal" or Part 3 words used in a geographical context are not undesirable or restricted. Practitioners must evidence the geographic context; an attempt to argue geographic use without supporting materials risks rejection.

8. Certain corporate descriptors are only de‑restricted where required by incorporation law. Section 9(4) states that words in Schedule 2 items 113, 117, 123, 135, 141, 142 or 143 are not restricted if the entity must include them because of the Act under which it is incorporated or registered. That does not give a general right to those words; it only prevents the Determination from blocking words that other Acts mandate.

9. ADI letters exception limited. Section 10(6)(b) says the letters ADI are not restricted if used as part of another word. That avoids over‑broad restriction (eg "traditional" contains adi), but it does not mean a standalone "ADI Bank" is permissible without APRA consent (see Schedule 2 Part 3 items 301-309).

10. Subjective offensiveness test. Section 8(1)(1) makes offensiveness a matter of ASIC's opinion. That creates uncertainty and opens potential for differing outcomes between applications. Practitioners should prepare submissions that address likely public perceptions and provide context.

11. Consent evidentiary ambiguity. Because s 10(7) states that written consent need not refer specifically to the use of the word in business names, a consent given under another statute or in another document may be treated as adequate. This increases the administrative discretion and potential for disputes about whether consent was effectively granted for business name registration.

12. Company name comparisons may follow different rules. Section 7 imports the Corporations Regulations approach for comparison with company names, which has its own disregarded matters and conventions. An applicant must therefore run both sets of rules when assessing risk of company‑name conflict.

Being mindful of these traps, and documenting contextual facts (eg geographic use, consent letters, evidence that a stylisation is used in a distinct commercial sphere), reduces the risk of rejection or post‑registration challenge.

Practically, applicants and advisers should adopt a stepwise compliance workflow that mirrors the Determination’s structure so that name searches, consent requests and applications are aligned with the prescribed rules.

1. Pre‑search against Schedule 1 and the register:

• Conduct a thorough textual and phonetic search of existing business names and company names. Apply the rules in s 5: ignore articles, company suffixes (eg "Ltd", "Pty"), punctuation, spacing, case, plurals, word order and domain prefixes/extensions when comparing. Use Schedule 1 as a direct mapping: for any candidate word, check whether it appears in a Schedule 1 item and treat all entries in that item as equivalent (s 6(1) and Schedule 1). Remember that characters and groups separated by spaces are treated as words for the purpose of order and equality rules (s 5(2) and s 6(3)).

2. Test phonetics:

• Read proposed names aloud and compare their likely pronunciation to existing names. Section 6(2) requires assessing whether despite different characters the names may be pronounced the same. Include common phonetic variants and stylised spellings in your search (eg "Kre8tive" v "Creative").

3. Check company name conflicts:

• For potential conflicts with company names, use the company‑name comparison rules imported by s 7 via Schedule 6 Part 1 to the Corporations Regulations. This is a distinct set of disregarded matters; make sure your search process applies both the Determination’s non‑company rules and the Corporations Regulations’ company rules.

4. Identify restricted words and obtain consents:

• Check Schedule 2. If the proposed name contains a word listed in Schedule 2 Part 1, determine whether ministerial consent is required under s 9 and, if so, which Minister is identified in Schedule 2 Part 2 for particular words. For financial terms in Schedule 2 Part 3, identify the public authority named (eg APRA for "bank", "ADI" etc) and request written consent from that authority (s 10(3) and Schedule 2 Part 3). Remember ss 9(2) and 10(2) extend to similar meaning words and abbreviations; s 10(5) also covers non‑English characters and words embedded in longer expressions. Because s 10(7) allows consents that do not expressly mention business name use, obtain written confirmation that explicitly authorises the specific business name where possible to reduce later evidentiary disputes.

5. Document geography or compelled inclusion defenses:

• If relying on the geographical exception for "Commonwealth" or "Federal" (s 8(2)) or the non‑restriction of certain words where incorporation law mandates inclusion (s 9(4)), assemble documentary evidence showing the geographic use or the incorporation requirement. For example, if the name contains "Commonwealth" because the business is located on Commonwealth Avenue, include maps or addresses that make the geographical context clear.

6. Avoid relying on domain differences or stylisations:

• Do not rely on adding ".com" or similar to create distinctiveness: s 5(1)(f) excludes domain extensions from the comparison. Similarly, avoid assuming that punctuation, capitals or accenting will create separation,s 5(1)(d) disregards these features.

7. Prepare narrative submissions for ASIC:

• Where a proposed name approaches the offensive/connection boundaries in s 8, provide a contextual submission to ASIC explaining usage, audience, and any mitigating factors. Because s 8 gives ASIC an opinion‑based role, well‑documented context can shape the outcome.

8. Timing and administrative process:

• Build time into the project plan for obtaining Ministerial or agency consents. Identify the consenting authority early, contact them about their evidence or application requirements, and request written consent that expressly refers to the name to avoid ambiguity even though s 10(7) does not require such specificity.

9. Evidential practice for consents:

• Secure and retain written consents in their original form. Because s 10(7) allows broader forms of consent, note any document that could be taken as granting consent and, if practical, seek a specific confirmation that the consent is intended to allow use as a business name.

10. Post‑registration monitoring:

• Monitor the register and any related corporate name registrations to ensure no subsequent company registrations or business name registrations create a plausible basis for a near‑identity claim. If disputes arise, be prepared to engage in administrative review under the Act.

11. Professional advice:

• Given the interpretative and subjective elements in the Determination (notably pronunciation and ASIC’s opinion on offensiveness), obtain legal advice where a name is borderline. The Determination’s tests are fact‑sensitive and often turn on context.

12. Recordkeeping:

• Keep a compliance file that records searches, consent communications, evidence of geographic or incorporation‑based exceptions, and internal reasoning on pronunciation or equivalence. This file is valuable if ASIC questions the registration or in any subsequent dispute.

Following these steps aligns application practice with the Determination’s textual requirements and reduces the administrative and legal risk of refusal or later enforcement action.