MPEP § 2164.07 — Relationship of Enablement Requirement to Utility Requirement of 35 U.S.C. 101 (Annotated Rules)

§2164.07 Relationship of Enablement Requirement to Utility Requirement of 35 U.S.C. 101

USPTO MPEP version: BlueIron's Update: 2025-12-31

This page consolidates and annotates all enforceable requirements under MPEP § 2164.07, including statutory authority, regulatory rules, examiner guidance, and practice notes. It is provided as guidance, with links to the ground truth sources. This is information only, it is not legal advice.

Relationship of Enablement Requirement to Utility Requirement of 35 U.S.C. 101

This section addresses Relationship of Enablement Requirement to Utility Requirement of 35 U.S.C. 101. Primary authority: 35 U.S.C. 112(a), 35 U.S.C. 112, and 35 U.S.C. 101. Contains: 2 requirements, 1 prohibition, 3 guidance statements, 1 permission, and 6 other statements.

Key Rules

Topic

How to Use the Invention (MPEP 2164.01(c))

4 rules
StatutoryInformativeAlways
[mpep-2164-07-d75a364ef211fa30904e078e]
Requirement for Describing How to Use Invention
Note:
The specification must describe how the invention can be used, distinguishing from the utility requirement of being useful.

The requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph as to how to use the invention is different from the utility requirement of 35 U.S.C. 101. The requirement of 35 U.S.C. 101 is that some specific, substantial, and credible use be set forth for the invention. On the other hand, 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph requires an indication of how the use (required by 35 U.S.C. 101) can be carried out, i.e., how the invention can be used.

Jump to MPEP SourceHow to Use the Invention (MPEP 2164.01(c))Enablement Requirement (MPEP 2164)35 U.S.C. 112(a) – Written Description & Enablement
StatutoryProhibitedAlways
[mpep-2164-07-ca0db3c3ff043aac7c707793]
Specification Cannot Teach How to Use Useless Compositions
Note:
If compositions are shown to be useless, the specification cannot teach how to use them, failing both utility and enablement requirements.

If a claim fails to meet the utility requirement of 35 U.S.C. 101 because it is shown to be nonuseful or inoperative, then it necessarily fails to meet the how-to-use aspect of the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As noted in In re Fouche, 439 F.2d 1237, 169 USPQ 429 (CCPA 1971), if “compositions are in fact useless, appellant’s specification cannot have taught how to use them.” 439 F.2d at 1243, 169 USPQ at 434. The examiner should make both rejections (i.e., a rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph and a rejection under 35 U.S.C. 101) where the subject matter of a claim has been shown to be nonuseful or inoperative.

Jump to MPEP SourceHow to Use the Invention (MPEP 2164.01(c))Enablement Requirement (MPEP 2164)Lack of Utility Rejection
StatutoryRecommendedAlways
[mpep-2164-07-1097b6a001b3e6d04101ed01]
Invention Must Be Useful
Note:
A claim is defective under 35 U.S.C. 112(a) if the invention as claimed lacks utility, meaning a skilled person would not be able to use it.

The 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should indicate that because the invention as claimed does not have utility, a person skilled in the art would not be able to use the invention as claimed, and as such, the claim is defective under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. A 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should not be imposed or maintained unless an appropriate basis exists for imposing a rejection under 35 U.S.C. 101. In other words, Office personnel should not impose a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection grounded on a “lack of utility” basis unless a 35 U.S.C. 101 rejection is proper. In particular, the factual showing needed to impose a rejection under 35 U.S.C. 101 must be provided if a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection is to be imposed on “lack of utility” grounds. See MPEP § 2107§ 2107.03 for a more detailed discussion of the utility requirements of 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 112, first paragraph.

Jump to MPEP Source · 37 CFR 2107.03How to Use the Invention (MPEP 2164.01(c))35 U.S.C. 112(a) – Written Description & EnablementDisclosure Requirements
StatutoryPermittedAlways
[mpep-2164-07-b45c2ae714fc962ab4593aa0]
Specification Must Describe Invention Fully
Note:
The specification must enable a skilled artisan to use the invention, even if it is highly useful.

