Writing Patents in the Fire Space

Why Fire Technology Needs Patents

Fire technology is having a moment. Wildfires are bigger, faster, and more destructive than at any point in modern history, and money is pouring into the field: drones, sensors, suppression chemistry, predictive software, hardened vehicles, new apparatus. Where money and invention meet, intellectual property follows. If you are building something new in this space and you do not protect it, someone else will build the same thing eighteen months behind you, with more capital, and you will have no recourse.

What a patent actually is

A patent is a deal between you and the public, brokered by the government. You teach the world exactly how your invention works, in enough detail that a skilled person could build it. In exchange, the government grants you the right to exclude others from making, using, selling, or importing that invention for a limited term, generally twenty years from the filing date of a utility application. That is the entire bargain. Disclosure for exclusivity.

Notice what a patent is not. It is not a license to build your own invention; regulations, certifications, and other people's patents may still stand in your way. It is not automatic enforcement; the Patent Office grants the right; you police it yourself, in court if necessary. And it is not a trophy. A patent that claims too little, or describes too little, is an expensive piece of wall art.

Why the fire space is different

Most patent guides are written for consumer gadgets or pharmaceutical compounds. Fire technology has its own gravity. Three forces shape how you should think about patents here.

First, the customer is often the government. Fire departments, state forestry agencies, and federal land managers buy most fire technology. Government procurement favors documented, defensible technology. A granted patent signals to a contracting officer that your system is genuinely yours, and it protects you when a request for proposals invites your competitors to study your demo.

Second, the environment destroys assumptions. Fire inventions must work where temperatures soar, oxygen drops, visibility vanishes, and communications fail. Those hostile conditions are not just engineering constraints. They are patentable distinctions. An invention that does what existing technology does, but does it inside a flame front, can be novel precisely because of how it survives there. We will return to this idea throughout the book, because it is the single most useful drafting insight for this industry.

Third, lives ride on the technology. When your invention protects crews and civilians, your patent application doubles as a safety document. The discipline of writing one, enumerating every sensor, every failure mode, every operational scenario, makes the technology itself better. I have walked out of patent drafting sessions with engineering improvements I would not have found any other way.

A patent that claims too little, or describes too little, is an expensive piece of wall art. The goal of this book is to make sure yours is neither.

Who this book is for

This book is for the firefighter who modified a pump and realized nobody else had thought of it. For the engineer at a wildfire startup who has been told to "get the IP filed" and does not know where to start. For the founder deciding whether a provisional application is worth the money this quarter. And for anyone working with a patent attorney who wants to be a competent partner in the process rather than a passive client.

One thing this book is not: legal advice. I am an inventor, not an attorney. Eleven of my inventions have gone through this process, and I have worked with excellent patent counsel along the way. This book teaches you the craft of the document and the logic of the system so that your time with professionals is productive and your filings are strong. When real money or real disputes are on the line, hire a registered patent attorney or agent. Chapter Eleven explains how to find one, including free options for inventors who qualify.

The Patent Landscape

Before you write anything, you need to know what kind of protection you are pursuing and whether your invention qualifies at all. This chapter maps the territory: the types of applications, the four legal requirements every invention must meet, and the special wrinkle that affects software and artificial intelligence inventions, which now make up a large share of new fire technology.

The three application types that matter

The provisional application is the fire industry's best friend. It is an informal filing that establishes a priority date, the official timestamp of your invention, without starting examination. It is never examined, never published on its own, and expires after twelve months. Its job is to hold your place in line while you refine the invention, raise money, or test the market. The government filing fee is modest: as of this writing, $325 for a large entity, $130 for a small entity, and $65 for a micro entity. Chapter Ten covers those categories. A provisional has minimal formal requirements: a written description, any drawings needed to understand the invention, a cover sheet, and the fee. No claims are required, although including at least one is wise.

The nonprovisional utility application is the real thing. It gets examined, it can mature into an enforceable patent, and it must contain every formal section described in Chapter Four, including claims. If you filed a provisional, your nonprovisional must be filed within twelve months to keep the earlier priority date. Most of this book is about writing a document strong enough to serve as either one, because the smartest practice is to write your provisional to nonprovisional standards. A thin provisional that fails to describe what you later claim gives you a priority date in name only.

The design patent protects ornamental appearance rather than function: the distinctive look of a helmet, a nozzle housing, an apparatus body. Design patents matter in consumer facing fire products but are a minor player in the technology covered here, so this book sets them aside after this paragraph.

The four requirements

To be patentable, an invention must clear four hurdles, found in Title 35 of the United States Code.

Patentable subject matter. The invention must be a process, machine, manufacture, or composition of matter. Hardware in the fire space almost always qualifies. Software and analytics need careful handling, discussed below.

Utility. The invention must do something useful. Fire technology never struggles here. Suppressing fire, predicting fire, and protecting people from fire are about as useful as utility gets.

Novelty. The invention must be new. If a single piece of prior art, meaning any earlier patent, publication, product, or public disclosure, shows every element of your claim, the claim is dead. Chapter Three covers how to search before you write.

