Impedance targets across rigid and flexible regions

A shared impedance target does not automatically imply one trace geometry throughout a rigid-flex PCB. Review each region using its actual construction and reference arrangement, then examine the transition between regions. A rule that covers the rigid island alone is not a complete description of a route that continues through flex.

Altium’s controlled-impedance routing documentation describes impedance profiles, routing rules, and the selected stack or substack. The practical implication for a review is to connect each routed section to the intended profile and construction, rather than relying only on a net name.

Start with a route inventory

Choose one representative signal path and divide it into sections: launch, first rigid island, transition, flexible span, second transition, and destination. For each section, record the conductor layer and reference structure. Note where either changes. This inventory is an original review aid; it does not replace field solving or a channel analysis.

Work a tolerance example without inventing trace widths

Suppose a project specifies a differential impedance target of 100 ohms with an agreed tolerance of plus or minus 10 percent. The arithmetic interval is 90–110 ohms: 100 × 0.90 and 100 × 1.10. These are illustrative project inputs, not a universal requirement or a statement of our manufacturing capability.

The interval alone does not specify the test method, measurement location, or what a short transition is allowed to do. Add those decisions to the requirement. If two reviewers apply the same numbers to different measurements, they may reach different acceptance conclusions while both believe they followed the drawing.

Keep assumptions next to the result

For each calculation, save a compact input record: stack revision, material property source, conductor dimensions used in the model, dielectric spacing, reference arrangement, and relevant solver settings. If an input is provisional, mark it as provisional. A result reported to many decimal places does not remove uncertainty in its inputs.

When a fabricator proposes a geometry change, compare the proposal with the region register. Determine whether it affects only one span or also changes the boundary and launch. Ask the design owner to approve the updated construction and geometry together. A manufacturing concession should not silently become an electrical design change.

Distinguish the electrical target from the geometry instruction

Begin the review with a requirement statement that identifies the signal type, target, tolerance, region, and verification method. A differential pair and a single-ended trace are different structures, even when their drawings use similar terminology. State the intended mode explicitly. Do not leave the fabricator to infer it from two adjacent tracks or from an abbreviated net label.

The geometry instruction should then identify which dimensions the approved construction uses to meet that target. These can include conductor width, pair spacing, conductor thickness, and distance to the reference structure. Where the rigid and flexible constructions differ, keep separate geometry records. The purpose is not to force identical numbers into every region but to make the relationship between construction and electrical intent reviewable.

Specify who may propose changes and who approves them. If the manufacturing review indicates that a different width is needed, ask for the affected regional geometry and its supporting construction assumptions together. A change limited to a long uniform section may have a different review scope from one that also changes the approach to a pad, via, or rigid-to-flex boundary.

Map reference continuity before optimizing a trace width

Follow the intended reference conductor along the signal route. Mark every point where the reference layer changes, stops, contains an opening, or adopts a different pattern. Then compare that map with the signal-layer map. A cross-section calculation made for a uniform reference arrangement cannot describe every local interruption in that arrangement.

For the illustrative R1–F1–R2 route, imagine that the signal remains on a shared copper layer while the surrounding construction changes. This removes one kind of layer transition, but it does not establish that the reference geometry is unchanged. Ask the reviewer to identify the reference in each region and explain the boundary treatment. Keep that explanation beside the transition detail rather than burying it in a general stack note.

If a patterned reference is proposed for mechanical reasons, document the pattern as part of the electrical model assumptions. Do not reuse a result calculated for a continuous plane without evaluating the actual structure. The appropriate analysis method depends on the geometry and the question being answered; a simple cross-section calculation may be useful for a uniform section while an irregular transition requires a different model.

Use an input matrix to make sensitivity visible

Use the matrix to organize a sensitivity study rather than treating a single nominal answer as the whole design. Start from the proposed nominal construction, then vary inputs over their justified ranges using the chosen analysis tool. Record which assumptions produce the limiting results. A numerical sweep is only as meaningful as its input bounds; arbitrary ranges should be labelled exploratory, not manufacturing evidence.

A useful review question is whether the chosen nominal geometry leaves room for the expected variation. This does not imply that all geometric deviations are independent or that a worst-case combination will occur in production. Discuss the process assumptions with the fabricator and keep the acceptance requirement separate from any statistical prediction. Do not claim a yield percentage from an input sweep without a justified statistical model.

Interpret a measurement trace in context

Polar Instruments’ application note on impedance measurement areas discusses selecting the measurement portion of a TDR trace. This supports a practical documentation requirement: identify the measurement window and the features excluded from it. Otherwise, one report may characterize a uniform section while another includes a launch or termination disturbance.

Polar also explains in its TDR View note that DC trace resistance can contribute to a rising measured trace on fine conductors. A slope therefore needs interpretation in the context of the test method rather than an immediate conclusion that the local characteristic impedance increases by the same amount. Preserve the raw trace, measurement settings, and evaluation method with the reported value.

For a rigid-flex project, ask which construction the test coupon represents and where it is located relative to the production design. If the project has more than one relevant regional cross-section, identify how each will be verified. A coupon built to represent one stack should not silently stand in for all other stacks or for an assembled connector transition.

Review short transitions without inventing a universal allowance

A short local feature and a long uniform transmission-line section can influence a channel differently. Do not apply a broad fabrication tolerance to every point of a transition trace without defining the intended interpretation. Conversely, do not dismiss a transition solely because it is physically short. Its significance depends on the signal, geometry, and surrounding channel.

Create a transition review record containing the adjacent regional cross-sections, the local geometry, the analysis objective, and the result that will support acceptance. Where system validation is required, connect that record to the applicable interface test plan. A fabrication impedance report and an assembled-channel result are complementary evidence, not interchangeable certificates.

Resolve an out-of-range result through traceable questions

If a reported value falls outside the agreed interval, first verify the identification: board revision, coupon, stack, signal mode, and target. Then review the measurement setup and compare the fabricated cross-section with the approved assumptions. Keep the investigation structured so that a naming error, a test interpretation issue, and a construction discrepancy are not treated as the same problem.

Record the disposition explicitly. A retest, a revised geometry proposal, or a design concession should identify the evidence reviewed and the person responsible for acceptance. Preserve the original result rather than replacing it with an unexplained passing number. This makes future comparisons possible when a material, routing rule, or manufacturing process changes.

Separate evidence by the question it answers

• Calculation: Does the model support the chosen cross-section under its stated assumptions?
• Manufacturing inspection: Does the fabricated geometry meet the agreed dimensional requirements?
• Impedance measurement: Does the specified measurement meet its agreed acceptance interval?
• System validation: Does the assembled product satisfy its channel or interface requirements?

Keep these evidence records distinct in the release checklist. A single “impedance checked” box is ambiguous unless it names the method, location, revision, and result. If the project needs channel-level evidence, define that work separately instead of assuming a fabrication report establishes it.

Use our rigid-flex design guide with the stackup review guide. Submit your impedance requirements for project review with the proposed stack, target and tolerance, signal-layer map, and measurement expectations.