In some instances, the utility of the claimed invention will be provided, but the skilled artisan will not know how to effect that use. In such a case, no rejection will be made under 35 U.S.C. 101, but a rejection will be made under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As pointed out in Mowry v. Whitney, 81 U.S. (14 Wall.) 620 (1871), an invention may in fact have great utility, i.e., may be “a highly useful invention,” but the specification may still fail to “enable any person skilled in the art or science” to use the invention. 81 U.S. (14 Wall.) at 644.

Jump to MPEP SourceHow to Use the Invention (MPEP 2164.01(c))Enablement Requirement (MPEP 2164)Determining Whether Application Is AIA or Pre-AIA
Topic

35 U.S.C. 112(a) – Written Description & Enablement

4 rules
StatutoryRequiredAlways
[mpep-2164-07-b550ac421354db862e3cca34]
Specification Must Describe How Invention Can Be Used
Note:
The written description must provide a detailed explanation of how the invention can be used as required by the utility requirement under 35 U.S.C. 101.

The requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph as to how to use the invention is different from the utility requirement of 35 U.S.C. 101. The requirement of 35 U.S.C. 101 is that some specific, substantial, and credible use be set forth for the invention. On the other hand, 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph requires an indication of how the use (required by 35 U.S.C. 101) can be carried out, i.e., how the invention can be used.

Jump to MPEP Source35 U.S.C. 112(a) – Written Description & EnablementDisclosure RequirementsEnablement Requirement (MPEP 2164)
StatutoryRecommendedAlways
[mpep-2164-07-0cb361650120c9b7878c8e32]
Utility Requirement for 35 U.S.C. 112(a) Rejection
Note:
A 35 U.S.C. 112(a) rejection should not be imposed unless a 35 U.S.C. 101 rejection is proper, ensuring the invention has utility and can be used by a skilled person.

The 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should indicate that because the invention as claimed does not have utility, a person skilled in the art would not be able to use the invention as claimed, and as such, the claim is defective under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. A 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should not be imposed or maintained unless an appropriate basis exists for imposing a rejection under 35 U.S.C. 101. In other words, Office personnel should not impose a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection grounded on a “lack of utility” basis unless a 35 U.S.C. 101 rejection is proper. In particular, the factual showing needed to impose a rejection under 35 U.S.C. 101 must be provided if a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection is to be imposed on “lack of utility” grounds. See MPEP § 2107§ 2107.03 for a more detailed discussion of the utility requirements of 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 112, first paragraph.

Jump to MPEP Source · 37 CFR 2107.0335 U.S.C. 112(a) – Written Description & EnablementPatent EligibilityDisclosure Requirements
StatutoryRequiredAlways
[mpep-2164-07-cfc6112e70731845a8d508d3]
Utility Requirement for 35 U.S.C. 101 Rejection
Note:
A factual showing must be provided to reject a claim under 35 U.S.C. 101 on utility grounds if a 35 U.S.C. 112(a) or pre-AIA 112, first paragraph, rejection is also considered.

The 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should indicate that because the invention as claimed does not have utility, a person skilled in the art would not be able to use the invention as claimed, and as such, the claim is defective under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. A 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should not be imposed or maintained unless an appropriate basis exists for imposing a rejection under 35 U.S.C. 101. In other words, Office personnel should not impose a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection grounded on a “lack of utility” basis unless a 35 U.S.C. 101 rejection is proper. In particular, the factual showing needed to impose a rejection under 35 U.S.C. 101 must be provided if a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection is to be imposed on “lack of utility” grounds. See MPEP § 2107§ 2107.03 for a more detailed discussion of the utility requirements of 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 112, first paragraph.

