How to Draft a Provisional Patent Application: A Step-by-Step Guide

Key Definitions

Before diving in, here are a few terms you'll see throughout this guide:

Provisional Patent Application

A preliminary filing with the USPTO that establishes an early filing date. It lasts 12 months and is not examined on its merits. It does not become a patent on its own.

Non-Provisional Patent Application

The formal utility patent application that gets examined by the USPTO. You must file this within 12 months of your provisional to keep your priority date.

Specification

The written description of your invention. This is the core of your provisional filing.

Claims

Legal statements that define exactly what your patent protects. Not required in a provisional, but strongly recommended.

Prior Art

Any existing patents, publications, products, or public knowledge that existed before your filing date and relates to your invention.

Priority Date

The date your provisional is filed with the USPTO. This date is what matters when determining who invented something first.

CPC Classification

The Cooperative Patent Classification system used to categorize patents by technology area. There are over 250,000 subclasses.

Introduction

Most inventors know they should file a provisional patent application. Fewer understand what actually goes into one.

A provisional is not a napkin sketch with legal protection. The USPTO requires that your application include a written description that satisfies the requirements of 35 U.S.C. §112(a). In practice, that means your description needs to be detailed enough that someone skilled in your technology field could understand and potentially recreate your invention without guessing.

This matters because a weak provisional creates a false sense of security. You get your “patent pending” status, your 12-month clock starts ticking, and when it comes time to file the non-provisional, you discover that your provisional didn't actually support the claims you need. At that point, your priority date may not protect you.

This guide walks through every step of drafting a solid provisional, with particular attention to software, SaaS, and blockchain inventions where the technical description requirements are especially demanding. Whether you draft it yourself, use an AI-assisted tool, or work directly with an attorney, the process follows the same structure.

What Is a Provisional Patent Application (and What It Actually Protects)

A provisional patent application is a U.S. national application filed under 35 U.S.C. §111(b). It is not a patent. It does not get examined. It does not grant you enforceable rights. What it does is establish an early filing date that you can claim in a later non-provisional application.

Here is what a provisional actually gives you:

A priority date. If someone else files a similar invention after your provisional filing date, your earlier date takes precedence, assuming your provisional adequately described the overlapping subject matter.

“Patent pending” status. You can legally use this term on your product, marketing materials, and pitch decks from the moment your provisional is filed.

12 months of runway. You have one year from the filing date to file a corresponding non-provisional application. This window cannot be extended (though a 14-month grace period exists with a petition for unintentional delay under 37 CFR 1.78). If you miss the deadline, you lose the benefit of your provisional filing date permanently.

Lower cost and fewer formalities. Provisional applications do not require formal claims, an oath or declaration, or an information disclosure statement. Filing fees as of 2025 are $320 for large entities, $160 for small entities, and $80 for micro entities.

What a provisional does not give you: it does not provide any enforceable patent rights, it is never examined by the USPTO, and it cannot be cited as prior art on its own. It also cannot claim the benefit of a previously filed application. And provisionals are only available for utility patents. Design inventions are not eligible.

The most important thing to understand is that a provisional is only as strong as its disclosure. If your provisional describes Feature A but not Feature B, and a competitor starts using Feature B during your 12-month window, your provisional filing date will not protect Feature B in your non-provisional claims.

What You Need Before You Start Drafting

Before you open a blank document or fire up a drafting tool, you should have the following ready:

A clear understanding of what your invention does and how it works. This sounds obvious, but many inventors can describe what their product does for users without being able to articulate the underlying technical mechanism. For a provisional, you need both. If your SaaS platform uses a novel algorithm to match users with service providers, you need to describe the algorithm, not just the matching outcome.

Any existing documentation. Source code, technical specifications, architecture diagrams, database schemas, API documentation, flowcharts, wireframes. Anything that helps describe how the invention works at a technical level. You will not necessarily include all of this in the provisional, but having it on hand makes the writing process significantly faster.

