PCB fabrication · Assembly · Engineering supportStan@4PCBA.COM
Artist 3D · Engineering & manufacturing

PCB Net Classes: Turning Electrical Requirements into Layout Rules

Translate electrical requirements into PCB net classes, verify effective rule scope and priority, control exceptions, and retain release evidence.

Discuss your project ↗

A net class is useful only when its membership and rules reflect a real electrical requirement. Giving several signals a name such as FAST or POWER does not prove that their routing is suitable. The class may select a convenient routing width while leaving a different minimum in the design-rule checker. A rule may target the wrong objects, or a later exception may override the intended constraint.

This guide develops a review process for translating requirements into layout constraints, checking their effective behavior, and retaining evidence at release. It complements the broader PCB design workflow. The objective is a traceable decision: which requirement led to this rule, which connections it covers, how it is enforced, and who approved any departure.

Start with a requirement register, not a class-name list

Before configuring the CAD project, list the connections that need special treatment. For each group, record the functional reason, the source of the requirement, the affected pins or nets, and the acceptance method. A current-carrying connection, a timing-sensitive bus, and a noise-sensitive analog input can require different checks even when their nominal routing widths happen to match.

Separate a measured or specified limit from a preferred design target. A target leaves room for a controlled tradeoff; a hard limit defines a rejection condition. Also distinguish electrical constraints from fabrication limits. A manufacturer’s minimum track width establishes a production boundary. It does not establish acceptable temperature rise, voltage drop, characteristic impedance, or noise coupling for a particular circuit.

Assign an owner to every requirement whose value is still unresolved. For example, the layout engineer should not silently invent a pair spacing because the interface owner has not supplied a stackup-dependent impedance target. Record the missing input and the temporary assumption. A visible unresolved item is easier to manage than a plausible number that later looks like an approved requirement.

Define membership so another engineer can reproduce it

Class membership deserves its own review. Naming patterns are convenient, but schematic changes can introduce a connection that no longer matches the pattern. Conversely, a broad wildcard can capture a test signal or control net that happens to share a prefix. Compare the resulting member list with the intended pin-to-pin connections, rather than reviewing the class name alone.

Consider a fictional controller with a sensor interface and a separate diagnostic connector. Both contain nets beginning with SENSOR, but only the acquisition path requires a tightly controlled analog environment. A name-based rule that includes the diagnostic connector could create needless restrictions. A rule that misses one renamed acquisition net could leave the important connection unconstrained. Neither problem is visible from a tidy class list.

Keep membership evidence in a form that survives review: an exported list, a report, or a clearly captured rule query and its selected objects. Repeat the membership check after schematic synchronization. Also check power nets, intentionally unconnected pins, and connector branches separately. A class can be internally consistent while still describing an incomplete electrical path.

Distinguish routing preferences from enforced limits

The KiCad 9.0 PCB Editor manual provides a useful version-specific example: a net class’s optimal track width supplies a routing default, rather than a minimum or maximum DRC limit. Width enforcement depends on board constraints or applicable custom rules. The documentation also describes a constraints-resolution tool for examining the rules affecting an object. Confirm behavior in the installed version before adopting this example.

The practical implication is that seeing the expected width in a routing toolbar is insufficient evidence. Choose a representative segment from each important group and inspect its effective limits. Check an existing routed segment as well as a newly placed one. An inherited board can retain geometry created under earlier settings, so a new routing preference does not automatically repair the old copper.

Use separate fields in the requirement register for preferred value, minimum, maximum, and allowed local exception. If a parameter has no meaningful maximum, say so instead of inventing one merely to fill a table. If a rule cannot express the complete requirement, identify the additional review or analysis that will provide acceptance evidence.

Review scope and priority together

A rule’s value can be correct while its scope is wrong. Ask whether it applies to tracks, pads, vias, pairs, regions, layers, or relationships between two objects. Then inspect overlaps. A general clearance rule and a special connector-area rule may both appear reasonable in isolation, but their interaction determines which geometry is actually accepted.

Altium’s rule-scoping documentation explains priority when multiple rules of the same type apply: lower priority numbers rank higher. It also identifies exceptions, including multiple applicable Matched Lengths rules. Therefore, do not assume that every CAD check follows a universal one-rule-wins model. Inspect the effective rule behavior for the specific constraint type and software configuration.

