Patent flowchart symbols are standardized shapes that denote specific steps, decisions, inputs, and outputs in method claims, with consistent meaning required by patent offices to avoid ambiguity during examination and enforcement. Each shape has a defined, universally accepted use case for method figure notation.
Core Patent Flowchart Symbols and Their Standard Use Cases
Consistent use of flowchart shapes in patents ensures examiners, litigators, and licensees can interpret your method claims without confusion, no matter their jurisdiction. Below are the most common symbols and their official meanings:
- Process box (rectangle): The most common symbol, used for any action, operation, or step that transforms an input to an output. All active method steps that are not decisions or inputs/outputs fall into this category.
- Decision diamond (rhombus): Used exclusively for yes/no or multiple-choice branching points in your method. Every decision diamond process box must have at least two outgoing arrows labeled to show each possible flow path, such as “Yes” and “No” for binary decisions.
- Terminator (oval): Marks the start and end of your method flow. Every flowchart should have exactly one start terminator and at least one end terminator to clearly define the scope of the claimed method.
- Input/output (parallelogram): Used for steps that involve receiving data or material from an external source, or delivering a final output to a user or external system.
- Connector (circle): Used to link separate sections of a long flowchart that spans multiple pages or drawing sheets, with a matching letter or number inside each paired connector to avoid disconnection.
Step-by-Step Workflow for Using Patent Flowchart Symbols Correctly
Follow this structured workflow to ensure your symbols meet patent office requirements and align with your claim language:
- Map your full method sequence as a plain text outline first, separating actions, decisions, inputs, and end points to avoid misclassification later.
- Assign the correct symbol to each step, referencing the standard use cases above to ensure you are not using non-standard shapes for common steps.
- Label each symbol with clear, concise language that matches the exact wording used in your method claims to avoid discrepancies during examination.
- Add directional arrows between every connected symbol, with clear labels for all outgoing paths from decision diamonds to eliminate ambiguous flow.
- Add reference numbers next to each symbol that match the reference numbers in your patent specification to make cross-referencing simple for examiners.
AI-assisted patent drawing workspaces like PatentDraw can pre-populate standard patent flowchart symbols to reduce manual formatting errors, though any AI output is a working draft and requires human technical and professional review before submission to ensure alignment with your specific invention details.
Concrete Example of Correct Patent Flowchart Symbol Usage
To illustrate proper use, consider a patent application for a portable solar-powered phone charger method:
- Oval terminator: Labeled “Start” to mark the beginning of the claimed method.
- Process box (rectangle): Labeled “Capture solar energy via photovoltaic panel” to denote the active energy collection step.
- Process box (rectangle): Labeled “Convert captured DC energy to regulated 5V output” to denote the power conversion step.
- Decision diamond (rhombus): Labeled “Is connected device fully charged?” with two outgoing paths: “Yes” leading to the end terminator, and “No” leading back to the energy conversion step.
- Parallelogram input/output: Labeled “Deliver charging power to connected mobile device” to denote the output step.
- Oval terminator: Labeled “End” to mark the conclusion of the claimed method.
This example follows all standard rules for method figure notation, with clear, consistent symbols that align directly with the language of the associated method claims.
Common Mistakes to Avoid With Flowchart Shapes in Patents
Even small errors in symbol use can lead to office actions or delayed examination, so watch for these common missteps:
- Using rectangles for decision steps: Swapping the decision diamond process box use is one of the most frequent errors, and can lead examiners to misinterpret branching paths as standard active steps.
- Vague, non-specific labels: Labels that do not match your claim language can create gaps between your visual disclosure and your legal claims, which can be used to invalidate your patent during litigation.
- Unlabeled decision paths: Failing to label outgoing arrows from decision diamonds creates ambiguity about the order of operations, which often leads to a requirement for a corrected drawing submission.
- Using custom symbols without definition: If you use a non-standard shape for a specific step, you must explicitly define its meaning in your patent specification; failure to do so will result in a rejection for lack of clarity.
Frequently Asked Questions
Do USPTO patent drawings require standard flowchart symbols?
Yes, the USPTO requires consistent, standard symbol use for method flowcharts to avoid ambiguity during examination. You can use non-standard symbols only if you explicitly define them in your patent specification, but standard shapes are preferred to reduce examination delays.
Can I use custom flowchart shapes in my patent application?
Custom shapes are permitted only if you provide a clear, unambiguous definition of each custom shape in the detailed description section of your application. Note that relying on standard symbols reduces the risk of your method figures being rejected for lack of clarity.
How do I cross-reference flowchart symbols to my patent claims?
You can add parenthetical reference numbers next to each flowchart shape that match the reference numbers used in your method claims. This helps examiners and judges quickly connect the visual flow to the legal language of your claims, reducing the risk of misinterpretation during examination or enforcement.
Describe your invention and create a focused working draft in PatentDraw.
Create a drawing