MPEP § 2164.04 — Burden on the Examiner Under the Enablement Requirement (Annotated Rules)

§2164.04 Burden on the Examiner Under the Enablement Requirement

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

This page consolidates and annotates all enforceable requirements under MPEP § 2164.04, 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.

Burden on the Examiner Under the Enablement Requirement

This section addresses Burden on the Examiner Under the Enablement Requirement. Primary authority: 35 U.S.C. 112(a), 35 U.S.C. 112, and 35 U.S.C. 101). Contains: 1 requirement, 1 guidance statement, 1 permission, and 5 other statements.

Key Rules

Topic

Types of Office Actions

3 rules
StatutoryInformativeAlways
[mpep-2164-04-f16a999b3cd089b1bedb7409]
Citing New References Prevents Final Office Action
Note:
If new references or expanded arguments are cited in a second Office action, it cannot be made final.

In accordance with the principles of compact prosecution, if an enablement rejection is appropriate, the first Office action on the merits should present the best case with all the relevant reasons, issues, and evidence so that all such rejections can be withdrawn if applicant provides appropriate convincing arguments and/or evidence in rebuttal. Providing the best rejection in the first Office action will also allow the second Office action to be made final should applicant fail to provide appropriate convincing arguments and/or evidence. Citing new references and/or expanding arguments in a second Office action could prevent that Office action from being made final. The principles of compact prosecution also dictate that if an enablement rejection is appropriate and the examiner recognizes limitations that would render the claims enabled, the examiner should note such limitations to applicant as early in the prosecution as possible.

Jump to MPEP SourceTypes of Office ActionsExaminer's Action (37 CFR 1.104)Office Actions and Responses
MPEP GuidancePermittedAlways
[mpep-2164-04-401bd206273a73278f17c99b]
Examiner Must Define Terms for Enablement Analysis
Note:
The examiner must select and explicitly define terms in the claims that are not well-known or have multiple meanings when examining an application.

Before any analysis of enablement can occur, it is necessary for the examiner to construe the claims. For terms that are not well-known in the art, or for terms that could have more than one meaning, it is necessary that the examiner select the definition that the examiner intends to use when examining the application, based on their understanding of what applicant intends it to mean, and explicitly set forth the meaning of the term and the scope of the claim when writing an Office action. See Genentech v. Wellcome Foundation, 29 F.3d 1555, 1563-64, 31 USPQ2d 1161, 1167-68 (Fed. Cir. 1994).

Jump to MPEP SourceTypes of Office ActionsExaminer's Action (37 CFR 1.104)Office Actions and Responses
MPEP GuidanceInformativeAlways
[mpep-2164-04-183cbd533f215bd0656f8d99]
Claims Must Be Construed by Examiner
Note:
Examiner must define terms in claims based on applicant's intent and explicitly state the claim scope in Office actions.

Before any analysis of enablement can occur, it is necessary for the examiner to construe the claims. For terms that are not well-known in the art, or for terms that could have more than one meaning, it is necessary that the examiner select the definition that the examiner intends to use when examining the application, based on their understanding of what applicant intends it to mean, and explicitly set forth the meaning of the term and the scope of the claim when writing an Office action. See Genentech v. Wellcome Foundation, 29 F.3d 1555, 1563-64, 31 USPQ2d 1161, 1167-68 (Fed. Cir. 1994).

Jump to MPEP SourceTypes of Office ActionsExaminer's Action (37 CFR 1.104)Office Actions and Responses
Topic

Scope Commensurate with Disclosure

2 rules
StatutoryRequiredAlways
[mpep-2164-04-34ded6b93de07197aa4fbfec]
Examiner Must Establish Reasonable Basis for Questioning Enablement
Note:
The examiner must provide a reasonable explanation to question the enablement of the claimed invention, as established in In re Wright.

