Flex PCB Fabrication Notes: Resolve Ambiguity Before Quoting

UPDATED October 9, 2026

Discuss your flex PCB project →

A fabrication note should remove a decision from the production team’s guesswork. Notes such as “standard flex construction” or “meet all applicable requirements” can do the opposite: they hide choices until the quote, tooling or inspection stage. A useful drawing makes the governing data, measurable requirements and unresolved decisions easy to identify.

This checklist focuses on preparing a coherent release package for flex PCB manufacturing. It is not a set of universal production notes to copy unchanged into every drawing.

Make the document hierarchy explicit

List the fabrication drawing, artwork, drill data, netlist and any controlled supporting specification with their revisions. Explain which document governs if two representations disagree, and require a documented resolution before production. A precedence rule does not make an actual conflict safe to ignore; it tells the reviewer where to start resolving it.

Minco’s design guide discusses drawing views, regional stackup information and the data needed for quotation and manufacturing. Würth Elektronik’s flex design guide similarly addresses clear drawing and data requirements. These manufacturer references support preparing a complete package; the proposed note examples below are original review aids, not quoted vendor instructions. Minco design guide, drawing and manufacturing information sections; Würth Elektronik flex design guide, drawing guidance.

Replace vague language with an answerable requirement

Do not populate those blanks with arbitrary numbers just to make the package look complete. An explicitly unresolved requirement is easier to manage than a precise value that no stakeholder has approved. Track unresolved items in a short decision list with an owner and a release condition.

Show regions that a single stackup cannot explain

A flex circuit may contain an exposed connector tail, a covered moving span and a reinforced component area. If their layers differ, show the relevant cross-sections and identify their extent on the outline. Relate those sections to the same datum scheme used for openings and reinforcement placement.

Distinguish the manufactured flat outline from the assembled shape. A formed view can communicate installation intent, but it should not leave the fabricator guessing which dimensions describe the delivered part. Label reference-only assembly geometry and separately identify any delivered forming requirement that has actually been agreed.

Use the design-rules guide to organize the geometry review. Keep supplier capability questions attached to the particular feature rather than adding a blanket “manufacturer to adjust as needed” note.

Keep quotation assumptions visible

Send every bidder the same revision and the same open questions. Ask quotations to identify proposed construction, deviations, tooling assumptions and any inspection or documentation exclusions. Otherwise a low and a high quotation may describe different deliverables even when they carry the same part number.

The cost estimator can structure early discussions, but it does not replace a quote against released data. When an input changes, update the comparison record before interpreting a price difference as manufacturing efficiency.

Work through a drawing conflict before issuing a quotation

Imagine an original example in which the outline drawing labels a connector tail as 0.30 mm finished thickness, while a purchasing note requests a 0.30 mm stiffener. These statements control different quantities. The finished section can contain the stiffener, its adhesive and the circuit layers, so the supplier cannot safely treat both notes as interchangeable. Do not resolve the conflict by letting the most recent email silently override the controlled drawing. Identify the intended interface and revise the affected requirements together.

A useful clarification record has four parts: the conflicting references, the supplier’s proposed interpretation, the design owner’s decision and the files affected by that decision. In this example, the owner would confirm the finished section to be controlled and the construction that is intended to achieve it. The revised package would identify the measuring location and accepted interval. The record should distinguish an approved finished requirement from a supplier’s proposed material choice.

Another conflict can arise when an assembled view includes a curved tail but the procurement request expects a flat circuit. Label the delivered state explicitly. If forming is included, define what the supplier must deliver and how that result is judged. If the curved view only explains installation, label it as assembly reference information. The purpose is not to add more notes; it is to prevent two suppliers from quoting different physical deliverables against the same illustration.

Separate requirements, references and proposals

Use the drawing to distinguish three kinds of information. A requirement defines what must be supplied or accepted. A reference helps explain design intent without creating an additional acceptance dimension. A proposal is a choice awaiting approval. Mixing these categories creates avoidable ambiguity: a nominal assembly sketch may be interpreted as an inspection requirement, while a critical finished dimension may be dismissed as illustrative.

