MPEP § 2173.05(d) — Exemplary Claim Language (“for example,” “such as”) (Annotated Rules)

§2173.05(d) Exemplary Claim Language (“for example,” “such as”)

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

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

Exemplary Claim Language (“for example,” “such as”)

This section addresses Exemplary Claim Language (“for example,” “such as”). Primary authority: 35 U.S.C. 112(b) and 35 U.S.C. 112. Contains: 3 guidance statements and 1 other statement.

Key Rules

Topic

Alternative Limitations (MPEP 2173.05(h))

4 rules
StatutoryInformativeAlways
[mpep-2173-05-d-8ed3e926f3573b456a106620]
Examples Should Not Be In Claims
Note:
Claims must clearly define the scope of protection without including examples that may cause confusion.

Description of examples or preferences is properly set forth in the specification rather than the claims. If stated in the claims, examples and preferences may lead to confusion over the intended scope of a claim. In those instances where it is not clear whether the claimed narrower range is a limitation, a rejection under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph should be made. The examiner should analyze whether the metes and bounds of the claim are clearly set forth. Note that the mere use of the phrase “such as” or “for example" in a claim does not by itself render the claim indefinite.

Jump to MPEP SourceAlternative Limitations (MPEP 2173.05(h))Lack of Antecedent Basis (MPEP 2173.05(e))Patent Application Content
StatutoryRecommendedAlways
[mpep-2173-05-d-8de600e7de10c60500e8f7e2]
Examples and Preferences May Lead to Claim Ambiguity
Note:
If examples or preferences are stated in the claims, it may cause confusion about the intended scope. A rejection under section 112(b) should be made if the narrower range is unclear.

Description of examples or preferences is properly set forth in the specification rather than the claims. If stated in the claims, examples and preferences may lead to confusion over the intended scope of a claim. In those instances where it is not clear whether the claimed narrower range is a limitation, a rejection under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph should be made. The examiner should analyze whether the metes and bounds of the claim are clearly set forth. Note that the mere use of the phrase “such as” or “for example" in a claim does not by itself render the claim indefinite.

Jump to MPEP SourceAlternative Limitations (MPEP 2173.05(h))Lack of Antecedent Basis (MPEP 2173.05(e))Numerical Ranges and Amounts (MPEP 2173.05(c))
StatutoryRecommendedAlways
[mpep-2173-05-d-b7683c01192097b99e41bce7]
Claims Must Clearly Set Boundaries
Note:
Examiners must ensure claims are clearly defined, avoiding indefinite language like 'such as' or 'for example'.

Description of examples or preferences is properly set forth in the specification rather than the claims. If stated in the claims, examples and preferences may lead to confusion over the intended scope of a claim. In those instances where it is not clear whether the claimed narrower range is a limitation, a rejection under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph should be made. The examiner should analyze whether the metes and bounds of the claim are clearly set forth. Note that the mere use of the phrase “such as” or “for example" in a claim does not by itself render the claim indefinite.

Jump to MPEP SourceAlternative Limitations (MPEP 2173.05(h))Lack of Antecedent Basis (MPEP 2173.05(e))Use Claims (MPEP 2173.05(q))
StatutoryRecommendedAlways
[mpep-2173-05-d-c37d2891d358cbad996dd6ab]
Indefinite Claim Language Not Per Se Rules
Note:
Guidance on when to reject claim language as indefinite under section 112(b) based on specific facts rather than applying it as a general rule.

The above examples of claim language which have been held to be indefinite are fact specific and should not be applied as per se rules. See MPEP § 2173.02 for guidance regarding when it is appropriate to make a rejection under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.

Jump to MPEP SourceAlternative Limitations (MPEP 2173.05(h))Lack of Antecedent Basis (MPEP 2173.05(e))Determining Claim Definiteness (MPEP 2173.02)

Citations

Primary topicCitation
Alternative Limitations (MPEP 2173.05(h))35 U.S.C. § 112
Alternative Limitations (MPEP 2173.05(h))35 U.S.C. § 112(b)
Alternative Limitations (MPEP 2173.05(h))MPEP § 2173.02

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