Every claim amendment carries a hidden risk: adding something the original application never actually disclosed. Patent offices call this “new matter,” and it’s one of the most common – and most avoidable – reasons an amendment draws a rejection or objection. This guide covers what new matter is, why it happens even to careful drafters and a practical proofreading workflow to catch it before you file.
What “New Matter” Actually Means
New matter is subject matter added to a patent application, through amendment, that was not disclosed – expressly, implicitly, or inherently – in the application as originally filed. The rule exists in different but closely aligned forms across jurisdictions:
- United States: 35 U.S.C. § 132(a) prohibits amendments that introduce new matter into the disclosure. This is tightly linked to the written description requirement under 35 U.S.C. § 112(a), since a claim amendment lacking support in the original disclosure is treated as both a new matter and written description problem.
- Europe: Article 123(2) EPC prohibits amending a European patent application in a way that adds subject matter extending beyond the content of the application as filed. The EPO’s Enlarged Board of Appeal has described the underlying rationale plainly: an applicant should not be allowed to improve their position by adding subject matter that wasn’t disclosed in the application as filed.
The core idea is the same everywhere: whatever you claim after amendment has to already be there – literally, implicitly, or inherently – in the specification, claims, or drawings as they existed on the filing date. You can rearrange, consolidate, or rephrase; you cannot supplement.
Why New Matter Is Easy to Introduce by Accident
Most new matter problems aren’t the result of someone trying to sneak in an improvement. They happen because:
- The inventor described the invention more broadly during prosecution than they did at filing – a natural drift as understanding of the invention’s advantages develops.
- A limitation gets pulled from a related application, a parent case, or an IDS reference rather than from the specification actually being amended.
- Claim language is “cleaned up” for clarity and the cleanup subtly shifts scope – a word that sounds like a synonym isn’t always legally equivalent.
- A numerical range or value gets adjusted slightly to better distinguish over prior art, without checking whether the new number (or its endpoints) was actually disclosed.
- A feature described only in one embodiment gets generalized into a broader claim limitation without support for that generalization elsewhere in the specification.
- Drawings are used as the sole support for a feature that isn’t described in the text, when the drawings don’t clearly and unambiguously convey that feature as claimed.
None of these require bad intent. They require a proofreading process that doesn’t just check grammar and antecedent basis, but actively traces every claim limitation back to its origin in the original disclosure.
The Core Proofreading Principle: Trace, Don’t Trust Memory
The single most useful habit in amendment proofreading is this: for every word or phrase changed or added in a claim, locate – and note – exactly where in the original specification, claims, or drawings that language (or its clear equivalent) appears. If you can’t point to it, that’s the signal to stop and investigate, not to assume it’s fine because it “sounds like” something from the disclosure.
This matters because literal wording is not required – the claim doesn’t need to use the specification’s exact words to satisfy the written description requirement – but the concept being claimed does need to be conveyed by the original disclosure. That distinction is exactly where careless proofreading goes wrong: it’s easy to confirm that similar-sounding language exists somewhere in the specification while missing that it doesn’t actually convey the same technical concept now being claimed.
A Practical Amendment Proofreading Workflow
1. Build a support map before drafting the amendment
Before you write a single amended claim, identify the specific passages, paragraphs, or drawing elements in the originally filed application that support the intended change. Do this first, not as an afterthought – if support doesn’t exist, you need to know that before committing to the amendment strategy, not after filing it.
2. Compare word-by-word against the “as-filed” version, not the current version
Always check new claim language against the application as originally filed, not against a previously amended version of the specification or claims. Earlier amendments can themselves contain drift from the original disclosure and comparing against an already-amended baseline can let errors compound silently across multiple rounds of prosecution.
3. Flag every synonym, generalization and numeric change
Create a simple table for the amendment with three columns: claim language before, claim language after and specific support location. Anything that isn’t a literal carryover – a broadened term, a narrowed range, a rephrased limitation, a newly added qualifier – gets its own row and its own explicit support citation. If a row has no citation, treat it as a red flag requiring resolution before filing.
4. Watch generalizations from a single embodiment especially closely
If the specification describes a feature only in the context of one specific embodiment, example, or figure, claiming that feature in more general terms is one of the highest-risk moves in an amendment. Check whether the specification’s own language, elsewhere, supports treating the feature as generally applicable – or whether you’re implicitly claiming something broader than what was actually disclosed as part of the invention.
5. Treat drawings as support cautiously
A feature shown only in a drawing, without textual description, can sometimes support a claim amendment – but only if the drawing clearly and unambiguously conveys that feature to a person skilled in the art. Don’t treat “it’s visible in Figure 3” as automatically sufficient support; ask whether the drawing actually discloses the specific limitation being claimed, including its relationship to other claimed features, or whether you’re reading more into the drawing than it shows.
6. Check ranges and numeric endpoints specifically
Numeric amendments are a frequent, easy-to-miss source of new matter. If a claim originally recited “10–50°C” and gets amended to “15–45°C,” confirm that both new endpoints (and not just values somewhere inside the original range) are actually disclosed or clearly derivable from the specification’s discussion of sub-ranges or examples. A value that merely falls within a previously disclosed range isn’t automatically itself disclosed unless the specification supports treating it as a distinct endpoint.
7. Re-run the check after every editing round
New matter risk resets with every subsequent edit. A claim amendment that was fully supported in draft one can drift out of support after a second or third round of “just cleaning up the language,” especially when multiple people are editing across time zones or between attorney and inventor review. Re-verify support after any substantive language change, not just at final filing.
8. Document your support reasoning, don’t just rely on it internally
Both U.S. and European practice reward – and sometimes require – pointing out exactly where support for an amendment exists. Under U.S. practice, applicants are encouraged to specifically point out the support for amendments made to the disclosure and in some circumstances the examiner’s initial burden to reject an amendment as unsupported can shift once the applicant has identified where support lies. Keep a written record (even an internal one) of your support citations for each amendment – this becomes directly useful if a written description or added-matter rejection is later issued and you need to respond quickly and precisely.
Special Situations Worth Extra Care
- Claims added late in prosecution. A brand-new claim introduced well into examination gets the same scrutiny as an amended one – it must be supported by the disclosure as filed, not just be a logical extension of allowed claims.
- Amendments responding to a rejection. There’s a natural temptation, when trying to distinguish over prior art, to add a limitation that “must be true” of the invention even if it isn’t explicitly stated anywhere. Resist filling gaps with what seems obviously implied; implicit support has to be genuinely and clearly conveyed by the original disclosure, not merely plausible in hindsight.
- Combining features from different embodiments. Merging a feature from Embodiment A with a feature from Embodiment B into a single claim can introduce new matter if the specification never suggests those features work together – even though each feature, individually, has support somewhere in the application.
- Amendments carried over from a related or parent application. Don’t assume language that was fine in a parent or continuation application is automatically supported in a different application’s disclosure – check support against the specific document being amended, not the broader family.
- Disclaimers and exclusionary language. Adding language to affirmatively disclaim or exclude certain prior art features is sometimes treated differently than adding new affirmative limitations, but this is jurisdiction- and fact-specific – don’t assume a disclaimer is automatically free of new matter risk without checking current practice.
What to Do If You Find a Gap
If your proofreading process turns up a limitation you can’t trace to clear support, you generally have a few paths and the right one depends heavily on timing and jurisdiction:
- Rephrase the amendment using language that stays within what’s actually disclosed.
- Look more broadly across the entire original disclosure – support doesn’t have to come from the specific paragraph you started with and information in any part of the application as filed (specification, claims, or drawings) can support an amendment to any other part.
- If no support exists anywhere in the application, don’t file the amendment as drafted – discuss alternative claim strategies with the attorney or agent handling the case rather than filing language you can’t support, since an unsupported amendment risks both an immediate rejection and potential validity problems for any patent that later issues.
Quick Pre-Filing Checklist
- Every changed or added claim term is matched to a specific location in the application as originally filed
- Comparison was made against the as-filed application, not an intermediate amended version
- Generalizations from single embodiments were checked against the specification’s own support for broader applicability
- Any reliance on drawings alone was checked for clear, unambiguous disclosure of the claimed feature
- Numeric ranges and endpoints were verified against actual disclosed values, not just “falls within” a broader disclosed range
- The check was re-run after the most recent round of edits, not only at the first draft
- Support citations are documented and ready to reference if a rejection or objection is issued
- Claims combining features from different embodiments were checked for disclosure of that specific combination
A Note on Accuracy
New matter and written description standards are well-established doctrine, but their application is highly fact-specific and both the USPTO and EPO continue to refine guidance and case law on edge cases like implicit disclosure, range amendments and disclaimers. This article describes the general framework and a practical proofreading process; it isn’t a substitute for a qualified patent attorney or agent reviewing your specific amendment against your specific disclosure before filing.