A pump RFQ may state 304 stainless on the arrangement drawing and 316L for wetted parts in the project specification. The data sheet may show an 85 °C design temperature while the buyer’s last email mentions 65 °C. Each statement looks plausible. Choosing the easiest one can change material, seal selection, supplier cost and the guarantee in the proposal.
A clarification log should show the exact conflict, the sources and revisions, the work that can continue, the work that must wait, the approved answer and the quote items that changed afterward. That gives sales, engineering, estimating and the customer the same commercial baseline.
Open a clarification when the quote needs a decision
Create a clarification when a missing fact, conflict or unclear statement can change product selection, compliance, cost, schedule, acceptance or the customer promise. Do not create one for every blank field. A shipping contact can wait. An unspecified hazardous-area classification can invalidate the motor and electrical design.
Start with the requirement package. The NIST MEP Supplier Scouting Playbook asks buyers to state the manufacturing process, dimensions, tolerances, performance, materials, certifications, regulations, volume, target price, delivery and packaging. Those categories are a useful completeness check because each one can change whether a manufacturer can supply the item and what it will cost.
| Clarification type | Example | Decision required |
|---|---|---|
| Missing requirement | The RFQ gives no site voltage or quantity | Customer supplies the fact or accepts a stated quote basis |
| Conflicting sources | Drawing calls for 304 stainless; specification calls for 316L | Customer identifies the governing requirement |
| Unclear language | “Suitable for outdoor service” gives no temperature, enclosure or corrosion basis | Customer defines the operating conditions and acceptance rule |
| Outside product envelope | Requested duty exceeds the released pump curve | Accountable engineer approves an alternate or the team declines |
| Missing referenced document | Specification cites a customer standard that was not supplied | Customer provides the current document and revision |
| Commercially material choice | Buyer has not chosen shop test or witnessed test | Customer chooses the option or accepts separate prices |
Write the conflict so another person can decide it
State each source, location and revision. Then state the difference and the commercial or technical effect. “Confirm material” sends the engineer or customer back through the files. “Drawing P-184 Rev C note 7 calls for 304 stainless; specification 21-07 Rev B section 4.2 requires 316L for wetted parts. Material selection changes the piping BOM, corrosion warranty and supplier prices” gives them a bounded choice.
Write one decision per clarification. A question that combines material, test pressure, delivery and documentation will come back half answered. The NASA Systems Engineering Handbook requirement checklist calls for requirements that are clear, unambiguous, complete, consistent, singular and traceable. It also recommends giving each unresolved item a rationale, owner and due date. Those rules work well for customer clarifications even when the equipment has nothing to do with aerospace.
| Clarification field | What to write |
|---|---|
| Question ID | Stable identifier that remains the same across email, portal and quote revisions |
| Source A | Document number, revision, page, section, drawing zone or message date |
| Source B | The conflicting source, or the place where required information is absent |
| Decision | One question the customer or accountable internal owner can answer |
| Why it matters | Product, compliance, cost, delivery or acceptance effect |
| Proposed basis | The assumption or option the OEM will use if the customer accepts it |
| Needed by | Date and dependent task that will stop or rework without an answer |
Decide what can continue while the answer is open
Assign a treatment when the clarification opens. A hard stop blocks the affected configuration, estimate or proposal. An approved assumption lets work continue against a visible basis. A priced option keeps two valid outcomes open. A formal deviation tells the customer exactly where the offered equipment differs from the request.
Apply the treatment to dependent work instead of freezing the whole bid. Estimating can price the standard frame while engineering waits for the wetted-material answer. Supplier RFQs for piping should wait or carry both material options. The proposal should not release until the selected basis appears in the compliance statement and price.
| Treatment | Use it when | Control |
|---|---|---|
| Hard stop | The answer controls feasibility, safety, regulatory compliance or a firm guarantee | Block affected work until the accountable owner approves an answer |
| Approved assumption | The team can price a defined basis and expose it to the customer | Name the approver and print the assumption in the offer |
| Priced option | Two customer choices remain technically valid | Show scope, price and schedule for each option |
| Deviation | The OEM intends to offer a different requirement or performance level | State the requested basis, offered basis and customer acceptance needed |
| Later-order item | The fact does not affect bid scope, price, compliance or delivery | Assign a downstream owner and required date |
Send the question to the person who can answer it
The customer owns missing or conflicting customer requirements. Your engineering team owns whether an offered design can meet the selected requirement. Sales owns the customer conversation and response deadline. The bid leader owns the quote basis. Do not ask engineering to invent a customer requirement, and do not ask sales to approve a technical exception.
Route each question by decision type. Application engineering may choose a product or alternate. Quality decides whether an inspection or certification route is acceptable. Sourcing confirms supplier capability and dates. Finance or legal handles payment, warranty, securities and liability. One owner answers; other functions review only when the answer changes their work.
| Decision | Accountable answer | People who need the result |
|---|---|---|
| Customer duty or operating condition | Customer technical contact | Sales, application engineering and estimating |
| Product selection or engineered alternate | Named product or application engineer | Sales, estimating, quality and proposal owner |
| Manufacturing or inspection feasibility | Manufacturing engineering or quality | Estimator, planner and bid leader |
| Supplier capability or bought-out lead time | Sourcing owner | Engineering, planning and commercial approval |
| Contract or commercial exception | Authorized commercial, finance or legal owner | Bid leader and proposal owner |
Control the answer and its revision
Store the answer with its sender, date, channel and source message. If the customer answers by phone, send a written summary and ask them to confirm it. Label an internal interpretation as an assumption until the buyer accepts it. A confident note from a salesperson is still different from a customer-approved requirement.
A later answer should create a new revision. Preserve the earlier answer, show what changed and identify which configuration, supplier package, estimate and proposal used it. ASME Y14.35 establishes methods for identifying and recording revisions to engineering product definition data and related documents. The clarification record needs the same discipline because its answer can change that product definition for the offer.
ISO 10007 applies configuration management from concept through disposal. During quoting, that means the team should be able to identify the requirement set and approved decisions behind each released commercial configuration. The customer can reverse a choice, but the system should never make the earlier quote look as if it used the new answer.
Make the answer update the entire quote
Closing the email is the beginning of the change. Map the answer to product configuration, drawings, material, supplier RFQs, cost lines, routing, test plan, schedule, compliance matrix, warranty and proposal language. Reopen only the items that depend on the changed requirement, then require their owners to accept the new basis.
A material answer may change the BOM and supplier requests. A design temperature may change seals, instruments and test pressure. A hazardous-area classification may change motors, enclosures, wiring and certification. A witnessed test can add customer notice, hold time, travel and documentation. The impact map should use the product team’s real dependencies instead of one generic “engineering affected” flag.
| Affected record | Update after the answer | Release check |
|---|---|---|
| Configuration | Selected product, option, material and approved exception | Engineer confirms the offered design satisfies the answer |
| Supplier package | Scope, specification, quantity and required date | Supplier response uses the current clarification revision |
| Cost and schedule | Changed material, labor, engineering, test, freight and lead time | Estimator and planner approve the effect |
| Compliance and risk | Code position, test evidence, deviation and warranty exposure | Quality or accountable specialist accepts the basis |
| Proposal | Scope, assumptions, options, delivery, exclusions and customer response reference | Bid leader confirms the customer can see the agreed basis |
Worked example: two files specify different materials
A customer requests four chemical dosing skids. Arrangement drawing P-184 Rev C calls for 304 stainless steel. Project specification 21-07 Rev B requires 316L for wetted parts. The data sheet names the process fluid but does not state whether the frame and drip tray count as wetted components.
The clarification cites both sources and asks one question: “Confirm that 316L applies to piping, valves, pump wetted parts and the drip tray, while the structural frame may remain 304 stainless.” The bid leader approves a temporary basis of all-316L wetted construction for supplier pricing. The piping and pump supplier RFQs carry the clarification ID and assumption. Frame design continues without waiting.
The customer confirms the proposed split. Bourne records the email and answer date, then updates the piping BOM, pump selection, supplier comparison, corrosion statement and proposal. The estimator removes the all-316L frame allowance, reducing the quote by $14,800. The proposal cites the clarification and states the final material boundary. The team closes the item only after each affected owner accepts the revised basis.
Test the process with difficult RFQs
Use recent bids with late customer answers, conflicting drawings and specifications, missing standards, verbal decisions, revised answers and assumptions that disappeared from the final proposal. Recreate what the team knew on each date. A good test should prove that the process preserves uncertainty instead of filling it with a plausible value.
Track clarification age by owner and type, but do not reward fast closure alone. A rushed answer that never reaches the estimate creates rework later. Measure whether the final answer changed every dependent item before submission and whether the purchase order later matched the clarified quote basis.
| Measure | What it reveals |
|---|---|
| Open clarification age | Where customer or internal decisions wait |
| Questions returned for rework | Whether the original question was specific enough to answer |
| Bids released with hard stops open | Whether the review process allows unsupported commitments |
| Late quote changes from clarification | How often answers arrive after costing or approval |
| Dependent items updated before release | Whether closure changes the configuration, cost and proposal |
| PO differences tied to clarified requirements | Whether the accepted order preserves the commercial baseline |
How Bourne handles clarification work
Bourne compares the RFQ package, identifies missing and conflicting requirements and drafts a question with the source locations already attached. It routes the decision to the customer or the accountable internal owner, follows the due date and shows which quote work can continue while the answer remains open.
After approval, Bourne updates the working requirement, reopens the affected configuration, costing, supplier or proposal tasks and preserves the earlier revision. The technical clarification workflow shows that chain in the product. Engineers still make engineering decisions. Bourne handles the evidence, routing and follow-through that otherwise disappear into email.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.