What does a patent specification contain?
The usual sections of a specification, why a part keeps one name in the claims and the description, and how to review the draft for gaps.
Publisher: patentagents.ai
Short answer
A patent specification is the written explanation of the technical subject, and it concludes with the claims. The same part keeps the same name in the description and in the claims, so the claim terms find support in the description.
Which sections does a patent specification contain?
A specification is arranged so a reader can find the explanation that matches the claims. Common sections are a background, a summary of the subject, a brief list of any drawings, and a detailed description of how the parts or steps work. The claims follow as the numbered claim set. An abstract is a short separate paragraph, and it uses the same names as the rest of the document.
Section 112(a) of title 35 requires a written description of the invention and of how to make and use it, plus the best mode contemplated by the inventor of carrying out the invention. Section 112(b) requires the specification to conclude with one or more claims that particularly point out and distinctly claim the subject matter. 37 CFR 1.75 states that closing requirement for the claims and sets the form for dependent claims.
The background states the technical setting in plain language, and every feature it names also appears in the detailed description. The summary tracks the subject the claims state, in the same words. The detailed description explains parts, steps, and alternatives in an order a reader can follow. Name a part before a later passage relies on it.
Put one subject in each block of the detailed description. A block that explains two mechanisms at once will hide a gap in one of them. Alternatives that the source notes already record belong after the main arrangement, labeled as alternatives. An open point belongs where a reader will see it.
Which drawings belong in the set?
When a drawing helps, the brief list names each drawing, and the detailed description refers to those names while it explains the parts. The drawing is a file you already have, such as a design diagram prepared with the notes. A text list of the parts can sit beside that reference. Keep the drawing file in the set beside that list.
If a drawing is missing, say so on the open-point list. Describe a drawing when its file is in the source set, and use the labels that drawing shows.
Why must the same word stay the same part?
37 CFR 1.75 requires the claims to conform to the invention set forth in the rest of the specification, and the terms in the claims to find clear support or antecedent basis in the description. Use one working term for each part in the summary, the detailed description, the abstract, and the claims. If the claims say gate, the sections say gate. An alias may appear once, where the part is introduced, and the working term takes over after that.
The specification may describe supported details and alternatives that are not recited in the current claims. Keep terminology consistent, and do not invent values, materials, or operating modes that the source material does not support.
When you change a term in the claims, change it in the specification in the same pass, including the abstract and the summary. Then read both documents for the old word. A leftover old word looks like a new part.
How do you review the draft for gaps?
Read the claims first. For each feature in an independent claim, find the passage in the detailed description that explains it. When no passage explains it, the specification has a gap. Add the explanation from the source notes, or write the gap down and leave it visible.
Then read in the other direction. A passage that no claim uses can still be background or an alternative the notes already record. Label it so its role is clear. A part that is named once and never used again is either a leftover word or a missing explanation.
Check the claims at the same time. An element is commonly introduced with 'a' or 'an.' Use 'the' to refer back to that element, including an element incorporated from a claim on which the claim depends. The description should use the working term for that part, not a new one.
Claim 1: A system comprising a processor. Claim 2: The system of claim 1, wherein the processor ...
Edit terms, then gaps, then sentence shape, so a renamed part is not missed. Keep the open-point list beside the draft and update it when a gap is filled. patentagents.ai can build a specification draft from the same source set as the claim draft and export that draft as a Word .docx file.
Specification reading flow
- 1Read the claims
- 2Find the section that explains each feature
- 3Align terms across the sections and the claims
- 4Mark any gap the source notes do not fill
Sources
Tradeoffs and limits
- Matching every claim term in the specification takes an extra reading and keeps one part from carrying two names.
- A separate block per subject is easier to check for gaps and makes the draft longer than one continuous narrative.
- Leaving an open point on the page keeps an invented value out of the draft and leaves a blank that a later reading has to resolve.
Next step
One link. Choosing it does not start a run.