What a complete manufacturing documentation package contains

When a supplier calls with a question about a drawing, the cost is not the call. It is the week the part waits, the guess they make if they do not call, and the scrap if the guess is wrong. A complete documentation package is the cheapest way to make those calls rare.

What goes in the package?

File	One per	Format	Must state
Detail drawing	Made part	PDF (+ native)	Revision, material, finish, tolerances, standard
Assembly drawing	Assembly or sub-assembly	PDF	Item balloons matching BOM line numbers
Bill of materials	Top assembly (multi-level)	XLSX / CSV	Part number, revision, quantity, make/buy, material
3D model	Made part	STEP	Same revision as the drawing
Flat pattern / profile	Sheet-metal or profile-cut part	DXF	Same revision; 1:1, unit stated
Revision record	Package	PDF or table	What changed, when, approved by whom
File index	Package	PDF or XLSX	Every file, its revision and its purpose

Optional but useful: a short specification sheet for coatings and heat treatment, an inspection plan for critical characteristics, and packaging instructions.

How the pieces relate

The checks that keep it consistent

Before release, check:

1. BOM vs. assemblies. Every assembly balloon has a BOM line; quantities match the model; no orphan lines.
2. Revisions. Each drawing’s revision equals its model’s; the STEP and DXF file names carry the same revision.
3. Part numbers. Unique, consistent between drawing, model file name and BOM.
4. Material and finish. On every made-part drawing, not only on the assembly.
5. Exports regenerated. STEP and DXF exported after the last change, not before.
6. Standards stated. Drawing standard and edition, general tolerance note, projection symbol.

Revision control without a PDM

A PDM system makes this easier, but small companies can run a sound process with folders and discipline:

• a released folder where files are only added by the person who approves releases;
• revision letters in file names (PN1042_C.pdf, PN1042_C.step);
• a revision table on each drawing and a package-level change log;
• superseded revisions moved to an obsolete folder, never deleted.

How detailed should each drawing be?

Detailed enough for a supplier who has never seen your product. A good test: hand the drawing to someone outside the project and ask them how they would make and inspect the part. Every question they ask is a gap.

Typical gaps by part type:

Part type	Often missing
Machined parts	Datum structure, thread classes, edge breaks, surface finish on functional faces
Sheet metal	Bend direction and radius, K-factor reference, grain direction, hardware insertion
Weldments	Weld symbols and sizes, distortion-critical dimensions after welding, finish after welding
Plastic parts	Draft, parting line, gate location constraints, cosmetic zones

Assembly drawings that help the shop

An assembly drawing is not just a picture with balloons. Make it useful:

• balloons numbered to match the BOM item numbers exactly;
• torque values for critical fasteners;
• adhesives, thread lockers and lubricants called out where they are applied;
• critical assembly dimensions or clearances that must be checked after assembly;
• exploded views when the assembly order is not obvious.

Supplier-specific packages

Different suppliers need different subsets of the package. A laser shop needs DXF and PDF for its parts; a machine shop needs STEP and PDF; a final assembly partner needs the whole tree. Build each supplier’s package from the released set, with the file index filtered to what they receive. That way nobody gets files they do not need, which also helps confidentiality.

Release notes that actually get read

When a revision changes, suppliers want to know three things: what changed, whether parts already made are still usable, and from when the new revision applies. A short release note answering exactly those three questions, attached to the package, prevents most of the “which revision did you mean?” emails.

Keeping the package alive

A package is complete on the day it is released and starts aging the day after. Assign an owner, route every engineering change through the same release process, and audit one product line a year: pick a part at random, check that its drawing, model, STEP, DXF and BOM line still agree. If they do, the process works. If they do not, fix the process before the files.

Naming files so they sort and match

A consistent naming rule does half the work of a document system. A pattern that works for most companies is PARTNUMBER_REV_description.ext, for example PN1042_C_bracket.pdf and PN1042_C_bracket.step. Files of the same part and revision then sort together in any folder, a supplier can see at a glance that the PDF and the STEP match, and a script can check the whole package for mismatched revisions in seconds.

Signs your package is not complete

• Suppliers ask for “the STEP” after receiving drawings, or “the drawing” after receiving STEP.
• Quotes for the same part vary widely between suppliers.
• Purchasing keeps a separate spreadsheet because the BOM “is not right”.
• Nobody can say which revision was sent to which supplier.

Each of those is cheaper to fix in the package than on the shop floor.