Expert report review
Tests run for litigation: how does a reviewer check the opposing technical expert's experiments in a patent case?
When a claim element cannot be seen on the outside of a product, the technical expert tests for it: measures a dimension, analyzes a composition, runs the software, rebuilds a prior art device. A review of the opposing report asks what exactly was tested, who chose and supplied the sample, how the test was run and whether the data reach every element of the claim. Rule 34 lets the other side inspect and test the same item.

Why does a patent expert run tests for the case?
Because the claim defines the invention element by element, and some elements exist only as a value, a material or a behavior. A test supplies the facts or data for those elements that Rule 702(b) requires.
Section 112(b) of the Patent Act requires that the specification "conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention." Claims are written in elements, and many of them are measurable: a thickness range, a particle size, a temperature, a signal sequence, a response time.
An infringement opinion on such an element needs data about the accused product, and an invalidity opinion needs the same data about the prior art. Rule 702(b) of the Federal Rules of Evidence requires that expert testimony be "based on sufficient facts or data," and Rule 702(c) requires that it be "the product of reliable principles and methods." A test designed for the case is a method in this sense, and the review treats it as one.
Rule 702 does not ask whether a test was designed for the case. It asks about the facts, the method and its application, so the review examines the record of the test: the item, the procedure, the raw results and the link between the results and the claim language.
What must the expert report disclose about a test?
The opinions with their basis and reasons, the facts or data considered and the exhibits. For a test that means the sample, the procedure, the raw data and the charts or photographs the expert will use.
Rule 26(a)(2)(B) of the Federal Rules of Civil Procedure requires a retained expert's report to contain "a complete statement of all opinions the witness will express and the basis and reasons for them," "the facts or data considered by the witness in forming them" and "any exhibits that will be used to summarize or support them."
A report that states only the result of a test, such as "the layer measured 12 microns," gives the result without the facts behind it. The reviewer lists what is missing: which unit was measured, at how many points, with which instrument and calibration, under what conditions, and where the raw readings are.
The IAE patent page notes that before the Patent Trial and Appeal Board, under 37 CFR 42.65(b), test data come with an affidavit on how the test was run. In district court the report and its exhibits carry that information, and gaps in it become deposition questions and arguments under Rule 702(b).
Was the tested sample the accused product, and who supplied it?
The review traces the sample: model, version, date of manufacture, source and chain of handling. Facts or data that counsel provided and the expert considered are discoverable under Rule 26(b)(4)(C)(ii).
Rule 703 states that an expert "may base an opinion on facts or data in the case that the expert has been made aware of or personally observed." For a test, the distinction matters: did the expert run the test himself, supervise a laboratory, or receive results from someone else?
The sample has its own history. A product bought at retail in the year of the lawsuit may differ from the version sold during the damages period, and a unit supplied by the party's own engineers may have been selected or modified. The reviewer records the model and version, the date of manufacture, who obtained the unit and how it reached the expert.
Rule 26(b)(4)(C) protects most attorney-expert communications but not those that "identify facts or data that the party's attorney provided and that the expert considered in forming the opinions to be expressed." When counsel chose the samples, that choice is open to questions: how many units were available, how many were tested, and what happened to the rest.
Can the other side inspect and test the same item?
Yes. Rule 34 lets a party request the opposing party to produce designated tangible things so the requesting party can inspect, copy, test or sample them, at a reasonable time, place and manner.
Rule 34(a)(1) permits a request "to produce and permit the requesting party or its representative to inspect, copy, test, or sample the following items in the responding party's possession, custody, or control," including "any designated tangible things." Under Rule 34(a)(2) a party may also request entry onto land or property to "inspect, measure, survey, photograph, test, or sample the property or any designated object or operation on it."
The request "must specify a reasonable time, place, and manner for the inspection and for performing the related acts" (Rule 34(b)(1)(B)). For a review of the opposing tests, this is the route to the same production line, the same software build or the same retained samples the expert used.
When the opposing expert's test consumed or altered the sample, the reviewer records what remains, what was photographed and measured before the test, and whether the other side had notice. A replication on a different unit is then compared with the original data, and differences between the units are part of the review.
How does the reviewer check the test method?
Against the claim and against the field. The reviewer asks whether the test measures the property the claim describes, whether it follows a published or accepted procedure, and whether another engineer could repeat it from the report.
Rule 702(c) asks whether the testimony is "the product of reliable principles and methods," and Rule 702(d) concerns the reliable application of those methods to the facts of the case. For a published test procedure, the reviewer compares each step in the report with the published text. For a procedure written for the lawsuit, the report itself has to describe it in enough detail for another engineer to repeat it.
The questions are concrete. Does the measured quantity match the claim term as construed, or only something related to it? Were controls run on a known sample? How many repetitions were made and how much did the results vary? Were instruments calibrated, and is the calibration record in the facts or data considered? Did the test conditions match the conditions of use the claim describes?
Rule 703 adds a field test of its own for the data: experts in the field must "reasonably rely on those kinds of facts or data in forming an opinion on the subject" if the underlying data are not themselves admissible. A reviewer from the same technical field can say whether engineers rely on that kind of measurement for that question.
Do the test data reach every element of the claim?
Only if each element has its own data. The reviewer maps the results onto the claim chart row by row and marks elements supported by the test, elements supported by other evidence, and elements with no support.
A test often answers one element and is cited for several. A chemical analysis can establish a composition but not a process step; a teardown can show a structure but not how the device behaves in use. The review separates what the data establish from what the report infers from them.
Ranges in a claim need special attention. When a claim recites a range, the reviewer checks whether every measured value falls inside it, how the report treats values near the boundary, and whether measurement uncertainty could move a result across the line.
The reviewer also checks the arithmetic. Averages, conversions between units, and values read from graphs are recomputed from the raw data in the report's exhibits. A difference between the recomputed value and the reported one is a finding with a page reference.
How have courts treated attacks on an expert's tests?
Often as questions of weight. In Apeldyn v. AU Optronics (D. Del. 2011) the court refused to exclude test-based testimony, and in Precision Fabrics v. Tietex (D.S.C. 2019) it held that criticisms of the tests went to weight.
In Apeldyn Corp. v. AU Optronics Corp., a memorandum order of November 15, 2011 in the District of Delaware, AUO moved to exclude opinions of the plaintiff's technical expert, Dr. Allen R. Kmetz. He had examined three MVA panels and one TN panel taken from LCD televisions under a polarizing microscope and photographed them. AUO argued that "a single data point" was inadequate and that eigen-axes had to be shown by testing at multiple voltages. The court held that the question "remains an issue of fact to be tried." AUO's expert, Dr. Pochi Yeh, had suggested that measuring actual transmission would be more scientific but had taken no such measurements, and the court called the suggestion "an insufficient basis to preclude Kmetz's testimony on eigen-axes."
In Precision Fabrics Group, Inc. v. Tietex International, Ltd., decided March 8, 2019 in the District of South Carolina, the jury had found no infringement, and the court denied the patent owner's renewed motion for judgment as a matter of law and its motion for a new trial. Tietex's expert, Dr. Horrocks, had written a test protocol for the litigation and applied a 45-micron layer of the coating to a glass fiber substrate. He had not measured the accused fabrics and estimated their coating at 25 to 53 microns. The criticisms concerned his old caliper, the substrate, the coating thickness and the protocol. The court wrote that "this criticism goes to the weight rather than the admissibility of Dr. Horrocks's testing" and that his "calculated rate of error was sufficient to survive the admissibility requirements of Rule 702."
Both cases point the review in the same direction. A criticism of a test carries more force when it is backed by a measurement of one's own, which the Apeldyn court noted the defense expert had not made. It also carries more force when it shows a gap between the tested sample and the accused product, such as a test layer chosen from an estimate instead of a measurement of the accused fabric.
What changes when the expert tests a prior art product?
The date. The tested unit must represent what was publicly available before the claim's effective filing date, so the review asks for evidence that the unit matches the version sold or used before that date.
Under 35 U.S.C. 102(a)(1), a claimed invention is not patentable if it was "in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention." A test of a prior art device proves what that device contained only if the tested unit is the device as it existed before the effective filing date.
Products change between versions. A unit bought on the secondary market years later may have been repaired, updated or built to a later specification. The reviewer asks for the serial number, the manufacturing date, the documents that tie the unit to the earlier version, and whether any part was replaced.
The burden for invalidity in district court is clear and convincing evidence (Microsoft Corp. v. i4i Ltd. Partnership, 564 U.S. 91 (2011)). A gap between the tested unit and the prior art version goes to whether that standard is met.
Can the expert run new tests after the report or the deposition?
Only within the rules on supplementation and rebuttal. Information missing from a required disclosure or supplement cannot be used unless the failure was substantially justified or is harmless (Rule 37(c)(1)).
Rule 26(e)(2) extends the duty to supplement "both to information included in the report and to information given during the expert's deposition," and "(a)ny additions or changes to this information must be disclosed by the time the party's pretrial disclosures under Rule 26(a)(3) are due."
A rebuttal test that answers the other side's test is evidence "intended solely to contradict or rebut evidence on the same subject matter" and, unless the court sets another schedule, is disclosed within 30 days after the other party's disclosure (Rule 26(a)(2)(D)(ii)).
Rule 37(c)(1) applies when a party "fails to provide information or identify a witness as required by Rule 26(a) or (e)." The party is not allowed to use that information to supply evidence on a motion, at a hearing or at a trial, unless the failure was substantially justified or is harmless. A new test that appears for the first time shortly before trial is measured against that rule.
What goes into a review of the opposing expert's tests?
A record for each test: the sample and its source, the procedure and its basis, the raw data, the recomputed results, the claim elements the test supports, and the questions for the deposition.
The review follows the order in which the opposing expert built the opinion, so counsel can use it at the deposition and in a motion under Rule 702.
- The reviewer identifies each test cited in the report and the opinion and claim element it supports.
- The reviewer records the sample: model, version, manufacturing date, source and handling before the test.
- The reviewer states the procedure, whether it is a published method or a custom one, and whether the report describes it in enough detail to repeat.
- The reviewer recomputes the results from the raw data in the exhibits and notes any difference.
- The reviewer maps the results onto the claim chart and marks elements without test support.
- The reviewer lists the facts, data and samples that counsel supplied, for questions under Rule 26(b)(4)(C)(ii).
- The reviewer recommends items to request under Rule 34 for inspection or replication.
What does IAE do when the opposing patent report rests on tests?
An IAE technical expert reviews the opposing report on infringement or validity, including the samples and test data it relies on, and prepares a review, a rebuttal expert report or deposition questions in up to 5 business days.
IAE's page on reviewing the opposing technical expert's report is written for patent litigators facing the other side's 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 and sufficient facts or data under Rule 702(b). Each finding is tied to a claim element, a page of the opposing report and a rule or decision.
The page lists what the reviewer needs: the opposing report with its exhibits, the facts or data it lists as considered under Rule 26(a)(2)(B)(ii), the claim construction order and both sides' contentions, and the source code, samples or test data the expert relied on. The IAE patent page adds that the reviewer checks whether test data come with an affidavit on how the test was run, as 37 CFR 42.65(b) requires before the PTAB.
The client sends the report or the case materials and describes the task, and the secretariat confirms receipt the same day. Within one business day IAE confirms the format, cost, deadline and the specialist from its registry, and the client approves the candidate and the CV before work starts. The signed PDF is issued in up to 5 business days; cases with tight deadlines have a 48-hour rush.
The specialist is a member of the public IAE registry who passed the council's attestation under the published Criteria Matrix, and the Member ID or QR code on the document opens the record. The specialist confirms in the document that he or she has no interest in the outcome. Neither IAE nor the reviewer guarantees the outcome, and IAE is not a law firm.
Sources
- United States Code, Title 35, Part II, 2022 edition: sections 103, 112, 120 (GovInfo)
- 35 U.S. Code 102, Conditions for patentability; novelty (LII, Cornell Law School)
- Federal Rules of Evidence, Rule 702 (LII, Cornell Law School)
- Federal Rules of Evidence, Rule 703, Bases of an Expert's Opinion Testimony (LII, Cornell Law School)
- Federal Rules of Civil Procedure, Rule 26 (LII, Cornell Law School)
- Federal Rules of Civil Procedure, Rule 34, Producing Documents, Electronically Stored Information, and Tangible Things (LII, Cornell Law School)
- Federal Rules of Civil Procedure, Rule 37, Failure to Make Disclosures or to Cooperate in Discovery; Sanctions (LII, Cornell Law School)
- Microsoft Corp. v. i4i Ltd. Partnership, 564 U.S. 91 (2011), opinion of the Court (ChanRobles)
- Apeldyn Corp. v. AU Optronics Corp., Civ. No. 08-568-SLR (D. Del. Nov. 15, 2011)
- Precision Fabrics Group, Inc. v. Tietex International, Ltd., No. 7:17-cv-03038, Document 346 (D.S.C. Mar. 8, 2019) (Justia)
Read also
All articles
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
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, allowedExpert 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.