Nonobviousness. Even if no single reference shows your invention, examiners can combine references. The question is whether a person of ordinary skill in the field would have found the combination obvious at the time of filing. This is where most fire technology applications fight their battles, and it is why your application must explain not just what you built but why nobody had built it before. The Background section, covered in Chapter Five, sets up that argument.

The software problem, and the fire industry's advantage

Since the Supreme Court's decision in Alice Corp. v. CLS Bank in 2014, claims directed to "abstract ideas" implemented on generic computers face an extra hurdle. Pure data analysis, pure prediction, pure recommendation: these can be rejected as abstract unless the claims tie the idea to something concrete and technical.

Fire technology has a structural advantage here, and you should press it. Fire software is never just software. It ingests data from physical sensors mounted on physical drones flying through physical smoke. It outputs deployment orders to physical trucks, physical aircraft, and physical crews. When you draft claims for a fire analytics invention, anchor them in that physical chain: the sensors that gather the data, the surveillance devices that carry the sensors, the command entities that receive the output, the assets that move because the system said so. An examiner reading a claim that recites "acquiring sensory data from a plurality of sensors hosted on at least one fire surveillance device" is looking at a machine interacting with the physical world, not an abstract idea.

Before You Write a Word

The most expensive patent mistakes happen before drafting begins: disclosing the invention too early, naming the wrong inventors, leaving ownership ambiguous, or skipping the prior art search and writing a beautiful application for something that already exists. This chapter is the preflight check.

The disclosure clock

The United States runs on a first inventor to file system. The date that matters is your filing date, not the date you conceived the idea in the shower. Two consequences follow.

First, file before you talk. Once you publicly disclose the invention, by demonstrating it at a fire conference, publishing it, pitching it without a nondisclosure agreement, or posting the demo video, a one year grace period clock starts in the United States. Miss that window and your own disclosure becomes prior art against you. Worse, most foreign countries have no grace period at all: public disclosure before filing destroys foreign rights immediately. The fire industry lives on trade shows and live demonstrations. Get a provisional on file before the demo, every time.

Second, speed beats secrecy. If a competitor independently invents the same system and files first, they win, even if you invented it earlier. The provisional application exists for exactly this race. A solid provisional can be prepared in days, not months.

Search before you draft

You are not required to search prior art before filing, but drafting blind is gambling. A few hours of searching tells you whether your invention is novel, and just as valuable, it shows you the vocabulary examiners will use and the closest existing systems your application must distinguish.

Use the Patent Office's free Patent Public Search tool at ppubs.uspto.gov, plus Google Patents at patents.google.com, which has friendlier search and links to related literature. Search the function, not just your words for it: a "water tender routing system" may live in the database as "resource dispatch optimization." Search the classification codes of the closest patents you find; fire suppression hardware clusters in Cooperative Patent Classification class A62C, and you can browse neighboring inventions there directly. Save everything you find. You may need to cite it later in an information disclosure statement, and your attorney will want it.

One caution: finding something close is not the end. The question is never "does anything similar exist." It is "does any single reference show every element of what I would claim, and would combining references have been obvious." Closeness is normal. Identity is fatal. Obvious combination is arguable.

Inventorship: a legal fact, not a courtesy

An inventor is a person who contributed to the conception of at least one claim. Not the person who funded it, not the technician who built it to spec, not the boss, and not the colleague who would feel left out. Naming the wrong inventors, in either direction, can render a patent invalid or unenforceable. Decide inventorship honestly, claim by claim, and document who conceived what. In the fire industry, where inventions often emerge from crews working a problem together, this deserves real care: the firefighter who said "what if the exhaust itself dispersed the agent" is an inventor; the one who welded the bracket afterward probably is not.

Ownership: who holds the patent

Inventorship and ownership are different. Patents start out owned by their inventors, and ownership moves by written assignment. If you invented something within the scope of your employment, your employment agreement almost certainly obligates you to assign it to your employer. If you are a founder, your company should own the patents, not you personally, and investors will check. The instrument that accomplishes this is a short contract called a patent assignment, and because you will need one, this book includes a real one.

Keep an invention record

Maintain a dated record of the invention's development: sketches, test data, photographs, the concept diagram you drew before any lawyer was involved. Under the first to file system this record no longer wins priority races, but it remains invaluable for proving inventorship, supporting your attorney's drafting, and defending against claims that you derived the invention from someone else. One of the applications excerpted in this book began as a single hand built mind map, dated and saved, that grew into a fifty plus page filing. That diagram appears in Chapter Eight.

The Anatomy of a Patent Application

A utility patent application is built from standard parts in a standard order. Once you know the parts, the blank page stops being blank: it becomes a form to fill, section by section. This chapter walks the skeleton from top to bottom using a real fire technology application as the model. The chapters that follow go deep on the sections that demand the most craft.

The sections, in order

Title. Short, technical, descriptive. "AI-Based Allocation of Wildfire Management Resources." "Oxygen Supplementation System for Supporting Combustion Engines in Oxygen Diminished Environments." No marketing names, no trademarks, no cleverness. The title should let a searcher know instantly what field they are in.

Cross-Reference to Related Applications. If this application claims priority to a provisional or continues an earlier application, say so here. If not, write "None." One line, but a legally important one: this is part of the chain that preserves your earliest filing date.

