Expert report review
Enablement and written description in the opposing invalidity report: what does a reviewer check after Amgen v. Sanofi?
An invalidity report under 35 U.S.C. 112 says that the patent's specification does not describe the invention or does not teach a skilled person to make and use it. A reviewer checks which requirement the opposing expert invokes, whether the opinion covers the full scope of the claims as Amgen v. Sanofi (2023) requires, and whether each statement about undue experimentation rests on tests, publications or other data.

What does section 112 require, and which defect is the opposing expert alleging?
Section 112(a) requires a written description and a disclosure that enables a skilled person to make and use the invention. Section 112(b) requires claims that particularly point out the invention. Each is a separate invalidity ground.
35 U.S.C. 112(a) states that the specification shall contain "a written description of the invention, and of the manner and process of making and using it," in terms that "enable any person skilled in the art" to make and use it. Under section 112(b) the specification ends with claims "particularly pointing out and distinctly claiming" the subject matter the inventor regards as the invention.
Under 35 U.S.C. 282(b)(3)(A), failure to comply with any requirement of section 112 is a defense in an infringement action. The statute carves out one requirement: failure to disclose the best mode is no basis for holding a claim invalid or unenforceable.
The Manual of Patent Examining Procedure of the USPTO, section 2163, calls the written description requirement "separate and distinct from the enablement requirement." A reviewer therefore starts by sorting the opposing report paragraph by paragraph. Some opinions say the inventor did not describe what is claimed. Others say a skilled person could not practice the claim. A third group says the claim boundaries are unclear. An opinion that blends the three cannot be checked against one legal test, and the review says so with page numbers.
Who carries the burden on a section 112 defense, and how much evidence is needed?
The party asserting invalidity. Under 35 U.S.C. 282(a) a patent is presumed valid, and in Cephalon v. Watson (Fed. Cir. 2013) the challenger had to prove lack of enablement by clear and convincing evidence.
Section 282(a) reads: "A patent shall be presumed valid." It adds that "the burden of establishing invalidity of a patent or any claim thereof shall rest on the party asserting such invalidity."
In Cephalon, Inc. v. Watson Pharmaceuticals, Inc., No. 2011-1325 (Fed. Cir. Feb. 14, 2013), Judge Wallach wrote for a panel with Judges Reyna and Bryson that "the challenger bears the burden, throughout the litigation, of proving lack of enablement by clear and convincing evidence." The court added that Watson "had the burden to show by way of testimony or documentary evidence the amount of experimentation needed."
For a review this fixes the order of work. When the client is the patent owner, the reviewer lists, claim by claim, the facts the challenger's expert offers and marks every statement that has no document, test or publication behind it. When the client is the challenger, the reviewer reads the patent owner's rebuttal report for the points where it answers that evidence and the points it leaves untouched.
What did Amgen v. Sanofi change for an enablement opinion?
The Supreme Court confirmed in 2023 that the specification must enable the full scope of the claims. An expert who examines only the worked examples of a broad functional claim has not covered the scope the claim reaches.
Amgen Inc. v. Sanofi, No. 21-757, was decided on May 18, 2023, in an opinion by Justice Gorsuch for a unanimous Court. Amgen's claims covered antibodies defined by what they do. In its patents Amgen "identified the amino acid sequences of 26 antibodies" that perform those functions.
The Court held that "the specification must enable the full scope of the invention as defined by its claims" and wrote: "The more one claims, the more one must enable." It also stated that a specification "may call for a reasonable amount of experimentation to make and use a patented invention."
Amgen pointed to two methods for making further antibodies, which the opinion calls the roadmap and conservative substitution. The Court described the first as Amgen's own "trial-and-error method for finding functional antibodies" and wrote that the two approaches "amount to little more than two research assignments." Its conclusion: Amgen "failed to enable all that it has claimed, even allowing for a reasonable degree of experimentation."
MPEP 2164.08 puts the same point in one sentence: "All questions of enablement are evaluated against the claimed subject matter." A reviewer checks three things in the opposing report. First, whether the expert states the scope of each asserted claim under the court's construction, including the classes of embodiments it covers. Second, whether the expert compares that scope with what the specification teaches beyond the worked examples. Third, whether the path to the undisclosed embodiments is a procedure with a predictable result or a screening exercise that has to be repeated for each candidate.
How is undue experimentation tested, and what must the expert show for each factor?
By the eight Wands factors, which the USPTO lists in MPEP 2164.01(a). A reviewer checks that the expert supports each factor with data. In Cephalon, unsupported testimony that the work would be difficult carried little weight.
MPEP 2164.01(a), revision of January 2024, says the Federal Circuit "developed a framework of factors in In re Wands, 858 F.2d 731" (Fed. Cir. 1988). The factors are the breadth of the claims, the nature of the invention, the state of the prior art, the level of one of ordinary skill, the level of predictability in the art, the amount of direction provided by the inventor, the existence of working examples, and the quantity of experimentation needed to make or use the invention based on the content of the disclosure.
Cephalon is an example of an opinion that named the conclusion and skipped the data. Watson's evidence on enablement rested heavily on its expert, Dr. Mumper. The Federal Circuit answered that his "ipse dixit statements" that co-administration would be "difficult" and "complicated" could not "be enough to constitute clear and convincing evidence." The court added: "Unsubstantiated statements indicating that experimentation would be 'difficult' and 'complicated' are not sufficient." The district court had found Dr. Mumper credible, but the Federal Circuit wrote that his testimony "is largely unsupported, and therefore, carries little weight in this analysis." It reversed the holding that the patents were invalid for lack of enablement and affirmed the finding of noninfringement.
A reviewer builds a table with one row per factor and one column for the evidence cited. The entries are concrete: a laboratory test with its protocol and result, a publication with its date, the number of candidates a skilled person would have to make and screen, the time each run takes, the share of failures. A row that holds an adjective and no source is marked. The same table works for a challenger's reviewer, who looks for the rows where the patent owner's expert answers a measured quantity with a general assurance that the work was routine.
How does a written description opinion differ from an enablement opinion?
A written description opinion asks whether the inventor possessed what is claimed, judged by the specification as filed. It is a question of fact, decided separately, so a claim can be enabled and still fail it.
MPEP 2163, revision of January 2024, cites Ariad Pharmaceuticals, Inc. v. Eli Lilly and Co., 598 F.3d 1336 (Fed. Cir. 2010) (en banc), for the rule that written description is separate and distinct from enablement. The same section states: "Compliance with the written description requirement is a question of fact." The test it describes is whether the specification conveys with reasonable clarity to those skilled in the art that the inventor possessed the claimed invention as of the filing date.
For a claim to a genus, MPEP 2163 discusses the disclosure of a "representative number of species." A reviewer therefore counts. How many species does the specification describe, how are they spread across the genus, and does the expert explain why that number does or does not represent the whole?
The reviewer also checks what the expert read. A written description opinion is built on the application as filed, including the original claims and drawings. If the opposing expert relies on the accused product, on the patent owner's later publications or on what a skilled person could have worked out, the opinion answers a different question. An argument that the embodiment could have been made is an enablement argument, and it does not show possession.
As of what date, and through whose eyes, must the expert judge the disclosure?
As of the filing date and through the eyes of a person skilled in the art. A reviewer checks that the expert defined that person, applied one definition throughout, and did not rely on knowledge that appeared later.
Section 112(a) is addressed to "any person skilled in the art." Two of the Wands factors, the state of the prior art and the level of one of ordinary skill, tie the analysis to that person. MPEP 2164.05(a) carries the heading "Specification Must Be Enabling as of the Filing Date."
The reviewer writes down the date the opposing expert used for each asserted claim and compares it with the priority claim on the face of the patent. Each publication cited to prove that the field was unpredictable, or that a technique was routine, is checked against that date. If the expert ran experiments for the case, the reviewer asks whether the materials, the equipment and the protocol were available on that date and whether the protocol is disclosed in full.
Consistency inside one report is a separate check where the same expert argues both obviousness and lack of enablement. If the skilled person is described as highly capable in the obviousness section and as unable to follow the specification in the section 112 section, the reviewer quotes both passages side by side and frames a deposition question on which description the expert stands by.
When is a section 112 opinion excluded or given little weight?
When the proponent cannot show that the opinion rests on sufficient facts or data and on a reliable application of a method. Rule 702 puts that showing on the party offering the expert, by a more-likely-than-not standard.
Federal Rule of Evidence 702, as amended in 2023, lets a qualified expert testify only if the proponent shows the court that it is more likely than not that four conditions are met. The expert's knowledge will help the trier of fact, "the testimony is based on sufficient facts or data," it "is the product of reliable principles and methods," and the opinion is a reliable application of those principles and methods to the facts of the case.
A review of a section 112 opinion ends in two lists. The first holds the opinions with no data behind them: a statement that experimentation would be extensive with no count of candidates, or a statement that the inventor lacked possession with no citation of the specification. Counsel uses that list for a motion under Rule 702. The second list holds opinions that have data which the reviewer disputes, such as a test run under conditions the patent does not describe. Those points go to cross-examination and to weight, as in Cephalon, where the Federal Circuit gave the unsupported testimony little weight.
Each entry cites the page and paragraph of the opposing report, the passage of the patent, and the source the reviewer relies on.
What does IAE do with an opposing section 112 opinion?
An IAE reviewer checks the opposing technical expert's report against the claim language and the evidence and prepares points for the rebuttal report and the deposition. The document is issued in up to 5 business days.
The IAE review is for patent litigators facing the other side's technical report on infringement or validity, in district court or before the PTAB. The reviewer checks whether every opinion is tied to the claim language and the evidence: each element mapped, the court's claim construction applied, sufficient facts or data under Rule 702(b). For a section 112 opinion that means the claim scope the expert assumed, the evidence for each Wands factor and the date of every source.
The client sends the opposing report with its exhibits, the patent and its file history, the claim construction order and the deposition transcript if there is one. Before work starts IAE confirms the patent, the asserted claims and the questions for the reviewer. The secretariat confirms receipt the same day. Within one business day IAE confirms the format, the cost, the deadline and the reviewer in its registry, and the client approves the candidate and the CV.
Every reviewer is a member of the public IAE registry, verifiable by Member ID or QR code, and confirms in the document that he or she has no interest in the outcome of the case. A review is material that the court weighs with the other evidence, and neither IAE nor the reviewer guarantees the outcome. IAE is not a law firm and does not advise on case strategy.
Sources
- 35 U.S.C. 112, Specification (LII, Cornell Law School)
- 35 U.S.C. 282, Presumption of validity; defenses (LII, Cornell Law School)
- Amgen Inc. v. Sanofi, No. 21-757 (U.S. May 18, 2023), slip opinion (Supreme Court of the United States)
- Cephalon, Inc. v. Watson Pharmaceuticals, Inc., No. 2011-1325 (Fed. Cir. Feb. 14, 2013) (Justia)
- MPEP 2164, The Enablement Requirement, including 2164.01(a), 2164.05(a) and 2164.08 (USPTO)
- MPEP 2163, the written description requirement (USPTO)
- Federal Rules of Evidence, Rule 702 (LII, Cornell Law School)
Read also
All articles
Is the opposing patent expert a person of ordinary skill in the art, and what follows if not?
Claim construction, obviousness and infringement are all judged through the eyes of a person having ordinary skill in the art. In Kyocera Senco
Amended, reissued or published claims: which version must the opposing expert compare with the product?
An infringement comparison is only as good as the claim it uses. Claims change after filing: they are published in an application, allowed
Anticipation in the opposing invalidity report: does one reference really disclose every element as claimed?
A claim is anticipated only if a single prior art reference discloses every limitation, expressly or inherently, arranged as the claim arranges itExpert report review
Ready to discuss your case?
Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

