Heavy Copper PCB Lead Time: How to Turn a Quoted Date Into a Commitment You Can Hold

Every heavy copper quotation you receive carries a lead time. Most of them carry nothing else — a number of working days, no start point, no scope, no conditions. Two suppliers can quote the same number and mean entirely different things, and you will only discover the difference in the week the shipment was supposed to leave.

This is not a problem you solve by asking for a shorter number. It is a problem you solve by asking what the number is attached to.

A quoted lead time is an answer to a question nobody asked out loud

When a supplier writes a lead time on a quotation, they are silently answering six questions at once. You did not ask any of them, so they answered with whatever assumption makes their number look reasonable.

• When does the clock start? At PO receipt, at file receipt, or at the moment every open engineering question has been closed? These are three different dates, and on a heavy copper job the gap between them is where most schedule disputes begin.
• Which revision is it based on? A lead time quoted against rev B does not survive your rev C, even when the change looks small to you.
• Which build does it cover? Copper weight, layer count and the lamination structure that follows from them all change the internal routing of the job. A number quoted against a simplified assumption is not a number quoted against your board.
• What is inside the scope? Surface finish, impedance verification, electrical test fixture fabrication and any outsourced step may or may not be counted inside the quoted window.
• Is it a capacity statement or a schedule statement? "We can build this" and "we have a slot for this in the week you need" are different claims. Only one of them is a commitment.
• What is allowed to move it? If no reschedule trigger is defined, every delay becomes a negotiation after the fact, with no agreed basis.

A supplier who answers all six in writing may quote a longer lead time than one who answers none. The longer number is usually the one that holds.

Define the start point before you compare anything

Lead time comparison is meaningless until the start point is identical across quotations. Ask each supplier to state the start point explicitly using one of three definitions, and ask them to use the same one.

PO receipt. The clock starts when the purchase order lands. This is the most favourable definition for the buyer and the least realistic one, because engineering clarification almost always happens after the PO. Suppliers who accept it usually protect themselves with a reschedule clause instead.

Complete file receipt. The clock starts when the full data package has arrived: fabrication drawing, Gerber or ODB++ data, drill data, stackup intent, copper weight per layer, impedance requirements if any, test requirement, and the acceptance criteria you expect to be measured against. "Complete" has to be defined as a list, otherwise it is just another word for "later".

Clarification closed. The clock starts when the supplier's DFM queries and declared exceptions have been answered and the build is frozen. This is the definition that most accurately reflects how a heavy copper job actually runs, and the one most likely to produce a date that holds. Its cost to you is visibility: you have to track clarification turnaround as a separate metric, because it is now outside the quoted window.

Whichever definition you adopt, make the clarification loop itself subject to a response obligation on both sides. A schedule that starts when clarification closes, with no obligation on how fast clarification moves, is an open-ended schedule wearing a number.

Break the window into milestones with an owner each

A single lead time figure cannot be managed. A milestone list can. Ask the supplier to split the quoted window into segments and to name who owns each one. You are not asking for their internal process times — you are asking for a structure you can status against.

A workable segmentation for a heavy copper job looks like this:

Two things matter more than the segment names. First, any step performed outside the supplier's own plant must be identified as such, because that is where a schedule loses its elasticity — you cannot expedite a queue you are not in. Second, each segment should have a status you can ask for by name. "Where is my order" invites a reassuring answer. "Has engineering release closed against rev C" invites a factual one.

Capacity commitment and schedule commitment are not the same purchase

Suppliers answer capacity questions readily and schedule questions reluctantly, because capacity is a statement about the plant and schedule is a statement about their other customers. You need the second one.

Ask for capacity evidence in a form that does not require you to trust an adjective:

• Confirmation that the declared build — copper weight, layer count, finished thickness, panel size — is inside the processes they run in-house, with any step that is outsourced named.
• Confirmation that the quoted lead time was produced against your declared build and revision, not against a generic assumption.
• A statement of which production window the order has been allocated to, and whether that allocation is reserved or conditional.
• The named contact who owns the schedule, and the escalation path above that contact.

Then ask the schedule question separately: if the PO is placed on a given date against a frozen build, what is the committed ship date, and what has to be true for it to hold? A supplier who can answer that in writing is quoting a schedule. A supplier who returns to describing their equipment is quoting capacity and letting you infer the rest.

Resist the temptation to accept production photographs, equipment lists or certificate scans in place of either answer. They are evidence of capability. Neither one is evidence that your order has a slot.

Write the reschedule rule before you need it

The clause that saves a programme is not the lead time. It is the one that says what happens when the lead time is at risk. Without it, the first delay arrives as a surprise and is resolved by whoever argues better.

Define the triggers that legitimately move the date, and agree them in advance:

• Buyer-side revision. Any change to the data package after engineering release moves the date, and the supplier states the new date before the change is accepted. This protects both sides: you find out what the change costs in schedule terms while you can still decline it.
• Unanswered clarification. If a DFM query stays open past the agreed response window, the clock pauses. Name the window.
• Declared exception rejected. If the supplier raised an exception and you reject it, the build changes and the date is requoted.
• Outsourced step disruption. Named in advance as a specific risk, with a notification obligation attached, so it cannot be used retroactively as a generic excuse.
• Rework after test. Agree whether a failed lot triggers a requote of the date or consumes buffer, and who decides.

