Skip to main content
GullySystem
Manufacturing

Workflow and Approvals for PCB manufacturers

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A buyer’s reply to an engineering query releases the file for the next step. CAM, a process engineer and the quality head sign the data before drilling starts. A rejected stack-up returns with comments.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

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

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

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

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

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.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

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.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
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 workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. 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. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

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. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals 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