Patentable Enough to File: The Check That Happens Before Drafting Starts

An invention is “patentable enough to file” when counsel can identify a claimable technical core, test it against a documented prior-art search, explain why the remaining differences may be novel and non-obvious in the target jurisdiction, and confirm that the disclosure supports the intended claim scope.

That is a filing decision under uncertainty, not a prediction or guarantee of grant.

A patentability assessment before drafting should lead to one of three actions:

1. Proceed to claim strategy and drafting.
2. Investigate a narrower or better-supported claim position.
3. Pause the filing, redesign the invention, or reassess the target jurisdictions.

The assessment should be performed for the jurisdictions where protection is being considered. Patent rights are territorial, so a conclusion about the United States does not automatically answer the position in India or Europe. The World Intellectual Property Organization explains that patent rights generally apply only in the country or region where protection is sought and granted. WIPO, Frequently Asked Questions: Patents

A preliminary search is also incomplete by nature. The USPTO warns that an examiner may find information that was not identified in an earlier search. USPTO, Applying for Patents

The six-check filing framework

Check 1: Identify a claimable technical core

Do not begin with the question, “Is the idea new?” Begin with a claim and evidence problem.

A useful intake should answer:

• What technical problem is being solved?
• What components, steps, or relationships produce the result?
• What is the minimum feature combination required for that result?
• Which features are essential, and which are optional embodiments?
• What technical effect, data, test result, or mechanism distinguishes the combination?
• What material supports each potential limitation?

The supporting material might include inventor notes, test data, diagrams, source code, prototypes, laboratory records, or system logs.

The objective is to move from an invention summary to a provisional claim hypothesis. For example:

A system that improves battery cooling

is not yet a useful claim core. A more useful hypothesis might be:

A control method that measures temperature variation at the battery-module level, predicts load, selects a cooling path based on those inputs, and adjusts coolant flow using a defined threshold.

The second formulation gives the searcher features to test and gives the drafter a relationship to investigate.

Check support before drafting

A strong search result is not enough if the team cannot explain how the proposed invention works.

For a US application, the written description must describe the claimed invention in enough detail for a skilled person to reasonably conclude that the inventor possessed the claimed subject matter. The USPTO’s MPEP treats written description as a requirement separate from enablement and emphasizes that the claimed invention must be described with all of its limitations. USPTO MPEP § 2163

A common failure case is an R&D disclosure that describes only the desired outcome, such as lower latency or higher accuracy, without explaining the technical mechanism producing it. The next action is targeted inventor questioning, not immediate claim drafting.

Check 2: Screen the subject matter under the target jurisdiction’s rules

Before searching deeply, identify any eligibility or exclusion issue that could make the proposed claim position unsuitable for a particular jurisdiction.

United States

For US utility applications, the USPTO summarizes four basic conditions for obtaining a patent:

• The invention must be useful.
• The application must clearly describe how to make and use it.
• The invention must be new, or novel.
• The invention must not be obvious in view of what came before.

USPTO, Patent essentials

US subject-matter eligibility requires more than showing that an invention is new and useful. Under the USPTO’s explanation of 35 U.S.C. § 101, a claimed invention must fall within a statutory category such as a process, machine, manufacture, or composition of matter, and must not be directed only to a judicial exception such as an abstract idea, law of nature, or natural phenomenon. USPTO MPEP § 2104

India

Under Section 2(1)(j) of the Indian Patents Act, an invention is a new product or process involving an inventive step and capable of industrial application. The Act also defines inventive step in terms of technical advance, economic significance, or both, together with non-obviousness to a person skilled in the art. IP India, Section 2 definitions

A separate exclusions screen is required. Section 3 includes exclusions covering, among other subject matter:

• Mere discoveries of scientific principles or naturally occurring substances.
• Certain new forms or uses of known substances.
• Methods of medical treatment.
• Mathematical or business methods.
• Computer programs per se and algorithms.
• Mere schemes, rules, or methods of performing mental acts.
• Certain arrangements or rearrangements of known devices.

IP India, Section 3

Software, diagnostics, treatment methods, natural products, and pharmaceutical incremental inventions should therefore be flagged for jurisdiction-specific counsel review. This article does not resolve those issues.

The same principle applies when considering European protection. A US eligibility analysis should not simply be copied into an EPO filing strategy.

Check 3: Run a search that can support a decision

A patent search retrieves potential prior art. A patentability assessment analyzes what the strongest references mean for a proposed claim.

