Defining What a PCB Length-Matching Report Actually Measures

Two routes can display equal lengths while representing different electrical paths. A length report depends on its endpoints, included objects, and treatment of packages, vias, and series components. Establish those boundaries before adding tuning shapes to satisfy a number that may not correspond to the timing requirement.

Choose the quantity required by the interface

Altium’s xSignals documentation distinguishes routed length, package contributions, and propagation delay. It also describes layer-stack-dependent routing delay and separately defined pad or via delay information. Check the behavior of the tool version in use instead of assuming every length column includes the same objects.

Write the requirement in terms of the actual transmitting and receiving points. Identify whether it concerns absolute flight time, relative delay, differential skew, or another relationship. Do not convert a timing requirement into a length target without documenting the propagation assumptions.

Audit the reported path

1. Confirm endpoints and direction for every compared signal.
2. Check paths through series resistors or other intervening components.
3. Review branches and fly-by topology explicitly.
4. Identify included package and via contributions.
5. Verify layer assignments and the stackup used for delay calculations.

For example, one signal routed mainly on an outer layer and another mainly on an inner layer may need more than geometric equality. Likewise, a report stopping at a series resistor may omit the final segment to the receiver. The displayed values can be correct for their definitions while answering the wrong question.

Tune only after the definitions are stable

Review the topology and constraints before introducing meanders. Added length can affect spacing, coupling, reference continuity, and routing congestion. A successful numerical match does not independently demonstrate acceptable waveform quality or receiver timing margin.

Use simulation or other justified analysis when the interface requires it, and preserve the model assumptions. Keep package-delay information tied to the actual device and package rather than copying an unexplained value from another design.

Release the matching report with its endpoints, calculation basis, tool configuration, and applicable stackup. If a layer, package, series component, or topology changes, reassess the path before carrying forward the old tuning result.

The useful report makes clear what has been matched and why that quantity supports the interface requirement. This prevents engineers from spending time perfecting a geometric number while an omitted segment or inconsistent reference definition dominates the actual timing relationship.

Include an annotated path image for complex nets so another reviewer can verify the measured route without reconstructing the selection manually.