Pad numbers on a PCB drawing can make connector and package orientation much easier to review. They can also mislead when labels overlap, disappear at the chosen scale, or are interpreted from the wrong viewing side. Inspect the generated document as an operator or supplier will receive it.

Know how the labels were generated

KiCad 9’s plotting documentation provides controls for sketching pads on fabrication layers and including pad numbers. These are output choices, so labels visible in one review document need not appear in another generated format.

Record the selected layers, pad-label settings, scale, page size, and mirror/view convention. Distinguish native pad numbers from manually placed text. Manual labels require their own update discipline and can become stale after a footprint change. Where practical, generate identifying information from the reviewed native objects.

Inspect difficult locations deliberately

  • Check dense arrays where adjacent labels may overlap.
  • Verify repeated or alphanumeric pad identifiers remain legible.
  • Review bottom-side parts against an explicit viewing-direction note.
  • Confirm hidden body outlines do not conceal critical labels.
  • Inspect a printed or realistically scaled view of the final document.

Pair this review with the assembly-view convention. A perfectly legible pad number still causes trouble if the reader assumes a mating-face view while the drawing shows the board side. Use asymmetrical features to confirm the intended orientation.

Keep identification separate from electrical proof

For example, a two-row connector may display every pad label correctly, yet its schematic mapping can still be reversed. Use the labels to support the pin-map audit, comparing the actual component drawing and electrical intent. The generated drawing is evidence of what the CAD data says, not independent proof that the library is correct.

If labels are unreadable, provide a local detail view or a separate pin table linked to the reference designator. Avoid enlarging the entire document until other essential information leaves the page. Keep the detail’s side and scale explicit so a copied view cannot lose its interpretation.

After correcting labels or views, regenerate the release from the same board revision and recheck critical packages. Retain the export preset with the document. This small review reduces assembly questions while preventing a convenient visualization from acquiring more authority than its underlying data deserves.

Move from reading to a build-ready project

Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.

Open the DFM checklist