Field of the Disclosure. One or two sentences placing the invention in its technical neighborhood, moving from general to particular. The wildfire command application does it in a single sentence: the disclosure "generally relates to wildfire management based on collected data, and more particularly, to an AI-based automated system for real-time allocation of wildfire management and suppression resources." General field, then particular contribution. Copy that rhythm.

Background. The problem your invention solves and why existing approaches fall short. This section has traps. Chapter Five is devoted to it.

Summary (or Brief Overview). A condensed statement of the invention, usually tracking the independent claims almost word for word. It often opens with boilerplate noting that the overview is not intended to limit the claims. That boilerplate is not decoration; it guards against a court later reading the summary as the outer boundary of your invention.

Brief Description of the Drawings. One sentence per figure. "FIG. 1A illustrates a network diagram of a system for an AI-based automated real-time allocation of wildfire management and suppression resources..." Mechanical, but mandatory.

Detailed Description. The body of the document and the subject of Chapter Six. This is where you teach the invention completely: every component, every connection, every variation, every alternative embodiment, keyed to the reference numerals in your drawings.

Claims. The numbered sentences at the end that define, with legal force, exactly what you own. Chapter Seven. Everything else in the application exists to support these.

Abstract. A single paragraph, 150 words or fewer in principle, summarizing the disclosure for searchers. Write it last. The common practice, visible in the example applications in this book, is to compress the first independent claim into prose.

Drawings. The figures themselves, filed as separate sheets. Chapter Eight.

How the parts reinforce each other

The application is not twelve independent essays. It is one argument assembled from interlocking parts. The Background establishes a problem. The Summary announces a solution. The Detailed Description proves you possess that solution by teaching it exhaustively. The Claims stake out the territory. The Drawings give the examiner a map. When an examiner rejects a claim, your attorney's response will quote the Detailed Description; if the support is not there, the argument fails. When a litigator attacks a granted patent, they will hunt for claim terms the description never explains. Every sentence you write in the description is ammunition you may need a decade later.

Write the description as if a stranger must build the invention from your words alone, with you unavailable for questions. Because legally, that is exactly the situation.

The hidden architecture: paragraph numbers and reference numerals

Two pieces of machinery hold the document together. Numbered paragraphs, written as [0001], [0002], and so on, let examiners and attorneys cite the specification precisely. Reference numerals, the numbers like 102 and 107 that tag every component in the drawings, tie the prose to the figures. The convention is to number by figure: components introduced in Figure 1 get numbers in the 100s, Figure 2 in the 200s, and so on. Once a component has a numeral, it keeps that numeral everywhere: the fire analysis server node 102 is "the FAS node 102" in every paragraph and every figure where it appears, forever. Consistency here is not style. Ambiguity about which component is which has sunk patents in court.

A note on boilerplate

Real applications contain pages of standard language: definitions of "a" and "an," statements that the embodiments are examples rather than limits, reservations of rights. The wildfire command application spends several paragraphs on exactly this. New drafters are tempted to cut it as filler. Do not. Each clause exists because some patent, somewhere, was narrowed or invalidated for lack of it. The paragraph stating that method steps "are not limited to being carried out in any particular sequence or order" exists because courts have held patentees to the listed order when the specification was silent. Borrow boilerplate from granted patents in your field, read it once so you understand what each piece does, and keep it.

The Background: Framing the Problem

The Background section sets the stage: here is the problem, here is what exists, here is why what exists falls short. Done well, it makes your invention feel inevitable and nonobvious at the same time. Done carelessly, it hands ammunition to examiners and future adversaries. The rule that governs everything in this section: describe the problem fully, and describe the prior art's failures carefully, but never characterize your own invention here and never admit more than you must.

The shape of a good Background

A strong fire technology Background moves through three beats. First, the stakes: why this problem matters. Second, the state of the art: what people currently do about it. Third, the gap: what the current approaches cannot do. Then it stops. The wildfire command application is a clean example of the form.

The trap: admitted prior art

Anything you describe in the Background as known or conventional becomes admitted prior art. You have sworn it exists, and the examiner can use it against your claims without finding a single document. So characterize prior art accurately but minimally. Say that battery powered drones lose lift in convective airflow; do not muse that "of course, one could imagine adding a turbine." Never describe your own contribution in the Background, even casually, or you risk converting your invention into the state of the art. The Fire Jet Drone application handles this edge skillfully: its background notes that prior art "avoids interaction between propulsion exhaust and suppression agents, based on assumptions of inefficiency, instability, or thermal degradation." That sentence does double duty. It describes the prior art's actual teaching, and it frames that teaching as a prejudice the invention overcame, which is one of the classic arguments for nonobviousness. When the entire field assumed something would not work, doing it anyway is the opposite of obvious.

The long felt need

Another nonobviousness signal worth planting: the long felt but unmet need. If the industry has wrestled with a problem for years and nobody solved it, that history argues your solution was not obvious. The Fire Jet Drone background states it directly: "There exists a long-felt but unmet need for an unmanned aerial system capable of predicting hazardous transitions... and coordinating mitigation actions across multiple responding assets." In the fire space this argument is unusually credible, because the need is documented in after action reports, fatality investigations, and decades of public agency wish lists. If such documents exist for your problem, your attorney will thank you for collecting them.