A useful review order is broad production limits first, functional groups second, and narrowly justified exceptions last. This is a review sequence, not a universal software priority prescription. The final priority arrangement must match the tool’s semantics. Give every exception a reason that is understandable without remembering the meeting in which it was introduced.

Use a controlled example to test enforcement

Suppose a fictional project specifies a preferred routing width of 0.50 mm and a minimum of 0.30 mm for a selected group. These are illustrative numbers, not current-capacity or fabrication recommendations. A reviewer wants to prove that selecting the class has not merely changed the preferred router width while leaving the minimum unenforced.

In a disposable copy of the project, create or modify a short representative segment to 0.25 mm. Run the appropriate rule check and examine the reported object, rule, and limit. If the expected failure does not appear, investigate membership, scope, rule activation, priority, and the distinction between a preference and a constraint. Do not immediately lower the requirement to make the report look correct.

Then restore compliant geometry and rerun the check. Retain both results as a small validation record, including the project revision and tool version. Never release the deliberately defective test copy. This exercise validates that a particular check catches a particular violation; it does not establish that every electrical requirement has been modeled or that the design is generally safe.

Treat local exceptions as engineering decisions

A narrow escape near a package may need different geometry from a long trace. That does not justify weakening the rule for the entire net. First determine why the exception is needed, what physical length or region it covers, and which performance or manufacturing concern changes there. Ask whether a different footprint, layer transition, or placement can remove the exception.

Record the approved exception with its affected objects, rationale, reviewer, and acceptance evidence. Where practical, express it as a narrow rule whose scope can be inspected. If the tool uses an exclusion or waiver instead, preserve the associated explanation and review it whenever the affected layout changes. A historical waiver is not permanent permission for new geometry.

For the fictional width example, a local reduction might be accepted only after evaluating its specific electrical and production consequences. Do not claim that a short segment is automatically harmless. Its location, surrounding copper, current waveform, and connection geometry still matter. The rule database should document the approved conclusion, not replace the analysis that supports it.

Recognize requirements that a net class cannot prove

A class label does not demonstrate a continuous return path, suitable reference-plane transitions, or acceptable coupling to a nearby switching node. Similarly, equal geometric lengths do not necessarily establish equal propagation delay when routes use different layers or structures. Keep the distinction between what a geometric check measures and what the circuit actually requires.

Build a release matrix with one acceptance method per requirement. Some items can be checked directly by DRC. Others need stackup review, simulation, a pin-to-pin routing inspection, or a prototype measurement plan. Marking these additional checks explicitly prevents the phrase DRC clean from becoming a substitute for engineering judgment.

For procurement and manufacturing handoff, include only requirements that the recipient needs to act on, with clear acceptance criteria. The fabrication DFM checklist helps organize the production review. Internal CAD class names should not be the sole way a fabricator discovers an impedance requirement, a special clearance, or a controlled construction detail.

Make the release evidence easy to audit

Freeze the schematic, board, constraint files, and manufacturing outputs as one identifiable revision. Save the rule-check report and a short list of reviewed exceptions. Include the software version and relevant rule configuration. If a reviewer cannot connect the report to the delivered board revision, the report offers much less assurance than its clean result suggests.

After any late engineering change, identify which requirements and classes are affected. A connector rename can alter membership; a layer change can alter the physical meaning of geometry; a new exception can alter rule resolution. Rerun the affected checks and the final whole-board check, then update the release evidence rather than attaching the earlier report unchanged.

  • Every special class has an identified electrical or production purpose.
  • The actual member list matches the intended connections after synchronization.
  • Preferred values and enforced limits are recorded separately.
  • Representative objects show the intended effective rules.
  • Overlapping scopes and priorities have been reviewed.
  • Intentional violations were tested only in a disposable project copy.
  • Each exception has a bounded scope, rationale, owner, and evidence.
  • Non-DRC requirements have separate acceptance methods.
  • The final report and manufacturing files belong to the same revision.

When preparing a prototype PCB fabrication package, submit the construction information and manufacturing requirements alongside the exported files. If a constraint remains uncertain, identify it explicitly before ordering. You can discuss the board requirements with the project team, email Stan@4PCBA.COM, or use WhatsApp at +86 185 7700 2040. A traceable constraint set makes that discussion more useful than a list of unexplained CAD settings.

WhatsApp ↗