Jump to MPEP Source · 37 CFR 2107.0335 U.S.C. 112(a) – Written Description & EnablementPatent EligibilityDisclosure Requirements
StatutoryInformativeAlways
[mpep-2164-07-f5c32d2950025a277245f2d8]
Enablement Must Be Demonstrated for Useful Invention
Note:
The specification must demonstrate how to use the invention, even if it is highly useful. A rejection under 35 U.S.C. 112(a) will be made if enablement is not provided.

In some instances, the utility of the claimed invention will be provided, but the skilled artisan will not know how to effect that use. In such a case, no rejection will be made under 35 U.S.C. 101, but a rejection will be made under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As pointed out in Mowry v. Whitney, 81 U.S. (14 Wall.) 620 (1871), an invention may in fact have great utility, i.e., may be “a highly useful invention,” but the specification may still fail to “enable any person skilled in the art or science” to use the invention. 81 U.S. (14 Wall.) at 644.

Jump to MPEP Source35 U.S.C. 112(a) – Written Description & EnablementAIA vs Pre-AIA PracticeDisclosure Requirements
Topic

Enablement Requirement (MPEP 2164)

3 rules
StatutoryInformativeAlways
[mpep-2164-07-8a84e7a7047556bdab5484cc]
Invention Must Have Specific Use
Note:
The rule requires that the invention must have a specific, substantial, and credible use set forth for it to be patentable under 35 U.S.C. 101.

The requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph as to how to use the invention is different from the utility requirement of 35 U.S.C. 101. The requirement of 35 U.S.C. 101 is that some specific, substantial, and credible use be set forth for the invention. On the other hand, 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph requires an indication of how the use (required by 35 U.S.C. 101) can be carried out, i.e., how the invention can be used.

Jump to MPEP SourceEnablement Requirement (MPEP 2164)How to Use the Invention (MPEP 2164.01(c))35 U.S.C. 112(a) – Written Description & Enablement
StatutoryInformativeAlways
[mpep-2164-07-26bd0ae2633ab6fec6120485]
Enablement Fails If Inoperative
Note:
If a claim is shown to be nonuseful or inoperative, it fails both the enablement and utility requirements.

If a claim fails to meet the utility requirement of 35 U.S.C. 101 because it is shown to be nonuseful or inoperative, then it necessarily fails to meet the how-to-use aspect of the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As noted in In re Fouche, 439 F.2d 1237, 169 USPQ 429 (CCPA 1971), if “compositions are in fact useless, appellant’s specification cannot have taught how to use them.” 439 F.2d at 1243, 169 USPQ at 434. The examiner should make both rejections (i.e., a rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph and a rejection under 35 U.S.C. 101) where the subject matter of a claim has been shown to be nonuseful or inoperative.

Jump to MPEP SourceEnablement Requirement (MPEP 2164)How to Use the Invention (MPEP 2164.01(c))Lack of Utility Rejection
StatutoryInformativeAlways
[mpep-2164-07-148f78bbdc6856ffaa1e38f9]
Enablement Must Describe Invention Usefully
Note:
The specification must enable a skilled artisan to use the invention, even if it lacks utility details.

In some instances, the utility of the claimed invention will be provided, but the skilled artisan will not know how to effect that use. In such a case, no rejection will be made under 35 U.S.C. 101, but a rejection will be made under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As pointed out in Mowry v. Whitney, 81 U.S. (14 Wall.) 620 (1871), an invention may in fact have great utility, i.e., may be “a highly useful invention,” but the specification may still fail to “enable any person skilled in the art or science” to use the invention. 81 U.S. (14 Wall.) at 644.

Jump to MPEP SourceEnablement Requirement (MPEP 2164)How to Use the Invention (MPEP 2164.01(c))Determining Whether Application Is AIA or Pre-AIA
Topic

Lack of Utility Rejection

3 rules
StatutoryInformativeAlways
[mpep-2164-07-0075807e28ff09bf0ee37dca]
Enablement Fails Without Utility
Note:
If a claim lacks utility, it also fails to meet the enablement requirement as it cannot be shown how to use the invention.

