The Doctrinal Framework
Under 35 U.S.C. § 112(a), a patent specification must contain a written description of the invention sufficient to enable a person skilled in the art to make and use it. The written description requirement — distinct from enablement — demands that the original disclosure convey to skilled artisans that the inventor possessed the claimed invention as of the filing date.
The Federal Circuit's seminal analysis in Ariad Pharmaceuticals, Inc. v. Eli Lilly & Co., 598 F.3d 1336 (Fed. Cir. 2010) (en banc), confirmed that written description is an independent requirement separate from enablement. The court held that adequate written description requires "a precise definition, such as by structure, formula, chemical name, physical properties, or other properties, of species falling within the genus."
"The test for sufficiency is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date."
— Ariad Pharmaceuticals v. Eli Lilly, Fed. Cir. 2010 (en banc)
Common Triggers for § 112(a) Rejections
Examiners most frequently raise new matter objections in three scenarios. Understanding each helps practitioners anticipate rejections and draft proactive arguments.
1. Claim Amendments That Broaden Scope
When applicants amend claims during prosecution — particularly to broaden claim scope after a prior art rejection — examiners scrutinize whether the amended language finds adequate support in the originally filed specification. This is especially common when applicants attempt to:
- Replace a specific embodiment with a genus claim
- Remove a structural limitation that was present in all disclosed examples
- Add functional language that encompasses structures not described in the specification
2. PCT Applications Entering the US National Phase
PCT applications frequently encounter § 112(a) issues at national phase entry, particularly when the original filing was drafted under Chinese practice (GB/T standards) or EPO conventions. The MPEP's written description requirements are stricter in certain respects than either CNIPA or EPO rules.
Chinese patent specifications drafted under GB/T 15834 conventions sometimes omit embodiment-level detail that USPTO examiners expect to see. When translating a Chinese priority application for US prosecution, consider whether the specification adequately "blaze[s] the trail" to each claim element, not just the preferred embodiment.
3. Continuation and CIP Applications
Continuation-in-part applications are inherently susceptible to § 112(a) rejections because the new matter added in a CIP can only support claims with an effective filing date of the CIP, not the parent. Examiners may reject claims that rely on the CIP's new disclosure when applicants assert the parent's priority date.
Building a Response Strategy
A well-structured § 112(a) response typically proceeds through three analytical steps before drafting the argument.
Step 1: Identify the Specific Rejection Basis
MPEP § 2163 sets out the examiner's burden: the Office bears the initial burden to present evidence or reasoning to support a prima facie case that the written description requirement has not been met. Examiners must do more than assert that a claim lacks support — they must identify specifically which claim language is unsupported and why.
Before drafting a response, confirm that the examiner has met this initial burden. If the rejection is merely conclusory — stating only that "the claims contain new matter" without identifying specific language — this is itself a procedurally insufficient rejection that can be overcome by demanding specificity.
Step 2: Map Claim Language to Specification Disclosure
Once the specific claim language at issue is identified, conduct a systematic search across:
- The specification's summary of the invention
- Each disclosed embodiment and example
- The original claims (which form part of the disclosure under § 112(a))
- The drawings and figure descriptions
- Any incorporation-by-reference material (though this is limited)
The Federal Circuit recognizes that a specification can implicitly disclose subject matter that is necessarily present in what is explicitly described. In Titanium Metals Corp. v. Banner, the court held that a disclosure of a range inherently discloses the endpoints and points within. Use inherency arguments carefully — they require strong technical support.
Step 3: Consider Whether to Amend or Argue
After mapping the claim language to the specification, practitioners face a strategic choice: amend the claims to track the specification language more closely, or argue that the claim is already supported. Each path carries different risks:
Amending claims to track specification language more closely can overcome the rejection but may create prosecution history estoppel that narrows claim scope under the doctrine of equivalents. Arguing without amending preserves claim scope but risks an advisory action if the examiner maintains the rejection.
Drafting the Response
An effective § 112(a) response argument typically follows this structure:
- Quote the legal standard — cite MPEP § 2163 and the Ariad test
- State the examiner's burden — note that the Office must provide substantive reasoning
- Identify specific support — cite column and line numbers, paragraph numbers, or drawing references for each claimed element
- Address each disputed term — do not respond globally; address each rejection point individually
- Conclude with a possession statement — affirmatively state that the specification demonstrates inventor possession as of the filing date
Conclusion
New matter rejections under § 112(a) demand a systematic, evidence-based response grounded in a careful reading of both the specification and the Federal Circuit's evolving jurisprudence on written description. The most common error practitioners make is responding at the level of general argument rather than specific textual support.
When the rejection is well-founded, strategic claim amendment — drafted to preserve maximum scope while tracking the specification — is usually preferable to an all-or-nothing argument. When the rejection is conclusory or misidentifies the disclosure, a well-structured traverse can overcome the rejection without any amendment at all.