MPEP § 1302.01 — General Review of Disclosure (Annotated Rules)

§1302.01 General Review of Disclosure

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

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

General Review of Disclosure

This section addresses General Review of Disclosure. Primary authority: 35 U.S.C. 112(a), 37 CFR 1.121(e), and 37 CFR 1.126. Contains: 4 guidance statements and 1 permission.

Key Rules

Topic

Maintenance Fee Payment

2 rules
MPEP GuidanceRecommendedAlways
[mpep-1302-01-ae77690f45b9321e80dd8b88]
Claims Must Be Supported by Description
Note:
When an application is apparently ready for allowance, the examiner must ensure claims are fully supported by the original disclosure.

When an application is apparently ready for allowance, it should be reviewed by the examiner to make certain that the whole application meets all formal and substantive (i.e., statutory) requirements and that the language of the claims is enabled by, and finds adequate descriptive support in, the application disclosure as originally filed. Neglect to give due attention to these matters may lead to confusion as to the scope of the patent.

Jump to MPEP SourceMaintenance Fee Payment
MPEP GuidancePermittedAlways
[mpep-1302-01-5095a1dfc6963c6bd30a07b1]
Claims Must Be Supported by Description
Note:
The application must ensure that the claims are fully supported by the original disclosure to avoid confusion about the patent's scope.

When an application is apparently ready for allowance, it should be reviewed by the examiner to make certain that the whole application meets all formal and substantive (i.e., statutory) requirements and that the language of the claims is enabled by, and finds adequate descriptive support in, the application disclosure as originally filed. Neglect to give due attention to these matters may lead to confusion as to the scope of the patent.

Jump to MPEP SourceMaintenance Fee Payment
Topic

Patent Application Content

1 rules
StatutoryRecommendedAlways
[mpep-1302-01-e8cb393fb2f8d5d8dc601f57]
Claims Must Be Supported by Specification
Note:
The claims must use terminology that is clearly supported in the specification to avoid ambiguity.

There should be clear support or antecedent basis in the specification for the terminology used in the claims. Usually, the original claims follow the nomenclature of the specification; but sometimes in amending the claims or in adding new claims, applicant employs terms that do not appear in the specification. This may result in uncertainty as to the interpretation to be given such terms. See MPEP § 608.01(o). It should be noted, however, that exact terms need not be used in haec verba to satisfy the written description requirement of 35 U.S.C. 112(a). Eiselstein v. Frank, 52 F.3d 1035, 1038, 34 USPQ2d 1467, 1470 (Fed. Cir. 1995); In re Wertheim, 541 F.2d 257, 265, 191 USPQ 90, 98 (CCPA 1976). See also 37 CFR 1.121(e) which merely requires substantial correspondence between the language of the claims and the language of the specification.

Jump to MPEP Source · 37 CFR 1.121(e)Patent Application ContentSpecificationDisclosure Requirements
Topic

Specification

1 rules
StatutoryRecommendedAlways
[mpep-1302-01-77345cc2dee902d14c1b7bd0]
Terms Not Appearing in Specification Require Antecedent Basis
Note:
The specification must provide clear support for terms used in claims that do not appear in the original specification.

There should be clear support or antecedent basis in the specification for the terminology used in the claims. Usually, the original claims follow the nomenclature of the specification; but sometimes in amending the claims or in adding new claims, applicant employs terms that do not appear in the specification. This may result in uncertainty as to the interpretation to be given such terms. See MPEP § 608.01(o). It should be noted, however, that exact terms need not be used in haec verba to satisfy the written description requirement of 35 U.S.C. 112(a). Eiselstein v. Frank, 52 F.3d 1035, 1038, 34 USPQ2d 1467, 1470 (Fed. Cir. 1995); In re Wertheim, 541 F.2d 257, 265, 191 USPQ 90, 98 (CCPA 1976). See also 37 CFR 1.121(e) which merely requires substantial correspondence between the language of the claims and the language of the specification.

Jump to MPEP Source · 37 CFR 1.121(e)SpecificationPatent Application ContentDisclosure Requirements

Citations

Primary topicCitation
Patent Application Content
Specification
35 U.S.C. § 112(a)
Patent Application Content
Specification
37 CFR § 1.121(e)
37 CFR § 1.126
37 CFR § 1.72
37 CFR § 606.01
37 CFR § 608.01(n)
MPEP § 1302.04
MPEP § 606
MPEP § 608.01(b)
MPEP § 608.01(j)
Patent Application Content
Specification
MPEP § 608.01(o)
Patent Application Content
Specification
Eiselstein v. Frank, 52 F.3d 1035, 1038, 34 USPQ2d 1467, 1470 (Fed. Cir. 1995)
Patent Application Content
Specification
In re Wertheim, 541 F.2d 257, 265, 191 USPQ 90, 98 (CCPA 1976)

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