Skip to main content
GullySystem
Manufacturing

Quality Control for PCB manufacturers

Record specified inspections and the disposition of checked goods.

Manufacturing

Does this function belong in your operation?

Use when goods or production stages require documented checks before release.

Material or output reaches an agreed inspection stage.

Micro-section checks, solderability tests and hole wall inspections are recorded by lot. A plating void found in a coupon holds the lot. The coupon report attaches to the certificate.

Bring the records the workflow depends on.

  • Inspection specifications
  • Sampling and acceptance rules
  • Authorised reviewers

Outputs to check

  • Inspection readings and evidence
  • Hold, release or rejection record
  • Nonconformance follow-up list

Follow the quality control workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Select the inspection

    Identify the receipt, job or output and applicable specification.

  2. 2. Record measurements

    Capture required readings, sample details and evidence.

  3. 3. Review nonconformance

    Hold failures and assign the authorised disposition.

  4. 4. Release or reject

    Record the responsible decision and affected quantity.

  5. 5. Follow rework

    Link corrective work and reinspection without overwriting the original results.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Quality checker

Fills the check at the station and holds what fails. Simple.

Production in-charge

Sees rejection by stage and by operator, and knows which machine is drifting before the customer says so.

Purchase

Takes the gate rejections to the supplier with dates and readings attached.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Reading outside tolerance

Hold the affected quantity and route the disposition to the authorised reviewer.

Inspection incomplete

Keep release pending and show the missing measurement or evidence.

Reworked goods returned

Create a linked reinspection rather than replacing the original failure record.

Can this work independently?

Quality records can be maintained independently against identifiable receipts or jobs. Inventory and production connections must enforce any hold or release decision. The module records authorised checks; it does not select a regulatory standard or replace a qualified inspector's judgement.

Systems and records it connects with

  • Work orders: Released production jobs, material issues and output records.
  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Purchase returns: Approved supplier-return quantities and adjustment references.
  • Batch and serial tracking: Lot or unit identifiers carried through stock movements.

Configure, test and introduce the workflow.

  • Show us where checks happen now. A note names the checkpoints and the parameters to record.
  • Provide limits and your list of rejection reasons. A test lot can then be checked on the trial screen. Checkers use it at a station for a trial run. Their remarks return as changes.
  • Checkers, production and purchase each practise their part. Each group gets a printed card. Other stations join as the trial station settles. The team reviews rejection reasons together.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Failed items follow the agreed hold rule.
  • Results retain the specification version.
  • Release decisions identify the reviewer.
PCB manufacturers

How the business operates.

A bare board order starts as a set of files and ends as a stack of boards in a vacuum bag. In between, a panel passes a dozen wet and dry steps, and every step has its own scrap. One late revision can sink a lot.

Order and file revision register

Hold the buyer’s Gerber set, fabrication note and revision, so CAM and the floor never image from an outdated pack.

Engineering query tracker

Log each CAM question, send it to the buyer, record the answer and release the lot only when all queries are closed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and quotations. Price boards from layer count, size, panel utilisation, finish and quantity bands, with every revision of a quotation kept.
  • File revision register. Attach the Gerber set, drill file and fabrication note to the order with a revision letter, and show the floor only the released set.
  • Engineering queries. Raise a CAM question, send it to the buyer, record the answer and block the lot until the query is closed.
  • Stack-up and panel plans. Hold the laminate, prepreg and copper weight of each build, with boards per panel and panel size.

Operational bottlenecks to check

The wrong Gerber revision gets imaged

The buyer resends files after CAM has started, and the film is made from the old set while the new revision waits in an inbox that the floor never opens. The error shows only on the electrical test.

Engineering queries wait in email

A clearance question to the buyer sits unanswered while the lot waits for tooling. The planner cannot tell which orders are blocked on a reply.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and quotation

    A buyer sends files and a fabrication note. The estimator checks layer count, size, finish and quantity, and prices from panel utilisation.

  2. 2. CAM review

    CAM checks clearances and drill data, raises engineering queries and lays out the panel. The order is released only after the buyer’s answers.

  3. 3. Lot creation

    A lot opens with the file revision, stack-up and a traveller by process step. Laminate and prepreg are issued against it.

  4. 4. Process steps

    Imaging, etch, lamination, drilling, plating, mask, legend, finish and routing are each logged with quantity in, quantity out and scrap reason.

  5. 5. Test and inspection

    Open and short test results are saved by board. Final inspection checks dimensions, finish and visual defects.

  6. 6. Packing and shipment

    Boards are counted, bagged and labelled with the date code. The certificate of conformance, test report and packing list are issued.

Industry reports to connect with

  • Yield by process step, by week and by board type
  • Orders waiting on engineering queries
  • Scrap reasons for drilling, plating and etching
  • Lots affected by a given bath change or press load

Questions before implementation.

When should pcb manufacturers consider quality control?

Use when goods or production stages require documented checks before release. Material or output reaches an agreed inspection stage.

What should we bring to the requirements discussion?

Bring anonymised examples of Inspection specifications; Sampling and acceptance rules; Authorised reviewers. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record specified inspections and the disposition of checked goods. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The software records your inspection process and does not certify product safety or regulatory conformity.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Failed items follow the agreed hold rule. Use this check when reviewing the first working version.

Talk to us

Discuss quality control for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements