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.4license: Apache-2.05---67# Markman Hearing Brief89Drafts a claim construction brief persuading the court to adopt the client's proposed constructions of disputed patent claim terms under the Phillips framework.1011## Prerequisites1213Gather before drafting:1415- **Patent-in-suit** — claims, specification (column:line or ¶ cites), drawings16- **Prosecution history** — office actions, responses, amendments, examiner interviews17- **Disputed terms** — each term with client's and opposing party's proposed constructions18- **Party position** — plaintiff/defendant; opening/responsive brief19- **Local rules** — font, margins, page/word limits, caption format, CM/ECF requirements20- **Case management order** — briefing schedule, page limits, claim construction procedures2122## Brief Structure2324### 1. Caption & Title Page2526Court name, parties, case number, and title per local rules. Title format: "[Party]'s Opening/Responsive Brief in Support of Claim Construction."2728### 2. TOC / TOA2930- **TOC**: all sections with page refs — generate after final draft31- **TOA**: cases (alphabetical, Bluebook), statutes/rules, treatises/dictionaries3233### 3. Introduction3435- Identify patent-in-suit, disputed terms, and proposed constructions36- Include claim construction summary table:3738| Disputed Term | [Party]'s Construction | Opposing Construction |39|---|---|---|40| "[term]" | … | … |4142- Roadmap arguments; write for a generalist judge4344### 4. Factual & Procedural Background4546- **The invention** — problem solved and how; plain language47- **Prosecution history** — amendments, arguments overcoming rejections, estoppel implications48- **Litigation posture** — accused products/processes, procedural history to Markman hearing49- Cite spec by column:line or ¶; prosecution history by date and document5051### 5. Legal Standards5253Present the Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc) framework:5455| Principle | Rule |56|---|---|57| Ordinary meaning | POSITA meaning at time of invention |58| Intrinsic hierarchy | Claims → specification → prosecution history |59| Specification as context | Read claims in light of spec; do not import limitations unless clearly intended |60| Claim differentiation | Different terms presumed different meanings |61| Validity preservation | Construe to preserve validity; cannot override ordinary meaning |62| Prosecution history estoppel | Clear, unmistakable disavowals bind patentee |63| Extrinsic evidence | May inform but cannot contradict intrinsic record |6465Cite analogous Federal Circuit cases with parentheticals.6667### 6. Proposed Constructions — Per Disputed Term6869For each term, follow this sub-structure:7071**A. "[Claim Term]"**72- **Proposed construction:** [precise language]73- **Claim language** — usage in context; cross-claim differentiation analysis74- **Specification** — quoted passages showing usage/definition; operation description; purpose/advantages75- **Prosecution history** — applicant statements on meaning; narrowing amendments; prior-art distinctions76- **Extrinsic evidence** (if applicable) — dictionaries, expert declarations, treatises; must confirm, not contradict, intrinsic record77- **Rebuttal** — why opposing construction conflicts with intrinsic evidence, renders language superfluous, or fails under Phillips hierarchy7879### 7. Conclusion8081- Summary table restating each proposed construction82- Request court adopt constructions83- No new arguments or evidence8485### 8. Certificate of Service8687Date, parties served, method (CM/ECF), counsel signature. Comply with FRCP 5 and local rules.8889## Critical Rules9091- **Phillips framework governs** — organize every term through intrinsic evidence hierarchy92- **Never import spec limitations** unless patentee acted as own lexicographer or clearly disclaimed scope93- **Quote precisely** — spec by column:line or ¶; prosecution history by document and date94- **Anticipate opposition** — preemptively address strongest counterarguments per term95- **Consistency** — proposed constructions must work across all claims containing the term96- **Accessibility** — explain technical terms for a non-specialist judge97- **Tone** — professional, respectful, forceful; never dismissive of opposing positions9899## Final QC Checklist100101- [ ] All citations verified against source documents102- [ ] Cross-references correct103- [ ] Word/page count within local-rule limits104- [ ] TOC/TOA regenerated after final edits105- [ ] Local-rule formatting confirmed (font, margins, spacing, caption)106- [ ] Certificate of service complete
ThomasMoreAI