How to Draft a Patent That Never Gets Rejected – A Practical Guide for Founders

Draft a Patent

When founders hear “patent rejection,” they usually imagine disaster: wasted money, lost time, and a demoralised tech team. In reality, almost every serious patent application will face at least one Office Action or objection from a patent examiner. That is normal.

The goal is not to avoid any objection; the goal is to draft your patent so well that:

  • Objections are manageable and easily overcome.
  • The examiner has very little genuine ammunition to use against your claims.
  • You almost inevitably navigate your way to a grant.

 

At Lance IP, we have achieved a 100% grant rate for patents and trademarks across multiple jurisdictions, driven by careful drafting and prosecution strategy rather than magic.

This guide is written for founders—especially those in tech, SaaS, AI, electronics, med-tech, and deep-tech—who want to understand what goes into a “rejection-resistant” patent draft.

 

The Examiner’s Playbook: What They Look For

To draft a robust patent, you must understand the examiner’s primary tools for rejection. An examiner typically relies on two main statutory grounds:

  1. Lack of Novelty (35 U.S.C. 102 / EPC Art. 54)

This is the most straightforward attack: The claimed invention (or every element of it) is already disclosed in a single prior art reference (e.g., another patent, a journal article, or a public use).

How a Poor Draft Fails: If your claims are written too broadly or vaguely, a single document from the past might accidentally read on your entire invention.

  1. Obviousness / Inventive Step (35 U.S.C. 103 / EPC Art. 56)

This is the examiner’s most potent weapon: They argue that, even if your invention isn’t directly described in one place, it would have been obvious to a person having ordinary skill in the art (PHOSITA) to combine two or more prior art references to arrive at your invention.

How a Poor Draft Fails: If your specification only describes the best way your invention works and doesn’t clearly delineate what is new and non-obvious about it, you leave the door open for the examiner to make seemingly logical combinations.

 

Four Pillars of a Rejection-Resistant Patent Draft

A robust patent application (often called the Specification or Disclosure) is built on layers of detail that anticipate and neutralize these two statutory attacks.

Pillar 1: The Principle of Maximal Description (The Engine Room)

The Specification is your legal insurance policy. It must contain significantly more detail than your final claims.

  • Describe Everything, Even the Obvious: Describe the invention working with multiple variations (e.g., using a wired connection, a wireless connection, or a combination). Describe the invention in terms of a software system, a hardware system, and a hybrid. This provides crucial fallback positions later in prosecution.
  • Identify the Problem Solved: Clearly articulate the technical problem that existed in the prior art and how your invention uniquely solves it. This narrative is critical for arguing non-obviousness.
  • Detailed Examples and Data: Include flowcharts, block diagrams, and, where possible, experimental or simulated data. For a software patent, include system architecture diagrams and detailed descriptions of key algorithms/modules.

 

Pillar 2: Strategic Claim Drafting (The Legal Fortress)

Claims are the legal boundaries of your invention. This is where most battles are fought.

Claim Type Purpose Strategy
Independent Claims Covers the core inventive concept broadly. Written with minimal limitations, maximizing scope but most likely to be challenged.
Dependent Claims Adds specific features, technical parameters, or optional details. These are your fallback positions. The more detail you have, the easier it is to narrow the scope later to overcome prior art.
Method & System Claims Protects both the process (steps) and the apparatus (components). Ensure full coverage. Draft claims that protect both the action and the product.

 

  • Functional vs. Structural Language: A skilled drafter knows when to use structural language (describing specific hardware) and when to use functional language (describing what a component does). Functional language must be carefully supported by the detailed examples in the specification.

 

Pillar 3: Clear Delineation of Novelty (The Silver Bullet)

This is the most critical step for combating Obviousness. You must explicitly teach the PHOSITA why your invention isn’t obvious.

  • The Unexpected Result: If your invention achieves a result that is surprisingly better than what the prior art suggests (e.g., 50% faster, 80% less power consumption), include that information. This is powerful evidence of non-obviousness.
  • Teaching Away: Explicitly describe how the prior art would discourage a person from making your specific combination or modification. Example: “Prior systems used Component A because it was deemed more reliable, but we discovered that replacing A with the less reliable but faster Component B, when paired with our novel error-correction method, yields a vastly superior result.”

 

Pillar 4: Defining Terms Precisely (Eliminating Ambiguity)

Vagueness is a killer during prosecution. The examiner can interpret an unclear term in a way that includes prior art, which leads to rejection.

  • Create Your Own Dictionary: If you use a technical term in your claims, ensure it is explicitly defined in the written description. For example, if your claims use the term “real-time processing,” the description must define what that means (e.g., “processing completed within 10 milliseconds of data reception”).
  • Consistency: Use the exact same terminology consistently throughout the description and claims. A slight variation can be grounds for rejection due to indefiniteness.

 

Conclusion: From Rejection to Grant

No serious patent lawyer will promise a grant without any Office Action—that’s unrealistic. What a great patent lawyer does promise is a patent application so thoroughly drafted that when the inevitable Office Action arrives:

  1. The broad claims may be rejected, but you have a large reservoir of narrower dependent claims to fall back on.
  2. The specification provides rich, detailed support (Pillar 1) to amend the rejected claims while still capturing the commercial value of the invention.
  3. The narrative (Pillar 3) clearly lays out the technical leap required, making the examiner’s obviousness argument difficult to sustain.

 

A rejection-resistant patent is not an accident—it’s a carefully engineered document designed to convert initial objections into a final notice of allowance.

Categories

Tags