Heavy Copper PCB Manufacturers: Who Approves a Mid-Production Deviation

The call that stops the line is an authority problem, not a technical one

Picture a live order. The panels are somewhere in the middle of the process. Your supplier sends a message, usually through whoever you have been talking to since the quote: one copper layer is measuring outside the figure on the drawing, or the solder mask will not hold the thickness the drawing calls for where it climbs the step of a thick copper feature, or a routed outline on part of the lot is running outside the profile tolerance. They want to know whether to proceed, rework, or scrap.

Most buyers treat this as a technical question and answer it as one. You look at the drawing, think about the application, decide you can live with it or you cannot, and reply.

Then nothing happens. Or something happens that nobody agreed to.

The reason is that your reply went to a person whose job is commercial, and the decision you just made has to be entered into the supplier's internal system by someone with the authority to accept a deviation from a released document. Your contact may well have forwarded it. They may also have simply replied "OK, noted" and left it sitting, because in their organization an accepted deviation requires a signature they do not hold. Meanwhile the panels are either waiting, or moving under the original instruction, or moving under an informal verbal instruction that will not exist when the lot is inspected.

This is the structural fact worth internalizing: on the supplier side, the person who talks to you and the person who can approve a departure from the drawing are usually not the same person, and the second one is usually not reachable by you. Everything in this article follows from that.

Why heavy copper produces this situation more often than thin boards

Thick copper does not create a new category of dispute. It makes the existing one routine, for reasons that are mechanical rather than contractual.

Thick copper etches with a profile, not an edge. When you remove a lot of copper, the sidewall of what remains is not vertical. Line width at the top and line width at the bottom differ, and which one the drawing meant becomes a live question partway through the job rather than at design review. A query about "which dimension are we holding" therefore arrives mid-process, with material already committed.

Mask over a step is a geometry problem. Solder mask has to cover a much taller feature on heavy copper than on thin, and the places it struggles are the flanks of conductors and the knee where a conductor meets the laminate. Coverage that was drawn as a uniform figure becomes a question of "what can actually be achieved here," and the answer is often available only after the first panels are coated.

Fabrication is slower and material is expensive, so scrapping is a real decision. On a thin-board order with short cycle time, a marginal lot is often simply remade and nobody escalates. Heavy copper consumes more material, more plating time and more process hours per panel, which means the supplier has a strong incentive to ask rather than scrap, and the buyer has a strong incentive to think rather than reject. Asking is exactly what generates the authority problem.

Mechanical operations on thick copper have less margin. Routing, drilling and any secondary machining behave differently against a lot of copper, so dimensional and edge-condition questions are more likely to surface on part of a lot rather than uniformly.

None of this is anyone's fault, and none of it is avoidable by specifying harder. It simply means that an order for heavy copper boards should be planned on the assumption that at least one decision requiring someone's signature will come up while the job is in process. If you only discover your supplier's approval structure at that moment, you will spend the schedule learning it.

Four roles, and which of them can actually sign

Supplier organizations vary, and the titles vary more than the functions. Across most of them you are dealing with some version of these four, and it is worth knowing which one you are talking to at any given moment.

The commercial contact. Sales, business development, account management, or an overseas sales engineer. This is who answered your RFQ and who you have in your messaging app. Their authority is over price, quantity, schedule commitments and the commercial relationship. On a technical deviation they are a conduit, not a decision maker, and the honest ones will tell you so. The failure mode here is not dishonesty. It is that a conduit who wants to be helpful says "no problem" about something they cannot actually authorize.

Engineering or CAM. The group that opened your files, built the tooling data and is now watching the job. They understand the question completely and they usually hold the authority to decide *process* matters inside the released specification. What they typically do not hold is the authority to accept something outside it on behalf of the customer, and in many shops they do not communicate with customers directly at all. This is the single most consequential gap: the people who understand the problem are the people you cannot reach.

Quality. Whoever owns conformance and the disposition of nonconforming material. In a shop with a functioning quality system, this is the role that formally dispositions a deviation — use as is, rework, repair, scrap — and records it. When you need something to be *on the record* rather than merely agreed, this is the function that puts it there. Note that quality can usually only disposition against a document; if the drawing says one thing and you verbally said another, quality has nothing to work with.

The plant or program decision maker. A production manager, plant manager, or in smaller shops the owner. This is the escalation endpoint when a decision has cost or schedule consequences that cross functions. You rarely need them. When you do need them, you need them within hours, and that is precisely when nobody can tell you who they are.

