Design Patent Drawings: Views, Broken Lines and Review

US design patent drawings are not simply utility illustrations with cleaner lines. They disclose the appearance of the claimed design. The USPTO design patent application guide explains that the visual disclosure must be clear and complete, with sufficient views to disclose the appearance. This article is a preparation guide, not advice about the scope of a particular claim.

Decide what the drawing set must communicate

Before preparing views, separate the physical source object from the legal question of what is claimed. An illustrator can reproduce geometry; that does not automatically answer which portions should be included in the claim. Record unresolved scope decisions for professional review rather than allowing a drawing tool to make them silently.

For a synthetic desk-lamp housing, note the exterior surfaces, controls, openings and any components that appear only as context. Keep these notes tied to one source revision. This exercise does not imply that the lamp is new or eligible for a design patent.

Plan and compare the views

The USPTO guide discusses front, rear, side, top and bottom views and the usefulness of perspective views. The requirement is sufficient disclosure, not a universal promise that any fixed number of images is enough. Use the official guide for the applicable details and permissible omissions.

View-review question	What to compare
Does the silhouette match?	Outline and proportions across views
Do openings stay in the same place?	Position, shape and number
Does an edge appear consistently?	Curvature and transitions
Is a component missing from one view?	Source object and view purpose
Does the perspective fit the orthographic views?	Corners, planes and connections

Do not approve each image independently. Review the complete set side by side. An AI-generated image may look convincing in isolation while moving a control or changing the shape of a seam between views.

Treat broken lines and shading as review decisions

The USPTO guide explains uses of broken lines for unclaimed subject matter or environment and discusses surface shading. These are not merely decorative styles. Do not ask a tool to convert arbitrary features to dashed lines without a reviewed reason. Consult the design application guide for the full requirements.

Maintain a written legend during preparation: feature, intended treatment, reason, reviewer and unresolved question. This working document is a coordination aid; it is not proposed filing language. Confirm the final drawings and any required descriptions with the practitioner handling the application.

Prepare a useful brief for an illustrator

Provide the source revision, a proposed view list, clear images or models, and the unresolved questions. Ask how corrections are handled when one change affects several views. Request an explanation of the deliverables and whether editable files are included. Do not evaluate a quote solely on its price per image.

The service selection guide includes questions you can send with the brief. Use the cost worksheet to compare equivalent work rather than different scopes.

Where an AI preview fits

AI can be tested as a way to create review material. It should not be treated as proof that a coherent design-application set has been produced. CNIPA.AI's drawing page describes its current draft-generation workflow; this guide does not promise a human-reviewed design filing service or guaranteed acceptance.

Start with a nonconfidential object, compare every view against the same source, and document each change required. Do not upload a client's design or an unpublished invention to a service without authorization and a review of its data terms.