A sense of what makes your invention different. You do not need a formal prior art search at this stage (that comes later), but you should be able to articulate why your approach is different from existing solutions. What problem are you solving? What is the conventional way to solve it? What does your invention do differently?

A list of all inventors. Under 35 U.S.C. §116, every person who contributed to the conception of the invention must be named as an inventor. Omitting an inventor, or naming someone who didn't contribute, can create enforceability problems later. If you have co-founders or collaborators, sort this out before you file.

If you are using Patent Geyser, Module 1 (Intake & Screening) handles much of this preparation by running your invention idea through an AI-powered Advocate/Examiner debate. The Advocate highlights strengths and patentable aspects, while the Examiner challenges weaknesses and identifies gaps. This process helps you pressure-test your description before you start formal drafting.

This is the most important part of your provisional application. The specification (your written description) must satisfy the enablement requirement under 35 U.S.C. §112(a): a person having ordinary skill in the art (often abbreviated PHOSITA) should be able to make and use your invention based on your description alone, without undue experimentation.

For software, SaaS, and blockchain inventions, this means describing the technical process, not just the user-facing result. The distinction matters enormously, especially in light of the Supreme Court's decision in Alice Corp. v. CLS Bank International (2014), which established that merely implementing an abstract idea on a generic computer is not enough to make it patent-eligible under 35 U.S.C. §101.

What to include in your description:

The problem your invention solves. Start with the technical problem, not the business problem. “Reducing customer churn” is a business problem. “Detecting anomalous usage patterns in real-time event streams to trigger automated retention workflows before a user churns” is a technical problem.

How your invention solves it. Walk through the technical implementation step by step. If your invention involves a multi-step process, describe each step. If it involves communication between components (a client, a server, a database, an API), describe the data flow between them. If it uses a specific algorithm or data structure, describe how it works.

Alternative embodiments. Do not describe just one way your invention can be implemented. Describe variations. If your system can use either a relational database or a graph database, mention both. If your algorithm can operate on batch data or streaming data, describe both scenarios. Alternative embodiments broaden the scope of what your priority date covers.

Technical specifics that distinguish your invention. This is where many provisional applications fall short, especially for software inventions. Generic phrases like “a computer system configured to process data” will not survive scrutiny. You need to describe what kind of data, what processing occurs, what the system does differently from conventional approaches, and why that difference produces a technical improvement.

Common mistakes at this stage:

Writing a product description instead of a technical description. Your provisional is not a marketing page. It needs to describe how the invention works under the hood.

Being too vague about the implementation. “The system uses machine learning to predict outcomes” is not a description. Which ML approach? What training data? What features? What is the prediction target? How is the model served?

Omitting the technical architecture. For SaaS and blockchain inventions, the system architecture often contains patentable elements. Describe the components, their interactions, and the data flows between them.

Even though a provisional application is not examined for patentability, the strength of your eventual non-provisional depends on how clearly your provisional establishes what is new about your invention.

Novelty, in patent terms, means your invention has not been previously disclosed in any publicly available document, product, or patent filing (this is “prior art”). Non-obviousness means that even if individual elements of your invention exist in the prior art, the specific combination or application you've created would not be obvious to someone skilled in your field.

You should be able to answer these questions clearly before moving forward: What existing solutions address the same problem? How does your approach differ from theirs? What technical advantage does your approach provide? Is there a specific technical mechanism in your invention that does not appear in any existing solution you're aware of?

Conducting a prior art search at this stage, even an informal one, significantly strengthens your provisional. It helps you identify the white space where your invention is most defensible and ensures your description emphasizes the right technical details.

If you are using Patent Geyser, Module 3 (Prior Art Search) uses vector embeddings in Google BigQuery to perform semantic prior art searches across the U.S. patent database. Rather than keyword matching, it finds patents that are conceptually similar to your invention, which surfaces prior art that simple text searches often miss. The AI then analyzes the results and identifies where your invention's claims are most vulnerable and where they are strongest.

