What Patent Applications Contain
Read from 32 US software non-provisional applications, section by section. Figures are of documents. Method and limits: how we read these filings.
All 32 applications followed the same section order and left sections out rather than moving them. Beyond that fixed skeleton they organise the explanation in four recognisable ways, and the same technical thing does visibly different work in the abstract, the claims and the description.
A patent application is not one document so much as several views of one invention, bound together in a prescribed order. Reading 32 of them makes two things visible: how little the order varies, and how much the organisation inside it does.
The Skeleton Is Fixed
Every one of the 32 followed the section order set out in 37 CFR 1.77(b). Sections were omitted. None were reordered.
| Section | Present in | Notes |
|---|---|---|
| Title | 32 of 32 | Required. |
| Cross-reference to related applications | 27 of 32 | Present when the benefit claim appears in the text. The application data sheet carries it either way. |
| Background | 31 of 32 | Permissive in the rule. Omitted once in this sample. |
| Summary | 25 of 32 | The most variable section. Omitted by three of the four problem-led applications. |
| Brief description of the drawings | 32 of 32 | Required where there are drawings. |
| Detailed description | 32 of 32 | Required. |
| Claims | 32 of 32 | Required. |
| Abstract | 32 of 32 | Required. |
The interesting row is the summary. It is the one substantive section that a quarter of these applications did without, and the ones that dropped it were disproportionately the applications that spend longest explaining the problem instead.
Four Ways of Organising the Same Explanation
Inside that skeleton, the 32 fall into four groups by how the detailed description is organised. These are ways of explaining, not application types, and nobody is required to choose one.
| Organisation | Documents | How the description runs |
|---|---|---|
| Mechanism-led | 20 of 32 | A walk through the figures, one at a time, carrying structure, behaviour, procedure and data. Background is short. The common case. |
| Problem-led | 4 of 32 | The setting and the field's concepts explained before and around the mechanism, with definitions and comparisons. Problem and context run 20% of elements against 5% elsewhere, and these are the longest applications in the sample at a median 18,879 words against about 10,000. |
| Interface-centred | 6 of 32 | The mechanism alongside a walk through the screens: what each shows, what the person does, what the system does next. All six carry interface figures, against 6 of the other 26. |
| Claim-dominant | 2 of 32 | A large claim set with a short description that restates each claim element with its alternatives. A drafting choice rather than a property of the invention. |
One Thing, Four Jobs
The clearest way to see why an application is structured this way is to follow a single element through it. In one application from the sample, the phrase "an input document" appears in the abstract, in the claims and in six paragraphs of the description, doing something different in each place.
| Where | As filed | What that section is doing |
|---|---|---|
| Abstract | "An input document can be subdivided into segments" | States the thing and what happens to it, in one sentence. |
| Claim 17 | "receiving a selection of an input document" | Recites it as a step, in the register claims use. |
| Description, paragraph 23 | "an input document may be referred to herein as an “original” document or a “source” document" | Fixes the vocabulary, so later paragraphs and the claims can be read together. |
| Description, paragraph 169 | "convert format of an input document" | Says what the system does with it, deep in the mechanism. |
This is why a practitioner asks for the things engineers find tedious: synonyms, alternatives, operating conditions, what each part is for. The description paragraph that defines a synonym is not padding. It is the paragraph that lets one word in a claim reach more than one implementation.
Passages are from a published US application, quoted as filed. The document is identified by the sample's own reference rather than by applicant or firm. Noting that a term appears in several sections is a textual observation. Whether any passage provides legally sufficient support for any claim is a separate question this reading did not reach.
What This Does Not Decide
- It does not say how an application should be organised. Four organisations appear here; the sample cannot say which serves a given invention.
- It does not say that any section, passage or definition supports any claim. Written description and enablement are decided on specific claims against a specific disclosure.
- It does not state the requirements themselves. Those are in the rule and the statute, not in a count of documents.
- The word counts and element shares describe this reading. A second reader segmented the same documents into 5% to 38% more elements, so treat element shares as a property of the reading rather than of the filings.
- It is 32 documents in one technology area. It is not a survey of US practice.
Educational, not legal advice. Drafting and filing decisions belong with a registered patent practitioner.
Related
- How we read these filings, the sampling, the definitions and the limits
- What real provisional applications contain, the same reading applied to the provisionals
- Showing possession of what you claim
- How broadly can I claim
- What happens during prosecution
- How to write a patent disclosure