Controlled Impedance on an HDI Quote: Who Owns the Target Number

Why "controlled impedance" is not a requirement

Open any HDI quote request you have sent in the last year and find the impedance line. There is a good chance it reads "controlled impedance" or "impedance control required," possibly with a tolerance beside it. That line feels like a specification. On a contract it behaves like a topic heading.

The reason is structural, not linguistic. A finished trace impedance is produced jointly. You supply trace width, spacing, reference plane assignment and the layer where each net lives. The fab supplies the material it can actually source, the copper weights it will press, the dielectric thicknesses available in that construction, and the etch compensation its own line requires. Neither side alone determines the number that a test probe will read.

So when you write "controlled impedance," you have named a shared output without naming who is accountable for it. The practical consequence shows up at exactly one moment: the fab measures the coupon, the reading sits outside the window, and someone has to decide what changes. If the stackup was yours, the fix is a design change and the rebuild is arguably your cost. If the stackup was theirs, the fix is a construction change and the rebuild is arguably theirs. Both readings of the same two-word phrase are available, which is why the phrase settles nothing.

A requirement that can be accepted or rejected needs four things attached: a target value, who authored it, what construction it was authored against, and how conformance will be shown. "Controlled impedance" carries none of the four.

Two authorities: customer-specified stackup versus fab-proposed stackup

Almost every HDI order resolves into one of two authority models. Choosing deliberately is more important than which one you choose.

You specify the stackup. You issue a layer-by-layer construction with dielectric materials, thicknesses, copper weights and the trace geometry that goes with it. You have modelled the impedance yourself, or your design service has. The fab's obligation becomes: build to this construction, substitute nothing without approval, and report what the coupon measures. If the reading misses, the fab has met its obligation by building what you specified — the target was yours, and so is the redesign.

This model is appropriate when your design is impedance-critical in ways the fab cannot see, when you are qualifying a second source against an existing construction (the broader evidence set for that case is covered in HDI PCB second source build equivalence qualification), or when the same stackup has to be reproducible across suppliers. The cost is that you now carry the modelling risk, and you must be prepared to receive boards that match your drawing and still miss your number.

The fab proposes the stackup. You issue target impedance values, the trace geometry you would prefer, and your constraints: layer count, finished thickness ceiling, any material class you require. The fab returns a construction that it believes meets those targets on its own process, possibly adjusting dielectric thicknesses or trace widths to get there. Now the target is yours and the construction is theirs. If the coupon misses, the construction was theirs to get right.

This model is appropriate for most buyers most of the time, because the fab holds the one input you cannot model: its own line's real behaviour. The cost is that you must approve the returned construction before build, and that approval is the moment the authority can quietly transfer back to you if the paperwork is careless.

The failure mode to watch for is the hybrid that nobody declared. You send a stackup "for reference," the fab adjusts it to something buildable, nobody signs the adjusted version, and the boards get made. Both parties now believe the other authored the construction.

Three impedance wordings on a quote, and what each one binds

These three lines appear on quotes constantly. They look like variations in phrasing. They are different contracts.

"Controlled impedance per customer stackup." The fab has agreed to build your construction and has priced the handling that controlled-impedance work requires. It has not agreed that your construction produces your target. If you never stated a target, there is nothing to miss and nothing to claim. If you stated one, read carefully whether the fab accepted it or merely received it.

"Controlled impedance per fab recommended stackup." The fab has agreed to produce a construction aimed at your targets. This is the stronger position for a buyer, but only if two conditions hold: your targets are written somewhere the quote references, and the recommended construction is returned to you and approved before build. Without the first, "recommended" is aimed at nothing. Without the second, you cannot later show which construction was the agreed one.

"Impedance controlled, tolerance ±X%." A tolerance without an authored target and a named construction is the weakest of the three, despite looking like the most precise. A tolerance is a window around a number. If the number's authorship is unsettled, the window is unenforceable — you will be arguing about the centre, not the width.

Price rarely separates these three at quote stage, which is why they are easy to accept without reading. The separation appears when a reading misses, and by then the wording is fixed.

Deviation ownership: etch compensation, material lot variation, lamination movement

When a coupon reads outside the window, the cause usually falls into one of three buckets. Each has a natural owner, and your document should confirm the natural owner rather than leave it to be argued.

Etch compensation. The trace width on the finished board differs from the width in your artwork, because the etch process removes copper from the sides as well as the top. Fabs compensate by adjusting the artwork before imaging. How much they adjust is a property of their line, their copper weight and their resist. This belongs to the fab in both authority models. Even when you specified the stackup, you specified a finished geometry; getting the imaged geometry to land on it is the fab's process knowledge. Your document should say your widths are finished-dimension targets, not artwork dimensions — that one sentence prevents a whole class of dispute.