The Detailed Description

The Detailed Description is where you pay for your patent. The law demands a written description showing you actually possessed the invention, an enabling disclosure teaching a skilled person to make and use it without undue experimentation, and disclosure of the best mode you contemplated. Meet those demands generously and your claims have a foundation. Skimp, and the strongest claims in the world will collapse for lack of support.

Write for the person of ordinary skill

Your reader is the legally imagined "person having ordinary skill in the art": for fire technology, picture a competent fire protection engineer or systems integrator. You need not explain what a centrifugal pump is. You must explain everything about your invention that such a person could not derive on their own: the architecture, the data flows, the operating logic, the component choices, the reasons behind them. When in doubt, include it. No patent has ever been invalidated for teaching too much.

The two magic words: "may" and "embodiment"

Read any granted patent and two words appear in nearly every paragraph. Components "may" include this; "in one embodiment," the system does that. This is not weak writing. It is precision. "May" signals that a feature is optional, preserving claim breadth: if the specification says the drone "must" carry an infrared camera, a competitor who omits the camera may escape your claims. "Embodiment" signals that each described version is an example, not the boundary. The wildfire command application describes a basic architecture, then a blockchain variant, then quantum computing extensions, each as separate embodiments. The granted claims can then cover the basic version while the description proves possession of the advanced ones, leaving room for continuation applications later.

Be your own lexicographer

Patent law lets you define your own terms, and courts will hold everyone to your definitions. This is the single most powerful drafting tool you have, and fire technology gives you constant reasons to use it, because fire environments break ordinary meanings. Consider what "air" means inside a smoke column.

The Fire Jet Drone application does the same for the materials it disperses, defining "agent" to include "liquids, foams, gels, powders, particulates, slurries, fire suppressants, fire retardants, decontaminants, neutralizing compounds, or combinations thereof." One sentence, and a claim reciting "an agent" now covers everything from water to seed slurry for post fire rehabilitation. That is leverage.

Enumerate the variations

Fire technology descriptions should be catalogs as much as narratives. Every place your invention could use one of several components, list the alternatives: the propulsion unit "includes gas turbines, turbojets, turbofans, pulse jets, ramjets, hybrid combustion engines, or functionally equivalent devices." Every data source your system could ingest, name it. The wildfire command application devotes entire pages to enumerating sensors, from anemometers to gas analyzers for specific compounds to lightning detectors, and then enumerating assets, from Type 1 trucks through water tenders to hand tools and drip torches. This is not padding. Each listed item is disclosed subject matter you can claim later, and each one blocks a competitor from arguing that their variant falls outside your disclosure. Chapter Nine returns to these catalogs, because building them well is a fire industry specialty.

Include concrete numbers and worked examples

Abstract architecture plus concrete detail is the winning combination. The wildfire command description includes a specification profile for a hypothetical truck: travels 60 miles per hour on zero slope laden with a full tank, 30 on a 25 degree slope, carries 2,000 gallons, applies water 200 feet, runs 16 hours between refills. It also includes a complete operational narrative: an incident commander named Sam logs in, identifies a fire on satellite imagery, ranks protection priorities, and receives a continuously optimized suppression plan. These passages do enormous work. They prove enablement, they make the invention vivid for the examiner, and they give your attorney concrete material for arguments years later. Every fire application should contain at least one fully worked scenario from ignition to outcome.

Claims: Where the Patent Lives

Everything before this chapter is preparation. The claims are the patent: numbered single sentence definitions of exactly what you own. Infringement is measured against the claims. Validity is attacked against the claims. Licensing value is priced against the claims. Learn to read and draft them, even if an attorney polishes the final version, because nobody understands your invention's essential elements better than you.

The grammar of a claim

Every claim has three parts. The preamble names the category: "A system for generation of wildfire suppression asset allocation..." The transition is a single legal hinge word, usually "comprising." The body lists the elements and how they connect. A claim is one sentence, no matter how long; the wildfire command system claim runs over two hundred words and remains, grammatically, a single sentence ending in a single period.

Comprising versus consisting of: the most expensive word choice in patent law

"Comprising" means "including at least." A claim to a system comprising elements A, B, and C is infringed by a system with A, B, C, and fifty other things. "Consisting of" means "exactly these and nothing more." A claim to a system consisting of A, B, and C is escaped by adding element D. The difference is one word and it can be worth the entire patent. Almost every claim you ever write should say "comprising."

Independent and dependent claims

An independent claim stands alone and defines the invention at its broadest. A dependent claim references an earlier claim and adds a limitation: "The system of claim 1, wherein the agent introduction interface comprises a Venturi geometry." Dependent claims are your insurance policy. If claim 1 turns out to be too broad and falls to prior art, claim 4 with its added Venturi limitation may survive, because invalidating it requires finding all of claim 1 plus the Venturi feature in the prior art. Build dependent claims around the features most likely to distinguish your invention: the regenerative thermal management, the consensus mechanism, the exhaust shear dispersion. Each dependent claim is a prepared fallback position, drafted in peacetime for use in war.

The system, method, medium triad

