What this toolkit is for, and who should use it

"Freedom to operate" (FTO) asks a deceptively simple question: Can we sell this product, under this name, using this code, without infringing someone else's intellectual property? Owning your own patents, trademarks, and copyrights does not answer it. A patent gives you the right to exclude others, not an affirmative right to practice—your product can be fully covered by your own patent and still infringe a competitor's. Clearance is the discipline of finding the blocking rights before you are committed, when you can still design around them, license them, or change course cheaply.

This toolkit maps clearance across all four IP families. It is written for product and brand teams and founders who need to understand what clearance buys them; in-house counsel coordinating a launch; and outside counsel running the searches and writing the opinions. It is a navigation guide—each stage hands you to the deep-dive article or the operational search checklist.

A word on calibration: clearance is a risk-management exercise scaled to stakes. A garage startup launching a low-revenue app does not need the exhaustive FTO study a medical-device maker needs before a nine-figure product launch. The art is matching depth and cost to exposure.

Roadmap at a glance

  1. Decide to clear — why pre-launch clearance is cheaper than litigation.
  2. Patent FTO — search live, in-force claims; map your product to them.
  3. Trademark clearance — make sure the name is available and won't confuse.
  4. Copyright & open-source clearance — content, code, and license obligations.
  5. Opinions & willfulness — defuse enhanced-damages exposure after Halo.
  6. Design-around — engineer or rebrand around blocking rights.
  7. Manage ongoing risk — clearance as a repeating process, not a one-time gate.

Stage 1 — Decide to clear: why pre-launch clearance pays

The economics are stark. Changing a product feature, swapping a brand name, or replacing an open-source dependency before launch costs a design review and some engineering hours. Discovering the same problem after launch can mean an injunction, recall, rebrand across all packaging and marketing, a damages award, and—if the infringement was willful—up to treble damages and attorney's fees. Clearance front-loads cheap decisions to avoid expensive ones.

Clearance also produces strategic intelligence: it reveals competitors' patent thickets, white space for your own filings, and licensing opportunities. Scope each clearance project deliberately: define the product/brand/code, the relevant markets and jurisdictions, the technical features at issue, the budget, and the launch timeline. Under-scoping wastes money; over-scoping delays launch.

There is also a hard truth about knowledge. Once you know of a blocking patent, you cannot un-know it, and willful-infringement exposure can attach if you proceed without a basis to believe you do not infringe (see Stage 5). This is why some companies historically avoided patent searches altogether—the "ostrich" strategy. That instinct is largely obsolete: the law (35 U.S.C. § 298) bars using the absence of an opinion against you, and a disciplined clearance process paired with a non-infringement or invalidity opinion converts knowledge from a liability into a shield. Clear deliberately and document the analysis; do not bury your head.

Illustration. A hardware startup is two weeks from a product launch when a board member asks, "Did we check whether this infringes anyone's patents?" A rushed search turns up a competitor's patent that reads on the core feature. Because the team built in a clearance gate at the design stage, the same discovery six months earlier would have cost a minor redesign; at launch minus two weeks it costs a delayed launch, emergency opinion work, and an anxious board.

Resources

Stage 2 — Patent freedom-to-operate search

A patent FTO (also called a clearance or right-to-use search) looks for unexpired, in-force patents whose claims your product would practice. This differs from a patentability search (which looks at all prior art, expired or not, to assess whether you can get a patent). For FTO you care about live claims in your target jurisdictions.

The workflow: deconstruct the product into its technical features and functions; search by classification (CPC), keyword, assignee, and citation chaining; narrow to live patents in your markets; then do claim-by-claim mapping—FTO turns on the claims, not the title or abstract. A feature that reads on even one independent claim is a hit. For each hit, assess validity (is there invalidating prior art?), whether it is in force (maintenance fees paid? expired?), and design-around options.

A critical and often-misunderstood point: U.S. patent infringement requires that an accused product practice every element of at least one claim (the "all-elements rule"). If your product omits even a single limitation of an independent claim, it does not literally infringe that claim—though the doctrine of equivalents may still capture insubstantial substitutions. This is why claim mapping must be element-by-element, not impressionistic. Read the independent claims first (they are broadest); dependent claims add limitations and are narrower, so if you clear the independent claims you generally clear their dependents.

Triage the hits. Not every live patent that mentions your field is a real threat. Sort hits into: (a) clear non-infringement (missing claim elements), (b) genuine concern requiring opinion-level analysis, and (c) patents that appear valid and infringed, demanding a design-around, a license, or an invalidity challenge. Concentrate the expensive lawyering on category (b) and (c).

Use multiple databases, because no single one is complete:

  • USPTO Patent Public Search (replaced PatFT/AppFT) — U.S. patents and applications.
  • Espacenet (EPO) — broad international coverage with machine translation.
  • Google Patents — fast full-text search and family/citation views.
  • WIPO PATENTSCOPE — PCT applications and national collections.

Resources

Stage 3 — Trademark clearance

Before committing to a brand name, logo, or slogan, clear it. Trademark clearance asks whether your proposed mark is (1) available—not confusingly similar to a prior user's or registrant's mark for related goods/services—and (2) protectable—distinctive enough to register and enforce. A likelihood-of-confusion conflict can force a costly rebrand or trigger an opposition or infringement suit.