The search should test more than the inventor’s preferred terminology. The USPTO’s multi-step search strategy provides a practical sequence:

1. Brainstorm alternative words for the invention’s purpose, composition, structure, function, and use.
2. Run broad keyword searches, then narrow them with additional features.
3. Identify relevant Cooperative Patent Classification codes.
4. Review complete patent documents and published applications, including claims, specifications, and drawings.
5. Follow backward and forward citations.
6. Expand into foreign patent documents and non-patent literature, including journals, websites, technical catalogs, and conference proceedings.

USPTO, Multi-Step U.S. Patent Search Strategy

Do not treat every result as a patent. The relevant record may include a granted patent, a published patent application, an international publication, a journal article, a technical website, a product manual, or another public technical disclosure.

Keep a search log

A defensible assessment should record:

• Databases searched.
• Search date and time.
• Keywords and alternative terminology.
• Classification codes.
• Citation paths followed.
• Documents retrieved.
• Reasons for excluding apparently relevant results.
• Jurisdictions and collections covered.
• Non-patent literature sources checked.

The USPTO specifically recommends recording the databases, date, keywords, and retrieved patent documents used in the search. USPTO, Multi-Step U.S. Patent Search Strategy

The success check is not the number of documents returned. It is whether a reviewer can explain why the search covered adjacent terminology and classifications rather than merely showing a list of keyword hits.

Check 4: Map the closest art to the proposed claim

The most useful decision tool is a feature-by-reference matrix.

Put each proposed independent-claim feature in a separate row. Put each close reference in a separate column. For every cell, record whether the feature is:

• Disclosed.
• Partially disclosed.
• Not located.

Attach a pinpoint citation, such as a claim number, paragraph, column and line, figure, or page. A conclusion that says “D1 is similar” is not enough. The reviewer needs to see which limitations D1 actually discloses.

The matrix should also distinguish between:

• A single reference that may disclose the complete combination.
• Multiple references that disclose different parts.
• A reference that shows a technically adjacent approach but not the claimed relationship.
• A result that is only background context.

This is consistent with the way the EPO describes relationships between cited documents and claims. EPO search reports identify the claims to which each document relates and can distinguish a document that is relevant on its own from documents that become relevant in combination. EPO Guidelines, Part B, Chapter X, 9.3

Check 5: Test novelty and inventive step separately

The matrix should answer two different questions.

Novelty

Does one earlier public disclosure contain every feature of the proposed claim?

If a single reference discloses the complete claimed combination, the proposed claim core faces a novelty problem. A searcher should identify the specific disclosures and avoid relying on a general statement that the reference is “close.”

Inventive step or non-obviousness

If no single reference contains every feature, would the differences likely be an obvious combination or predictable variation for a skilled person?

For US applications, 35 U.S.C. § 103 asks whether the differences between the claimed invention and the prior art would have been obvious to a person having ordinary skill in the art before the effective filing date. The USPTO identifies the relevant factual inquiries as the scope and content of the prior art, the differences between the claim and the prior art, and the level of ordinary skill in the relevant field. USPTO MPEP § 2141

The assessment should therefore explain:

• What D1 teaches.
• What D2 teaches.
• What feature or relationship is missing from D1.
• Whether D2 supplies that feature or relationship.
• Why a skilled person would or would not have combined them.
• Whether the combination produces more than a predictable result.
• Whether technical evidence supports the asserted effect.

The USPTO’s discussion of obviousness cautions against treating a combination of familiar elements as inventive when it merely produces predictable results. At the same time, an obviousness conclusion should include a reasoned explanation rather than a bare assertion that the combination would have been routine. USPTO MPEP § 2141

Check 6: Confirm that the disclosure supports the intended scope

The final check asks whether the available disclosure can support the claim position that the team actually wants to file.

Review:

• Every proposed independent-claim limitation.
• The technical mechanism associated with each limitation.
• Alternative embodiments and fallback positions.
• Data supporting any asserted technical effect.
• Definitions for specialized terms.
• Relationships between components or process steps.
• Drawings, diagrams, and formulas that show the invention.
• Material that supports narrower and broader positions.

A broad claim may look attractive after the search, but it is not a useful filing position if the disclosure supports only one narrow implementation. Conversely, a narrow claim may avoid the closest reference but fail to protect the commercial implementation.

The practical question is:

Can counsel explain both why the claim may distinguish over the closest art and where the application supports each limitation?

If the answer is no, the matter is not ready for ordinary drafting. It needs inventor follow-up, additional technical evidence, a narrower claim hypothesis, or a different filing decision.

