The Pre-Launch FTO Self-Check List: Finish This Before You Brief Counsel

Why self-check: the correct use of counsel's time

The boundary first: the conclusions of an FTO (freedom-to-operate) analysis must come from practicing patent counsel. Claim construction, equivalence judgment, risk characterization — these are legal, not engineering, determinations.

But a substantial share of a formal FTO's cost goes to organization: figuring out what technical features the product actually has, which markets matter, what searching was already done, which patents have already surfaced. Companies can do this work themselves — faster, because nobody knows the product better.

The goal of a self-check is not replacing counsel. It is making every counsel-hour a judgment-hour, not a filing-hour.

The pre-launch FTO self-check list

1. Product side: turn "the product" into a feature list

• [ ] Feature decomposition: split the product into independent technical features (structure, mechanism, material, algorithm, process), each stated in one sentence — what it is, how it is implemented. This list is the baseline for every comparison that follows.
• [ ] Tag each feature's origin: in-house, open source, supplier module, expired-patent teaching, licensed technology. For supplier modules, check the IP warranty clauses in the contract while you are at it.
• [ ] Circle the high-visibility features: which ones would headline a competitor's launch event? High-visibility features draw scrutiny — search them deeper.

2. Market side: confirm where you sell

• [ ] List every target market: manufacturing, sales, and transit jurisdictions. Patents are territorial — a US patent does not reach a product made and sold only in China, and vice versa.
• [ ] Run each market separately: the same product has an entirely different risk surface per market, and family members are often granted with different scopes in different countries.

3. Search side: leave a reproducible record

• [ ] Search feature by feature, not just by product name — infringement mapping is element-wise, so searching should be too.
• [ ] Record queries and databases: keywords, classification codes, which database, when. A reproducible search record is itself evidence of reasonable care.
• [ ] First-pass legal status: triage hits into estimated in-force / expired / unknown — but verify any "expired" call against the official register before production.
• [ ] Competitor portfolios as a dedicated pass: pull your main competitors' portfolios separately, including pending applications (they become new risk upon grant).

4. Signal side: rank, don't conclude

• [ ] Tag overlap signals per feature: which claim of which patent might overlap which of your features — down to the claim number, never stopping at "this patent looks similar."
• [ ] Grades are for ordering only: high signals go to counsel first. At the self-check stage, do not conclude "non-infringing" for any feature — that judgment comes only after counsel's claim construction.
• [ ] Equivalence self-questioning: for every feature that "escapes literally," run function-way-result once — if you cannot articulate a substantive difference in the way, flag it honestly as a doubt.

5. Honesty side: write down what you don't know

• [ ] Gap list: features not searched thoroughly, markets not covered, legal statuses not verified — list them plainly. Hiding blind spots from counsel means paying for an opinion built on false premises.
• [ ] Historical baggage: warning letters received, known disputes in the space, technology employees brought from prior employers — counsel must know.

After the self-check: the handover package

A good handover lets counsel start analyzing on day one:

1. The feature list (with origin tags);
2. The target-market list;
3. Search records (queries, databases, dates, hit lists);
4. The risk-signal ranking table (specific to claim numbers);
5. The gap-and-doubt list;
6. The specific questions you want counsel to answer.

The reports our design-around and related tools produce are, in essence, drafts of this handover package: feature decomposition, per-feature overlap signals, equivalents self-check records, legal-status labels with estimation bases, and a verification checklist — every item designed for the destination of "hand to counsel," never for "replace counsel."

The closing timing question

The optimal FTO moment is before design freeze: features fixed, analysis targeted, changes still possible. The most expensive moment is after inventory is stocked — every red light then is real money. Do the self-check early, spend counsel where it cuts, and reserve the launch date for a clean conclusion.