In order to make a rejection, the examiner has the initial burden to establish a reasonable basis to question the enablement provided for the claimed invention. In re Wright, 999 F.2d 1557, 1562, 27 USPQ2d 1510, 1513 (Fed. Cir. 1993) (examiner must provide a reasonable explanation as to why the scope of protection provided by a claim is not adequately enabled by the disclosure). A specification disclosure which contains a teaching of the manner and process of making and using an invention in terms which correspond in scope to those used in describing and defining the subject matter sought to be patented must be taken as being in compliance with the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, unless there is a reason to doubt the objective truth of the statements contained therein which must be relied on for enabling support. Assuming that sufficient reason for such doubt exists, a rejection for failure to teach how to make and/or use will be proper on that basis. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). As stated by the court, “it is incumbent upon the Patent Office, whenever a rejection on this basis is made, to explain why it doubts the truth or accuracy of any statement in a supporting disclosure and to back up assertions of its own with acceptable evidence or reasoning which is inconsistent with the contested statement. Otherwise, there would be no need for the applicant to go to the trouble and expense of supporting his presumptively accurate disclosure.” 439 F.2d at 224, 169 USPQ at 370 (emphasis in original).

Jump to MPEP SourceScope Commensurate with DisclosureDetermining Whether Application Is AIA or Pre-AIAEnablement Support for Claims
StatutoryRecommendedAlways
[mpep-2164-04-0c0e94974c99ada8ef271c6c]
Examiner Must Explain Why Specification Fails To Teach Invention Without Undue Experimentation
Note:
The examiner must provide specific findings of fact and evidence to conclude that the specification fails to teach how to make and use the claimed invention without undue experimentation or that the enablement provided is not commensurate with the claims.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceScope Commensurate with DisclosureUndue ExperimentationTest of Enablement (MPEP 2164.01)
Topic

Utility Requirement

2 rules
StatutoryInformativeAlways
[mpep-2164-04-1b492054b2f6fffea535574d]
Examiner Must Explain Enablement Uncertainty
Note:
The examiner must provide reasons for any uncertainty regarding the enablement of the invention, even in the absence of evidence of operability beyond disclosed embodiments.

According to In re Bowen, 492 F.2d 859, 862-63, 181 USPQ 48, 51 (CCPA 1974), the minimal requirement is for the examiner to give reasons explaining the uncertainty of the enablement. This standard is applicable even when there is no evidence in the record of operability without undue experimentation beyond the disclosed embodiments. See also 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)) (discussed in MPEP § 2164.07 regarding the relationship of the enablement requirement to the utility requirement of 35 U.S.C. 101).

Jump to MPEP SourceUtility RequirementPatent Eligibility
StatutoryInformativeAlways
[mpep-2164-04-739c7e28485a643f0ef74d73]
Examiner Must Explain Uncertainty of Enablement Without Undue Experimentation
Note:
The examiner must provide reasons for the uncertainty in enablement if there is no evidence of operability beyond the disclosed embodiments without undue experimentation.

According to In re Bowen, 492 F.2d 859, 862-63, 181 USPQ 48, 51 (CCPA 1974), the minimal requirement is for the examiner to give reasons explaining the uncertainty of the enablement. This standard is applicable even when there is no evidence in the record of operability without undue experimentation beyond the disclosed embodiments. See also 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)) (discussed in MPEP § 2164.07 regarding the relationship of the enablement requirement to the utility requirement of 35 U.S.C. 101).

Jump to MPEP SourceUtility RequirementPatent Eligibility
Topic

Establishing Prima Facie Case

2 rules
StatutoryRequiredAlways
[mpep-2164-04-9518db24ff73dd17034395a1]
Examiner Must Consider All Enablement Evidence
Note:
The examiner must analyze all evidence related to enablement factors and base any non-enablement conclusion on the overall evidence, not just one factor.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceEstablishing Prima Facie CaseScope Commensurate with DisclosureUndue Experimentation
StatutoryRequiredAlways
[mpep-2164-04-dc2de3fce401396e17b70abf]
Prima Facie Case for Lack of Enablement Not Always Required But Specific Technical Reasons Are
Note:
The examiner must provide specific technical reasons to support a lack of enablement but does not always need references to establish a prima facie case.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceEstablishing Prima Facie CaseClaim Patentability AnalysisEnablement Support for Claims
Topic

Undue Experimentation