The practical reading: a deviation you accept has to end up with quality, as a document, and the path from your message to quality runs through people you may not be able to see. Your job before the order is to make that path explicit.

What to ask before the PO, not during the crisis

These are questions to put to a heavy copper supplier while you still have commercial leverage, which is before the order is placed. They are also entirely reasonable questions, and a supplier who finds them intrusive has told you something useful.

1. Who is permitted to accept a deviation from the released drawing, by function? Not a name — a function, because names change. You are asking whether that authority sits with engineering, quality, the plant, or with your commercial contact. The answer determines who your reply actually has to reach.

2. What form does an accepted deviation take on your side? A signed concession or deviation form, an entry in a quality system, a revised work instruction, an email from a specific role? This matters because it tells you what artifact will exist at inspection time. "We'll make a note" is not an artifact.

3. Can I reach engineering or quality directly when the question is technical, and under what conditions? Many shops will say yes for defined circumstances and no in general. Either answer is workable. What is not workable is discovering mid-order that the answer was no.

4. Who is the named backup for my commercial contact, and how do I reach them without going through my contact? A supplier who has thought about continuity will answer immediately with a role and a shared channel. A supplier who has not will give you the contact's personal number, which is the opposite of what you asked for.

Two more that cost nothing to ask: does my order have an internal reference number I can quote to anyone in your organization, and will technical correspondence about this order be attached to that reference. These determine whether a stranger inside the supplier can pick up your problem on day one.

What an escalation path has to contain to be usable

An escalation clause that just says "the parties shall escalate as necessary" is decoration. A usable one specifies a small number of concrete things, and none of them require you to know the supplier's org chart.

A trigger, stated as a condition rather than a feeling. The useful formulation is event-based: a question about conformance to the released drawing, a request to proceed outside it, or a stop in production, each of which puts the matter on the escalation path rather than the normal path. This keeps you from having to argue about whether something is "serious enough."

A functional addressee at each level. First the commercial contact, then the function that owns technical conformance, then the plant or program decision maker. Roles, not names, so the clause survives staff turnover.

A channel that is not one person's personal account. A shared mailbox, an account-level address, a ticket reference. The point is that the channel exists independently of who is sitting behind it.

A default behavior while the matter is open. This is the clause most often missing and most often needed. In the absence of a written instruction from the buyer, what does the supplier do: hold the material, or proceed? Both are defensible choices and they have opposite consequences. Deciding in advance is what keeps a silent weekend from turning into a committed lot.

An explicit statement that only a written instruction changes the build. Verbal agreement, a chat message, or a phone call may be how the conversation happens, but the clause should say what counts as the instruction. Otherwise you will be relying at inspection time on something nobody can produce.

A record requirement. Whatever is decided gets written against the order reference and against the specific lot or panel range it applies to. A deviation with no scope attached is a deviation that quietly applies to every future order.

What this is not: a demand for response times, staffing levels, or penalties. Those are separate commercial negotiations and they do not solve the authority problem. A supplier can promise a fast response and still have nobody authorized to answer.

When the contact is unavailable: keeping order information off a single person

The scenario that exposes everything: your contact is on leave, has left the company, or has simply stopped replying, and the job is in process.

What fails first is not the relationship. It is information retrieval. If the entire history of the order — the files you sent, the clarifications, the one thing you agreed to change, the deviation you accepted last week — lives in a chat thread between you and one individual, then that individual's absence erases the order's memory on the supplier side. Someone new picks it up, finds a PO and a set of files, and has no idea that anything was agreed beyond them.

A few habits make this survivable, and they are all on your side of the fence, which is why they are worth doing regardless of what the supplier agrees to.

Quote the order reference in every technical message. Not the project nickname. The supplier's own order or job number, which is what a stranger inside their organization can search.

Put anything that changes the build in writing, in a medium the supplier can file. Chat is fine for the conversation. The conclusion goes into an email or a document, stating what changed, which lot or panel range it applies to, and who agreed. One short message per decision.

Keep your own chronological record of the order. Date, what was asked, what you answered, what artifact the supplier said would exist. This costs minutes and is the only version of events you fully control.

Ask for the agreed artifact rather than the agreement. After a deviation is accepted, request the concession form, the quality record, or the revised instruction. If it does not arrive, the deviation probably does not exist inside their system yet — which is exactly what you want to find out now rather than at inspection.

Use the account-level channel from the start, not just in emergencies. If the shared mailbox only receives your messages when something has gone wrong, nobody there knows who you are. Routine traffic through a shared channel is what makes the channel real.

How to write it so it survives a personnel change

