A useful electronics RFQ explains the product configuration, the requested work and the evidence needed to accept the result. You do not need every answer before starting a conversation, but unresolved decisions should be identified rather than hidden inside inconsistent files.
Start with a one-page project brief
State what you need delivered: bare boards, assembled boards, tested assemblies or a complete product. Include the product stage, the initial quantity, expected repeat demand and the date you are trying to meet. Separate an engineering target from a firm customer commitment. Name a technical contact and a person who can approve purchasing or scope changes.
Describe the intended environment and any mandatory product requirements. A requirement to provide a certificate or a specific record should be visible in the RFQ, with the relevant scope identified. Do not assume that a general supplier brochure establishes project suitability.
Build one controlled file package
| Input | What to make explicit |
|---|---|
| BOM | Manufacturer, full part number, quantity per assembly, reference designators, variants and approved alternatives. |
| Fabrication data | Board outline, layer and drill data, construction drawing, revision and mandatory material or finish requirements. |
| Assembly data | Placement file, coordinate units and origin, polarity, no-fit parts and assembly notes. |
| Programming and test | Release identifiers, interfaces, fixtures, acceptance limits, test data and ownership of development work. |
| Mechanical integration | Enclosure, harness, fasteners, labels, accessories, packaging and interface drawings when included. |
Use a manifest to identify the files and their revisions. Open the manufacturing exports and compare their visible contents with the design you intended to release. A filename containing “final” is not a substitute for agreement between the BOM, drawings and placement data.
Assign sourcing and acceptance responsibilities
For each material group, identify whether the supplier purchases it or the customer supplies it. State who approves substitutions, how shortages are escalated and who owns unused stock. Ask for recurring costs, setup or engineering charges, and optional work as separate items. Define whether inspection, programming, functional testing and final packaging are included.
Include an open-question register
Give each unresolved item an owner and a decision point. For example, a provisional component may be acceptable for estimating but may block purchasing until approved. An unfinished test procedure may allow a budgetary discussion while preventing a production release. Mark the RFQ as preliminary when that is the actual status.
Copy this inquiry starter
We need [deliverable] for [product stage], with an initial quantity of [quantity]. The released revision is [revision]. We can provide [files]. We need help resolving [open questions]. Please identify sourcing responsibilities, included verification, separate setup charges and the assumptions behind the proposed schedule.
Download the editable RFQ brief and blank BOM column template. These are starting documents, not evidence that a manufacturing package is complete.
Use the local BOM checker to identify missing required columns or MPN values. It does not validate electrical suitability, approved substitutions or every manufacturing requirement. Then review how to compare proposals.
Public reference: the NIST MEP supplier-scouting form also separates technical requirements, commercial needs and supporting documents. This checklist is an original project-planning aid.
Turn the checklist into a project inquiry
Share the product stage, requested deliverable, quantity and unresolved decisions. Start with the files you have and identify what still needs review.