Wands Factors for Patent Enablement: All Eight After Amgen

The Wands factors for patent enablement are eight considerations that patent examiners and courts weigh together to decide whether a patent’s specification teaches a person skilled in the field how to make and use the invention without undue experimentation. They come from the Federal Circuit’s 1988 decision in In re Wands, and they remain the working framework for every enablement dispute in U.S. patent law.¹

Why Enablement Matters

The patent bargain is straightforward. An inventor gets exclusive rights for a limited time, and the public gets a complete explanation of how the invention works. That trade is codified in 35 U.S.C. § 112(a), which requires the specification to describe the invention “in such full, clear, concise, and exact terms as to enable any person skilled in the art . . . to make and use the same.”²

A patent doesn’t have to read like an assembly manual. Some experimentation is normal whenever a skilled person adapts an invention to their own lab or shop. The legal line runs between routine experimentation, which is fine, and undue experimentation, which means the specification failed its job. The Wands factors exist to make that line less subjective by giving examiners and judges a structured way to weigh the evidence.

The Eight Wands Factors

Each factor captures a different dimension of whether a patent teaches enough. They don’t work as a checklist. A strong showing on several can offset weakness on another.¹

Quantity of Experimentation Necessary

How much trial and error would a skilled person need to get the invention working? A small number of straightforward tests points toward enablement. An open-ended research program points away from it. In Wands itself, the applicants ran their procedure three times and produced at least one qualifying antibody each time, which the Federal Circuit found persuasive that the workload was manageable.¹

Amount of Direction or Guidance

A specification that spells out specific protocols, parameters, and step-by-step instructions is much easier to follow. Vague phrases like “combine the reagents under suitable conditions” leave too much to the reader. The more guidance the patent gives, the less experimentation is needed, and the stronger the enablement case.

Presence or Absence of Working Examples

Working examples are concrete demonstrations that the inventor actually built or tested the invention. Lab data, prototype results, and detailed experimental write-ups carry real weight because they show the invention isn’t just theoretical. Working examples aren’t strictly required, but their absence makes it harder to argue that someone else could reproduce the results without excessive effort.

Nature of the Invention

Some technologies are inherently harder to describe on paper than others. A new bracket for mounting solar panels can be written up in a way that a mechanical engineer will readily reproduce. A novel gene therapy protocol involves so many variables that the same level of description would leave gaps for a molecular biologist. Examiners take this seriously: complex fields face a higher disclosure bar because those fields genuinely require more information to recreate results.

State of the Prior Art

Prior art is the body of knowledge, including published patents, academic papers, and textbooks, available when the patent was filed. If the relevant technology is already well-documented, an inventor can lean on that shared foundation and skip explanations of established techniques. If the invention sits in less-charted territory, the specification has to fill in more of the background because the reader can’t look it up elsewhere.

Relative Skill of Those in the Art

This factor measures what the typical professional in the field already knows. A specification aimed at experienced semiconductor engineers can safely assume familiarity with photolithography basics. One aimed at a newer field with less standardized training may need to spell more out. A high baseline skill level effectively compensates for less hand-holding in the document.

Predictability or Unpredictability of the Art

In predictable fields like mechanical engineering, knowing an input usually tells you the output. Adjust a gear ratio and the change in torque is calculable. In unpredictable fields like pharmaceutical development or biotechnology, small changes can produce very different results, and the reasons aren’t always understood. The less predictable the technology, the more detailed the disclosure must be, because a skilled person can’t simply extrapolate from a few examples to cover the full scope of the claims. Artificial intelligence sits in an interesting middle ground: its roots are in mathematics and computer science, traditionally predictable, but AI systems often produce results that are hard to predict in advance.³

Breadth of the Claims

Broad claims covering many variations demand proportionally more enabling disclosure. A patent claiming a single specific compound needs to show that compound works. A patent claiming an entire class of compounds defined by a shared function needs to show how a skilled person could make and use that entire class. This is where many enablement fights play out. Inventors want the widest protection possible, but the law requires the disclosure to keep pace with the scope of the claims.

How the Factors Balance

The USPTO and federal courts treat the eight factors as an integrated framework, not isolated criteria. An examiner analyzing a biotech patent will often focus on predictability, working examples, and claim breadth, because those tend to be decisive in that space. For a mechanical invention, the state of the prior art and the skill level in the field may matter more. The MPEP is explicit that reaching a conclusion based on only one factor while ignoring the others is improper; the analysis has to weigh all the relevant evidence.³

