Reference numerals live in two documents at once. The drawings carry the numbers; the specification defines them; and the space between the two belongs to nobody. The illustrator labels every part they can see, the spec never catches up. The spec goes through three more revisions than the drawings and picks up a part along the way. Each document looks fine on its own — the mismatch only appears when you check them against each other, which most people do once, at the end, if at all.
The cost of getting it wrong is concrete: a drawing objection under the numeral rules and a multi-week correction round trip. And the errors are not carelessness problems. They are process problems, and the process that prevents them is short: a numeral register, a two-way audit, and a full recheck after every change.
This guide covers all three, plus copy-paste prompts for generating multi-view sets in PatentFig AI with the numerals locked from the start.
One number, one part, in every view — the difference between clean and objectionable numbering is visible at a glance.
Quick answer: the rule in one sentence
The same part must carry the same reference numeral in every view, and the drawings and the specification must mirror each other in both directions. For US filings the rule is explicit in 37 CFR 1.84: paragraph (p)(4) requires that the same part appearing in more than one view always be designated by the same reference character, and that the same character never designate different parts; paragraph (p)(5) closes the loop from the other side — reference characters not mentioned in the description shall not appear in the drawings, and vice versa; paragraph (q) governs lead lines — every numeral needs one, and they must not cross each other. MPEP 608 is where objections on these grounds get their teeth. The same-sign-same-feature principle carries through PCT practice, though sheet formatting diverges by office; the office-by-office comparison covers the differences.
The four ways numerals go wrong
1. Same part, different number across views
Symptom: the clamp is 14 in FIG. 2 and 41 in the exploded view drawn three weeks later. Each figure is self-consistent, so nothing catches the error inside a single sheet — it only shows when the full set is laid side by side.
Fix: never assign a number from memory. Every new view starts with the register (below) open next to it.
2. Orphan numerals
Symptom: a numeral in FIG. 4 that the spec never mentions, or a "biasing spring 52" in the text that no figure shows. Both come from the two documents revising at different speeds — the same disease in opposite directions.
Fix: the two-way audit. A one-way check catches exactly half of these.
3. Cascade renumbering
Symptom: numbers are packed sequentially, a part gets added mid-project, and everything after the insertion point shifts — across every figure and every paragraph that cites those parts. A ten-minute edit becomes a late night.
Fix: leave gaps. Number in tens per subassembly (body 10–19, hinge assembly 20–29) or skip a few values between groups. The new latch drops into an existing gap as 27 and nothing else moves.
4. Vague lead lines
Symptom: the number is right, the line is drawn, but it ends on the boundary between two parts, and nobody can say whether 26 means the slot or the boss next to it. An examiner who can't tell will not guess in your favor.
Fix: end the lead line inside the part's outline, add a detail view if the area is crowded, and ask of every line before filing: can this possibly point at more than one thing?
The numeral register: four columns
Keep one flat table per application, started the moment the first part gets a number — never reconstructed after the fact, because a reconstructed register already contains the errors it was supposed to catch.
| Numeral | Part name | First appears in | Spec paragraph |
|---|---|---|---|
| 10 | stand body | FIG. 1 | [0021] |
| 12 | hinge | FIG. 1 | [0023] |
| 26 | slot | FIG. 3 | [0028] |
Each column earns its place:
- Numeral — one row per number. Assign 26 twice and the conflict stares at you at entry time.
- Part name — one canonical name per part, so "clip" and "latch member" can't coexist in the text.
- First appears in — tells you which sheet to open first during the audit, and doubles as a blast-radius map when something changes later.
- Spec paragraph — pays off in the final pass against the last draft. Update it the moment paragraph numbers move; a stale register is worse than none, because it certifies errors instead of catching them.
A CSV template with these columns is at patentfig.ai/resources — take that instead of rebuilding the table from scratch.
The two-way audit
Each direction catches a different error class, so both are mandatory:
- Figures to spec — walk each sheet, tick each numeral off against the register. Anything you can't tick is an orphan in the drawings.
- Spec to figures — every numbered part in the text must land on a register row and a visible numeral in at least one figure. This is the only pass that finds the undrawn spring 52.
- Row-conflict check — one numeral, one row, so a number pointing at two different parts surfaces as a duplicate-row collision.
- Full recheck after any change — never just the figure you touched. You think you only edited FIG. 3, but the renumbering rippled into four figures and eleven paragraphs; you think you only renamed a part, but the old name survives in three places. Change impact is exactly what human memory tracks worst, so the recheck has to be mechanical and total.
An exploded view shares its numeral map with every other view in the set — regenerating one figure should never renumber the rest.
Tooling helps most at this step. PatentFig AI holds one numeral map across all views, so regenerating a single figure after a design tweak leaves the other views' numbers untouched, and version history shows what moved between drafts instead of you eyeballing two PDFs. Before filing, the Figure Checker cross-checks numerals against the figure set and lists mismatches directly. The tool is the second net, though: software catches inconsistencies while missing the semantic error — the numeral that is perfectly consistent and points at the wrong part. That one only falls out of the register.
Prompt examples
Write the numeral map into the generation prompt so consistency is locked at the source:
Generate patent line drawings of a folding phone stand in four views: front, side,
top, and exploded. Use one shared set of reference numerals across all views:
10 stand body, 12 hinge, 14 latch member, 20 support plate, 26 slot.
Give every numeral a straight lead line ending inside the part outline;
lead lines must not cross. Black and white line art, white background,
no shading or grayscale, numerals clearly legible.
To fix a single numeral, scope the chat instruction so the other views stay untouched:
In FIG. 3, extend the lead line of numeral 26 so it ends inside the slot outline.
Keep every other numeral, part, and view unchanged, and regenerate FIG. 3 only.
FAQ
Do reference numerals have to be sequential?
No. Gapped and grouped numbering is fully acceptable, and it is the main defense against cascade renumbering. The rules require consistency and correspondence, not continuity.
What if a part is added mid-project?
With gaps in the sequence: assign a free number, add a register row, add a spec paragraph, and redraw or regenerate only the views that show the new part. Without gaps, a cascade renumber is unavoidable — and it must be followed by a full two-way audit of every figure and the entire spec.
Do different embodiments reuse the same numeral for the same part?
The same part keeps the same numeral. Corresponding parts in different embodiments conventionally take a prime mark or a shifted hundreds digit (12 and 112) to signal "corresponding but distinct."
Can software replace the manual audit?
It replaces the mechanical part: orphan numerals and figure/spec mismatches are found faster and more reliably by machine. What it cannot replace is the semantic judgment — a numeral that is consistent everywhere but attached to the wrong part only surfaces when you confirm each register row by hand.
Before your figures go out, run the numeral cross-check — it lists figure/spec mismatches directly instead of making you find them by hand.
Top comments (0)