Free Word download β’ Edit online β’ Save & share with Drive β’ Export to PDF
An Assumption of Risk on Proposed Name is a legally binding document in which a business entity or individual formally acknowledges that a proposed trade name, corporate name, or brand name may conflict with an existing registered name or trademark, and voluntarily accepts all legal consequences that may arise from proceeding with that name. It functions as both a risk acknowledgment and an indemnification instrument β the applicant releases the approving authority (typically a state registrar, franchisor, or corporate administrator) from liability and agrees to defend it against any third-party claims stemming from the approved name. Unlike a simple consent letter, a properly drafted assumption of risk document includes express representations by the applicant that a name search was conducted, that the name was not selected in bad faith, and that the signatory has authority to bind the entity.
Without a signed Assumption of Risk on Proposed Name, many registrars will refuse to approve a business name that resembles an existing registration β stalling your entity formation entirely. More importantly, proceeding informally without this document exposes the approving authority to contribution claims if a third-party trademark holder later files suit, and it leaves the applicant without a clear record of what risk was disclosed and accepted at the time of registration. If a competitor or brand owner asserts infringement down the line, the absence of a formal acknowledgment makes it harder to demonstrate that the name choice was deliberate and informed rather than negligent. This template gives you a structured, attorney-ready document that satisfies most registrar requirements, creates an unambiguous record of informed consent, and protects both parties in the event a name-conflict dispute escalates β all in the time it takes to fill in a form.
| If your situation is⦠| Use this template |
|---|---|
| Registrar requires written acknowledgment before approving a similar entity name | Assumption of Risk on Proposed Name |
| Applicant also needs to indemnify a third-party trademark holder | Indemnification Agreement |
| Franchisor requires the franchisee to assume name-similarity risk in writing | Franchise Agreement Addendum |
| Company is pursuing a full trademark clearance search and opinion | Trademark License Agreement |
| Entity needs a broader release of all corporate-registration liabilities | General Release of Liability |
| DBA filing requires a name-risk disclosure alongside the assumed-name certificate | Assumed Name Certificate (DBA) |
Why it matters: An acknowledgment that references only 'potential similarities' without naming the specific conflicting name fails to document genuine informed consent and may not satisfy the registrar's submission requirements.
Fix: Insert the exact existing name flagged in the registrar's notice, and attach the similarity report as an exhibit to the signed document.
Why it matters: A document signed by an employee, agent, or officer without documented authority to bind the entity may be voidable, leaving the approving authority without enforceable indemnification protection.
Fix: Confirm the signatory's authority in the signature block, and attach a corporate resolution or operating agreement excerpt if the registrar or approving authority requires it.
Why it matters: Without an explicit disclaimer, applicants have argued that the registrar's approval implied a representation that the name was clear of conflicts, creating unexpected liability for the approving body.
Fix: Include a clause expressly stating that approval of the name does not constitute an endorsement of the applicant's exclusive rights or impose any duty on the registrar to monitor or defend the name.
Why it matters: Phrases like 'if a conflict should arise' or 'in the event of any future claim' introduce conditions that weaken the assumption and may allow the applicant to argue the risk never actually materialized in a qualifying way.
Fix: Draft the assumption as unconditional and present-tense: 'Applicant assumes all risk arising from the use of the Proposed Name, whether or not a claim is ultimately asserted.'
Why it matters: If the applicant selects its home-state law and the registrar is in a different state, enforcement of the indemnification requires cross-jurisdictional litigation, raising costs and uncertainty for both parties.
Fix: Set governing law to the jurisdiction of the registrar β or the jurisdiction where the entity is being registered β and confirm the forum selection clause is consistent.
Why it matters: If a third party later asserts a name-conflict claim, the applicant and the registrar both need the original signed document to prove the scope of the risk assumption and indemnification. A file copy without countersignature may be challenged.
Fix: Obtain a countersigned copy from the registrar or approving authority at the time of submission, and store it alongside the entity's formation documents and name-search records.
In plain language: Identifies both parties β the applicant and the approving authority β and states the exact proposed name that is the subject of the document, along with any reference number assigned by the registrar.
WHEREAS, [APPLICANT LEGAL NAME] ('Applicant') has submitted a request to register the name '[PROPOSED NAME]' (File No. [REFERENCE NUMBER]) with [REGISTRAR / AUTHORITY NAME]; and WHEREAS, [REGISTRAR] has advised Applicant that the proposed name may be similar to one or more existing registered names or marks.
Common mistake: Using a trade name or abbreviated version of the applicant's name instead of its full legal entity name β this creates ambiguity about which legal person is assuming the risk.
In plain language: The applicant expressly states that it has been informed of the potential name conflict, understands the nature of the similarity, and voluntarily chooses to proceed despite that risk.
Applicant acknowledges that [REGISTRAR] has identified a potential similarity between the Proposed Name and the existing name(s) [EXISTING NAME(S)], and that proceeding with registration may expose Applicant to claims of infringement, passing off, or unfair competition.
Common mistake: Omitting the specific existing name or names that triggered the conflict warning. A vague acknowledgment of 'possible similarities' may not satisfy a registrar's requirement or adequately document informed consent.
In plain language: States unambiguously that the applicant is proceeding of its own free will, having had the opportunity to seek independent legal advice, and accepts all risk associated with using the proposed name.
Applicant voluntarily assumes all risk, liability, and legal exposure arising from the registration and use of the Proposed Name, including but not limited to claims by third parties asserting prior rights in the same or a confusingly similar name or mark.
Common mistake: Framing this clause as conditional ('if any conflict arises') rather than unconditional. Conditional language weakens the assumption and may not satisfy the approving authority's standard.
In plain language: Releases the registrar or approving body from any liability resulting from its approval of the proposed name, including any future claims brought against the applicant by third parties.
Applicant releases [REGISTRAR / AUTHORITY NAME], its officers, agents, and employees from any and all claims, damages, losses, costs, and expenses (including attorneys' fees) arising out of or related to the registration or approval of the Proposed Name.
Common mistake: Limiting the release to direct claims only and omitting indirect or consequential damages. A narrow release exposes the registrar to contribution claims if litigation arises.
In plain language: Obligates the applicant to defend and compensate the approving authority β and, where applicable, identified third parties β against any claims, actions, or costs arising from the approved name.
Applicant agrees to indemnify, defend, and hold harmless [REGISTRAR / AUTHORITY NAME] from and against any and all claims, suits, demands, judgments, losses, costs, and attorneys' fees arising from or related to Applicant's use of the Proposed Name.
Common mistake: Drafting the indemnification as one-directional without a mutual defense trigger. Where the registrar is a government body, one-directional indemnification is standard β but private approving authorities sometimes require mutual terms.
In plain language: The applicant warrants that it has conducted a reasonable name and trademark search, has not deliberately chosen the name to trade on another party's goodwill, and has the authority to sign the document.
Applicant represents and warrants that: (a) it has conducted or commissioned a reasonable search of existing business names and trademarks prior to submitting the Proposed Name; (b) it has not selected the Proposed Name with intent to cause confusion with any existing name or mark; and (c) the individual signing below has full authority to bind Applicant.
Common mistake: Omitting the authority-to-bind warranty. If the signatory lacks authority, the entire document may be voidable, leaving the registrar unprotected.
In plain language: Clarifies that the approving authority's acceptance of this document and approval of the name does not create any ongoing duty to monitor, enforce, or defend the applicant's rights in the name.
[REGISTRAR / AUTHORITY NAME]'s acceptance of this Assumption of Risk and approval of the Proposed Name shall not constitute an endorsement of Applicant's exclusive rights to the name, nor impose any obligation on [REGISTRAR] to defend or support Applicant's use of the name.
Common mistake: Leaving this clause out entirely, which can lead applicants to claim the registrar implicitly guaranteed name availability or exclusivity by approving the registration.
In plain language: Specifies which jurisdiction's law governs the agreement and where disputes must be resolved.
This Agreement shall be governed by and construed in accordance with the laws of the State of [STATE], without regard to its conflict-of-laws principles. Any dispute arising hereunder shall be resolved exclusively in the courts of [COUNTY], [STATE].
Common mistake: Selecting a governing law different from the jurisdiction of the registrar. A mismatch creates enforcement complexity if the registrar ever needs to invoke the indemnification clause.
In plain language: Confirms that this document is the complete agreement between the parties on the subject of name-risk assumption and can only be modified in writing.
This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior representations, communications, and understandings. No amendment shall be binding unless in writing and signed by both parties.
Common mistake: Omitting the entire-agreement clause when the applicant has also submitted correspondence or emails promising indemnification. Without it, prior written communications could be construed as supplementary obligations.
In plain language: Provides space for authorized signatures from the applicant and, where required, a countersignature from the approving authority, with printed names, titles, and the execution date.
IN WITNESS WHEREOF, the undersigned has executed this Assumption of Risk on Proposed Name as of [DATE]. [APPLICANT LEGAL NAME] By: ___________________ Name: [SIGNATORY NAME] Title: [TITLE] Date: [DATE]
Common mistake: Having an officer sign without confirming their authority is reflected in a corporate resolution or incumbency certificate. Some registrars reject documents signed by individuals whose authority is not documented.
Use the exact registered legal name of the entity applying β the same name that appears on the formation documents or articles of incorporation. Include the entity type (LLC, Inc., Corp., LP) and the jurisdiction of formation.
π‘ Cross-check the name against your state or provincial business registry to confirm the exact spelling before inserting it into the document.
Enter the full proposed name as submitted to the registrar, including any stylization, punctuation, or entity suffix. Also include the registrar's file or reference number if one has been assigned to the application.
π‘ If the registrar's similarity warning references a specific existing name, include that exact name in the acknowledgment clause β a vague reference is harder to enforce and may not satisfy the registrar's requirements.
Insert the full official name of the registrar, government body, or private authority whose approval is being sought β for example, 'Secretary of State of [STATE]' or '[FRANCHISOR LEGAL NAME].' Avoid abbreviations that could create ambiguity.
π‘ For state registrars, confirm the official name of the division handling business name registrations β it may differ from the office's common shorthand.
List the specific existing name or names flagged by the registrar, describe the nature of the similarity (phonetic, visual, or conceptual), and confirm that the applicant has been advised of the conflict in writing.
π‘ Attach the registrar's similarity notice or search report as an exhibit. Incorporating it by reference strengthens the document's record of informed consent.
Confirm that the indemnification clause covers direct claims, attorneys' fees, and costs β not just final judgments. If the approving authority is a private entity, confirm whether it requires mutual indemnification or a one-way obligation.
π‘ If the applicant is a single-member LLC or sole proprietor, consider whether personal assets are exposed under the indemnification β this is a key question for a legal review.
Check each warranty statement against actual facts: confirm a trademark and name search was conducted, confirm the signatory's title and authority, and confirm that no intent to cause confusion existed in selecting the name.
π‘ Retain a copy of the trademark search report (USPTO TESS, WIPO BRAND, or equivalent) dated before the signing date to support the warranty that a search was conducted.
Enter the state, province, or country where the registrar is located and where the entity is being registered. Confirm that the chosen forum (county and court) is consistent with that jurisdiction.
π‘ For multi-state or cross-border registrations, consider having a lawyer confirm which jurisdiction's law controls β conflict-of-laws issues are common when applicant and registrar are in different states.
Have the document signed by an officer or member with explicit authority to bind the entity β typically a CEO, President, or Managing Member. Attach a board resolution or operating agreement excerpt if the registrar requires proof of authority.
π‘ Date the document on the same day it is signed, not the day it is filed. A signing date that post-dates the filing can raise questions about the document's validity at the time of registration.
An Assumption of Risk on Proposed Name is a legal document in which a business entity or individual formally acknowledges that a proposed business or trade name may be confusingly similar to an existing registered name or trademark, and voluntarily accepts all legal consequences of proceeding with that name. It typically includes a release of the approving authority and an indemnification obligation running in the approving authority's favor. Registrars and franchisors use it to protect themselves from liability while still accommodating an applicant's name preference.
A registrar typically requires this document when a name availability search returns a similar β but not identical β existing registration, and the registrar is willing to approve the application only if the applicant formally accepts the risk of conflict. This commonly occurs when names are phonetically similar, share distinctive words, or operate in overlapping industry sectors. The registrar protects itself from future claims that it improperly approved a conflicting name.
No. Signing an Assumption of Risk on Proposed Name does not clear the name for use or confirm that it is free of trademark conflicts. It documents your acknowledgment that a potential conflict exists and confirms that you β not the registrar or approving authority β bear full responsibility for any legal consequences. A third-party trademark holder can still assert infringement claims against you regardless of what the registrar has approved. A clearance opinion from a trademark attorney is the only way to assess actual infringement risk.
No. A trademark clearance search is a factual investigation β conducted by an attorney or search service β that identifies existing registered and unregistered marks similar to your proposed name. An Assumption of Risk on Proposed Name is a legal agreement executed after a potential conflict has already been identified, in which you accept responsibility for that conflict. The search informs your decision; this document documents it.
Liability depends on how the applicant is structured. If the applicant is a properly formed LLC or corporation, personal liability is generally limited to the entity β unless the individual signed in a personal capacity, the entity is a single-member LLC whose veil may be pierced, or the signatory made representations that were personally false. Review the indemnification clause carefully with a lawyer if your entity's liability protection is not firmly established before signing.
No. This document runs in favor of the approving authority β it protects the registrar or franchisor from liability, not the applicant. It does not create any rights in the proposed name, does not bar third parties from asserting prior trademark rights, and does not constitute a defense to an infringement action. Its sole function is to document the applicant's informed consent and transfer risk from the approving authority to the applicant.
If a third party asserts trademark infringement, passing off, or unfair competition after registration, the Assumption of Risk document confirms that you accepted this risk in writing β it does not shield you from the claim. The registrar or approving authority may use the document to deflect any attempt to hold it responsible. You would need to defend the infringement claim on its merits, potentially including evidence of a prior trademark search, good-faith selection of the name, and market differentiation from the conflicting mark.
Legal review is strongly recommended. The indemnification clause in this document can expose the applicant to substantial costs β attorneys' fees, damages, and defense obligations β if a name-conflict dispute escalates. A trademark attorney can assess the actual likelihood of a successful infringement claim against the proposed name, advise on whether to proceed or modify the name, and ensure the representations and warranties you are making are accurate. For most businesses, a 1β2 hour trademark clearance consultation ($300β$600) is worthwhile before signing.
Yes. Many county clerks and state offices that process DBA or assumed-name filings will request an assumption-of-risk acknowledgment when a proposed DBA is similar to an existing trade name in the same county or state. The document functions identically in that context β the applicant assumes risk, releases the filing authority, and indemnifies it against future claims arising from the approved DBA name.
An Indemnification Agreement is a standalone contract in which one party broadly agrees to defend and compensate another for a defined category of losses. An Assumption of Risk on Proposed Name is narrower β it combines a risk acknowledgment with an indemnification obligation specifically tied to a named business-name conflict. Use the standalone indemnification agreement when the scope of risk extends beyond a single name decision.
A General Release of Liability extinguishes past or future claims broadly between two parties, often in the context of settling a dispute or concluding a business relationship. An Assumption of Risk on Proposed Name is prospective and context-specific β it documents acceptance of a known, ongoing risk rather than releasing claims that have already arisen. The two documents serve different litigation postures.
A Trademark License Agreement grants a licensee the right to use a trademark owner's mark under defined conditions β it creates rights. An Assumption of Risk on Proposed Name does the opposite: it acknowledges the absence of cleared rights and accepts the legal exposure that comes with proceeding anyway. Use a license agreement when a name conflict has been resolved through a deal with the mark's owner.
An NDA protects confidential information exchanged between parties during business discussions. An Assumption of Risk on Proposed Name addresses public legal exposure β trademark and name conflicts β that arise from registering and using a business name. The two documents have no functional overlap; they may be used together when a name is being disclosed to a counterparty under confidentiality before the risk-assumption document is finalized.
Franchisors require this document from franchisees seeking to operate under a location-specific or modified name that resembles another franchisee's approved name within the network.
Law firms, accounting practices, and consulting firms frequently encounter name similarity issues when state bars or professional associations flag near-identical firm names in the same practice area and geography.
Retailers registering trade names for new store concepts or private-label brands must address similarity flags before the name appears on storefronts, packaging, or domain registrations.
Tech startups frequently encounter product and company name conflicts in crowded categories; this document is used when a founder insists on a flagged name before a full trademark clearance opinion is completed.
State secretaries of state may accept or require an assumption-of-risk letter when approving a corporate or LLC name that resembles an existing registration. State-level approval does not protect against federal trademark infringement claims under the Lanham Act. Non-compete enforceability of the name is governed separately by USPTO registration status. California, New York, and Delaware each have distinct standards for name similarity in entity filings.
Corporations Canada and provincial registrars β including Ontario's ServiceOntario and the Registraire des entreprises in Quebec β may require a name-risk consent when a NUANS search reveals a similar existing name. Federal incorporation under the CBCA and provincial incorporation are separate processes; a risk assumption filed federally does not satisfy provincial requirements. Quebec-registered entities must ensure any name assumption document is available in French.
Companies House in England, Wales, Scotland, and Northern Ireland will reject names that are the same as or 'too like' an existing registered company name under the Companies Act 2006. An objection to a similar name can be raised by an existing company within 12 months of registration. Where a name is approved despite similarity, a written assumption of risk supports the applicant's record of informed consent and can be relevant if a complaint is later filed with the Company Names Tribunal.
Business name registration in EU member states is governed by national law; there is no single EU-wide business name register. EUIPO trademark registrations cover the entire EU and can conflict with nationally registered business names in any member state. Companies operating across multiple EU jurisdictions should conduct name searches in each relevant national register and the EUIPO database before executing a risk-assumption document, as the document's enforceability and form requirements vary by member state.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Straightforward registrar filings where the similarity is minor and the business operates in a non-competitive market segment | Free | 20β30 minutes |
| Template + legal review | Applicants whose proposed name closely mirrors an established brand, or where the indemnification exposure is material | $300β$600 for a trademark attorney review | 1β3 days |
| Custom drafted | Franchise networks, regulated industries, or cross-border name registrations where multi-jurisdictional trademark exposure is significant | $800β$2,500+ | 1β2 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Free Forever PlanΒ Β·Β No credit card required