If a claim fails to meet the utility requirement of 35 U.S.C. 101 because it is shown to be nonuseful or inoperative, then it necessarily fails to meet the how-to-use aspect of the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As noted in In re Fouche, 439 F.2d 1237, 169 USPQ 429 (CCPA 1971), if “compositions are in fact useless, appellant’s specification cannot have taught how to use them.” 439 F.2d at 1243, 169 USPQ at 434. The examiner should make both rejections (i.e., a rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph and a rejection under 35 U.S.C. 101) where the subject matter of a claim has been shown to be nonuseful or inoperative.

Jump to MPEP SourceLack of Utility RejectionEnablement Requirement (MPEP 2164)Utility Requirement
StatutoryRecommendedAlways
[mpep-2164-07-1b93df0eb22f894cb3d2578a]
Nonuseful Subject Matter Requires Both Utility and Enablement Rejections
Note:
When a claim is shown to be nonuseful or inoperative, the examiner must reject it under both 35 U.S.C. 101 for lack of utility and 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112 for failure to enable.

If a claim fails to meet the utility requirement of 35 U.S.C. 101 because it is shown to be nonuseful or inoperative, then it necessarily fails to meet the how-to-use aspect of the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As noted in In re Fouche, 439 F.2d 1237, 169 USPQ 429 (CCPA 1971), if “compositions are in fact useless, appellant’s specification cannot have taught how to use them.” 439 F.2d at 1243, 169 USPQ at 434. The examiner should make both rejections (i.e., a rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph and a rejection under 35 U.S.C. 101) where the subject matter of a claim has been shown to be nonuseful or inoperative.

Jump to MPEP SourceLack of Utility Rejection35 U.S.C. 112(a) – Written Description & EnablementPatent Eligibility
StatutoryInformativeAlways
[mpep-2164-07-44de7ea42e7b3dcfbec255f9]
Burden on Examiner to Support Lack of Utility Rejection
Note:
The examiner must provide a reasonable basis when concluding an application claims an invention that is nonuseful, inoperative, or contradicts known scientific principles.

When the examiner concludes that an application claims an invention that is nonuseful, inoperative, or contradicts known scientific principles, the burden is on the examiner to provide a reasonable basis to support this conclusion. Rejections based on 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, and 35 U.S.C. 101 should be made.

Jump to MPEP SourceLack of Utility RejectionUtility RequirementPatent Eligibility
Topic

Responding to 101 Rejections

2 rules
StatutoryRecommendedAlways
[mpep-2164-07-77776a521ad32c282bf99edd]
Utility Requirement for 101 Rejection
Note:
Office personnel must establish a 35 U.S.C. 101 rejection before imposing a lack of utility rejection under 35 U.S.C. 112(a) or pre-AIA 112, first paragraph.

The 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should indicate that because the invention as claimed does not have utility, a person skilled in the art would not be able to use the invention as claimed, and as such, the claim is defective under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. A 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection should not be imposed or maintained unless an appropriate basis exists for imposing a rejection under 35 U.S.C. 101. In other words, Office personnel should not impose a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection grounded on a “lack of utility” basis unless a 35 U.S.C. 101 rejection is proper. In particular, the factual showing needed to impose a rejection under 35 U.S.C. 101 must be provided if a 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, rejection is to be imposed on “lack of utility” grounds. See MPEP § 2107§ 2107.03 for a more detailed discussion of the utility requirements of 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 112, first paragraph.

Jump to MPEP Source · 37 CFR 2107.03Responding to 101 Rejections35 U.S.C. 112(a) – Written Description & EnablementPatent Eligibility
StatutoryInformativeAlways
[mpep-2164-07-c4e81f92e5bc7372c6d48de6]
Burden of Proving Utility Shifting to Applicant After Examiner’s Evidence
Note:
The examiner must first provide evidence that one of ordinary skill would doubt the utility. If so, the burden shifts to the applicant to provide sufficient rebuttal evidence.

