Skip to content
PatentResolve
Upload Office Action

Your claims were called ineligible under §101

What a 35 USC 101 subject matter eligibility rejection means for software, diagnostics and business methods, and how these are answered.

A §101 rejection says the claim is directed to something the patent system does not cover — an abstract idea, a law of nature or a natural phenomenon — and does not add enough beyond it to be eligible. Examiners apply a two-part analysis: is the claim directed to one of those excluded concepts, and if so, does it integrate that concept into a practical application or add something significantly more. Answers work on either part: showing the claim is not directed to an excluded concept at all, or showing that it recites a concrete technical improvement rather than an idea implemented on a generic computer.

They are saying my software is just an abstract idea. It is a real product.

The gap between a working product and an eligible claim is the whole problem here. Eligibility is judged on the words of the claim, not on the system you built.

The claims that survive tend to recite a specific technical mechanism and a specific improvement it produces — how the thing works, not what it achieves. Claims that recite a business outcome with a computer performing it are the ones that struggle.

The test the examiner is applying

  1. Step 1: is the claim in a statutory category?

    Process, machine, manufacture or composition of matter. Most claims pass this trivially.

  2. Step 2A: is it directed to a judicial exception?

    An abstract idea, a law of nature, or a natural phenomenon. Under current USPTO guidance the examiner also asks whether the exception is integrated into a practical application — a real technical improvement, a particular machine, a transformation.

  3. Step 2B: does it add significantly more?

    If the claim is directed to an exception and does not integrate it, the examiner asks whether the additional elements amount to more than well-understood, routine and conventional activity.

What tends to work

Pointing to the technical improvement in your own specification, in the language the specification already uses. Improvements described but not claimed are a recurring, fixable problem.

Amending to recite the mechanism rather than the objective — how the result is achieved, in specific structural or algorithmic terms.

Showing the examiner’s characterisation of the claim is over-generalised. A claim summarised in six words has usually lost the limitations that make it eligible.

Where the examiner asserts elements are conventional, holding them to the evidentiary requirement for that assertion.

Be realistic about art units

Eligibility outcomes vary substantially by technology and by art unit. In some business-method units, §101 is the central obstacle and a claim strategy that avoids it must be planned rather than argued. An honest assessment of that is more valuable than an optimistic one.

Statute

35 U.S.C. 101

Framework

Alice/Mayo two-step, as applied through USPTO eligibility guidance

Examiner guidance

MPEP 2103–2106.07

Most affected

Software, business methods, diagnostics

Typical reply period

Three months from the mailing date

Find out exactly how the examiner characterised your claims

The wording the examiner used to summarise your claim is where a §101 answer starts. We pull it out of the document with its page.

Upload my Office Action

Questions people ask

Yes. Software-implemented inventions are patented routinely. What fails is claiming an idea or a business practice and adding a generic computer. Claims that recite a specific technical mechanism and a concrete improvement in how a system operates are granted every week.

Frequently both, and the argument depends on your specification. If the specification describes a technical improvement in detail, amending to claim that mechanism and arguing integration into a practical application is the usual route. If it does not, the options narrow considerably.

Often more than with any other ground. Eligibility turns on how the examiner reads the claim as a whole, and a short conversation about proposed claim language can settle in twenty minutes what several written rounds do not.

Where this comes from

Every statement of law or procedure on this page traces to a primary source you can check yourself.

If this was not quite your situation

The examiner objected to how your claims are written: §112

The difference between 112(a) written description and enablement and 112(b) indefiniteness, and how each is answered.

Responding to a USPTO Office Action

What a response to a USPTO Office Action involves, what it costs, what the deadline is, and how to start with the document you already have.

The four rejection grounds, told apart

What each section number in an Office Action means: 101 eligibility, 102 anticipation, 103 obviousness and 112 claim drafting.

What responding to an Office Action actually costs

Indicative professional fee ranges for a USPTO Office Action response, what drives the number up, and which USPTO fees are separate.