The Wands case itself illustrated the balancing. The patent office had focused on the number of stored cell lines that hadn’t produced ideal antibodies, characterizing them as failures that showed unpredictability. The Federal Circuit called that reading “strained and unduly harsh,” pointing to the applicants’ considerable guidance, working examples, high baseline skill in the field, and use of well-known methods. Together those factors outweighed concerns about the volume of experimentation.¹

No single factor is a knockout blow in either direction. A patent with no working examples can still be enabled if the prior art is rich and the field is predictable. Detailed examples won’t save a patent whose claims are so broad they cover vast territory the specification never addresses.

What Amgen v. Sanofi Changed

The most significant development in enablement law since Wands came in 2023, when the Supreme Court unanimously decided Amgen Inc. v. Sanofi. Justice Gorsuch’s opinion sharpened a principle that was always implicit in the Wands factors: “The more one claims, the more one must enable.”⁴

Amgen held patents on antibodies that lower cholesterol by blocking a protein called PCSK9. Rather than claiming only the specific antibodies it had identified, Amgen claimed an entire class of antibodies defined by their function. To enable that class, the patent described two methods: a “roadmap” that walked scientists through generating and testing candidate antibodies, and “conservative substitution,” where scientists would tweak known antibodies and see if the modified versions still worked. The Court found both methods amounted to “little more than two research assignments” that sent skilled scientists on open-ended trial and error rather than actually teaching them how to make every antibody within the class.⁵

The Court did leave room for broad claims when the specification discloses “some general quality running through the class” that lets a skilled person predict which members will work. The bar is high: you need to identify a structural or functional feature common to the entire claimed class, not just hand the reader a screening method. In January 2024, the USPTO updated its examination guidance to confirm that the Wands factors remain the tool for evaluating enablement across all technologies, now explicitly measured against the full scope of the claims.³

For anyone drafting or defending a patent today, Amgen is the case that gives the breadth-of-claims factor real teeth. Broad functional claims in unpredictable fields face steeper enablement scrutiny than before, and applicants need structurally diverse working examples along with a clear explanation of the shared quality that ties the claimed class together.

Burden of Proof and Answering a Rejection

The examiner carries the initial burden. To reject claims for lack of enablement, the examiner must build a reasonable case explaining why the specification doesn’t teach a skilled person how to make and use the full scope of the claimed invention. A conclusory statement isn’t enough; the examiner has to identify which claimed subject matter is not enabled and apply the Wands factors to the evidence. Once that initial case is made, the burden shifts to the applicant, who can respond with expert declarations, test results, prior art references, or arguments about how the examiner read the specification. The standard is preponderance of the evidence.³

An enablement rejection isn’t the end of the road. Applicants have several practical options, and the best response depends on where the weakness lies.

Narrow the claims. If the examiner’s concern is that the claims cover more ground than the specification supports, reducing claim scope to match what is disclosed often resolves the issue. This is the most common fix after Amgen for applicants with broad functional claims.
Submit declarations or test data. Expert declarations under 37 CFR 1.132 can explain what a skilled person would have understood from the specification. Actual experimental results demonstrating that the invention works as described carry particular weight.
Argue the examiner’s analysis. If the examiner leaned too heavily on one Wands factor while ignoring others that favor enablement, walk through the full balancing analysis and show that the overall weight of evidence supports the disclosure.
Cite prior art references. Published patents and papers dated before the application’s filing date can show that the relevant techniques were well-known, reducing the amount of disclosure the specification needed to provide.

One boundary worth flagging: enablement is judged as of the patent’s filing date. You cannot file a bare specification and then backfill it with data generated later to cure a disclosure that was insufficient when filed.³

1
Justia. In Re Jack R. Wands, Vincent R. Zurawski, Jr., and Hubert J.P. Schoemaker
2
Office of the Law Revision Counsel. 35 U.S. Code 112 – Specification
3
United States Patent and Trademark Office. Manual of Patent Examining Procedure Section 2164 – The Enablement Requirement
4
Justia. Amgen Inc. v. Sanofi, 598 U.S. 594
5
Supreme Court of the United States. Amgen Inc. v. Sanofi, No. 21-757