For each important characteristic, identify the governing reference and the responsible approval owner. A proposed stackup should not look like an approved construction merely because it appears in the same PDF. If the fabrication drawing points to another controlled document, include that document or provide an agreed way for the supplier to access the correct revision. A reference to an unavailable internal specification does not make a quotation complete.

Keep standards references precise without inventing their contents. If a project requires a particular standard, identify the designation, revision and agreed applicability using the project’s approved requirements. Resolve acceptance class or other choices with the responsible engineering and quality personnel. A general instruction to comply with every applicable standard does not tell a bidder which actual inspection and documentation obligations it is being asked to price.

Assign ownership for manufacturing adjustments

The production artwork may require supplier preparation, but the permission to prepare data is not permission to change every functional feature. Define which proposed changes need approval, with attention to the actual circuit. A change affecting a connector finger, controlled trace geometry, coverlay opening or reinforcement location can alter an interface the designer intended to control. Ask the supplier to identify such changes in a reviewable comparison before release.

Separate compensation for an agreed process from an engineering change to the delivered requirement. The fabricator may have its own way to produce an accepted finished feature. The drawing still needs to state the feature that matters and the acceptance basis. If the supplier cannot meet that requirement, record a deviation request with the proposed alternative. Avoid accepting a broad note that allows unspecified adjustments while retaining an expectation of exact interchangeability.

For an approved deviation, state whether it applies to a prototype quantity, a named lot or the continuing design. A temporary acceptance should not become a permanent drawing change by being copied into the next order. Conversely, a permanent design decision should be incorporated into the controlled package rather than remaining in a closed prototype discussion. This distinction makes later repeat orders easier to evaluate.

Define what evidence arrives with the circuits

Separate the physical circuit requirements from the records requested with delivery. Identify the reports, inspection results or material identification that the project actually needs and that the supplier agrees to provide. If a test is required, specify its governing requirement and the expected record. A note saying electrical test required leaves open whether the delivery includes only a pass statement or more detailed evidence.

Do not ask for documents merely because they appear in a generic template. Tie each requested record to a use: receiving inspection, assembly release, traceability or a specific verification decision. This keeps the package focused and exposes missing evidence. For example, a dimensional report is only useful for a controlled tail if it identifies the relevant section and revision; an unrelated overall thickness reading does not close that requirement.

Include the disposition of nonconforming or conditionally accepted features in the release record. If the design owner agrees to inspect initial samples before a larger build, define the hold point and what approval releases it. The supplier and buyer should be able to identify that condition from the same package, without reconstructing a long chain of messages.

Run a receiving-team rehearsal

Before issuing the package, ask a reviewer to act as the receiving inspector. Have that person select one critical interface, identify its controlled dimensions and locate the evidence needed to accept it. Then ask a manufacturing reviewer to locate the corresponding construction and artwork. If the two reviewers select different sections or revisions, resolve the discrepancy before requesting a firm quotation.

Finish with a package manifest listing the included files and their revisions. Retain the supplier’s acknowledgement of that manifest and any approved exceptions. File names alone can be misleading when several drafts have circulated, so use the project’s existing document-control method to identify the actual release. The resulting package should let a new reviewer reconstruct both what was ordered and the conditions under which it was approved.

Close the review with a small release record

Before release, have one reviewer trace each critical requirement to its controlling document and another inspect the package as if receiving it for the first time. Can they identify the delivered state, connector interface, protection boundaries, material construction and acceptance evidence without asking the original designer? Any disagreement is a useful signal to improve the package.

Record the approved revision, supplier acknowledgements, resolved deviations and outstanding conditions. If production must wait for a sample review, say so explicitly in the release record. Do not rely on an email fragment that is absent from the drawing package.

Request a fabrication-package review with the drawing, manufacturing data and decision list. The objective is a quotation and build instruction that refer to the same controlled product.

Explore the flex PCB guide and tools →