2 rules
StatutoryPermittedAlways
[mpep-2164-04-af8f2e111ad2677cbf3b12fe]
Specification Must Describe Invention Without Undue Experimentation
Note:
The specification must provide sufficient detail for one skilled in the art to make and use the invention without undue experimentation.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceUndue ExperimentationTest of Enablement (MPEP 2164.01)Enablement Support for Claims
StatutoryRecommendedAlways
[mpep-2164-04-132ff5d7a3e71d04c9ca38ac]
Examiner Must Identify Missing Information for Undue Experimentation
Note:
The examiner must specify what information is missing and why it cannot be supplied without undue experimentation.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceUndue ExperimentationTest of Enablement (MPEP 2164.01)Enablement Support for Claims
Topic

First Action on Merits (FAOM)

2 rules
StatutoryRecommendedAlways
[mpep-2164-04-7a11c2e0862314b4639c921f]
First Office Action Must Present Best Case for Enablement Rejection
Note:
The first Office action on the merits should include all relevant reasons, issues, and evidence for an enablement rejection so that it can be withdrawn if applicant provides convincing rebuttal arguments or evidence.

In accordance with the principles of compact prosecution, if an enablement rejection is appropriate, the first Office action on the merits should present the best case with all the relevant reasons, issues, and evidence so that all such rejections can be withdrawn if applicant provides appropriate convincing arguments and/or evidence in rebuttal. Providing the best rejection in the first Office action will also allow the second Office action to be made final should applicant fail to provide appropriate convincing arguments and/or evidence. Citing new references and/or expanding arguments in a second Office action could prevent that Office action from being made final. The principles of compact prosecution also dictate that if an enablement rejection is appropriate and the examiner recognizes limitations that would render the claims enabled, the examiner should note such limitations to applicant as early in the prosecution as possible.

Jump to MPEP SourceFirst Action on Merits (FAOM)First Action on MeritsNon-Final Action Content
StatutoryRecommendedAlways
[mpep-2164-04-417c956aa17880a245a935e0]
Best Rejection in First Office Action
Note:
If the first Office action does not receive convincing arguments, it can lead to a final rejection in the second Office action.

In accordance with the principles of compact prosecution, if an enablement rejection is appropriate, the first Office action on the merits should present the best case with all the relevant reasons, issues, and evidence so that all such rejections can be withdrawn if applicant provides appropriate convincing arguments and/or evidence in rebuttal. Providing the best rejection in the first Office action will also allow the second Office action to be made final should applicant fail to provide appropriate convincing arguments and/or evidence. Citing new references and/or expanding arguments in a second Office action could prevent that Office action from being made final. The principles of compact prosecution also dictate that if an enablement rejection is appropriate and the examiner recognizes limitations that would render the claims enabled, the examiner should note such limitations to applicant as early in the prosecution as possible.

Jump to MPEP SourceFirst Action on Merits (FAOM)Non-Final Action ContentTypes of Office Actions
Topic

How to Make the Invention (MPEP 2164.01(b))

1 rules
StatutoryRequiredAlways
[mpep-2164-04-c5f557303d85778b11d88cd8]
Specification Must Describe Invention Completely
Note:
The specification must teach how to make and use the invention in detail, without doubt, for it to comply with the enablement requirement.

In order to make a rejection, the examiner has the initial burden to establish a reasonable basis to question the enablement provided for the claimed invention. In re Wright, 999 F.2d 1557, 1562, 27 USPQ2d 1510, 1513 (Fed. Cir. 1993) (examiner must provide a reasonable explanation as to why the scope of protection provided by a claim is not adequately enabled by the disclosure). A specification disclosure which contains a teaching of the manner and process of making and using an invention in terms which correspond in scope to those used in describing and defining the subject matter sought to be patented must be taken as being in compliance with the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, unless there is a reason to doubt the objective truth of the statements contained therein which must be relied on for enabling support. Assuming that sufficient reason for such doubt exists, a rejection for failure to teach how to make and/or use will be proper on that basis. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). As stated by the court, “it is incumbent upon the Patent Office, whenever a rejection on this basis is made, to explain why it doubts the truth or accuracy of any statement in a supporting disclosure and to back up assertions of its own with acceptable evidence or reasoning which is inconsistent with the contested statement. Otherwise, there would be no need for the applicant to go to the trouble and expense of supporting his presumptively accurate disclosure.” 439 F.2d at 224, 169 USPQ at 370 (emphasis in original).