Material lot variation. Dielectric constant varies between lots of the same material within the supplier's published range. Under a fab-proposed stackup, the fab chose the material and should be building with enough margin to absorb normal lot spread; a miss caused by ordinary variation is theirs. Under a customer-specified stackup, if you fixed both the material and every thickness, you removed the fab's margin and you own the result — which is why the material class you name matters as much as the target, a decision covered in HDI base material declaration for RFQ. Note the asymmetry: specifying a stackup transfers more risk to you than most buyers realise, because it closes the fab's compensation options.

Lamination movement. Dielectric layers compress and resin flows during press, so the as-built thickness between a trace and its reference plane is not exactly the pre-press thickness. This is fab process behaviour in both models. The exception worth naming is the asymmetric construction you insisted on against the fab's written advice — if the fab flagged a construction as movement-prone and you directed it anyway, that advice becomes part of the record.

What makes these three worth writing down is that none of them is a defect. All three are normal process behaviour operating inside published ranges. A dispute about them is not a dispute about workmanship; it is a dispute about whose margin was supposed to absorb them. That question has no default answer.

Coupons and reports: no requirement means no evidence

Impedance on a finished board is not measurable by looking at it, and in most cases it is not practically measurable on the product itself after delivery. Conformance is demonstrated on test coupons built on the same panel, in the same press cycle, with the same geometry as the controlled nets. If you did not require coupons, you did not require evidence.

This is the single most common gap in buyer-side impedance paperwork, and it is quiet. The order does not fail. The boards arrive. Nothing seems missing until a signal integrity problem appears months later and you ask for the impedance report that nobody was ever asked to produce.

Four decisions belong in your document, and none of them are defaults:

Coupons required or not. State it affirmatively. Coupons consume panel area, so they have a cost, and a fab quoting against a thin spec may reasonably leave them out. If you want them, say so at RFQ, not after the quote is accepted.

Which nets the coupons represent. A coupon structure represents one geometry on one layer pair. A board with several distinct controlled-impedance configurations needs the coupon set to cover the ones you care about, and you have to say which those are. Assuming "all of them" is how coupon area turns into an unexpected cost conversation.

Report delivery and timing. A report that exists in the fab's file but does not ship with the lot is not available to you when you need to make a ship-or-hold decision. State that the report accompanies the delivery and identifies the lot it belongs to.

What happens on a miss. This is the decision most orders omit. If a coupon reads outside the window, does the fab hold the lot and notify you, ship with the measured data disclosed, or scrap and rebuild on its own judgement? All three happen in practice. Only one of them matches what you would have chosen. Name it in advance, because the moment of the miss is a schedule-pressure moment and the default behaviour will be whatever is fastest.

For buyers whose impedance requirements sit alongside other acceptance evidence, it is worth placing these four decisions in the same document as the rest of the specification rather than in an email thread. Our HDI PCB quote package checklist covers what the complete package looks like; this article is the expansion of one line inside it, and writing a fabrication specification sheet that binds the quote covers how such a sheet acquires contractual force in the first place.

When several impedance networks coexist, declare the priority

Dense HDI designs rarely have one controlled impedance. A board can carry single-ended nets at one target, differential pairs at another, and a third configuration on a different layer pair, all in the same construction.

Here is the part buyers miss: these targets compete. A dielectric thickness change that moves a single-ended net toward its target moves the differential pair on the adjacent layer as well, and not necessarily in the direction you want. A trace width change to fix one network may violate the spacing the other network needs. The fab, holding your list of targets and one construction to build, will resolve those conflicts. It will resolve them with whatever information you gave it, and if you gave it no priority order, it will resolve them by its own judgement about which nets matter.

That judgement may be perfectly sound. It is still your call, and it is cheap to make explicitly:

Rank your controlled networks. Say which one is hard-constrained and which ones may be traded. If a high-speed interface drives the design and a slower bus can tolerate more spread, write that. If one network can be dropped from control entirely under pressure, write that too. The fab cannot infer your system's sensitivities from a table of numbers.

The hidden benefit of ranking is that it surfaces impossible requirement sets at RFQ instead of at first article. A fab reviewing a ranked list can tell you that targets two and four cannot both be hit in the layer count you asked for. A fab reviewing an unranked list has no basis to raise it, so it quotes, builds, and discovers the conflict with your money in the panel. If this exposes a construction problem rather than an impedance problem, the question becomes which construction decisions were yours to make — covered in HDI PCB build class: which specification decisions are yours.

