PCB Assembly Drawing: What It Has to Tell the Line

An assembly drawing is the document that turns a design into a build instruction. The manufacturing data says where the copper goes and the centroid file says where the components sit, but neither of them explains what the assembly house is expected to do with a do not populate part, which orientation is correct for a polarised component, or what standard the joints will be judged against. Those gaps are filled by the drawing, and when it is incomplete they are filled by assumptions.

What the Drawing Contains

A complete assembly drawing carries several distinct kinds of information, and they are usually arranged so that the mechanical detail, the placement detail and the notes are each readable on their own.

The identification block states the part number and the revision, and those two fields must match every other document in the package. A mismatch between the drawing revision and the centroid file is one of the most common causes of a build that is assembled correctly to the wrong revision.

The placement view shows each component in its location, with its reference designator, its outline and its polarity or pin one marking. This is what an operator uses when a board has to be touched by hand, and it is what a technician uses when a board has to be repaired.

The component table lists the references, the values or part numbers, and the package or footprint. Where the design has variants, the table usually carries a column per variant, which is cleaner than a separate drawing for each.

The notes carry everything that cannot be drawn. This is where the acceptance class belongs, along with the DNP list, the variants, the soldering method for specific joints, the cleaning requirement, the conformal coating areas, and any instruction about a part that must not be heated.

Assembly Drawing and Fabrication Drawing

The two documents are often confused because both are drawings of the same board, and they serve different audiences.

A fabrication drawing is read by the bare board supplier. It carries the stackup, the material, the copper weight, the finish, the impedance requirements, the hole table and the tolerances. It says nothing about components.

An assembly drawing is read by the assembly house, the test engineer and the service technician. It carries the components, their orientation, the process notes and the acceptance criteria. It may not need the stackup at all, though it usually includes the finished thickness and the board outline for reference.

The Rest of the Data Package

The drawing is one file in a set, and the assembly house needs the whole set to be consistent.

• Gerber or ODB++ data for every layer, including the solder mask, the legend and any mechanical layer that defines the outline.
• NC drill file with the hole table, in a defined format.
• Pick and place data with the reference, the position, the rotation and the layer, generated from the same revision as the board.
• Bill of materials with reference designators, approved sources and any alternates.
• Fabrication drawing with the stackup and tolerances, where the assembly house is also buying the bare boards.
• Netlist data such as an IPC-356 file, so the assembly house can run a bare board test or verify the electrical test setup.
• Assembly drawing with placement, polarity, notes and acceptance criteria.

Two consistency checks catch most problems before a build. The first is that the reference designators in the BOM, the centroid file and the drawing are an exact match, with no component present in one and missing from another. The second is that the rotation convention in the centroid file matches what the assembly house expects, since a machine that interprets the rotation differently will place a component sideways, and the error is systematic rather than random.

Variants, DNP and Optional Parts

Most products exist in several versions, and the assembly drawing is where the differences have to be unambiguous.

A do not populate instruction must state clearly which references are affected for which variant. The safest approach is a table with one column per variant and a marker in each cell, combined with a note that overrides any default. A drawing that leaves the DNP parts to a note reading “fit as required” will eventually be built with the wrong population.

The centroid file has to agree. Some houses prefer every component to be present in the file with a variant marker, others prefer a separate file per variant. Whichever convention is used, it should be stated on the drawing so there is no room for interpretation.

Where a variant changes more than the population, such as a different value or a different part in the same footprint, the change should be visible on the drawing and not only in the BOM, because the operator may be working from the placement view rather than from the parts list.

The Gaps That Cause Build Errors

Almost every assembly problem that traces back to documentation falls into one of a small number of categories.

Missing polarity information. A footprint without a pin one marking, or a symbol that is ambiguous on a part with more than one orientation, leads to a fitted backwards component. Where the polarity is visible on the legend it should also be checked that it survives the component being fitted, since a mark hidden under the body is not a mark.

