PCB Manufacturing and Assembly FAQ

What information is needed for an initial inquiry?

Provide the board or assembly quantity, intended deliverable, controlled design files and important technical requirements. Describe whether you need bare PCBs, populated boards or a more complete integrated assembly. Include your target milestone and explain its purpose, such as laboratory evaluation or a planned integration event. A target helps planning; it is not an automatic delivery promise.

If the design is incomplete, identify what is preliminary and what decision you need help reviewing. For example, a proposed stackup can support an early discussion while final fabrication files remain in progress. Avoid filling unknown fields with guessed values merely to make the inquiry look complete. A clearly stated unknown is easier to resolve than a false specification.

Which files belong in fabrication and assembly requests?

Fabrication typically needs manufacturing images, drill information, a board profile and construction requirements. Assembly adds a BOM, placement data, assembly drawings and population information. Provide firmware and test instructions when those activities are requested. The exact accepted formats and supplementary information are confirmed during review.

Keep every file aligned to one release and use a manifest to identify the revision. Do not include multiple competing versions without explaining which is authoritative. The table connects common request types with the additional information they need. Follow the detailed file-preparation guide before submitting a production package, and inspect the exported results rather than only the native CAD view.

How should materials, stackup and special processes be specified?

Start with the properties and constraints that matter to the product. A broad material name may not capture thermal behavior, electrical needs, thickness or required documentation. State whether a specific product is mandatory or whether an engineering proposal may be reviewed. For controlled impedance, identify the relevant nets, targets and tolerances rather than sending only a preferred trace width.

Unusual vias, flexible sections, metal substrates and other specialized constructions should be flagged in the written inquiry. Their appearance in an educational guide does not establish that every option is available for the project. Engineering review confirms feasibility and the proposed construction. Use capability planning to organize questions and retain the approved stackup or material decision with the release.

Can purchasing responsibility and assembly scope be mixed?

A project can be proposed with supplier purchased components, customer supplied components or a combination. Mark the owner for each BOM line and identify who can approve alternatives. Supplied material should have a packing list, complete part identity, quantities and relevant packaging or handling information. A mixed arrangement still needs one coherent assembly revision.

Define programming, cleaning where required, inspection, test, cables and mechanical integration explicitly. Do not assume that the phrase complete assembly includes every possible operation. Likewise, establish how unused material, shortages and failed units are handled. Compare turnkey and consigned planning to choose the responsibility model that matches your team.

What does testing establish, and can a first article be reviewed?

Bare-board electrical testing, assembly inspection and functional testing address different questions. Specify the intended checks and their acceptance criteria. A continuity pass does not demonstrate full product behavior; an optical inspection does not establish every hidden connection; a successful boot does not exercise every interface. The useful request is a coverage plan connected to your product risks.

First-article review can be requested as a defined gate before the remaining build proceeds. State whether you need images, a report, a physical sample or electrical results, and name the approval role. Confirm what work pauses while the review is pending. See first-article inspection and electrical testing to define the evidence rather than relying on an undefined approval label.

What happens after submission or when a design changes?

Use the inquiry form for the project description and attachments, observing the limits displayed there. Keep your local copy of the submitted package. If the form reports an upload problem, correct it and retry with the intended files; a message without the required engineering attachment may not support the review you requested. Do not put passwords or sensitive access credentials in ordinary design notes.

For a design change, identify the earlier release, provide the revised package and explain the affected requirements. Ask how purchasing and work in progress are affected before assuming the change can be applied immediately. Delivery condition, packaging, records and the confirmed schedule should be agreed for the actual scope. Browse resources or request engineering review with the project information you already have.

Continue your project research