The examiner has the initial burden of challenging an asserted utility. Only after the examiner has provided evidence showing that one of ordinary skill in the art would reasonably doubt the asserted utility does the burden shift to the applicant to provide rebuttal evidence sufficient to convince one of ordinary skill in the art of the invention’s asserted utility. In re Fisher, 421 F.3d 1365, 76 USPQ2d 1225 (Fed. Cir. 2005); In re Swartz, 232 F.3d 862, 863, 56 USPQ2d 1703, 1704 (Fed. Cir. 2000); In re Brana, 51 F.3d 1560, 1566, 34 USPQ2d 1436, 1441 (Fed. Cir. 1995) (citing In re Bundy, 642 F.2d 430, 433, 209 USPQ 48, 51 (CCPA 1981)).

Jump to MPEP SourceResponding to 101 RejectionsPatent EligibilityUtility Requirement
Topic

35 U.S.C. 101 – Patent Eligibility

2 rules
StatutoryRecommendedAlways
[mpep-2164-07-93decb375ca196a87a2f67af]
Rejections Based on 35 U.S.C. 112(a) and 101 Required
Note:
Examiners must provide a reasonable basis for rejecting claims that an invention is nonuseful, inoperative, or contradicts known scientific principles under 35 U.S.C. 112(a) or 101.

When the examiner concludes that an application claims an invention that is nonuseful, inoperative, or contradicts known scientific principles, the burden is on the examiner to provide a reasonable basis to support this conclusion. Rejections based on 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, and 35 U.S.C. 101 should be made.

Jump to MPEP SourcePatent EligibilityUtility RequirementLack of Utility Rejection
StatutoryInformativeAlways
[mpep-2164-07-e3ae770480b3c73f1a8bac8b]
Examiner Must First Challenge Utility
Note:
The examiner must first provide evidence showing reasonable doubt of the invention’s utility before shifting the burden to the applicant to provide rebuttal evidence.

The examiner has the initial burden of challenging an asserted utility. Only after the examiner has provided evidence showing that one of ordinary skill in the art would reasonably doubt the asserted utility does the burden shift to the applicant to provide rebuttal evidence sufficient to convince one of ordinary skill in the art of the invention’s asserted utility. In re Fisher, 421 F.3d 1365, 76 USPQ2d 1225 (Fed. Cir. 2005); In re Swartz, 232 F.3d 862, 863, 56 USPQ2d 1703, 1704 (Fed. Cir. 2000); In re Brana, 51 F.3d 1560, 1566, 34 USPQ2d 1436, 1441 (Fed. Cir. 1995) (citing In re Bundy, 642 F.2d 430, 433, 209 USPQ 48, 51 (CCPA 1981)).

Jump to MPEP SourcePatent EligibilityResponding to 101 RejectionsUtility Requirement
Topic

Assignee as Applicant Signature

2 rules
StatutoryRequiredAlways
[mpep-2164-07-f396bc82ae6d86cffd8781d6]
Burden Shifts to Applicant to Rebut Utility Assertion
Note:
If a rejection under 35 U.S.C. 101 is properly imposed, the applicant must provide evidence supporting the asserted utility without needing to prove it beyond a reasonable doubt.