Jump to MPEP SourceHow to Make the Invention (MPEP 2164.01(b))Enablement Support for ClaimsEnablement Requirement (MPEP 2164)
Topic

Assignee as Applicant Signature

1 rules
StatutoryInformativeAlways
[mpep-2164-04-4aff61f049607a6bef219a8f]
Examiner Must Provide Reason for Doubting Disclosure
Note:
The examiner must provide a reason to doubt the accuracy of an applicant's disclosure when questioning enablement, otherwise, the applicant’s presumptively accurate disclosure should be accepted.

In order to make a rejection, the examiner has the initial burden to establish a reasonable basis to question the enablement provided for the claimed invention. In re Wright, 999 F.2d 1557, 1562, 27 USPQ2d 1510, 1513 (Fed. Cir. 1993) (examiner must provide a reasonable explanation as to why the scope of protection provided by a claim is not adequately enabled by the disclosure). A specification disclosure which contains a teaching of the manner and process of making and using an invention in terms which correspond in scope to those used in describing and defining the subject matter sought to be patented must be taken as being in compliance with the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, unless there is a reason to doubt the objective truth of the statements contained therein which must be relied on for enabling support. Assuming that sufficient reason for such doubt exists, a rejection for failure to teach how to make and/or use will be proper on that basis. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). As stated by the court, “it is incumbent upon the Patent Office, whenever a rejection on this basis is made, to explain why it doubts the truth or accuracy of any statement in a supporting disclosure and to back up assertions of its own with acceptable evidence or reasoning which is inconsistent with the contested statement. Otherwise, there would be no need for the applicant to go to the trouble and expense of supporting his presumptively accurate disclosure.” 439 F.2d at 224, 169 USPQ at 370 (emphasis in original).

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

Enablement Requirement (MPEP 2164)

1 rules
StatutoryInformativeAlways
[mpep-2164-04-6dfb999963efa63d0e8e9cd7]
Examiner Must Explain Doubts on Enablement
Note:
The examiner must provide evidence or reasoning to doubt the enablement of a claim before rejecting it.

In order to make a rejection, the examiner has the initial burden to establish a reasonable basis to question the enablement provided for the claimed invention. In re Wright, 999 F.2d 1557, 1562, 27 USPQ2d 1510, 1513 (Fed. Cir. 1993) (examiner must provide a reasonable explanation as to why the scope of protection provided by a claim is not adequately enabled by the disclosure). A specification disclosure which contains a teaching of the manner and process of making and using an invention in terms which correspond in scope to those used in describing and defining the subject matter sought to be patented must be taken as being in compliance with the enablement requirement of 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, unless there is a reason to doubt the objective truth of the statements contained therein which must be relied on for enabling support. Assuming that sufficient reason for such doubt exists, a rejection for failure to teach how to make and/or use will be proper on that basis. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). As stated by the court, “it is incumbent upon the Patent Office, whenever a rejection on this basis is made, to explain why it doubts the truth or accuracy of any statement in a supporting disclosure and to back up assertions of its own with acceptable evidence or reasoning which is inconsistent with the contested statement. Otherwise, there would be no need for the applicant to go to the trouble and expense of supporting his presumptively accurate disclosure.” 439 F.2d at 224, 169 USPQ at 370 (emphasis in original).

Jump to MPEP SourceEnablement Requirement (MPEP 2164)Scope Commensurate with DisclosureHow to Make the Invention (MPEP 2164.01(b))
Topic

Test of Enablement (MPEP 2164.01)

1 rules
StatutoryInformativeAlways
[mpep-2164-04-7852d8956df89ea5202f107c]
Requirement for Considering All Enablement Factors
Note:
Examiners must consider all factors in MPEP § 2164.01(a) and base conclusions on evidence as a whole, not just one factor.

