Patentability Search SOP: Build an Internal Review Workflow
Introduction
If your enterprise files more than 20 patent applications per year, the model of “outsourcing every patentability search” will eventually break down — not because of quality, but because response speed cannot keep up, costs cannot be contained, and knowledge cannot be accumulated.
A patentability search SOP helps growing IP teams make search quality repeatable. Building an internal Patentability Search SOP (Standard Operating Procedure) that transforms patentability searching from “relying on individual experience” into a “structured organizational capability” is a required course for the IP team of a growing enterprise. This article provides a practical, implementable blueprint for building a patentability search SOP.
Why You Need a Patentability Search SOP
Typical Pain Points Without an SOP
- Xiao Ming performed a patentability search. His methods and standards are what you trained him on, but no one else can replicate them.
- Xiao Hong resigned, and all her experience on “how to search more accurately” walked out the door with her.
- For the same invention, three patentability search analysts produced three different conclusions — you don’t know whom to trust.
- You also don’t know how to review reports from third-party patentability search firms — you lack an internal “evaluation framework.”
Benefits of Having an SOP
- Unified quality standards for patentability searching — whether done by newcomers or veterans, all reports follow the same judgment framework.
- Knowledge can be accumulated — every patentability search case can be archived and studied within the SOP framework.
- Efficiency becomes quantifiable — you can measure the time consumed by each step of the SOP in a specific technical field.
- Outsourcing becomes manageable — with internal standards, you have a benchmark when reviewing third-party reports.
Core Components of a Patentability Search SOP
Component 1: Invention Classification Rules
The entry point of the patentability search SOP is answering one question — what type does this invention belong to, which then determines which process to follow:
| Invention Type | Reference Criteria | Corresponding Process |
|---|---|---|
| Type A: Core Invention | Fundamental platform technology, intended for global filing | Full-process in-depth patentability search (including NPL and multiple jurisdictions) |
| Type B: Significant Improvement | Core technical improvement of a key product, domestic invention patent application | Full-process standard patentability search |
| Type C: General Improvement / Peripheral | Utility model, minor product iteration | Expedited patentability search process |
Classification rules should be formulated by the IP head based on the enterprise’s technical characteristics and strategic priorities. It is recommended to articulate them as explicit written criteria to avoid subjective drift.
Component 2: Standard search templates
For each technical field (or technical direction), establish preset search templates so that patentability search analysts do not start from scratch but begin by adapting a template:
Template Contents:
- Core Classification Numbers (IPC/CPC) — a list of the 3–5 most critical classification numbers in this technical field
- Core Keyword Pool — Chinese–English bilingual keywords, divided into two tiers: “must-search terms” and “candidate terms”
- Database Checklist — which databases to search in this field (sorted by priority)
- NPL Search Checklist — which NPL sources to search in this field
Method for Building Templates:
- Review the patentability search reports from this field over the past year
- Extract the most frequently used classification numbers and keywords from each report
- Select the 3–5 most important patents in this field and extract their classification numbers and commonly used vocabulary
- Validate in collaboration with external patent firms — confirm whether these classification numbers / keywords are indeed the “core barriers” of this field
Component 3: Fixed-Standard feature comparison table template
The SOP should prescribe a standard template for the feature comparison table. This is not merely a formatting issue — it compels the patentability search analyst to perform a feature-by-feature comparison and avoids judgments based on “overall impression.”
Template Requirements:
- Must include at minimum: invention feature number, feature description, whether disclosed in D1, whether disclosed in D2, analysis remarks
- The table must be completed for each prior art document
- Any notation of “partially disclosed” or “similar” must be explained in detail with reasoning in the “analysis remarks” column
Component 4: Standard Structure and Mandatory Checkpoints for Patentability Search Reports
Standard Structure:
- Search Information Summary
- Summary of Invention Understanding
- Search Results
- Feature Comparison
- Patentability Analysis (Novelty → Inventive Step → Secondary Considerations)
- Strategic Recommendations
Mandatory Checkpoints (items the patentability search analyst must self-verify before submitting the report):
- [ ] At least 3 databases have been searched (cross-language)
- [ ] NPL search has been completed (if applicable to the field)
- [ ] Feature comparison table has been fully completed
- [ ] The Closest Prior Art has been clearly identified with reasons for its selection
- [ ] The Problem-Solution Approach analysis has been fully performed and reflected in the report
- [ ] Any judgment of “implicit disclosure” or “partial similarity” has been explained in detail
- [ ] The “limitations of the search” have been stated in the report
Component 5: Internal Review / Re-examination Mechanism for Patentability Search Reports
Establish a review process for patentability search reports:
Patentability search for Type A core inventions → mandatory independent review by another patentability search analyst or patent agent
The review shall include, but is not limited to:
- Is the selection of the Closest Prior Art reasonable?
- Is there an alternative “Closest Prior Art” worth considering?
- Is there any hindsight in the Problem-Solution Approach analysis?
- Are there any overlooked directions in the Search Strategy?
- Are the strategic recommendations practical?
Patentability search for Type B / C → spot-check review (recommended spot-check rate of 10–20%)
Component 6: Patentability Search knowledge base
Incorporate each patentability search case into a searchable, learnable dataset:
Contents archived for each case:
- Core technical field tags
- Patent numbers of prior art documents
- Comparison of the final patentability assessment with the actual examination outcome (if available)
- Special Search Strategies encountered during the patentability search (e.g., newly discovered classification numbers or keywords)
- Did the examiner ultimately cite a prior art document that was not found during the patentability search? (If yes → study and close the search gap)
Pitfall Avoidance Guide for Patentability Search SOP Implementation
Pitfall 1: An SOP That Is Too High-Level Is Useless; One That Is Too Micro-Level Is Suffocating
Too high-level: “Step 2: Formulate a Search Strategy” → states the obvious without telling the newcomer how to do it
Too micro-level: requiring searching in a specific classification number → this requirement becomes obsolete when the technical field changes
The golden balance: The SOP prescribes “what must be done” and “what must be checked,” while templates and parameters are set in layers by technical field.
Pitfall 2: Rules Without Cases
Every rule in the SOP should be accompanied by representative positive and negative examples that actually occurred within the enterprise to aid understanding. For example:
- “In this case, the patentability search analyst missed Japanese-language patents because J-PlatPat was not searched → Rule: for inventions involving Japanese-origin technology, J-PlatPat must be searched”
- “In this case, because the patentability search analyst used the ‘reverse validation method,’ a key prior art document missed by conventional keywords was successfully discovered”
Pitfall 3: Failure to Establish Regular SOP Update Cadence
Patent examination practice evolves, new search tools emerge, and new technology classification numbers are continuously created. The SOP is a living document — a comprehensive update every 12 months is recommended. Recurring errors identified during patentability search reviews should serve as the priority items for the next SOP update cycle.
Key Takeaways: A patentability search SOP turns individual experience into repeatable team practice. An enterprise Patentability Search SOP should include six core components — Invention Classification Rules, Standard search templates (by technical field), Fixed feature comparison table template, Standard Report Structure and Mandatory Checkpoints, Internal Review / Re-examination Mechanism, and a Patentability Search knowledge base. A good SOP prescribes “what must be done” and “what must be checked” while leaving room for operational discretion. Update the SOP every 12 months on a regular basis and incorporate lessons learned from patentability search cases.
For teams operationalizing a patentability search SOP, PatSnap Analytics can help centralize prior art review, assignee checks, and portfolio context across recurring invention disclosures.