Required fields for the impedance line in your RFQ

The impedance line in an RFQ needs seven fields. Each one closes a specific argument that happens without it.

1. Authority model. State plainly whether the stackup is customer-specified or fab-proposed. One sentence. This field alone determines where most deviation disputes land.

2. Target values and who authored them. List each controlled network with its target. Then state whether those targets are your requirement that the fab must meet, or your preference that the fab should evaluate. Those are different things and they are routinely written identically.

3. Tolerance, with its basis. If you state a window, state what it is a window around and who owns the centre. A tolerance attached to an unauthored target is decoration.

4. Finished-dimension declaration. State that your trace widths and spacings are finished dimensions and that etch compensation is the fab's to apply. This is the field that prevents a fab from building your artwork literally and a buyer from claiming the fab should have known better.

5. Construction approval gate. If the stackup is fab-proposed, state that the proposed construction must be returned and approved before build, and that the approved version is the one the order references. Without this, nobody can later identify which construction was agreed.

6. Coupon and report requirements. Coupons yes or no, which networks they represent, report delivered with the lot, and the disposition rule on a miss.

7. Priority order across networks. Ranked, with any network that may be traded identified as such.

Seven fields is a short paragraph, not a document. Compare the effort of writing it to the effort of arguing about a rebuild after the panels exist, and the arithmetic is not close. If you want these fields evaluated against a specific construction before you commit, send them with your HDI PCB enquiry — the page lists the construction options available to quote, which are selectable ranges rather than a commitment for any particular build, and a quote request that carries the seven fields gets a reply that can actually be compared against another supplier's.

FAQ

Is "controlled impedance ±10%" a sufficient specification?

Not on its own. The tolerance tells the fab how wide the acceptance window is, but not what the window is centred on, who authored the centre, or against which construction it was authored. If the target's authorship is unsettled, a tolerance has nothing to attach to. Add the authority model and the target list, and the tolerance becomes enforceable.

If I send a stackup, does the fab still carry any impedance responsibility?

It carries process responsibility, not outcome responsibility. The fab remains responsible for building the construction you specified, applying appropriate etch compensation to land on your finished dimensions, and reporting what the coupon measures. It does not become responsible for your target being achievable in that construction. If you want outcome responsibility on the fab side, you need the fab-proposed model, which means giving it latitude to change thicknesses or geometry to get there.

Who pays for the rebuild when a coupon reads out of tolerance?

It follows the authority model, which is why the model has to be declared before build rather than argued after. Under a fab-proposed stackup that the fab warranted against your targets, a miss caused by the construction is the fab's. Under a customer-specified stackup built as drawn, a miss is a design change and the cost conversation starts on your side. The ambiguous case — a construction you sent that the fab silently adjusted — is the expensive one, and it is prevented by an approval gate, not by a clause.

Do I need impedance coupons on a prototype order?

You need them more on a prototype than in production, because the prototype is where you learn whether your targets and the construction are compatible. Skipping coupons on a prototype means carrying an unverified assumption into volume, where the panel count makes the same discovery much more expensive. If coupon area is the concern, limit the coupon set to your highest-priority networks rather than dropping coupons entirely.

Can the fab change my stackup to hit my impedance targets?

Only if you said it may. That permission is exactly what the authority model declares. If you want the fab to optimise toward your targets, say the construction is fab-proposed and that substitutions and thickness adjustments are permitted subject to your approval of the returned construction. If you need the construction held exactly — for second-source equivalence, for example — say customer-specified and accept that the target becomes yours to make work.

What if my design has impedance targets that conflict with each other?

That is common in dense HDI and it is better discovered at RFQ. Send the targets ranked by priority with any tradeable networks marked. A fab reviewing a ranked set can tell you before quoting that two of your targets are mutually exclusive in the layer count you asked for. An unranked set gives it no basis to raise the conflict, so the conflict surfaces during build instead.

Sources: Controlled-impedance acceptance practice, test coupon construction and impedance reporting conventions are defined by the publicly available printed-board performance and qualification standards, and by each material supplier's published dielectric property documentation. This article deliberately cites no numeric impedance tolerances, dielectric constant values, etch compensation amounts or test frequencies — those belong to the standards and to the material and fabricator documentation, and should be referenced directly in your contract rather than restated from a third party. PCB168 makes no claim here regarding its own test equipment, measurement capability, certifications, lead times, yields or capacity. The only PCB168 information referenced is the construction options published on the HDI PCB page, which are selectable quoting ranges and not a committed value for any particular build.

---