Total layers versus flex layers: why both matter

Specify both the total copper-layer construction and the copper layers present in each flexible region when describing a rigid-flex PCB. A global layer count can describe the most complex rigid section while revealing little about an individual flex span. Regional construction is the information a reviewer needs to understand what actually continues between the rigid islands.

Altium’s layer-stack documentation explains the use of multiple substacks in rigid-flex design. A practical procurement description should preserve that distinction instead of collapsing all regions into one number.

Use a region-by-layer presence table

Imagine an educational design with eight globally named copper layers. Its first flex span carries L4 and L5, while a second flexible region uses a different reviewed construction. The word “eight-layer” alone cannot tell the reviewer whether these spans are equivalent. List the assigned substack for each region and identify its copper layers.

Here, F1 has two copper layers and F2 has four, despite sharing one eight-layer headline description. Each still needs its own reviewed material construction and bend requirement. These invented assignments explain the naming problem; they are not a recommended or production-ready stackup.

Define what you are counting

Use the label “copper layers” when that is what the number means. Do not mix dielectric films, coverlay, adhesives, and local stiffeners into the same unlabeled count. Those materials still belong in the construction documentation, but they answer a different question from the number of conducting layers.

For an inquiry, attach the actual stack table rather than relying on a product-name field. If the design is still preliminary, identify which counts are confirmed and which alternatives remain under consideration. This allows a supplier response to address the uncertainty explicitly.

Keep global and local names connected

A flex drawing might call its two conductors “top” and “bottom” even though they correspond to internal layers in a rigid region. Add a naming cross-reference so a reviewer can follow a net or drill reference across the boundary. Avoid restarting layer numbers without explaining the mapping.

A simple review exercise is to select one continuous conductor and mark it in the rigid stack, flex stack, and layout. If its identity changes ambiguously between views, fix the documentation before discussing dimensions or tolerances.

Use the distinction in quotations

Follow a connection through the complete assembly

Take a hypothetical connection that starts on L1 in rigid region R1 and must reach another island through F1. In the example above, F1 contains only L4 and L5. The design therefore needs a reviewed way to bring that connection onto a layer present in F1 before it enters the span. The layer count identifies this routing question; it does not answer where a transition is permitted or how it should be fabricated.

Mark the connection on both the plan view and the cross-section. Include any via or pad involved and its regional location. A net that looks continuous in a simplified schematic may still have an unresolved physical layer transition. Conversely, a conductor that remains on the same globally named layer can pass between regions while its surrounding dielectric and reference arrangement change. Review continuity of the conductor and continuity of its electrical environment as separate questions.

Distinguish available layers from assigned functions

A two-layer flex span does not automatically provide two unrestricted routing layers. One layer may be assigned primarily to a reference conductor, while the other carries signals. Alternatively, the design may allocate both layers differently, subject to its electrical and mechanical requirements. Add a function column to the regional stack description so the routing plan does not assume that every copper layer offers the same usable space.

For example, a fictional span must carry twelve signals and their required references. Counting twelve traces across two layers is not enough to establish that the routing fits. The review also needs the usable span width, allowed routing dimensions, edge margins, reference geometry, and any placement restrictions. Start with a routing study against the proposed construction. Do not reduce the flex layer count in a quotation before checking what happens to those constraints.

Use a width budget to reveal the real routing question

Consider a purely illustrative row of twelve traces, each 0.10 mm wide, separated by eleven gaps of 0.10 mm. The traces and internal gaps occupy 12 × 0.10 + 11 × 0.10 = 2.30 mm. If the preliminary drawing also reserves 0.50 mm at each edge, the resulting width allocation is 3.30 mm. These invented dimensions are arithmetic inputs, not recommended fabrication rules or an impedance design.

The calculation deliberately excludes additional spacing between signal groups, changes near terminations, reference requirements, and other geometric constraints. Its purpose is to make the assumptions visible. If the mechanical design offers only 3.00 mm, the simple allocation already fails before those additional considerations are included. The team can then investigate a wider span, another routing arrangement, or a different architecture instead of assuming that an extra global rigid layer will solve a local flex constraint.

Keep copper count separate from finished thickness

Two regions with the same copper-layer count can still have different finished constructions. Copper thickness, dielectric films, bonding materials, and protective layers all need explicit definitions. A procurement description that says “two-layer flex” should therefore point to a stack reference rather than acting as the entire stack specification. Ask which thickness is being quoted and how that thickness is defined in the flexible area.

Do not infer bending suitability from the copper count alone. A mechanical review needs the actual construction and intended motion, including whether the span is formed during installation or repeatedly moved during use. The count is useful for identifying a class of design alternatives, but the released bend requirement belongs to a particular construction. If a material or protective layer changes, evaluate the effect on the previously reviewed configuration.

Document split and locally different constructions clearly

The educational F1 and F2 example requires more than two independent stack tables. The complete assembly drawing must explain how each region connects to its neighboring rigid section and where each material begins or ends. A collection of individually plausible cross-sections does not prove that they form one manufacturable board. Bring the regional transitions into the supplier review early, while architectural changes are still manageable.

Use a distinct identifier for each construction that is actually different. If two regions share one stack, say so explicitly rather than maintaining duplicate tables that can drift apart. If they differ only in a local feature, describe the difference and its extent. The goal is enough detail to reproduce the intended board without creating unnecessary copies of the same information.

Check fabrication outputs against the regional intent

Before release, compare the copper outputs and supporting drawings with the presence map. Review a representative location in each rigid and flexible region. Confirm that the intended layer names remain recognizable and that the supplier can locate the region boundaries. An output filename such as “inner two” may be understandable inside one team’s workflow but ambiguous when it is separated from the native design project.

Keep drill references equally explicit. A description of a connection between two named layers needs to match the global naming system and the region where the feature exists. If a supplier proposes renaming layers for its process documents, retain a cross-reference to the customer drawing. This reduces the chance that a technically reasonable manufacturing discussion turns into an accidental agreement about different layers.

Compare alternatives with a change register

Suppose an alternative keeps eight layers in the rigid section but changes F2 from four copper layers to two. Record the affected nets, reference assignments, stack thickness definition, routing space, and motion review. The headline layer count remains eight, yet the engineering change can be substantial. The quotation comparison should show these differences next to the commercial terms so the decision maker understands what is being purchased.

Ask for unresolved assumptions to be listed explicitly in the response. A supplier may quote a preliminary construction pending routing or mechanical review; that can be useful early information if its limits are clear. It should not be recorded as approval of a final stack that has not been evaluated. Preserve the accepted revision when the questions are closed and use that revision in subsequent purchasing documents.

Two offers both described as eight-layer rigid-flex may cover different regional constructions. Compare the approved stack references, material definitions, and flex-region assignments alongside price. A changed flexible construction should be identified as a technical alternative requiring review, not treated as an equivalent quote by default.

Also check that the purchase description identifies the board revision. Otherwise, a correct layer-count description can still accompany an obsolete regional map. The approved package should let purchasing, design, and fabrication identify the same construction without relying on a remembered conversation.

See our stackup and materials overview and rigid-flex PCB guide. Send the global layer map and regional stackups to make your inquiry unambiguous.