How to read a patentability search report

A useful report should connect the search record to a proposed claim position. It should not end with a list of documents and a confidence score.

Hypothetical example, not a legal opinion

Invention: Thermal-management control method for battery modules Search date and scope: September 28, 2026; patents, published applications, and non-patent literature; US, EP, PCT, and India collections; keywords, CPC/IPC classes, and citation searching listed in appendix. Proposed claim core: Measure module-level temperature variation; select a cooling path based on the variation and predicted load; adjust coolant flow using a defined control threshold. Closest reference D1: Discloses module temperature sensing and variable coolant flow. Closest reference D2: Discloses load prediction for cooling control. Feature matrix finding: The defined relationship between module-level variation, predicted load, and the specified control threshold was not located in D1 alone. D1 plus D2 creates an inventive-step risk requiring counsel review. Assessment: Yellow. Proceed only if inventor evidence supports the threshold’s technical effect and counsel can articulate why the D1-D2 combination would not have been routine at the relevant date. Drafting instruction: Develop one independent claim around the integrated control relationship and include narrower fallbacks for the threshold, sensor arrangement, and response logic.

The conclusion is useful because it does not claim that the invention is patentable. It identifies:

• The technical relationship worth developing.
• The closest individual references.
• The difference between the references and the proposed claim.
• The risk created by combining the references.
• The evidence still required.
• The drafting direction if the matter proceeds.

An actual report should preserve the search strategy behind the conclusion. EPO guidance states that an information-on-search-strategy sheet records the databases searched, classification symbols used, and keywords reflecting the searched subject matter. EPO Guidelines, Part B, Chapter X, 3.4

Filing decision: green, yellow, or red

The colors below are an internal decision framework, not official patent-office categories.

Assessment	Typical finding	Recommended action
Green	No single novelty-destroying reference was found. The inventive-step rationale is plausible, and the disclosure supports a commercially relevant claim position.	Proceed to Strategy and drafting.
Yellow	The closest art is dense, the inventive-step rationale depends on technical evidence, or the disclosure contains material gaps.	Obtain inventor evidence, narrow the claim hypothesis, or run a focused second search before drafting.
Red	A single reference appears to disclose the core combination, the expected combination is likely predictable, the subject matter is excluded in the target jurisdiction, or the disclosure cannot support the desired claim.	Pause, redesign, preserve the invention as know-how, or reassess the filing jurisdictions.

A green result still does not guarantee a patent. A yellow result does not necessarily mean the invention should be abandoned. It means the team should identify what evidence or claim adjustment is needed before authorizing production work.

Patentability is also separate from:

• Freedom to operate.
• Commercial value.
• Validity.
• Enforceability.
• A guarantee of grant.

Those questions require their own analysis.

Carrying the assessment into claim strategy

The value of a patentability assessment is not only finding references. It is using the findings while the claims remain editable.

Esgenix describes its patent workflow as a decision-gated agentic patent workflow platform. Its Prior Art Radar is positioned as prior-art intelligence that can inform strategy and drafting within the same matter workflow. The product page describes semantic search, graded rounds, X, Y, and A-style triage, a feature-by-reference matrix with evidence quotes, and suggested D1-plus-D2 combination groups. Esgenix Prior Art Search

Those are product capabilities, not independent legal outcomes. Counsel still decides which references matter, whether the proposed claim position is defensible, and whether the matter should proceed.

The workflow also reflects a clear boundary between production and professional judgment:

1. Intake: Confirm the invention understanding, resolve technical gaps, and choose jurisdictions.
2. Strategy: Set claim direction, breadth, and fallback positions.
3. Claims: Approve, modify, or reject the claim set.
4. Specification & Figures: Review the specification, provenance, figures, and consistency.
5. Sign-off: Complete professional review and approve the output.

Esgenix’s drafting material describes Technical Gap Detection before drafting and a drafting workflow in which counsel reviews the work at these five decision gates. Esgenix Patent Drafting

That operating model matters for a pre-drafting assessment. The machine can help organize search rounds, map features, surface combinations, and carry graded references into a draft. The patent professional remains responsible for the substantive filing decision.

The practical threshold is therefore not “Did the search find nothing?” It is:

Do we have a supportable claim position, a documented search record, a reasoned response to the closest art, and enough disclosure to justify moving into drafting for the target jurisdiction?

Bring one invention disclosure to a demo and see how Prior Art Radar can carry a documented search assessment into claim strategy.