Software adjacent fire inventions should be claimed three ways: as a system (the machine), as a method (the steps), and as a non-transitory computer readable medium (the stored instructions). The wildfire command application does exactly this: claims 1 through 10 cover the system, 11 through 16 the method, and 17 through 20 the medium, all reciting parallel elements. The three categories catch different infringers. The system claim catches whoever runs the server. The method claim catches whoever performs the steps. The medium claim catches whoever distributes the software. Hardware inventions get a parallel treatment: the Fire Jet Drone application pairs an apparatus claim ("An unmanned aerial hazard-mitigation system, comprising...") with method of use claims ("A method of mitigating a hazard event, comprising: (a) deploying a combustion-powered unmanned aerial vehicle into a hazardous environment..."), then fans out into forty total claims covering operational scenarios from flame front separation to seed slurry dispersal.

Drafting your claim set: a working method

This method produces a respectable first draft, suitable for a provisional and ready for an attorney to refine into a nonprovisional.

Step one: write the elevator elements. List the three to six components or steps without which your invention is not your invention. For the fire jet drone: an airframe, a combustion propulsion unit, a thrust vectoring assembly, an agent interface positioned in the exhaust, a control system. That list, joined by "comprising," is your independent claim.

Step two: subtract until it hurts. For each element, ask whether a competitor could build something commercially equivalent without it. If yes, cut it from the independent claim and save it for a dependent claim. The broadest valid claim is the goal; every unnecessary element in claim 1 is a free exit door for infringers.

Step three: add the distinguishing twist. Your independent claim should end with the feature that makes the invention new, often introduced with "wherein." The drone claim ends: "wherein dispersion of an agent occurs due to exhaust-induced shear forces without mechanical pumping." That clause is the invention's signature, the thing no prior art shows.

Step four: ladder the dependents. Write ten to twenty dependent claims, each adding one feature from your Detailed Description's catalog: the specific engine types, the Venturi geometry, the fuel cooled electronics, the absence of batteries, the prediction module, the ad hoc networking.

Step five: mirror into methods. Rewrite the system as steps performed in sequence, then add method claims for each operational use case your description teaches.

Drawings That Carry Weight

Patent drawings are not illustrations. They are disclosure. Anything shown in a figure counts as described, and the rules require drawings wherever they are necessary to understand the invention, which in fire technology means always. The standard for utility drawings is clarity, not beauty. Black and white line work, clear labels, consistent reference numerals. A clean block diagram beats a gorgeous rendering every time.

The figures every fire system application needs

The system overview. One figure showing every major component and how they connect. The wildfire command application's Figure 1A is a model of the genre: drone and unmanned vehicle (111) feed a sensor array (112), sensory data flows to the fire analysis server (102) hosting the analytics module (107), local data (103) and remote cloud data (106) feed in from the sides, and recommendations flow out to command and control entities (113). Every arrow is a labeled data flow: Sensory Data, Recommendation, Allocations. An examiner can absorb the whole invention from this one sheet before reading a word of prose.

The variant architecture. If your description teaches alternative embodiments, give each its own figure. Figure 1B of the same application redraws the system with a blockchain ring and consensus flow added. Two figures, two embodiments, both locked in as disclosure.

The component detail. A closer view of the heart of the invention. Figure 2 zooms into the server node and, notably, renders the machine readable instructions as labeled blocks (214 through 224), one per claimed function. The craft here: the figure mirrors the claim structure, so every claim element has a visible anchor.

The flowchart. Method claims want flowcharts. Figures 3A and 3B chart the claimed methods step by numbered step (302 through 330), in the same order as the method claims. When the examiner reads "at block 308, the processor may query a local fires'-related database," the claim, the prose, and the figure all click together.

The hardware figure. Software heavy applications conventionally close with a generic computing device figure, the block diagram of processor, bus, memory, and input and output. It looks like furniture, but it grounds computer implemented claims in physical hardware, which matters for the subject matter battles described in Chapter Two.

The concept diagram: where inventions are born

Before any of those formal figures existed, the wildfire command invention was a single sprawling mind map, hand assembled and dated June 29, 2023, with the system name in the center and branches radiating outward: digital inputs on one side, wind speed through soil moisture probes through infrared cameras; user input resources on the other, aircraft quantities through water tenders through hand crews; protection priorities to rank; outputs flowing to crews and remote controlled assets. That one page later expanded into dozens of pages of specification, hundreds of enumerated elements, and twenty claims, but the diagram came first.

Draw your invention this way on day one. Put the system in the middle. Branch every input you could ever ingest, every resource you could ever direct, every output you could ever produce. Date it. The exercise costs an afternoon and delivers three things: a conception record for inventorship, a complete checklist for your Detailed Description's catalogs, and, cleaned up, the skeleton of your formal figures. The cover of this book is drawn in homage to exactly that diagram.

Formalities worth knowing

Use one figure per sheet where possible, number figures consecutively (FIG. 1, FIG. 1A, FIG. 2), and label with reference numerals that match the description exactly. Arrows show data or material flow; dashed lines show optional or wireless connections, a convention Figure 1A uses for the cloud data paths. For a provisional, informal drawings, even neat hand drawings or photographs, are acceptable; the formal ink work can wait for the nonprovisional. What cannot wait is completeness: a drawing you do not file with the provisional adds nothing to that priority date.

