Contact Us

PCBA Rework and Repair Authorization

PCBA Rework and Repair Authorization

Rework is the one step on a PCBA line where the product changes after it has already been tested. That is why every serious customer asks the same question at audit: who allowed this unit to be reworked, and what exactly did they allow?

When the answer is a verbal instruction from the line supervisor, the unit leaves the building with a history that exists only in memory. If it fails in the field, the failure cannot be separated from the rework, and the whole lot becomes suspect.

Why rework without a record becomes an audit finding

Three failures repeat. A joint is reworked twice with no note, so the second attempt lands on a pad that has already been heated and lifted. A BGA is removed and replaced without the customer knowing, so the shipped configuration is no longer the approved one. A unit is repaired with a part from another maker, which turns a build-to-print job into a deviation nobody signed.

Each of these is cheap to prevent and expensive to explain. The preventive step is not more inspection. It is one authorization that names the unit, the defect, the method and the limit before the iron touches the board.

Four actions, four approval paths

ActionWhat it isWho authorizesRecord
ReworkBringing a unit back to the drawing after a process defectInternal quality, inside a method the customer has approvedTicket tied to the serial number
RepairRestoring function on a unit that failed test or came backInternal quality, plus the customer when the method is outside the approved procedureRecord with the defect, the method and the test after
ModificationChanging the build from the released drawingCustomer only, in writingChange record, new revision, first article
ScrapDeciding the unit cannot be brought inside limitsQuality, with the customer informedScrap record with the reason and the quantity

The distinction matters because each path carries a different signature. A rework inside an approved method does not need the customer to sign every unit. A modification does, every time, even when it looks like a small improvement to a part that is hard to buy.

What has to be named before work starts

An authorization that says rework as needed authorizes nothing. The usable version names four things: the unit or the range of serial numbers, the defect and its location, the method with its reference to the IPC-7711 and IPC-7721 procedure, and the limit beyond which the unit is scrapped instead of reworked.

The limit is usually the missing part. Every pad, every through hole and every BGA site has a point where another cycle does more harm than the original defect. Once that point is written down, the decision stops depending on who is at the bench that shift.

The authorization also names who may do the work. Rework on fine pitch, on BGA and on RF transmission lines stays with a small group, because the difference between a sound joint and a damaged one is measured in tenths of a millimetre.

Limits that cannot be signed away

Some conditions are a scrap decision whoever signs. A lifted pad that takes the land with it, a delaminated area under a BGA, a cracked package body, or a connector housing melted during removal are all cases where the unit is already outside the drawing. Approving a rework on top of them produces a unit that passes test today and fails later.

Thermal history is the other limit. A board that has been through rework twice at one site is not the same board as one that has been through it once, and that count belongs on the record so the next decision has a fact to stand on. Where a customer sets a cycle limit in their own procedure, that number overrides ours.

How SUPERB PCBA runs rework under authorization

Every rework opens a ticket carrying the serial number, the defect, the method and the operator, and the unit does not return to the line until the ticket closes with a test result. The ticket links to the unit record, so a return from the field resolves to the exact rework that was done.

Work is done at a station with the board supported, under magnification and with controlled temperature. BGA work is confirmed by X-ray to IPC-7095 with voiding under five percent before release, fine pitch work is checked by 3D AOI, and any reworked unit goes through the same functional test as a new build rather than a shorter check.

The build itself runs on seven SMT lines with 01005 placement, through a seventeen step flow with ten QC stations under IPC-A-610 Class 2 and Class 3, with ISO 9001 and ISO 13485 for medical work. Rework is counted against the lot, so a lot with an unusual number of tickets is treated as a process question and not as a run of bad luck.

PCBA rework and repair authorization questions

Does every reworked unit need customer approval?

No. Rework inside a method the customer has already approved is an internal quality decision, recorded per unit and reported with the lot. Approval is needed when the method sits outside the approved procedure, or when the action changes the build.

What happens to a unit that passes the rework limit?

It is scrapped and removed from the shipped quantity. Shipping it would put a unit in the field that cannot be defended at the next audit or field failure review. How a customer-approved departure is handled instead is covered under supplier deviation and waiver process.

How is the rework history visible to the customer?

Through the unit record: serial number, defect, method, operator, the test after rework and the count of cycles at that site. Where the customer asks, the count is reported with the outgoing record. The method follows IPC-7711 and IPC-7721 rework and repair limits.

Next step

Send one returned unit, or the lot where a rework question is open, with the defect you found and the method you expect. The reply returns the approval path for that case, the limit that decides rework or scrap, and the fields to add to your own ticket so the next audit reads it without a follow-up question. What the unit has to be tested against afterwards is set out under PCBA test coverage strategy.