Before you file: a founder's walkthrough of what the USPTO will check in your patent application

Why the week before filing matters most

A patent application is judged mostly on what it says the day it is filed. After filing you can narrow claims, fix wording, and argue with an examiner, but you cannot add new technical content (35 U.S.C. § 132(a)). That makes the first draft the place where most of the requirements are won or lost.

The requirements come from a few sections of the patent statute, Title 35 of the U.S. Code, plus USPTO rules in Title 37 of the Code of Federal Regulations. This walkthrough is for a founder holding a draft and a filing date. It goes through nine key requirements for a U.S. utility application in the order an examiner tends to think about them: what each asks, what to look for in your draft, and how a PatentAgents.ai draft is written to address it. Formal filing requirements and design-patent rules are outside this list.

Can it be patented at all? (35 U.S.C. § 101)

What it asks. A patent can cover a process, a machine, a manufacture, or a composition of matter. The invention must also be useful. Abstract ideas, laws of nature, and natural phenomena are not patentable on their own, and this is where many software applications draw a rejection.

How the draft handles it. For a computer-implemented invention, the description explains the technical problem and how the claimed steps change the way the computer or system works. The claims then recite those steps in three forms: a method, a computer system, and a non-transitory computer-readable storage medium containing instructions. A draft cannot turn an abstract idea into an eligible one, but it can make sure the technical substance you have is written down where an examiner will look for it.

Is it new? (35 U.S.C. § 102)

What it asks. Subject to § 102's exceptions, a claim lacks novelty when one qualifying prior-art reference or activity discloses every element arranged as claimed. The United States gives inventors a one-year grace period for their own disclosures (35 U.S.C. § 102(b)(1)), but many other countries do not, so a public disclosure before filing can cost rights abroad.

How the draft handles it. Novelty depends on what already exists, which no draft controls. The draft starts from your account of what is new and recites that core in the broadest claim. Narrower dependent claims then add features from your material, so there are fallback positions if earlier work turns up during examination. If you have a prior-art search, include it with your source material so the claims are written with it in view.

Is it more than obvious? (35 U.S.C. § 103)

What it asks. Even if no single reference shows the whole invention, a claim fails if the differences would have been obvious to a person of ordinary skill in the field before the claimed invention's effective filing date. Examiners often reject by combining two or three references.

How the draft handles it. The description sets out the technical problem, how your approach differs from the conventional approaches your material describes, and the benefit that follows. That gives you something concrete to point to when you argue the invention is not obvious. Dependent claims carry the specific features that distinguish it, so you can narrow without starting over.

Does the application describe what it claims? (35 U.S.C. § 112(a), written description)

What it asks. The application as filed has to show that the inventor had the claimed invention, and the USPTO rules require claim terms to find clear support in the description (37 CFR 1.75(d)(1)). A claim that reaches beyond what the description supports can be rejected.

How the draft handles it. 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 nothing the description does not carry.

Could someone build it from the application? (35 U.S.C. § 112(a), enablement)

What it asks. Written description asks whether you had the invention. Enablement asks whether you taught it: a person skilled in the field must be able to make and use the claimed invention from the application without undue experimentation.

How the draft handles it. 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 you file. Thin descriptions are a common weakness in self-written applications, and the fix is cheapest before filing.

Does it include your preferred way? (35 U.S.C. § 112(a), best mode)

What it asks. The application has to set out the best way the inventor knows of carrying out the invention at the time of filing. Since the America Invents Act (2011), failing to disclose best mode can no longer be used to cancel or invalidate an issued patent (35 U.S.C. § 282(b)(3)(A)), but the requirement still applies to the application.

How the draft handles it. The draft describes the implementation your material presents as preferred, along with the alternatives, rather than only a generic version.

Are the claims clear? (35 U.S.C. § 112(b))

What it asks. Claims must particularly point out and distinctly claim the invention, so a reader can tell what is covered and what is not. One common problem is antecedent basis: a claim that says "the sensor" before ever introducing "a sensor" can leave the reader unsure which sensor is meant.

How the draft handles it. The draft gives each thing one name throughout the claims and specification, uses clear references when referring back to claim elements, and avoids loose terms of degree such as "substantially" unless the description gives a standard for them.

When "means for" changes a claim (35 U.S.C. § 112(f))

What it asks. 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. Without corresponding disclosure, the claim can be indefinite.

How the draft handles it. The claims recite concrete structure or steps 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 the drawings must show (35 U.S.C. § 113; 37 CFR 1.81, 1.83, 1.84)

What it asks. Drawings are required where they are needed to understand the invention (35 U.S.C. § 113; 37 CFR 1.81). 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)). Rule 1.84 sets the format standards.

How the draft handles it. A PatentAgents.ai draft plans the figures from the claims. Check that every claimed feature is shown before filing. A figure added later cannot bring in anything the application did not already disclose. Later drawings cannot cure inadequate disclosure or supplement the original disclosure to interpret claim scope (35 U.S.C. § 113; 37 CFR 1.81(d)).

A note on provisional applications

A provisional application does not need claims and is not examined (35 U.S.C. § 111(b)(2), (8)), but it is not a placeholder either. A later nonprovisional application gets the provisional's filing date only for what the provisional actually describes and enables (35 U.S.C. § 119(e)). Writing the provisional to the same written description and enablement standard keeps that earlier date useful.

Your pre-filing checklist

• The invention is useful, and the claims meet subject-matter eligibility requirements.
• The broadest claim recites what is new, with narrower dependent claims as fallbacks.
• The description states the problem, how the approach differs, and the benefit.
• Every claim limitation has clear support in the application as filed.
• The application teaches a skilled person to make and use the claimed invention across its full scope without undue experimentation.
• Your preferred implementation is described.
• References back to claim elements are clear.
• Each § 112(f) element has corresponding structure, material, or acts disclosed, including an algorithm when required.
• For a nonprovisional application, every claimed feature appears in a figure, with matching reference numerals.

See a sample draft