One revision, one release package
Use a clearly named archive containing only the files for the requested build. Add a short manifest with the project name, revision, date and contact for engineering questions. If multiple assembly variants share one bare board, describe each variant explicitly.
Bare-board fabrication data
- Gerber files or another manufacturing format accepted by the receiving manufacturer.
- Plated and non-plated drill data, routed slots and a dimensioned board outline.
- Layer order, finished thickness, material, copper requirements and surface finish.
- Solder-mask and legend requirements, tolerances and any special features.
- Controlled-impedance table and approved stack-up, where required.
Assembly and sourcing data
- BOM with manufacturer part numbers, quantities, reference designators and approved alternates.
- Pick-and-place file with units, origin, side and rotation conventions.
- Assembly drawings showing polarity, connector orientation and do-not-populate parts.
- Consigned-parts list, packaging condition and available quantities.
- Programming files, firmware revision, coating and cleaning requirements.
Commercial and acceptance requirements
- Prototype and production quantity breaks.
- Required delivery destination and target date.
- Inspection, electrical and functional-test requirements.
- First-article approval, traceability and shipment records.
- Any required qualifications that must be verified before project acceptance.
Common causes of quotation delays
Mixed revisions, missing part-number suffixes, contradictory quantities and ambiguous board outlines generate preventable questions. Review the exported package with the same discipline as the source design. If a requirement is unknown, identify it as an open question rather than leaving the manufacturer to assume.