If a rejection under 35 U.S.C. 101 has been properly imposed, along with a corresponding rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, the burden shifts to the applicant to rebut the prima facie showing. In re Oetiker, 977 F.2d 1443, 1445, 24 USPQ2d 1443, 1444 (Fed. Cir. 1992). There is no predetermined amount or character of evidence that must be provided by an applicant to support an asserted utility. Rather, the character and amount of evidence needed to support an asserted utility will vary depending on what is claimed (Ex parte Ferguson, 117 USPQ 229, 231 (Bd. App. 1957)), and whether the asserted utility appears to contravene established scientific principles and beliefs. In re Gazave, 379 F.2d 973, 978, 154 USPQ 92, 96 (CCPA 1967); In re Chilowsky, 229 F.2d 457, 462, 108 USPQ 321, 325 (CCPA 1956). Furthermore, the applicant does not have to provide evidence sufficient to establish that an asserted utility is true “beyond a reasonable doubt.” In re Irons, 340 F.2d 974, 978, 144 USPQ 351, 354 (CCPA 1965). Instead, evidence will be sufficient if, considered as a whole, it leads a person of ordinary skill in the art to conclude that the asserted utility is more likely than not true. See MPEP § 2107.02 for a more detailed discussion of consideration of a reply to a prima facie rejection for lack of utility and evaluation of evidence related to utility.

Jump to MPEP SourceAssignee as Applicant SignatureApplicant and Assignee Filing Under AIA35 U.S.C. 112(a) – Written Description & Enablement
StatutoryInformativeAlways
[mpep-2164-07-8ebdfa336163ceb3410e3f3a]
Amount of Utility Evidence Varies Depending on Claimed Utility
Note:
The character and amount of evidence needed to support an asserted utility vary based on the claim and whether it contradicts established scientific principles.

If a rejection under 35 U.S.C. 101 has been properly imposed, along with a corresponding rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, the burden shifts to the applicant to rebut the prima facie showing. In re Oetiker, 977 F.2d 1443, 1445, 24 USPQ2d 1443, 1444 (Fed. Cir. 1992). There is no predetermined amount or character of evidence that must be provided by an applicant to support an asserted utility. Rather, the character and amount of evidence needed to support an asserted utility will vary depending on what is claimed (Ex parte Ferguson, 117 USPQ 229, 231 (Bd. App. 1957)), and whether the asserted utility appears to contravene established scientific principles and beliefs. In re Gazave, 379 F.2d 973, 978, 154 USPQ 92, 96 (CCPA 1967); In re Chilowsky, 229 F.2d 457, 462, 108 USPQ 321, 325 (CCPA 1956). Furthermore, the applicant does not have to provide evidence sufficient to establish that an asserted utility is true “beyond a reasonable doubt.” In re Irons, 340 F.2d 974, 978, 144 USPQ 351, 354 (CCPA 1965). Instead, evidence will be sufficient if, considered as a whole, it leads a person of ordinary skill in the art to conclude that the asserted utility is more likely than not true. See MPEP § 2107.02 for a more detailed discussion of consideration of a reply to a prima facie rejection for lack of utility and evaluation of evidence related to utility.

Jump to MPEP SourceAssignee as Applicant SignatureApplicant and Assignee Filing Under AIAEnablement Requirement (MPEP 2164)
Topic

Specific, Substantial, and Credible Utility

1 rules
StatutoryInformativeAlways
[mpep-2164-07-0cf5d2e652ebb1ad4d370732]
Disclosure of Utility Does Not Guarantee Compliance with 112(a)
Note:
An applicant's disclosure of a specific and substantial utility for an invention, along with a credible basis supporting it, does not alone ensure compliance with the requirements of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph.

If an applicant has disclosed a specific and substantial utility for an invention and provided a credible basis supporting that utility, that fact alone does not provide a basis for concluding that the claims comply with all the requirements of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. For example, if an applicant has claimed a process of treating a certain disease condition with a certain compound and provided a credible basis for asserting that the compound is useful in that regard, but to actually practice the invention as claimed a person skilled in the relevant art would have to engage in an undue amount of experimentation, the claim may be defective under 35 U.S.C. 112, but not 35 U.S.C. 101. To avoid confusion during examination, any rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, based on grounds other than “lack of utility” should be imposed separately from any rejection imposed due to “lack of utility” under 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph.

Jump to MPEP SourceSpecific, Substantial, and Credible UtilityAssignee as Applicant SignatureApplicant and Assignee Filing Under AIA
Topic

Composition of Matter