Ambiguous reference designators. Two components that look like each other on the placement view, or a legend that cannot be read at production speed, produce swap errors. The drawing should be legible at the scale the operator actually uses.

Silence about process. The drawing does not say whether the assembly is cleaned, whether a part must not be reflowed twice, whether a connector has to be hand soldered or whether a shield goes on after test. The assembly house will decide, and their decision may not match the design intent.

No acceptance class. Without a stated standard, the joints are judged by the operator’s own experience. Two builds of the same design can then be accepted and rejected for the same joint.

Revision mismatch. A drawing at revision B and a centroid file at revision A is a systematic error affecting every board built from that package, and it is only caught when something is visibly wrong.

A note that contradicts the data. A note saying a part is not fitted while the centroid file includes it, or a value in the table that does not match the BOM, will be resolved differently by different people.

Who Reads an Assembly Drawing

The document serves several audiences, and each of them needs something slightly different from it.

The assembly house needs placement, orientation, population and the process notes, together with the acceptance criteria. The test engineer needs the same placement view to build the program and the fixture, and needs to know which nets are critical. The service technician needs the component references and the polarity to diagnose and repair a unit years later. The mechanical designer needs the height and interference information to confirm that the assembly fits the enclosure.

That range is why the drawing should be organised rather than merely complete. A single page with the placement view, a component table and a notes block will be read by all four. A drawing where the crucial note is buried on a third sheet will be read by none of them.

Revision Control

A drawing is only useful if it matches what was built, and that requires discipline in how revisions are issued and recorded.

The simplest rule is that one revision identifier applies to the board, the BOM, the placement data and the drawings together. A change to any one of them produces a new revision for all of them, even when the change looks trivial. That avoids the situation where a board revision C is fitted with a BOM revision B and nobody can reconstruct what was actually built.

The second rule is that a change is recorded with a reason and an effective date. When a unit returns from the field, the first question is which revision it is, and the answer has to be available from the marking on the board and the build records.

The third rule concerns the assembly house. When a change is issued, the tooling that has to change with it should be identified at the same time: a stencil, a fixture, an inspection program or a placement program. On a turnkey build, those are the assembler’s responsibility, and they can only act on a change they know about.

Checklist

• State the part number and revision on every document, and confirm they match across the package.
• Show every component with its reference designator, outline and polarity on the placement view.
• Include a component table with values, packages and variant columns where applicable.
• List the DNP references explicitly for each variant rather than relying on a general note.
• State the acceptance class and the inspection standard for the assembly.
• Record the process notes: cleaning, coating areas, hand soldered parts, parts that must not be reflowed twice.
• Confirm the reference designators and rotations in the centroid file match the drawing and the BOM.
• Note any component with a height or keepout constraint that affects the enclosure.
• Keep the drawing legible at the scale the operator will use, and organise the notes so the critical ones are not buried.

FAQ

• Is an assembly drawing required? For hand assembly and for any build with polarised parts, variants or process requirements, yes. A fully machine placed board with a single variant can be built from the data package alone, but the drawing is what proves the intent.
• Can the drawing be the same file as the fabrication drawing? They can share a template, but the content is different and combining them usually makes both harder to read.
• Who owns the assembly drawing? The design owner. The assembly house may annotate it with process notes, but the population and orientation belong to the design.
• How detailed should the notes be? Specific enough that a competent operator who has never seen the product can build it correctly without asking a question.

Summary

An assembly drawing exists to remove ambiguity. It states what goes where, which way round, which parts are not fitted in which variant, how the joints will be judged and what process constraints apply. The manufacturing data describes the board; the drawing describes the build.

Keeping the package consistent is the discipline that makes it work: one revision across the board, the fabrication drawing, the BOM, the centroid file and the assembly drawing. Where the design is handed to a partner, the package is the interface, and the questions they ask about it are the measure of how complete it is. A design with a clear drawing is also easier to test, which is why the notes belong with the test requirements rather than being added separately at the end of the project.