Send each supplier the same controlled requirement package and ask for the same structured response. Keep proposed deviations separate from the baseline; otherwise different prices may describe different components.
For hardware teams preparing a custom-component quotation request using their own approved requirements. Not an engineering design or production-release document. Our review methodology →
A practical decision table
Illustrative RFQ completeness check. Replace example quantities and references with your approved requirements before issuing an RFQ.
Weak request
More useful response requirement
Why it matters
See attached files.
Acknowledge each document and revision in the issue manifest.
Prevents silently quoting different baselines.
About 5,000 per year.
Price 1,000 and 5,000 unit orders separately; annual demand is planning only.
Separates order quantity from forecast.
Tooling included?
State tooling/setup charges separately and whether they recur.
Exposes costs that change with volume.
Same quality as the sample.
Respond to drawing requirements and the agreed sample/test plan.
Makes the acceptance basis explicit.
Suggest anything cheaper.
List each deviation, requirement reference, cost and lead-time effect.
Keeps alternatives separate from compliant offers.
An RFQ—request for quotation—asks suppliers to price a defined scope. For a custom hardware component, that scope should identify what is being quoted, in which quantities, against which requirements and on what commercial basis. It is not permission to manufacture or an engineering approval.
State whether you are comparing an existing component, exploring a feasible process or pricing a proposed second source. If the design is unresolved, label the package exploratory and list the open technical questions. Do not present an assumption as an approved requirement simply to obtain a number.
Create one controlled technical baseline
Create a file manifest with document names, revisions and issue date. Ask suppliers to confirm the package they used. If a drawing, model or specification conflicts, have the engineering owner resolve the conflict and state precedence; do not ask purchasing to guess which file wins.
Identify the component, revision, material and finish from customer-approved documents.
List critical interfaces, tolerances and performance requirements, with the applicable test or inspection criteria supplied by engineering.
Identify permitted alternatives, prohibited substitutions and questions requiring approval. Require suppliers to disclose proposed process or material deviations.
Define sample deliverables, identification and the evidence needed for review. Keep sample approval separate from production authorization.
Ask for a quote that can be normalized
Specify order quantities separately from annual planning demand. Request currency, unit price at each quantity, MOQ, validity, payment milestones and lead-time assumptions. Break out tooling, setup, samples, testing and packaging rather than hiding them inside an unexplained total.
Record the delivery basis and named place. ICC explains that Incoterms® rules allocate delivery tasks, costs and risks; an unexplained shipping label is therefore not a sufficient comparison basis. Have the logistics owner clarify the applicable rule and version, and identify costs still needing a separate estimate.
Request one-time versus recurring charges and the conditions that trigger repeat charges.
Ask what starts the quoted lead time: order, deposit, drawing approval, tooling completion or sample acceptance.
Require an explicit included/excluded/not quoted response for each cost field. Blank is not zero.
Request tooling deliverables and proposed ownership/access terms as questions for written agreement; refer legal interpretation to counsel.
Worked example: replace “quote the attached enclosure”
Illustrative only: an email says “quote the attached enclosure, about 5,000 a year, best price.” One supplier prices an old drawing at a 5,000-piece order quantity; another prices the current revision at 1,000 pieces. The apparent price gap is not yet meaningful.
A more useful request identifies enclosure E-01, revision B, the controlled drawing and finish specification, and separate order quantities of 1,000 and 5,000 units. Annual demand is labeled planning information, not a commitment. It requests tooling separately, the same buyer-selected delivery basis, and a deviation list referencing each requirement.
The improved request still needs the actual approved files and delivery details. This example is a structure to adapt, not a ready-to-issue specification or a supplier quotation.
Close clarifications without changing the baseline silently
Give each question an ID, requirement reference, owner, answer and effect on cost or timing. If the answer changes the RFQ, issue a dated revision to all participating suppliers and obtain acknowledgment. Share the clarified requirement, not another supplier’s confidential pricing or proprietary proposal.
Evaluate alternatives in a separate column. Keep the original compliant offer distinguishable from an optional deviation so that engineering can decide whether the alternative is acceptable before purchasing treats it as comparable.
Run the issue check and assign the next owner
Before sending, confirm that the attachment manifest matches the files, the requested quantities are unambiguous, the response fields are complete and critical unresolved requirements have named owners. After replies arrive, transfer the responses into the comparison workbook and keep missing values visible.
RivetBridge can organize requirements your team supplies and expose gaps; this is not engineering design, product certification or production approval. Engineering owns technical acceptance, the appropriate specialists own testing and regulatory interpretation, and you approve the final purchasing commitment.
Engineering confirms the technical baseline and unresolved questions.
Purchasing confirms quantities, commercial response fields and quote deadline.
Quality confirms sample and inspection evidence requirements.
The RFQ owner checks revision acknowledgment and records every deviation before comparison.
APPLY THIS TO YOUR COMPONENT
Technical RFQ Preparation · $500–$1,000
Have drawings and requirements spread across files and emails? We can consolidate them into a supplier-ready RFQ brief, clarification list and comparison structure.