Drafting for the Fire Industry

Everything so far applies to any technology. This chapter is the fire specific playbook: the recurring patterns, opportunities, and hazards that come from drafting for an industry defined by hostile environments, government customers, mutual aid interoperability, and life safety stakes.

Claim the environment

The defining move of fire technology drafting is claiming operation under conditions that defeat conventional equipment. The Fire Jet Drone application is built on this move from its first page: battery electric drones fail in high temperature, the prior art assumed exhaust and agents must never mix, and the claimed system thrives exactly where the assumptions break. Its method claims make the environment an explicit limitation: "wherein operation occurs in ambient temperatures exceeding battery-safe limits." The Oxygen Supplementation system is the same idea in a different vehicle: engines fail in oxygen depleted air, so a system that keeps them running inside the smoke column is novel because of where it works. When you draft, ask what your invention does that ordinary equipment cannot, in heat, in smoke, in oxygen depletion, in communications blackout, in darkness, and write those conditions into both the description and the claims. The environment is your prior art moat.

Build the catalogs: sensors, assets, agents, water

Fire systems are integrators. They drink from many data sources and command many resources, and your application should enumerate every one, because each enumerated item is claimable subject matter and a closed escape route. The wildfire command application enumerates thirty three sensor input categories, from wind speed and vegetation moisture probes through gas analyzers for specific compounds (carbon monoxide, hydrogen cyanide, particulate matter) to lightning detectors and decibel meters, then adds the future proofing clause: "and any future sensors that may be developed." It enumerates the asset world with the same completeness: aircraft classes, the full ladder of Type 1 through Type 6 trucks, water tenders, marine assets, hand crews, drone operators, chainsaws, drip torches, suppressants, retardants, foams, and gels. It even enumerates water itself: hydrants, ocean, rivers, streams, lakes, ponds, swimming pools, storage tanks, water treatment plants.

These catalogs are not overkill. They are strategy. The fire service already organizes the world into typed resources, and the typing systems of the National Wildfire Coordinating Group and the Incident Command System hand you a ready made, industry standard vocabulary. Use it. An examiner or judge can verify that a "Type 3 truck" is a real, defined thing, and a competitor cannot argue their water tender falls outside a disclosure that names water tenders.

Claim the interoperability

Fire technology never operates alone. It plugs into computer aided dispatch, resource ordering systems, reverse 911 notification, tactical data links, and mutual aid networks. Those connections are inventive subject matter. The wildfire command application claims automatic querying of nearby agencies' dispatch systems to inventory available assets; the drone application claims operation as "a virtual forward air controller, generating digital targeting or release vectors for manned aircraft" in zero visibility and satellite denied conditions. When your system touches the existing emergency infrastructure, describe the touchpoint precisely and claim it. Integration features are also where procurement officials look first, so the patent and the sales deck reinforce each other.

Claim the lifecycle

A fire technology invention rarely has one use. The drone application's forty claims sweep the entire fire lifecycle and beyond: pre ignition prediction, infrastructure patrol, frontal suppression, pneumatic flame separation, radiant heat curtains, smoke clearing at evacuation choke points, anchor point establishment, prescribed fire support, mop up, hazardous material decontamination, riparian protection with eco safe agents, and post fire rehabilitation by dispersing seed and soil stabilizer slurry. Each scenario became a method claim. Walk your own invention through the same timeline, before the fire, during the fire, after the fire, and through adjacent emergencies, hazardous materials, industrial accidents, defense applications. Every credible use you describe and claim multiplies the patent's licensing surface.

Mind the public safety wrinkles

Three issues peculiar to this industry deserve a sentence each. Government use: under 28 U.S.C. § 1498, when the federal government uses a patented invention, the remedy is compensation in the Court of Federal Claims, not an injunction; you cannot enjoin the government mid fire, and you would not want to. Standards and certification: patents do not substitute for listings and approvals from bodies like Underwriters Laboratories or compliance with National Fire Protection Association standards; keep the patent claims free of standard mandated features where possible, since features every compliant product must have make poor distinguishing limitations. Emergency ethics: nothing in patent law stops you from licensing generously to public agencies while enforcing against commercial competitors, and that posture serves both the mission and the business.

Filing Mechanics

The writing is done. Now the paperwork. Filing is the most mechanical part of the process and the easiest to demystify, because one of the applications in this book comes with its complete filing package: cover sheet, application data sheet, fee transmittal, and the electronic receipt that came back. This chapter walks that package end to end.

Entity status: the first money question

The Patent Office charges three price tiers. A large entity pays full fare. A small entity, generally an individual inventor, a nonprofit, or a business with fewer than 500 employees counting affiliates, pays fees reduced by 60 percent. A micro entity is a small entity that also has fewer than five prior nonprovisional applications and gross income below a threshold tied to median household income, and pays fees reduced by 80 percent. As of this writing, the provisional filing fee runs $325, $130, and $65 across the three tiers, and the combined filing, search, and examination fees for a nonprovisional utility application run roughly $2,000, $800, and $400. Fees change; confirm the current schedule at uspto.gov before filing. Claim your status honestly. Falsely claiming a discount, with intent to deceive, is fraud on the Patent Office and can render the resulting patent unenforceable.