The USPTO does not require formal claims in a provisional application. Many inventors skip them entirely. This is a mistake.

Claims define the legal boundaries of your patent protection. They specify exactly what you are claiming as your invention. When you file your non-provisional application, the claims you include must be fully supported by the disclosure in your provisional. If your provisional does not describe something, you cannot claim it with the benefit of your provisional's priority date.

By drafting claims at the provisional stage, you force yourself to think precisely about what you are trying to protect. This exercise almost always reveals gaps in your specification that you can fix before filing.

Understanding claim structure:

An independent claim stands on its own and describes the broadest version of your invention. A dependent claim references an independent claim and adds additional limitations or specifics.

For example, an independent claim might describe a method for detecting anomalous user behavior in a SaaS platform using a specific combination of event stream processing and statistical modeling. A dependent claim might specify that the statistical model uses a particular algorithm, or that the event stream is processed in real-time with sub-second latency.

Broad vs. narrow claims:

Broader claims provide wider protection but are more vulnerable to prior art challenges. Narrower claims are more defensible but protect a smaller territory. A strong provisional includes both.

You want at least one set of broad claims that capture the core concept of your invention and a set of narrower claims that describe your specific implementation. This gives your patent attorney options when prosecuting the non-provisional.

In Patent Geyser, Module 4 (White Space & Claims) generates multiple claim variations, from broad to narrow, based on the prior art analysis from Module 3. You review each variation, select the ones that best represent your invention, and the system compiles them into the provisional specification. Module 5 (The Showcase) also lets you generate broader claim alternatives and compare them side-by-side with your specific claims before exporting.

The USPTO does not require formal patent drawings in a provisional application, but including them is strongly recommended. Under 35 U.S.C. §113, any drawing necessary to understand the invention cannot be added after the filing date without constituting new matter.

For software, SaaS, and blockchain inventions, the right diagrams can communicate in seconds what would take pages of text to describe. The types of drawings that strengthen a provisional include:

System architecture diagrams. Show the major components of your system and how they interact. For a SaaS platform, this might include the client application, API gateway, microservices, databases, and any third-party integrations. For a blockchain invention, this might include the network nodes, consensus mechanism flow, smart contract interactions, and on-chain/off-chain data flow.

Flowcharts. Walk through the key processes step by step. If your invention includes a novel method for processing transactions, validating data, or routing requests, a flowchart makes the sequence clear and supports the method claims in your specification.

Data flow diagrams. Show how data moves through your system. This is particularly important for inventions where the novel aspect involves a specific way of transforming, routing, or aggregating data.

User interface workflows (where relevant). If your invention includes a novel user interaction pattern that is tied to the underlying technical process, showing the UI flow can help illustrate how the system works end-to-end.

Informal sketches, screenshots, and computer-generated diagrams are all acceptable for a provisional. The key is completeness: every functional aspect of your invention that you describe in your specification should have a corresponding visual reference.

In Patent Geyser, Module 5 (The Showcase) generates technical diagrams automatically using the Eraser.io API, producing system architecture diagrams, flowcharts, and component interaction diagrams based on your provisional specification. These are included in the final PDF or DOCX export.

With your written description, claims, and drawings complete, it is time to assemble the full provisional application. The filing package includes:

A cover sheet. The USPTO encourages use of Form PTO/SB/16, which captures the application title, inventor names, residence addresses, correspondence address, and attorney/agent information (if applicable). The cover sheet must identify the filing as a provisional application.

The specification. This is your complete written description, organized into sections: title of the invention, background, summary, detailed description, and (if included) claims. There is no mandated format for a provisional specification, but following the structure used in non-provisional applications makes the conversion process much smoother.

Drawings. All diagrams, flowcharts, and figures referenced in your description.

The filing fee. As of 2025, the fees are $320 (large entity), $160 (small entity), or $80 (micro entity).

