1. Identify the released design
Use a project identifier and revision across the drawing, board data, BOM and assembly instructions. State whether the package is released for production or still under review. Include a short list of unresolved questions instead of leaving suppliers to infer your intent.
2. Define the fabrication scope
- Gerber or agreed fabrication format, drill data and board outline.
- Layer order, stackup, material, thickness and copper requirements.
- Surface finish, solder mask and special mechanical features.
- Impedance, electrical test, inspection and documentation requirements.
3. Add the assembly package
- BOM with exact manufacturer part numbers, quantities and references.
- Placement data and assembly drawing with polarity and orientation.
- DNP positions, fitted variants and quantity by variant.
- Consigned components, approved alternatives and sourcing restrictions.
- Programming, test, coating, cleaning and final integration requirements.
4. Set the commercial assumptions
Specify build quantity, requested delivery date, shipping destination and any split delivery. Ask the quote to identify components, boards, setup, assembly, tooling, programming, testing and freight as applicable. Confirm what is excluded and how long the quotation remains valid.
5. Compare scope before price
A lower total may omit testing, use a different material or assume a different sourcing route. Resolve those differences before comparing unit prices. Request explicit approval for alternatives that affect function, fit, qualification or the agreed acceptance criteria.
Separate a quote package from a production release
Preliminary data can support an initial discussion, but identify what is provisional: stackup, BOM, quantity, test method or delivery target. Ask the quotation to list its assumptions. Production should use an approved revision after open engineering questions and sourcing decisions are closed.
For fabrication, include layer data, drill information, a clear outline, material and copper requirements, finish and critical tolerances. For assembly, add the BOM, placement data, drawings, variants and supplied-part details. For programming or test, define the required files, interfaces and acceptance results.
Share files through the agreed route
The local project inquiry records your requirements and contact details. Use the file-submission route linked from the contact page when files are required, or agree a transfer method with the project contact. Identify the revision and contents of the package so a recipient can detect missing or conflicting files.
Before sharing confidential design information, establish any required handling agreement and access restrictions. Send a manifest with the final package, remove superseded exports from that package and retain a copy of exactly what was released. A later change should be issued as a clearly identified revision.