How a draft addresses key U.S. utility patent requirements
A U.S. utility patent application has to meet requirements set by the patent statute and USPTO rules. Here are key ones, what each asks, and how a PatentAgents.ai draft is written to address it.
Is the invention something a patent can cover? (35 U.S.C. § 101)
Section 101 limits patents to a process, machine, manufacture, or composition of matter, and abstract ideas, laws of nature, and natural phenomena are not patentable on their own. The invention must also be useful. For software and other computer-implemented inventions, the description explains the technical problem and how the claimed steps change the way the computer or system works, and the claims recite those steps as a method, a computer system, and a non-transitory computer-readable storage medium containing instructions.
Is the invention new? (35 U.S.C. § 102)
Subject to § 102's exceptions, a claim lacks novelty when one qualifying prior-art reference or activity discloses every element arranged as claimed. A draft cannot make an invention new, so it is built from your account of what is new: the broadest claim recites that core, and narrower dependent claims add features from your material as fallback positions. If you have a prior-art search, add it to your source material so the claims are drafted with it in view.
Is it more than an obvious variation? (35 U.S.C. § 103)
Section 103 bars a patent when the differences from earlier work would have been obvious to a person of ordinary skill in the field before the claimed invention's effective filing date, even if no single reference shows the whole invention. The description sets out the technical problem, how your approach differs from the conventional approaches your material describes, and the benefit that follows. Dependent claims add the specific features that give further ground if an examiner combines references.
Does the application describe everything it claims? (35 U.S.C. § 112(a), written description)
Written description requires the application as filed to show that the inventor had the claimed invention, and USPTO rules require claim terms to find clear support in the description (37 CFR 1.75(d)(1)). The specification is written from the claims outward: each claim element is described in the detailed description using the same words the claim uses, and the claims are drafted to add no feature the description does not carry.
Could someone in the field make and use it? (35 U.S.C. § 112(a), enablement)
Enablement requires enough detail that a person skilled in the field could make and use the claimed invention without undue experimentation. The detailed description walks through how each claimed feature works, with implementation examples and variants taken from your notes, diagrams, and code. Where it fits, and your material is thin on a point, the draft adds a general implementation example for you to confirm or replace before filing.
Does it include the way you prefer to build it? (35 U.S.C. § 112(a), best mode)
Section 112(a) requires the application to set out the best way the inventor knows of carrying out the invention at the time of filing. The draft describes the implementation your material presents as preferred, along with the alternatives, rather than only a generic version. Since the America Invents Act (2011), a failure to disclose best mode can no longer be used to invalidate an issued patent (35 U.S.C. § 282(b)(3)(A)), but the requirement still applies to the application.
Are the claims clear? (35 U.S.C. § 112(b), definiteness and antecedent basis)
Section 112(b) requires claims that particularly point out and distinctly claim the invention, so a reader can tell what is and is not covered. The draft gives each thing one name throughout, uses clear references when referring back to claim elements (called antecedent basis), and avoids loose terms of degree unless the description gives a standard for them.
When does a claim become "means-plus-function"? (35 U.S.C. § 112(f))
An element written using 'means' or 'step' for a function, or a generic placeholder such as 'module' or 'unit,' can invoke §112(f) when it does not recite sufficient structure, material, or acts for performing the function. When §112(f) applies, the element is construed to cover the corresponding structure, material, or acts the description discloses for that function and their equivalents. The draft recites concrete structure or steps in the claims by default. When a means-plus-function element is used on purpose, the description sets out the corresponding structure. For a computer-implemented function, this generally includes a computer programmed with a disclosed algorithm.
What do the drawings have to show? (35 U.S.C. § 113; 37 CFR 1.81, 1.83, 1.84)
Drawings are required where they are needed to understand the invention. In a nonprovisional application, drawings must show every claimed feature. A conventional feature can be shown as a labeled box or symbol when its details are not needed to understand the invention (37 CFR 1.83(a)). A PatentAgents.ai draft plans the figures from the claims. Check that every claimed feature is shown before filing, because a figure added later cannot bring in anything the application did not already disclose (35 U.S.C. § 132(a)).
PatentAgents.ai is drafting software, not a law firm, and does not give legal advice.
Whether an application meets these requirements is decided in examination at the USPTO.
See what a full draft looks like.
PatentAgents.ai is drafting software. It is not a law firm and does not give legal advice. Drafts need technical and legal review before filing.