1 rules
StatutoryRecommendedAlways
[mpep-2164-07-fd362b022ae49535301e45d8]
Claims Must Be Supported by Utility
Note:
The claims must be supported by a credible basis for utility, but an undue amount of experimentation required to practice the invention does not comply with 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph.

If an applicant has disclosed a specific and substantial utility for an invention and provided a credible basis supporting that utility, that fact alone does not provide a basis for concluding that the claims comply with all the requirements of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. For example, if an applicant has claimed a process of treating a certain disease condition with a certain compound and provided a credible basis for asserting that the compound is useful in that regard, but to actually practice the invention as claimed a person skilled in the relevant art would have to engage in an undue amount of experimentation, the claim may be defective under 35 U.S.C. 112, but not 35 U.S.C. 101. To avoid confusion during examination, any rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, based on grounds other than “lack of utility” should be imposed separately from any rejection imposed due to “lack of utility” under 35 U.S.C. 101 and 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph.

Jump to MPEP SourceComposition of MatterProcess (Method)Quantity of Experimentation (MPEP 2164.06)
Topic

Test of Enablement (MPEP 2164.01)

1 rules
StatutoryInformativeAlways
[mpep-2164-07-e28e26d8ad203e2a83ba7690]
Evidence Must Likely Prove Utility
Note:
Applicant must provide evidence that leads a person of ordinary skill to conclude the asserted utility is more likely than not true.

If a rejection under 35 U.S.C. 101 has been properly imposed, along with a corresponding rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, the burden shifts to the applicant to rebut the prima facie showing. In re Oetiker, 977 F.2d 1443, 1445, 24 USPQ2d 1443, 1444 (Fed. Cir. 1992). There is no predetermined amount or character of evidence that must be provided by an applicant to support an asserted utility. Rather, the character and amount of evidence needed to support an asserted utility will vary depending on what is claimed (Ex parte Ferguson, 117 USPQ 229, 231 (Bd. App. 1957)), and whether the asserted utility appears to contravene established scientific principles and beliefs. In re Gazave, 379 F.2d 973, 978, 154 USPQ 92, 96 (CCPA 1967); In re Chilowsky, 229 F.2d 457, 462, 108 USPQ 321, 325 (CCPA 1956). Furthermore, the applicant does not have to provide evidence sufficient to establish that an asserted utility is true “beyond a reasonable doubt.” In re Irons, 340 F.2d 974, 978, 144 USPQ 351, 354 (CCPA 1965). Instead, evidence will be sufficient if, considered as a whole, it leads a person of ordinary skill in the art to conclude that the asserted utility is more likely than not true. See MPEP § 2107.02 for a more detailed discussion of consideration of a reply to a prima facie rejection for lack of utility and evaluation of evidence related to utility.

Jump to MPEP SourceTest of Enablement (MPEP 2164.01)Enablement Requirement (MPEP 2164)Assignee as Applicant Signature
Topic

Determining Whether Application Is AIA or Pre-AIA

1 rules
StatutoryInformativeAlways
[mpep-2164-07-4c6e9e6e47857246c2a97268]
Enablement Must Be Demonstrated for Useful Invention
Note:
The specification must enable a skilled artisan to use the invention even if it has great utility.

In some instances, the utility of the claimed invention will be provided, but the skilled artisan will not know how to effect that use. In such a case, no rejection will be made under 35 U.S.C. 101, but a rejection will be made under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph. As pointed out in Mowry v. Whitney, 81 U.S. (14 Wall.) 620 (1871), an invention may in fact have great utility, i.e., may be “a highly useful invention,” but the specification may still fail to “enable any person skilled in the art or science” to use the invention. 81 U.S. (14 Wall.) at 644.

Jump to MPEP SourceDetermining Whether Application Is AIA or Pre-AIADetermining AIA vs Pre-AIA Applicability (MPEP 2159)Enablement Requirement (MPEP 2164)

Citations

