Patent Enablement After Amgen v. Sanofi: What the Disclosure Has to Carry

A short rule, applied with new force

The enablement requirement in 35 U.S.C. § 112(a) has been on the books since 1952. Its operative phrase is unchanged: a patent specification must describe the invention “in such full, clear, concise, and exact terms as to enable any person skilled in the art” to make and use it.

For decades, the doctrinal weight of that phrase rode on In re Wands, 858 F.2d 731 (Fed. Cir. 1988), and the eight Wands factors for assessing whether a claim required undue experimentation. Wands gave practitioners a workable framework. It did not give the courts a hard ceiling on how much a single specification could be asked to carry.

In Amgen Inc. v. Sanofi, 598 U.S. 594 (2023), a unanimous Supreme Court supplied the ceiling. The Court held that a specification must enable the full scope of the invention claimed, and that “the more one claims, the more one must enable.”

The decision did not add new statutory text. It made clear what was already there. For in-house IP counsel and prosecution teams, the result is a sharper rule and a heavier evidentiary load on the disclosure record.

What Amgen actually held

Amgen claimed a genus of antibodies defined by two functional properties: binding to a particular region of the PCSK9 protein, and blocking the protein’s interaction with LDL receptors. The specification disclosed 26 antibodies by amino-acid sequence and described two methods skilled artisans could use to find others.

The claimed genus, on Amgen’s own pleadings, spanned potentially millions of antibodies. The 26 disclosed examples did not run a “general quality” through the genus that would let a skilled artisan reach the rest without the kind of trial-and-error process the Court treated as undue experimentation.

Justice Gorsuch’s opinion stated the principle in unambiguous terms: if a patent claims an entire class of processes, machines, manufactures, or compositions of matter, the specification must enable a person skilled in the art to make and use the entire class. A handful of working examples does not enable a class of millions when no general teaching connects the examples to the rest.

Two corollaries follow.

The first is functional: claims that read on a class defined by what the invention does must be supported by disclosure that explains how a skilled artisan reaches the entire class without inventing each member from scratch.

The second is structural: a specification that names a few embodiments without surfacing the underlying technical principle has a known weakness. Drafting cannot reverse that weakness if the disclosure that produced the spec did not capture the principle.

The decision is not limited to biotech

Amgen is a biotechnology case. Its reasoning is not confined to biotechnology.

Federal Circuit panels have continued applying the same enablement-scope logic across chemical and pharmaceutical genus claims since the decision came down. The pattern is consistent with pre-Amgen cases like Idenix Pharmaceuticals LLC v. Gilead Sciences Inc., 941 F.3d 1149 (Fed. Cir. 2019), which invalidated genus claims to nucleoside compounds for similar reasons, a genus too broad for the disclosed examples to bridge.

For software and AI inventions, the practical pressure points are familiar. Functional claim language (“a system that detects anomalies,” “a model that selects the optimal route”) describes a class. If the specification does not show the structural mechanism, the architectural choice, or the operating constraint that ties the class together, the claim is inviting an Amgen-style enablement attack.

The same disclosure record that supports a § 101 win under Berkheimer also supports an Amgen-style enablement defense. Both inquiries reward specifics: the technical mechanism, the operating regime, the alternatives considered, the constraints addressed. Neither inquiry rewards functional language unanchored to a teaching that runs through the claimed scope.

What the disclosure has to carry

A specification that survives Amgen-style scrutiny on a genus claim has to do three things.

It has to disclose enough working examples to anchor the claim, not a handful when the claim sweeps to millions. Amgen does not state a numeric threshold. It states a relationship: the breadth of the disclosure has to scale with the breadth of the claim.

It has to surface the general technical principle that connects the examples. The Court in Amgen explicitly preserved the longstanding rule that a specification need not describe every embodiment if it discloses “some general quality… running through” the class that gives it “a peculiar fitness for the particular purpose.” The general quality has to be in the spec. It cannot be inferred from the bare fact that some embodiments work.

It has to capture the alternatives considered and rejected. The Wands factors still control the practical analysis of “undue experimentation.” Two of those factors, the working examples and the predictability of the art, are functions of how thoroughly the disclosure documents what the inventor actually tried.

The disclosure intake that produces this kind of specification looks different from a one-page IDF. It looks like a record of the engineering and scientific work that produced the invention.

What thin disclosures cost

A thin disclosure caps the eventual specification’s enablement defense.

The cap shows up in three places. The first is during prosecution, when an examiner issues a § 112(a) rejection citing Amgen or Idenix and the response options are limited by what the disclosure already supports. The second is during a post-grant challenge, IPR or PGR, where the petitioner argues that the spec does not enable the full scope of the claims and the patentee’s rebuttal record is whatever the spec contains. The third is during litigation, where a Wands-factor analysis under Amgen draws on every working example, every alternative considered, and every operating constraint the spec records.

In each setting, the question that decides the outcome is not what the inventor knew. It is what the disclosure preserved.

A disclosure intake that captures working examples at the time the work happens, surfaces the general technical principle in the inventor’s own framing, and preserves the alternatives evaluated and the operating constraints addressed gives downstream counsel something to work with. Intake that asks only for “a description of the invention” gives downstream counsel a paragraph and a problem.

Practical implications for in-house IP counsel

The post-Amgen environment changes a few operational assumptions.

Functional claim language is more expensive than it was. Teams that habitually draft broad functional claims because the underlying technical mechanism is hard to articulate now run a real enablement risk on those claims. The cost of that habit is higher.

Genus claims need a teaching, not a list. If the strategic value of a claim depends on covering a broad class (variants of an algorithm, classes of compounds, families of devices), the specification has to disclose what makes the class cohere. Disclosing several members and labeling them “examples” is not a substitute for that teaching.

The disclosure intake is the leverage point. Amgen does not change what a strong specification looks like. It changes how visibly the specification fails when the underlying disclosure was thin.

A reasonable starting checklist for intake on inventions likely to support broad or functional claims:

• Capture the general technical principle in the inventor’s own words, before drafting begins.
• Preserve working examples (code paths, experimental runs, model architectures) at the level of detail a person skilled in the art would need to reproduce them.
• Document the alternatives considered, including the engineering or scientific reasons they were rejected.
• Identify the operating constraints the invention addresses and the specific technical contributions that satisfy those constraints.

None of these are new disclosure practices. They are the practices that produce specifications which survive Amgen-grade enablement scrutiny without retreat to narrower claims.

What to read next

Amgen is short. The longer reading list is the doctrine it sits inside: In re Wands on undue experimentation, Idenix v. Gilead on the pre-Amgen application of the same logic, Enzo Biochem v. Calgene, 188 F.3d 1362 (Fed. Cir. 1999) on enabling the full scope of broad claims, and the USPTO’s MPEP § 2164 series on examiner-facing enablement analysis.

For the structural question Amgen presses on, see our note on Section 101 eligibility starting with the disclosure record, the same disclosure-record discipline supports both eligibility and enablement.

ALID surfaces invention candidates from engineering artifacts and packages each one with the technical specifics, alternatives, and source citations that produce specifications which can carry the enablement load Amgen now requires. To see how the discovery and disclosure flow operates, read how ALID works, or request access to run a first discovery against your own engineering data.