Before you file, review the complete package:

Does the specification describe every feature you want to claim in your non-provisional? Have you included alternative embodiments? Do your claims (if included) align with what the specification describes? Are your drawings referenced in the text and clearly labeled? Have you named all inventors?

The most important step: professional review

This is where we need to be direct. AI-assisted drafting tools, including Patent Geyser, produce drafts. They do not produce final, filing-ready applications, and they do not constitute legal advice. Patent law is complex, the consequences of a poorly drafted application can be severe, and the nuances of claim language, enablement, and subject matter eligibility require expertise that goes beyond what any AI tool can provide today.

Before you file your provisional with the USPTO, have a registered patent practitioner review your application. A practitioner can identify gaps in your disclosure, strengthen your claim language, flag potential §101 eligibility issues (particularly important for software and blockchain inventions), and ensure your provisional provides the strongest possible foundation for your non-provisional filing.

You can find a practitioner through the USPTO's roster of registered attorneys and agents, or through the PatentFit Directory, which scores practitioners based on their actual USPTO filing history across 112 CPC technology areas. This lets you find someone with specific experience in your invention's technology class.

Common Mistakes That Weaken a Provisional Application

Even when inventors follow the right process, certain recurring mistakes weaken provisional filings:

Treating the provisional as a formality. Some inventors view the provisional as a checkbox, something to get “patent pending” on their website. They file a thin description and plan to “fill in the details later” in the non-provisional. This defeats the purpose. Your priority date only protects what your provisional actually discloses.

Describing what the invention does without explaining how. This is the most common issue with software provisionals. Describing outcomes (“the system automatically optimizes delivery routes”) without describing the technical mechanism (“using a modified Dijkstra's algorithm applied to a weighted graph of delivery nodes with real-time traffic data as edge weights”) leaves your most important technical contribution unprotected.

Filing without any claims. While not legally required, claims are the single best tool for forcing precision in your description. The exercise of writing claims almost always reveals blind spots in the specification.

Ignoring the Alice framework. For software, SaaS, and blockchain inventions, the two-part test from Alice Corp. v. CLS Bank (2014) remains the most significant barrier to patent eligibility. Your description must go beyond abstract ideas and demonstrate a specific technical improvement. Describing “a method for managing digital transactions” is an abstract idea. Describing a specific cryptographic validation protocol that reduces transaction confirmation time by eliminating redundant consensus rounds is a technical improvement.

Not conducting any prior art research. Filing without awareness of existing patents in your space means you might spend 12 months building on a provisional that describes something already patented. Even a preliminary search can prevent this.

Omitting alternative embodiments. If your specification only describes one implementation, your non-provisional claims will be limited to that specific implementation. Competitors can design around a narrow patent by changing one detail. Alternative embodiments broaden your protection.

Missing inventors. Under 35 U.S.C. §116, all individuals who contributed to the conception of the invention must be named. Missing an inventor can make the patent unenforceable. If you're unsure about inventorship, Patent Geyser includes an optional Pannu Test module that helps validate each inventor's contribution against the three-prong legal standard.

Conclusion

A provisional patent application is only as strong as the detail you put into it. Cutting corners on your specification, skipping claims, or ignoring prior art can leave your most valuable ideas unprotected, even though you technically have a filing date.

The good news is the process is structured and repeatable. Describe your invention thoroughly, identify what makes it novel, draft claims that define your boundaries, create supporting drawings, and compile everything into a complete specification. Whether you work with an attorney from the start, use an AI-assisted drafting tool to build your first draft, or do it yourself, the steps are the same.

Patent Geyser walks you through this entire process, from intake and brainstorming through prior art search, claim generation, and technical diagram creation. But remember: the output is a draft, not a finished product. Before you file anything with the USPTO, have a registered patent practitioner review your application. If you need help finding one matched to your technology area, the PatentFit Directory can help.

Frequently Asked Questions

Before You Start

After You Draft