Attach a notification obligation to all of them: the supplier informs you within a defined period of becoming aware of a risk to the date, with the new expected date and the reason. The value of this clause is not that it prevents delay. It is that it converts delay from something you discover into something you are told, early enough to act on.

Clause language you can put in the PO

The following structure is intentionally free of numbers — every bracketed value is something you and your supplier fill in together, and a supplier who will not fill them in has told you something useful.

> Lead time basis. The committed ship date is [date], based on data package revision [rev] received on [date] and on the build declared in the fabrication specification of the same revision, including copper weight per layer, layer count, finished thickness and surface finish as stated there.

>

> Start point. The lead time clock starts on [PO receipt / complete file receipt / closure of all DFM clarifications], defined as [definition]. Items required for the package to be considered complete are listed in [reference].

>

> Scope. The quoted window includes [surface finish / electrical test / fixture fabrication / impedance verification / packing]. Steps performed outside the supplier's own facility are: [list]. Steps excluded from the window are: [list].

>

> Milestones. The supplier will report status against the following segments on request: [segment list]. Each report states the segment, its state, and the revision it is executing against.

>

> Reschedule triggers. The committed date may be revised only on the following events: [trigger list]. In each case the supplier states a new committed date in writing before work continues.

>

> Notification. The supplier notifies the buyer within [period] of becoming aware of any risk to the committed date, stating the cause, the affected segment and the revised expected date.

>

> Escalation. Schedule owner: [name/role]. Escalation contact: [name/role].

Deliberately absent: penalty amounts and liquidated damages. They belong in the commercial terms, not in the schedule definition, and arguing about them early tends to stop suppliers from answering the questions that actually protect your date.

What the quoted number looks like once you have done this

You will usually end up with a longer number than you started with, split into named segments, tied to one frozen revision, with two or three conditions written on it. That is not a worse offer. It is the same offer with its assumptions made visible, which is the only form in which two quotations can be compared at all.

The supplier who gives you this structure is also the supplier who will call you in week two rather than week six. That behaviour, not the number, is what you were trying to buy.

Buyer self-check before you compare quotations

• [ ] Every supplier quoted against the same revision, and you know which revision that is.
• [ ] The start point is stated in words, not implied, and it is the same definition across all quotations.
• [ ] You know what is inside the quoted window and what is outside it, including every outsourced step by name.
• [ ] The window is split into segments you can status against, each with an owner.
• [ ] You have a schedule commitment, not only a capacity statement, and you can tell which one you received.
• [ ] Reschedule triggers are listed and agreed before the PO, including the ones that are your own fault.
• [ ] A notification obligation exists with a defined response period and a named schedule owner.
• [ ] You have not accepted equipment photographs or certificates as evidence that your order has a production slot.

Related reading

• Heavy copper PCB quote comparison and cost drivers — what the price side of the same quotation is actually made of.
• Heavy copper PCB purchase specification and acceptance — how to write the specification that the lead time gets quoted against.
• Order quantity, panel plan and price breaks — why quantity changes both the price and the production window.
• Repeat order change control terms — the clause set that keeps reorders from silently becoming new jobs.
• Prototype to production transfer — when the schedule basis changes as the build moves into volume.
• Making the fabrication specification sheet binding on the quote — the mechanism that ties a date to one frozen revision.
• Heavy copper PCB capability overview and request a quote — to state a declared build and ask for a schedule commitment against it.

---

FAQ

Is a shorter quoted lead time ever the better offer?

Only when both quotations define the same start point, the same scope and the same revision. Until then you are comparing a number against a different number's assumptions. In practice the shortest quote in a set is often the one that excluded the most from its window.

The supplier quotes from "file receipt". Is that acceptable?

It is, provided "complete file" is defined as an explicit list and the clarification loop carries a response obligation on both sides. Without those two things, "file receipt" quietly becomes "whenever we are satisfied", and the date floats.

What is the difference between a capacity confirmation and a schedule commitment?

Capacity confirmation says the declared build is inside the processes the supplier runs, with outsourced steps named. A schedule commitment says your specific order has been allocated to a production window and states the committed ship date and its conditions. Suppliers answer the first readily. You have to ask for the second separately.

We changed one copper weight on one layer after release. Does the date move?

Treat it as a revision and ask for a restated date before the change is accepted, even if it looks minor. A change in copper weight can change the lamination structure and the internal routing of the job, so the honest answer is that only the supplier can say — and the point of the clause is that they say it before, not after.

Should we write penalties into the schedule clause?

Keep them in the commercial terms. Raising them inside the schedule definition tends to make suppliers defensive and vaguer about the start point, scope and triggers, which are the parts that actually protect your date.

How much buffer should we add on top of the committed date?

Add buffer to your own programme, not to the supplier's number, and keep the two visible separately. Padding the requested date hides the real requirement and makes the supplier's own planning worse. State the real need-by date and hold your buffer on your side.

Can we get a committed date before engineering release?

You can get an indicative date. A committed date before the build is frozen is a guess with a signature on it, and both sides know it. The useful version is an indicative date plus an agreed point at which it becomes committed.