Primary topicCitation
35 U.S.C. 101 – Patent Eligibility
35 U.S.C. 112(a) – Written Description & Enablement
Assignee as Applicant Signature
Composition of Matter
Determining Whether Application Is AIA or Pre-AIA
Enablement Requirement (MPEP 2164)
How to Use the Invention (MPEP 2164.01(c))
Lack of Utility Rejection
Responding to 101 Rejections
Specific, Substantial, and Credible Utility
Test of Enablement (MPEP 2164.01)
35 U.S.C. § 101
35 U.S.C. 101 – Patent Eligibility
35 U.S.C. 112(a) – Written Description & Enablement
Assignee as Applicant Signature
Composition of Matter
Determining Whether Application Is AIA or Pre-AIA
Enablement Requirement (MPEP 2164)
How to Use the Invention (MPEP 2164.01(c))
Lack of Utility Rejection
Responding to 101 Rejections
Specific, Substantial, and Credible Utility
Test of Enablement (MPEP 2164.01)
35 U.S.C. § 112
35 U.S.C. 101 – Patent Eligibility
35 U.S.C. 112(a) – Written Description & Enablement
Assignee as Applicant Signature
Composition of Matter
Determining Whether Application Is AIA or Pre-AIA
Enablement Requirement (MPEP 2164)
How to Use the Invention (MPEP 2164.01(c))
Lack of Utility Rejection
Responding to 101 Rejections
Specific, Substantial, and Credible Utility
Test of Enablement (MPEP 2164.01)
35 U.S.C. § 112(a)
35 U.S.C. 112(a) – Written Description & Enablement
How to Use the Invention (MPEP 2164.01(c))
Responding to 101 Rejections
37 CFR § 2107.03
35 U.S.C. 112(a) – Written Description & Enablement
How to Use the Invention (MPEP 2164.01(c))
Responding to 101 Rejections
MPEP § 2107
Assignee as Applicant Signature
Test of Enablement (MPEP 2164.01)
MPEP § 2107.02
35 U.S.C. 101 – Patent Eligibility
Responding to 101 Rejections
In re Brana, 51 F.3d 1560, 1566, 34 USPQ2d 1436, 1441 (Fed. Cir. 1995)
35 U.S.C. 101 – Patent Eligibility
Responding to 101 Rejections
In re Bundy, 642 F.2d 430, 433, 209 USPQ 48, 51 (CCPA 1981)
Assignee as Applicant Signature
Test of Enablement (MPEP 2164.01)
In re Chilowsky, 229 F.2d 457, 462, 108 USPQ 321, 325 (CCPA 1956)
35 U.S.C. 101 – Patent Eligibility
Responding to 101 Rejections
In re Fisher, 421 F.3d 1365, 76 USPQ2d 1225 (Fed. Cir. 2005)
Enablement Requirement (MPEP 2164)
How to Use the Invention (MPEP 2164.01(c))
Lack of Utility Rejection
In re Fouche, 439 F.2d 1237, 169 USPQ 429 (CCPA 1971)
Assignee as Applicant Signature
Test of Enablement (MPEP 2164.01)
In re Gazave, 379 F.2d 973, 978, 154 USPQ 92, 96 (CCPA 1967)
Assignee as Applicant Signature
Test of Enablement (MPEP 2164.01)
In re Irons, 340 F.2d 974, 978, 144 USPQ 351, 354 (CCPA 1965)
Assignee as Applicant Signature
Test of Enablement (MPEP 2164.01)
In re Oetiker, 977 F.2d 1443, 1445, 24 USPQ2d 1443, 1444 (Fed. Cir. 1992)
35 U.S.C. 101 – Patent Eligibility
Responding to 101 Rejections
In re Swartz, 232 F.3d 862, 863, 56 USPQ2d 1703, 1704 (Fed. Cir. 2000)

Source Text from USPTO’s MPEP

This is an exact copy of the MPEP from the USPTO. It is here for your reference to see the section in context.

BlueIron Last Updated: 2025-12-31