When one supplier prices an as-cast part and another prices a machined, leak-tested part, the two totals do not answer the same question. A comparison becomes valid only when product revision, demand, work scope, and acceptance criteria are clear to everyone.

Not everything needs to be final at first contact. It is enough to identify which data are confirmed, which assumptions still need review, and who decides each change. This distinction keeps a preliminary estimate separate from an order-ready quotation.

Define the Decision Stage Before Requesting a Price

A feasibility request, technical proposal, and order-ready quotation do not carry the same level of commitment. In feasibility work, material, geometry, or production method may remain open. In an order-ready quotation, data revision, delivery scope, exclusions, and acceptance conditions should be more explicit. State at the outset whether the response is needed for selecting a technical route, budgeting, or final purchasing.

Elgh's research on quotation processes for engineer-to-order products showed that linking design, process, and cost information supports decisions across product variants. That research examined a specific system and industrial study; this checklist is therefore a practical framework for a component RFQ, not a universal mandatory standard for every die-casting project. [1]

Describe the part application in a few sentences: installation location, contact with other components, service conditions, and consequences of failure. If the part replaces an existing product, record the purpose of the change separately—for example, reducing finishing operations, improving assembly, or correcting a defined nonconformity.

Send a Controlled Reference That Defines the Product

The product authority may be a combination of a 3D model and 2D drawing, or, in a model-based process, a 3D model carrying manufacturing and inspection information may be the primary reference. What matters is that the supplier knows which file governs and where to find dimensions, tolerances, material, surface finish, technical notes, and measurement datums.

Research by Ruemler and colleagues on model-based definition showed that required information depends on the workflow and that combined use of a model and drawing remained common in the surveyed sample. The result does not mean a drawing is always required or a 3D model is always sufficient; the practical lesson is that the product definition must be complete and interpretable for design, manufacturing, and inspection. [2]

Keep part name, code, date, and revision number consistent across files. If the model and drawing conflict, define the governing reference before the RFQ. A physical sample, photograph, or scan can supplement the data, but it does not replace a technical product definition until acceptance criteria and the controlled data revision are clear.

  1. 1Application and drawing or sample
  2. 2Requirements and demand plan
  3. 3Acceptance requirements
  4. 4Technical review
  5. 5Resolve assumptions
  6. 6Propose the production route
Educational view of the decision path; return to earlier stages when refinement is needed.Original diagram based on the stages described in this article.

Connect Critical Characteristics to an Evaluation Method

Mark sealing surfaces, bearing seats, assembly axes, threads, visible areas, and every characteristic affecting safety or function on the drawing or specification list. Phrases such as “defect-free” or “excellent quality” are not measurable. For each critical characteristic, state an evaluable value or description, inspection location, and, where necessary, test method.

Do not label every dimension equally critical. Stringency should follow function, assembly, and the inspection method. State the alloy together with its specification reference. If selection is open, describe service temperature, loads, environment, coating needs, and any heat treatment or welding, then ask the supplier for a reasoned recommendation.

Separate Firm Demand from Forecasts

List sample quantity, first-order quantity, order-batch size, and estimated annual demand separately. Label each number as firm, a planning target, or a possible scenario. Do not present a sales forecast as a purchase commitment; decisions on cavity count, capacity, and delivery planning should not rest on an unexplained optimistic number.

If the design is still changing, state the expected date for revision freeze. Also write the required date together with dependencies: drawing completion, sample approval, die readiness, or material receipt. A customer's desired date is not an agreed production schedule until capacity and the approval route have been reviewed.

Part sample during finishing; Novin Industrial Group archiveImage source: Novin Industrial Group archive

Clarify Delivery Scope and Responsibilities Line by Line

State whether the request includes product engineering, die design or manufacture, as-cast parts, machining, finishing, coating, assembly, testing, quality records, and packaging—or only part of that chain. If a die already exists, disclose ownership, location, repair history, documentation, and permission to evaluate it.

TopicInformation Required in the RFQ
Product revisionCode, revision, governing file, and approval status
Delivery conditionAs cast, machined, coated, or assembled
Sampling and approvalQuantity, records, approver, and correction route
Inspection and testingCharacteristic, method, frequency, and required report
Packaging and deliverySurface protection, pack quantity, destination, and transport responsibility

Raise leak testing, internal examination, and special documentation from the start, but do not treat their mention as confirmation of supplier capability or capacity. The technical response should classify each item as “feasible,” “requires review,” or “out of scope.”

Compare Quotation Assumptions Before the Final Number

Place responses in a common table: drawing revision, alloy, baseline volume, tooling scope, finishing operations, exclusions, sample schedule, and acceptance method. If an item is ambiguous, ask a specific question—for example, where the quotation accounts for an inspection fixture or a modification caused by a drawing change.

Archive the technical and commercial proposal with the same package you sent. Every revision should have a number and date so it remains clear which version each price and delivery date refers to. To prepare the technical route, see Product & Die Engineering capabilityandStart a Project page .

Documents to Prepare for the RFQ

  • The RFQ purpose and required response level are defined.
  • The governing file, part code, and revision number are consistent.
  • The alloy, critical characteristics, and their evaluation methods are stated.
  • Sample quantity, firm order, and demand forecast are separated.
  • Tooling, machining, testing, documentation, and packaging scope is clear.
  • Unknowns, excluded items, and the person approving changes are recorded.

Frequently Asked Questions

Can an RFQ begin without a drawing?

A preliminary feasibility review can begin with a sample, model, or application description, but the response should remain conditional on completing the product definition. Before tooling or order acceptance, the technical authority and acceptance criteria must be controlled.

Is a 3D file alone sufficient?

It may be sufficient if the 3D file is the controlled authority and carries all information needed for manufacturing and inspection. A purely geometric model usually does not fully define material, tolerances, finish, datums, and testing.

What should we state if final volume is unknown?

Separate the firm quantity from estimates and provide several realistic scenarios. Ask the supplier to state its assumptions for quantity and order size and how changes would affect the quotation.

References and Further Reading

  1. Elgh (2012) — Decision support in the quotation process of engineered-to-order products ↗Peer-reviewed industrial research on managing design, process, and cost information when preparing quotations for engineer-to-order products.DOI: 10.1016/j.aei.2011.07.001
  2. Ruemler et al. (journal 2017; online 2016) — Promoting Model-Based Definition to Establish a Complete Product Definition ↗Peer-reviewed ASME/NIST research on product-definition completeness and information needs in model-based workflows.DOI: 10.1115/1.4034625

Submit Information for Technical Review

Send the documents already available and list unresolved items separately. This distinction helps clarify the assumptions behind the review and proposal.

View the Related Capability → Send Project Information and Start a Review

Related Articles

Which Parts Are Suitable for Die Casting?Die-Cast Product and Die Design & EngineeringWhat Determines Die and Die-Cast Part Cost?

Back to All Insights →