The clauses that keep working are the ones written against functions, documents and references rather than people. A compact way to think about what belongs in the PO or the supply agreement:

• Authority: who, by function, may accept a departure from the released drawing, and a statement that no other role's agreement changes the build.
• Form: what artifact an accepted departure produces, and that the buyer may request a copy.
• Scope: that every accepted departure names the order and the lot or panel range it covers, and does not carry forward to later orders by default.
• Escalation: the event triggers, the functional levels, and the shared channel.
• Default during an open question: hold or proceed, stated explicitly.
• Continuity: a functional backup contact and an account-level channel, with the supplier's internal order reference quoted in all technical correspondence.
• Records: that technical correspondence is attached to the order reference and retained, so a successor can reconstruct the history.

None of these ask the supplier for a capability. They ask for clarity about a structure that already exists. That is why reasonable suppliers agree to them readily, and why the ones who resist are worth a second look during qualification.

If you are still choosing between suppliers, this is a qualification question rather than a contract question, and it belongs with the other things you check before a shortlist becomes an order. Our notes on screening heavy copper suppliers in the right order and on what process evidence to request during the RFQ cover the stages before this one. If the order is a repeat, the related question of how changes between runs get controlled is covered in change control terms for repeat heavy copper orders.

Scope note

This article describes commonly observed organizational patterns at PCB fabricators and what a buyer can usefully specify in a purchase order. It does not describe any particular supplier's internal structure, and it does not state response times, staffing, approval limits, or acceptance limits for any supplier including PCB168. Rights and obligations on an actual order are governed by the contract between the parties and the applicable law. Nothing here is legal advice.

Where to go next on PCB168

• Heavy copper PCB capabilities and build options — the product scope these orders are placed against.
• Screening heavy copper PCB manufacturers in the right order — the stage before an order exists.
• What process evidence to request from a heavy copper supplier — what to ask for during the RFQ.
• Prequalification scope and expiry for heavy copper manufacturers — how long a qualification decision stays valid.
• Change control terms for repeat heavy copper orders — controlling what moves between runs.
• Lead time and capacity commitments on heavy copper orders — the schedule side of the same relationship.
• Multilayer PCB product scope and process capability overview.
• Request a quote or contact us with your drawing and the authority questions above.

FAQ

Can my sales contact approve a deviation if they say yes in writing?

It depends entirely on whether that authority sits with their role, which is why it is worth asking before the order. A written yes from someone without the authority is still better than a verbal one, because it establishes what you were told. But it may not produce the internal record that quality needs, which means the lot can still be inspected against the original drawing. Ask what artifact the acceptance produced.

Is it reasonable to ask for direct access to engineering or quality?

Asking is reasonable. Getting a blanket yes is uncommon, and a no is not a red flag. Many fabricators deliberately route all customer contact through one function to prevent contradictory instructions, which is a defensible design. What you want is a defined circumstance under which a technical question reaches a technical function, and a channel that is not one individual's inbox.

What should the supplier do while they are waiting for my answer?

Whatever you agreed in advance. If nothing was agreed, you are relying on their judgment, and the two reasonable judgments — hold the material or continue under the original instruction — lead to very different outcomes. Specify one. Holding protects against committing material to a decision you did not make; proceeding protects the schedule. Which one you prefer depends on the order, and that is the point: it is your call, made in advance.

My contact left the company mid-order. What do I do first?

Send a message to the account-level channel quoting the supplier's own order number, asking who now owns the order and asking them to confirm the current build status and any accepted deviations on file. Then send your own chronological record of what was agreed and ask them to confirm each item against their records. The discrepancies between the two lists are the actual risk, and you want them surfaced before the lot ships, not at incoming inspection.

Does a signed deviation on this order apply to my next one?

It should not, and you should make sure the document says so. A deviation accepted without a stated scope is the most common way a one-time concession becomes the permanent build standard, usually discovered two orders later when someone asks why the boards no longer match the drawing. Every accepted departure should name the order and the lot or panel range it covers.

Should we write penalties into the escalation clause?

Penalties address a different problem. The escalation clause exists so that a decision can be made quickly by whoever is allowed to make it; a penalty does not create authority where none exists, and it tends to make suppliers reluctant to raise questions at all — which is the opposite of what you want on a heavy copper job, where the supplier raising a question early is the good outcome.

We only order occasionally. Is this worth the effort?

Low-volume and occasional buyers have the strongest case for it, because they have the least informal access. A high-volume customer gets their call taken. An occasional customer gets a queue. Writing the authority and continuity points into the PO is what substitutes for relationship leverage you do not have. It is also a few lines of text, reused on every order.