While the analysis and conclusion of a lack of enablement are based on the factors discussed in MPEP § 2164.01(a) and the evidence as a whole, it is not necessary to discuss each factor in the enablement rejection. However, it is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others. The examiner’s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole. In re Wands, 858 F.2d 731, 737, 740, 8 USPQ2d 1400, 1404, 1407 (Fed. Cir. 1988). The explanation of the rejection should focus on those factors, reasons, and evidence that lead the examiner to conclude e.g., that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims. This can be done by making specific findings of fact, supported by the evidence, and then drawing conclusions based on these findings of fact. For example, doubt may arise about enablement because information is missing about one or more essential parts or relationships between parts which one skilled in the art could not develop without undue experimentation. In such a case, the examiner should specifically identify what information is missing and why one skilled in the art could not supply the information without undue experimentation. See MPEP § 2164.06(a). References should be supplied if possible to support a prima facie case of lack of enablement, but are not always required. In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971). However, specific technical reasons are always required.

Jump to MPEP SourceTest of Enablement (MPEP 2164.01)Enablement Support for ClaimsEstablishing Prima Facie Case
Topic

Non-Final Action Content

1 rules
StatutoryRecommendedAlways
[mpep-2164-04-f791a836aa3bb527854e59e8]
Examiner Must Note Enablement Limitations Early
Note:
The examiner should identify and inform the applicant of limitations that would enable the claims as soon as possible during prosecution if an enablement rejection is appropriate.

In accordance with the principles of compact prosecution, if an enablement rejection is appropriate, the first Office action on the merits should present the best case with all the relevant reasons, issues, and evidence so that all such rejections can be withdrawn if applicant provides appropriate convincing arguments and/or evidence in rebuttal. Providing the best rejection in the first Office action will also allow the second Office action to be made final should applicant fail to provide appropriate convincing arguments and/or evidence. Citing new references and/or expanding arguments in a second Office action could prevent that Office action from being made final. The principles of compact prosecution also dictate that if an enablement rejection is appropriate and the examiner recognizes limitations that would render the claims enabled, the examiner should note such limitations to applicant as early in the prosecution as possible.

Jump to MPEP SourceNon-Final Action ContentRejections Not Based on Prior ArtRejection of Claims

Citations

Primary topicCitation
Utility Requirement35 U.S.C. § 101
Assignee as Applicant Signature
Enablement Requirement (MPEP 2164)
How to Make the Invention (MPEP 2164.01(b))
Scope Commensurate with Disclosure
35 U.S.C. § 112
Assignee as Applicant Signature
Enablement Requirement (MPEP 2164)
How to Make the Invention (MPEP 2164.01(b))
Scope Commensurate with Disclosure
35 U.S.C. § 112(a)
Establishing Prima Facie Case
Scope Commensurate with Disclosure
Test of Enablement (MPEP 2164.01)
Undue Experimentation
MPEP § 2164.01(a)
Establishing Prima Facie Case
Scope Commensurate with Disclosure
Test of Enablement (MPEP 2164.01)
Undue Experimentation
MPEP § 2164.06(a)
Utility RequirementMPEP § 2164.07
Utility RequirementIn re Brana, 51 F.3d 1560, 1566, 34 USPQ2d 1436, 1441 (Fed. Cir. 1995)
Utility RequirementIn re Bundy, 642 F.2d 430, 433, 209 USPQ 48, 51 (CCPA 1981)
Assignee as Applicant Signature
Enablement Requirement (MPEP 2164)
Establishing Prima Facie Case
How to Make the Invention (MPEP 2164.01(b))
Scope Commensurate with Disclosure
Test of Enablement (MPEP 2164.01)
Undue Experimentation
In re Marzocchi, 439 F.2d 220, 224, 169 USPQ 367, 370 (CCPA 1971)
Assignee as Applicant Signature
Enablement Requirement (MPEP 2164)
How to Make the Invention (MPEP 2164.01(b))
Scope Commensurate with Disclosure
In re Wright, 999 F.2d 1557, 1562, 27 USPQ2d 1510, 1513 (Fed. Cir. 1993)

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