The provisional package, document by document

The Oxygen Supplementation provisional filed in October 2021 consisted of four documents, and yours will look the same.

The Provisional Cover Sheet (Form SB/16). Inventor name and city, title of the invention, correspondence address, entity status, and a statement about government funding. The example checks "No" on government funding; if your fire technology was developed under a federal grant or contract, you must say so, and the government acquires certain rights.

The Application Data Sheet (Form AIA/14). The bibliographic backbone: inventor legal name and mailing address, applicant (in the example, the inventor's company, PyroNemesis, Inc., listed as assignee applicant), correspondence customer number, and signature. When a company is the applicant, a registered practitioner must sign.

The application itself. Specification, claims if included, abstract, and drawings, filed as a single document. The receipt for the example breaks it down: specification pages 1 through 3, claims page 4, abstract page 5, drawings page 6. Six pages total. A provisional does not have to be long. It has to be enabling.

The fee transmittal and payment. The example paid the then current small entity provisional fee electronically and received an electronic payment confirmation number within seconds. In return came the Electronic Acknowledgement Receipt: application number 63/270,268, a confirmation number, a timestamp to the second, and a digest of every file received. That receipt is your proof of priority date. Archive it like the deed to a house, because that is what it is.

Filing through Patent Center

All filing now runs through Patent Center at patentcenter.uspto.gov, which replaced the older EFS-Web system that appears on the example's receipts. Create a USPTO.gov account, verify your identity, and you can file as an unregistered filer for your own provisional. Upload documents as text searchable PDFs, pay by card or deposit account, and download your receipt immediately. The whole session, with documents prepared in advance, takes under an hour.

Government fees only, as of mid 2026; professional drafting typically adds several thousand dollars more. Always verify against the current USPTO fee schedule.

After You File

Filing is the starting gun, not the finish line. Three clocks start ticking, and how you manage them determines whether your application becomes an asset or a souvenir.

The twelve month clock

A provisional expires twelve months from filing, with no extension worth relying on. Before it does, you must file the nonprovisional claiming its benefit, or file an international application under the Patent Cooperation Treaty, or let the priority date go. Calendar the deadline the day you file, at month nine, not month twelve, because converting well takes weeks. Conversion is also the moment to fix everything this book has flagged: upgrade "consisting of" to "comprising," fill description gaps, expand the claim set, formalize the drawings. You may also file additional provisionals during the year as the invention evolves; a nonprovisional can claim priority to several.

From "patent pending" to prosecution

The moment you file anything, provisional included, you may mark your technology "patent pending." Use it; it deters copyists and signals seriousness to buyers and investors. After the nonprovisional is filed, expect quiet for a year or more, then a first Office Action: the examiner's written rejection or allowance of each claim. Rejection is normal. The overwhelming majority of applications receive at least one rejection, and the back and forth that follows, amendment, argument, sometimes an examiner interview, is called prosecution. This is where a registered practitioner earns their fee, and where the deep Detailed Description you wrote pays out: every amendment must find support in the specification as filed, with no new matter allowed. The application publishes eighteen months from the earliest priority date unless you request nonpublication at filing, a request available only if you forgo foreign filing.

Assignments, again, and on the record

If ownership is moving, from inventor to startup, from startup to acquirer, execute the assignment promptly and record it with the Patent Office's assignment branch, ideally within three months. The Team Wildfire assignment reproduced in Chapter Three was executed with the company's chief executive and the inventor signing on the same day, with the application number and filing date inserted by counsel, and language authorizing the attorneys to complete those details. That is standard, efficient practice. Investors performing diligence on a fire technology company will pull the public assignment records first; make sure what they find matches what you have told them.

How to choose a patent attorney

Hire on three criteria: registration, technical fit, and proof of work. Everything else is salesmanship.

Registration first. Only registered patent attorneys and patent agents may represent you before the Patent Office. Both have passed the patent bar and both can draft and prosecute applications; the difference is that an agent is not a lawyer and cannot handle litigation, licensing contracts, or infringement opinions. Agents typically cost less, and for drafting and prosecution they are every bit as qualified. Verify anyone you are considering on the official practitioner roster at oedci.uspto.gov. If a name is not on that roster, the conversation is over.

Technical fit second. Patent practitioners hold technical degrees, and the degree matters. Fire technology spans mechanical systems, chemistry, electronics, and software, and your drafter should be fluent in whichever your invention lives in. A practitioner who writes pharmaceutical claims all day will struggle with a thrust vectored drone; one who writes software claims all day will miss the chemistry in a suppression agent. Ask directly: what fraction of your docket is in my technical area?

Proof of work third. Ask for the numbers of granted patents the practitioner personally drafted in adjacent technology, then pull them on Google Patents and read claim 1 of each. You now know how to read a claim; use the skill. Tight, layered claim sets with strong dependent ladders tell you the person can do the job. While you are reading, check who will actually do your work: at larger firms the partner who pitches you may hand the drafting to a first year associate. Ask, and ask what the supervision looks like.

Settle the money in writing. Most practitioners draft applications for a flat fee and prosecute hourly. Get a written estimate that runs through the first Office Action response, not just through filing, because filing is the cheap part. A typical professionally drafted fire technology application runs several thousand dollars for a provisional and five figures through grant; precise numbers vary with complexity, so get yours in advance.

Know the red flags. Walk away from anyone who guarantees a patent, discourages a prior art search, quotes a price before asking a single technical question, or shows no curiosity about how your invention works. A good practitioner interrogates you: how does the agent enter the exhaust stream, what happens when the sensor fails, why has nobody done this before. That interrogation is the work. Be especially wary of invention promotion companies, the outfits advertising on late night television that promise to patent and market your idea for a package fee. The Patent Office publishes complaints against them and federal law gives inventors specific protections because the industry has burned so many people. They are not patent counsel. Hire patent counsel.

Working with the attorney you chose

Even confident self drafters should bring a registered patent attorney or agent into the process no later than the provisional to nonprovisional conversion. To make the engagement efficient: arrive with your dated concept diagram, your prior art search results, your enumerated catalogs of sensors and assets and agents, your worked operational scenario, and a draft claim built by the five step method in Chapter Seven. An attorney handed those materials drafts faster, charges less, and produces a stronger application than one handed a phone call and a brochure. Resources for inventors who cannot afford counsel: the Patent Office's Pro Se Assistance Program supports inventors filing on their own, the Patent Pro Bono Program matches financially qualifying inventors with volunteer attorneys, and the Inventors Assistance Center answers procedural questions by phone. All three are reachable through uspto.gov/patents/basics.

Building the family

Strong inventions outgrow single patents. While your application is pending you may file continuations, new applications sharing the same specification and priority date but with new claims, and continuations in part adding new matter. The embodiments you generously disclosed but did not claim, the blockchain variant, the quantum extension, the decontamination use case, are exactly what continuations harvest. The fire industry moves fast; a pending continuation lets you write tomorrow's claims against today's competitors using yesterday's priority date. Keeping one application in the family alive is the cheapest strategic option in patent law.

The Fire Patent Checklist

Everything in this book, compressed to one working list. Print it, pin it over the desk, and check items off as you go. When every box is marked, you are ready to file.

Before drafting

• No public disclosure, demonstration, sale, or offer for sale has occurred; if one has, the United States one year grace period deadline is calendared and foreign rights have been assessed.
• Prior art searched on Patent Public Search and Google Patents, including Cooperative Patent Classification class A62C neighbors; results saved for the information disclosure statement.
• Inventorship determined claim by claim and documented.
• Ownership settled; assignment drafted if the applicant will be a company.
• Dated concept diagram and development records preserved.

The specification

• Title is short, technical, and searchable.
• Background states the stakes, the state of the art, and the gap, and says nothing about the invention itself.
• Long felt need and industry prejudice documented where they exist.
• Summary tracks the independent claims and carries non limiting boilerplate.
• Special terms defined ("air," "agent," "vehicle," "water source") with fire environment breadth.
• Every optional feature introduced with "may"; every variation framed as an embodiment.
• Catalogs enumerated: sensors, assets by Incident Command System type, agents, water sources, data integrations, with future proofing language.
• Hostile environment operation described explicitly: heat, smoke, oxygen depletion, darkness, communications loss.
• At least one worked operational scenario from detection through outcome.
• Concrete numbers included: capacities, ranges, rates, endurance.
• Every claim term appears and is explained in the description.

Claims and drawings

• Independent claims use "comprising" and end with the distinguishing "wherein" clause.
• Dependent claims ladder the fallback features, ten to twenty deep.
• Software inventions claimed as system, method, and non transitory computer readable medium; hardware paired with method of use claims across the fire lifecycle.
• System overview figure, component detail figure, and method flowcharts prepared; reference numerals consistent everywhere.
• Generic computing device figure included for computer implemented claims.

Filing

• Entity status verified honestly against the small and micro entity rules.
• Cover sheet or Application Data Sheet complete, signed, names matching across all documents.
• Government funding question answered accurately.
• Text searchable PDFs uploaded through Patent Center; fee paid; Electronic Acknowledgement Receipt archived.
• Twelve month conversion deadline calendared at month nine.
• Assignment executed and recorded if ownership is moving.

Resources

United States Patent and Trademark Office, patent basics: uspto.gov/patents/basics. The official starting point, including the Inventors Assistance Center, the Pro Se Assistance Program, and the Patent Pro Bono Program.

Patent Center: patentcenter.uspto.gov. Where applications are filed and tracked.

Patent Public Search: ppubs.uspto.gov. The official full text search of United States patents and published applications.

Google Patents: patents.google.com. Friendlier searching, machine translations of foreign art, and citation graphs.

USPTO fee schedule: uspto.gov fee schedule. Always confirm current fees here before filing.

Manual of Patent Examining Procedure: uspto.gov/mpep. The examiners' own rulebook. Dense, but authoritative when you need the actual rule.

Cooperative Patent Classification, class A62C: the classification home of fire fighting technology, browsable from either search tool above. An afternoon spent reading your classification neighbors is the best prior art education available at any price.