The workflow runs from a quick knockout search (identical and near-identical marks in the relevant classes) to a comprehensive/full search covering the federal register, state registers, common-law uses, domain names, and business names, often with a professional search vendor. Analyze hits under the multi-factor likelihood-of-confusion standard. Note the post–January 18, 2025 USPTO environment: the cloud-based Trademark Search tool replaced TESS, and filings now go through the Trademark Center.

Two clearance traps recur. First, common-law rights: a senior user who never registered can still block you in its geographic trading area under the Tea Rose–Rectanus doctrine, so a clean federal register is not a clean bill of health—search beyond the register. Second, related goods: confusion is judged by the relationship between the goods/services, not just the literal class. A mark cleared in your filing class can still conflict with a registrant in an adjacent class whose goods consumers would assume share a source. Calibrate the search to the real-world commercial overlap, not the administrative class boundaries.

Illustration. A beverage startup clears "SUMMIT" on the federal register for soft drinks and launches, only to receive a cease-and-desist from a regional craft brewery that has sold "Summit" beer in three states for a decade without ever registering. The federal-only search missed a senior common-law user with enforceable rights in its territory.

Resources

Stage 4 — Copyright and open-source clearance

Two distinct exposures live here. Copyright clearance covers content you reproduce, adapt, or distribute—photos, music, text, fonts, video, third-party assets. Confirm you have a license or that use is otherwise permitted; do not assume "found on the internet" means free.

A practical wrinkle in copyright clearance is the chain of rights. A stock-photo license, for example, may permit web use but not merchandise; a font license may cover desktop use but not embedding in an app; a freelancer's deliverable may not have transferred copyright at all absent a written work-made-for-hire or assignment clause. Confirm not just that a license exists but that it covers your actual use, and that the licensor had the rights it purported to grant.

Open-source software (OSS) clearance is often the larger risk for technology products. Modern software is assembled from hundreds or thousands of open-source components, each carrying license obligations. Permissive licenses (MIT, BSD, Apache 2.0) impose modest attribution duties; copyleft licenses (GPL, LGPL, AGPL) can require you to disclose and license your own source code under the same terms when you distribute—an existential problem for a proprietary product if triggered inadvertently. Generate a software bill of materials (SBOM), inventory every component and its license, identify conflicts and copyleft triggers, and remediate before launch. License compatibility is enforceable: in Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008), the Federal Circuit held that violating open-source license conditions can constitute copyright infringement, not merely breach of contract.

Resources

Stage 5 — Opinions of counsel and willfulness

Clearance is also a shield against enhanced damages. Patent infringement is enhanceable up to three times the award where the infringement is willful (35 U.S.C. § 284). In Halo Electronics, Inc. v. Pulse Electronics, Inc., 579 U.S. 93 (2016), the Supreme Court swept away the rigid Seagate test and gave district courts discretion to enhance damages for egregious, willful misconduct—judged by the infringer's subjective culpability at the time of the challenged conduct.

This is where a competent, documented clearance investigation and a well-reasoned opinion of counsel (concluding non-infringement, invalidity, or unenforceability) earn their keep: good-faith reliance on such an opinion is strong evidence against willfulness. Note the cross-currents: there is no affirmative duty to obtain an opinion (35 U.S.C. § 298 bars using the absence of an opinion to prove willfulness or inducement), and relying on an opinion typically waives privilege over it. The same good-faith logic appears in trademark law, where clearance searches and attorney opinions blunt willful-infringement and enhanced-recovery arguments.

What makes an opinion competent? Courts look for substance, not a rubber stamp: a written opinion from qualified counsel, based on the actual claims and the actual accused product, that engages the real issues (claim construction, the all-elements analysis, validity) and reaches a reasoned conclusion. A conclusory letter ("we see no problem") carries little weight. Timing matters too—the opinion should predate or accompany the launch, because willfulness is judged by the infringer's state of mind at the time of the conduct. An opinion obtained only after suit is filed does little to negate pre-suit willfulness.

Be deliberate about privilege. Asserting reliance on an opinion to defeat willfulness generally waives attorney-client privilege over that opinion and related communications, and courts may extend the waiver. Many companies therefore use separate opinion counsel and trial counsel to cabin the waiver. Decide the privilege strategy before the opinion is written, not in the middle of litigation.

Resources

Stage 6 — Design-around

Design-around is not failure; it is the system working as intended. The whole point of clearing early is to preserve cheap options, and a deliberate design-around is usually the cheapest. When clearance surfaces a blocking right, design-around is the engineering or branding response: modify the product so it no longer practices the asserted claims, or change the brand so it no longer confuses. A patent design-around works claim element by claim element—if you eliminate or substantially change even one element of every independent claim, you avoid literal infringement (watch the doctrine of equivalents for insubstantial substitutions). For trademarks, design-around means choosing a distinct, distinctive name. For OSS, it means replacing a copyleft-encumbered component with a permissively licensed or proprietary equivalent. Document the design-around rationale; it reinforces good faith and can itself support a non-infringement opinion.

Resources

Stage 7 — Manage ongoing risk

Clearance is not a one-time gate. New patents issue, new marks register, and dependencies update. Build clearance into recurring processes: monitor competitor patent and trademark filings; re-clear at major product or branding changes; maintain the SBOM as code evolves; preserve clearance records and opinions; and revisit insurance (IP infringement / media liability coverage) and indemnification terms in vendor and customer contracts. Treat clearance as a living risk register tied to your product roadmap.

Resources

Master resource index

Articles

Checklists

Related toolkits

External & primary sources

This toolkit is general information, not legal advice. Clearance reduces but never eliminates risk; verify current search tools and fees at the official sites.