Markman Hearing Brief
Drafts a claim construction brief persuading the court to adopt the client's proposed constructions of disputed patent claim terms under the Phillips framework.
Prerequisites
Gather before drafting:
- Patent-in-suit — claims, specification (column:line or ¶ cites), drawings
- Prosecution history — office actions, responses, amendments, examiner interviews
- Disputed terms — each term with client's and opposing party's proposed constructions
- Party position — plaintiff/defendant; opening/responsive brief
- Local rules — font, margins, page/word limits, caption format, CM/ECF requirements
- Case management order — briefing schedule, page limits, claim construction procedures
Brief Structure
1. Caption & Title Page
Court name, parties, case number, and title per local rules. Title format: "[Party]'s Opening/Responsive Brief in Support of Claim Construction."
2. TOC / TOA
- TOC: all sections with page refs — generate after final draft
- TOA: cases (alphabetical, Bluebook), statutes/rules, treatises/dictionaries
3. Introduction
- Identify patent-in-suit, disputed terms, and proposed constructions
- Include claim construction summary table:
| Disputed Term |
[Party]'s Construction |
Opposing Construction |
| "[term]" |
… |
… |
- Roadmap arguments; write for a generalist judge
4. Factual & Procedural Background
- The invention — problem solved and how; plain language
- Prosecution history — amendments, arguments overcoming rejections, estoppel implications
- Litigation posture — accused products/processes, procedural history to Markman hearing
- Cite spec by column:line or ¶; prosecution history by date and document
5. Legal Standards
Present the Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc) framework:
| Principle |
Rule |
| Ordinary meaning |
POSITA meaning at time of invention |
| Intrinsic hierarchy |
Claims → specification → prosecution history |
| Specification as context |
Read claims in light of spec; do not import limitations unless clearly intended |
| Claim differentiation |
Different terms presumed different meanings |
| Validity preservation |
Construe to preserve validity; cannot override ordinary meaning |
| Prosecution history estoppel |
Clear, unmistakable disavowals bind patentee |
| Extrinsic evidence |
May inform but cannot contradict intrinsic record |
Cite analogous Federal Circuit cases with parentheticals.
6. Proposed Constructions — Per Disputed Term
For each term, follow this sub-structure:
A. "[Claim Term]"
- Proposed construction: [precise language]
- Claim language — usage in context; cross-claim differentiation analysis
- Specification — quoted passages showing usage/definition; operation description; purpose/advantages
- Prosecution history — applicant statements on meaning; narrowing amendments; prior-art distinctions
- Extrinsic evidence (if applicable) — dictionaries, expert declarations, treatises; must confirm, not contradict, intrinsic record
- Rebuttal — why opposing construction conflicts with intrinsic evidence, renders language superfluous, or fails under Phillips hierarchy
7. Conclusion
- Summary table restating each proposed construction
- Request court adopt constructions
- No new arguments or evidence
8. Certificate of Service
Date, parties served, method (CM/ECF), counsel signature. Comply with FRCP 5 and local rules.
Critical Rules
- Phillips framework governs — organize every term through intrinsic evidence hierarchy
- Never import spec limitations unless patentee acted as own lexicographer or clearly disclaimed scope
- Quote precisely — spec by column:line or ¶; prosecution history by document and date
- Anticipate opposition — preemptively address strongest counterarguments per term
- Consistency — proposed constructions must work across all claims containing the term
- Accessibility — explain technical terms for a non-specialist judge
- Tone — professional, respectful, forceful; never dismissive of opposing positions
Final QC Checklist
1---2name: markman-hearing-brief3description: Drafts Markman Hearing Briefs for patent claim construction under the Phillips framework. Structures disputed-term analysis from intrinsic evidence (claims, specification, prosecution history) with local-rule-compliant formatting. Use when preparing claim construction briefs, Markman hearing submissions, or patent claim interpretation arguments in US federal court.4---56# Markman Hearing Brief78Drafts a claim construction brief persuading the court to adopt the client's proposed constructions of disputed patent claim terms under the Phillips framework.910## Prerequisites1112Gather before drafting:1314- **Patent-in-suit** — claims, specification (column:line or ¶ cites), drawings15- **Prosecution history** — office actions, responses, amendments, examiner interviews16- **Disputed terms** — each term with client's and opposing party's proposed constructions17- **Party position** — plaintiff/defendant; opening/responsive brief18- **Local rules** — font, margins, page/word limits, caption format, CM/ECF requirements19- **Case management order** — briefing schedule, page limits, claim construction procedures2021## Brief Structure2223### 1. Caption & Title Page2425Court name, parties, case number, and title per local rules. Title format: "[Party]'s Opening/Responsive Brief in Support of Claim Construction."2627### 2. TOC / TOA2829- **TOC**: all sections with page refs — generate after final draft30- **TOA**: cases (alphabetical, Bluebook), statutes/rules, treatises/dictionaries3132### 3. Introduction3334- Identify patent-in-suit, disputed terms, and proposed constructions35- Include claim construction summary table:3637| Disputed Term | [Party]'s Construction | Opposing Construction |38|---|---|---|39| "[term]" | … | … |4041- Roadmap arguments; write for a generalist judge4243### 4. Factual & Procedural Background4445- **The invention** — problem solved and how; plain language46- **Prosecution history** — amendments, arguments overcoming rejections, estoppel implications47- **Litigation posture** — accused products/processes, procedural history to Markman hearing48- Cite spec by column:line or ¶; prosecution history by date and document4950### 5. Legal Standards5152Present the Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc) framework:5354| Principle | Rule |55|---|---|56| Ordinary meaning | POSITA meaning at time of invention |57| Intrinsic hierarchy | Claims → specification → prosecution history |58| Specification as context | Read claims in light of spec; do not import limitations unless clearly intended |59| Claim differentiation | Different terms presumed different meanings |60| Validity preservation | Construe to preserve validity; cannot override ordinary meaning |61| Prosecution history estoppel | Clear, unmistakable disavowals bind patentee |62| Extrinsic evidence | May inform but cannot contradict intrinsic record |6364Cite analogous Federal Circuit cases with parentheticals.6566### 6. Proposed Constructions — Per Disputed Term6768For each term, follow this sub-structure:6970**A. "[Claim Term]"**71- **Proposed construction:** [precise language]72- **Claim language** — usage in context; cross-claim differentiation analysis73- **Specification** — quoted passages showing usage/definition; operation description; purpose/advantages74- **Prosecution history** — applicant statements on meaning; narrowing amendments; prior-art distinctions75- **Extrinsic evidence** (if applicable) — dictionaries, expert declarations, treatises; must confirm, not contradict, intrinsic record76- **Rebuttal** — why opposing construction conflicts with intrinsic evidence, renders language superfluous, or fails under Phillips hierarchy7778### 7. Conclusion7980- Summary table restating each proposed construction81- Request court adopt constructions82- No new arguments or evidence8384### 8. Certificate of Service8586Date, parties served, method (CM/ECF), counsel signature. Comply with FRCP 5 and local rules.8788## Critical Rules8990- **Phillips framework governs** — organize every term through intrinsic evidence hierarchy91- **Never import spec limitations** unless patentee acted as own lexicographer or clearly disclaimed scope92- **Quote precisely** — spec by column:line or ¶; prosecution history by document and date93- **Anticipate opposition** — preemptively address strongest counterarguments per term94- **Consistency** — proposed constructions must work across all claims containing the term95- **Accessibility** — explain technical terms for a non-specialist judge96- **Tone** — professional, respectful, forceful; never dismissive of opposing positions9798## Final QC Checklist99100- [ ] All citations verified against source documents101- [ ] Cross-references correct102- [ ] Word/page count within local-rule limits103- [ ] TOC/TOA regenerated after final edits104- [ ] Local-rule formatting confirmed (font, margins, spacing, caption)105- [ ] Certificate of service complete
lev-os