Building Continuation Room into the Original Specification

Continuation claims are only as broad, and only as varied, as the original specification allows. Under 35 U.S.C. 120, a continuation receives the parent’s filing date only for claims the parent adequately describes, and new matter cannot be added after filing. Building continuation room into a specification means drafting it so that claims nobody has written yet are more likely to find written description support: describing alternatives, stating ranges and intermediate values, supplying intermediate generalizations, and avoiding language that narrows the invention.

This article collects the techniques that matter most, particularly for electrical and computer technologies.

The constraint: written description support for claims not yet written

The written description requirement of 35 U.S.C. 112(a) asks whether the specification reasonably conveys to a skilled person that the inventor had possession of the claimed subject matter as of the filing date. The Federal Circuit confirmed in Ariad Pharmaceuticals, Inc. v. Eli Lilly & Co., 598 F.3d 1336 (Fed. Cir. 2010) (en banc) that this requirement is separate from enablement.

For continuation practice, the important consequence is that a claim supported in substance by the specification can still fail if the specification does not describe the claimed combination or scope. The specification has to be drafted with claim scopes in mind that may not be pursued for years, often targeting products that do not yet exist.

Describe alternatives for each element

Every element of the core embodiment is a potential point of design-around. For each one, describe other ways of performing the same function and explicitly connect them to the same role in the system.

For software and systems inventions, typical alternatives include:

• Different algorithms or models that can perform a given step
• Different allocations of functions between client, server, and edge devices
• Synchronous and asynchronous versions of a process
• Different data structures, storage arrangements, or communication protocols
• Hardware and software implementations of the same logic

It also helps to state which elements are optional and to describe embodiments that omit them. A later claim that leaves out an element is easier to support when the specification already describes the invention without it.

State ranges, endpoints, and intermediate values

Where a parameter matters, describe it as a range rather than only as the value used in the prototype. Include several nested ranges and specific intermediate values, so that a later claim can recite a narrower range with a clear basis in the text. This applies to thresholds, window sizes, sampling rates, voltages, frequencies, update intervals, model sizes, and similar quantities.

Listing values and alternatives is not a guarantee, though. Whether a later claim is adequately supported depends on what the specification as a whole conveys to a skilled person, and a bare list of numbers or options, without explanation of how and why they work, may not establish possession of every combination, subcombination, or intermediate generalization later claimed. Ranges and alternatives are most useful when the specification explains them. The USPTO’s guidance on written description is collected in MPEP 2163.

Ranges are easy to omit when the inventors have tested only one configuration. Asking the inventors what values would still work, and why, usually produces useful ranges and often surfaces additional embodiments.

Supply intermediate generalizations

Between the broadest statement of the invention and the specific embodiment, there are usually several useful levels of generality. A claim at one of those intermediate levels may be the one that best covers a competitor’s product, but it needs support for that specific combination of features.

Drafting for this means describing groupings of features that work together, not only listing every feature of the preferred embodiment. If a combination of three features delivers the core advantage independently of the rest, say so, and describe that combination as an embodiment in its own right.

Avoid language that narrows the invention

Statements in the specification can limit claim scope in ways that also constrain continuations. Common examples:

• Describing a feature as part of “the present invention” or “the invention” rather than as part of an embodiment
• Calling a feature essential, critical, or required
• Disparaging an alternative approach in a way that may later be read as disclaiming it
• Defining a term narrowly when a broader ordinary meaning would serve better

Consistent use of “in some embodiments” and similar framing, along with deliberate definitions for terms that matter, keeps the scope open.

Draft functional language with structure behind it

Software claims often recite functions. If a later claim recites a function using a nonce term such as “module” or “unit” without sufficient structure, it may be construed as a means-plus-function limitation under 35 U.S.C. 112(f), limited to the corresponding structure disclosed in the specification. For computer-implemented functions, that structure is generally an algorithm.

To preserve options, describe the algorithm for each important function: the steps, the inputs and outputs, and alternative algorithms that achieve the same result. That supports both conventional claims and, if one is ever drafted that way, a means-plus-function claim with adequate corresponding structure.

Plan for multiple claim formats and applications

Specifications that support only one claim format limit continuation options. Describe the invention so that it can be claimed as a method, a system, a device, and a non-transitory computer-readable medium, and describe different perspectives where they exist, such as client-side and server-side operations, or transmitter and receiver behavior.

Similarly, describe the technology’s other applications and environments. A technique developed for one product line can often be claimed separately for others, if the specification describes them.

Use figures to anchor support

Figures often provide the clearest support for later claims. Include figures for the overall system, each significant method, alternative arrangements, and key data structures or signals. Flowcharts that show optional steps and alternative branches are particularly useful for future claims that combine steps differently from the main embodiment.

Keep the family pending when the technology is still moving

Runway in the specification only matters if there is a pending application from which to claim it. Under 35 U.S.C. 120, a continuation generally must be filed while the parent, or a qualifying intermediate application in the same chain, is still pending. For families covering active product lines, practitioners often evaluate whether a continuation is warranted before paying the issue fee on an allowed application. Whether one is worthwhile depends on the commercial value of the unclaimed subject matter, its cost, and the prior art.

A practical takeaway

Before finalizing a specification, review each element of the core embodiment and ask three questions: what else could perform this function, which parameters need ranges, and which combinations of features could stand alone as a claim. Then read the specification for limiting language. Those passes take relatively little time and can significantly affect how much the family is able to claim years later.