Resolve a supplier technical question by identifying the exact requirement in doubt, assigning the decision to its technical owner, and returning an approved answer that the supplier can use. Keep the question open until its effect on the quote is understood. An engineer replying internally does not mean the supplier has a complete or current offer.
The technical clarification register and handoff template (Excel) connects the supplier's question, technical decision, released requirement, and revised commercial response. Use it for RFQ-stage questions about drawings, specifications, testing, packaging, or material requirements. Supplier selection and technical acceptance remain with the authorized people.
Turn a vague question into a reviewable issue
Start with the RFQ identifier and revision, line, supplier, document title and revision, and the precise feature or requirement being questioned. Capture the supplier's wording and source message. Attach only the documents the reviewer needs to understand it.
Ask what prevents quotation: missing information, an apparent contradiction, an unclear acceptance requirement, or a proposed deviation. A supplier asking whether a tolerance applies before or after coating needs a different answer from one proposing a wider tolerance to reduce cost.
Record the consequence in operational terms. Is the supplier unable to price tooling, confirm yield, estimate lead time, or quote the requested material? This helps the technical owner understand why the question matters and which answer would unblock the offer.
If the question lacks a document reference, request one before forwarding a general “please clarify” message to engineering. The buyer can help make the question precise without deciding its technical substance.
Distinguish clarification from a requirement change
A clarification explains the existing approved requirement. A change alters the requirement. A supplier deviation offers something different from it. Keep those distinctions in the record rather than treating every answer as permission to modify the RFQ.
For example, identifying which drawing revision applies may resolve a document-control question. Changing the specified material, dimension, inspection method, or acceptance criterion may require engineering and quality review. The appropriate process depends on the company's ownership rules and the purchase; a buyer should not infer approval from an informal suggestion.
When the technical owner determines that the requirement should change, capture the approved replacement and the scope of its use. It may apply to this RFQ, a specific prototype batch, or a permanent specification revision. An exception for one order should not silently become a general supplier instruction.
Keep the original question, original requirement, and approved disposition. That history explains why the supplier's later quote differs from the first request.
Assign one accountable owner and the necessary reviewers
The owner is the person responsible for producing the next usable answer, not everyone copied on the email. Identify the decision role: design engineering for a drawing requirement, quality for an acceptance-document question, or the material owner for a specification issue. Involve purchasing when the decision changes cost, timing, or supplier eligibility.
Set a due time based on the sourcing decision and the supplier's remaining preparation work. If the supplier needs two working days to reprice tooling after the answer, a response on the quote deadline is already late for that plan. Make that dependency explicit rather than asking engineering to prioritize an unexplained urgent request.
The buyer coordinates the handoff and supplier communication. The technical owner decides the technical question. The supplier confirms what it can offer against the answer. The buyer then evaluates the resulting commercial choice. Keeping those jobs separate prevents a technical reply from being mistaken for an award.
If the owner cannot meet the date, ask for a credible next step and impact. The buyer may need to change the sourcing schedule or pursue another approved option. Do not forward an unreviewed technical guess to keep the conversation moving.
Give the reviewer a bounded decision packet
A useful packet fits the question on one page and links the supporting documents. Include the current requirement, exact supplier question, proposed alternative if any, why it blocks the quote, deadline, and requested form of answer.
RFQ / revision / line / supplier:
Document / revision / feature or requirement:
Current approved requirement:
Supplier's precise question:
Supplier's proposed deviation, if any:
What cannot be quoted until this is answered:
Answer needed by / supplier preparation time afterward:
Technical owner / required reviewers:
Requested disposition: clarify / revise / reject deviation / more evidence
Approved wording or released document required:
Ask the owner to state whether the response changes the requirement, which document now governs, and whether it applies to other suppliers. “Looks okay” leaves the buyer to invent those answers. If acceptance depends on a test, sample, or certificate, record who evaluates that evidence and when the supplier must provide it.
For repeat questions, link the earlier approved answer only after checking its scope and revision. A decision about an old material grade or prototype batch may not apply to production.
Control who receives the answer
Keep internal discussion separate from the message intended for suppliers. An engineering thread may contain cost assumptions, confidential designs, or comments about another supplier. Send the approved answer and relevant released documents, not the entire internal exchange.
Where the answer clarifies a requirement common to participating suppliers, have the buyer distribute the substantive clarification consistently under the sourcing process. Do not reveal the originating supplier's confidential offer or proprietary method. If the response is specific to that supplier's proposed deviation, record why the communication scope differs.
Oracle's online messaging documentation shows that negotiation messages can reach selected recipients or all participants. Recipient scope is therefore something to verify before sending, not infer from the thread title. Oracle online messages.
Check attachment access as the intended recipient would experience it. A released drawing behind an inaccessible link does not resolve the supplier's question. Record the version sent, recipients, date, and evidence of receipt or access where the process requires it.
Reopen the commercial comparison when scope changes
If the approved answer changes material, processing, quantity, testing, or documentation, ask the supplier to confirm its effect on price, lead time, validity, and exceptions. Do not combine an old price with a newly accepted specification unless the supplier confirms that combination.
Oracle's amendment workflow illustrates this distinction: an amended negotiation can require suppliers to acknowledge the changes and resubmit responses. Use the equivalent controlled process in your own environment. Oracle negotiation amendments.
A clarification that changes no requirement may still affect supplier assumptions. Ask whether the existing offer remains valid against the clarified basis. Retain the answer with the quote version so the award reviewer knows what was priced.
Check the decision timetable again. A re-quote can shorten the period available for approval. If necessary, open a quote-validity action rather than letting an answered technical question leave an expired commercial offer behind it.
Worked example: a coating question changes the offer
In this illustrative example, an RFQ requests 800 sleeves to drawing S-18 revision C. The supplier asks whether a diameter tolerance applies before or after coating. It cannot confirm its finishing process or price until that point is resolved. Its preliminary indication is $15 per sleeve, expressly subject to the answer.
The buyer records the drawing feature and routes the question to design engineering, with quality reviewing the acceptance implications. Engineering confirms that the tolerance applies after coating and releases an explicit note under the company's document process. The buyer sends the approved clarification to the affected suppliers without forwarding the internal discussion.
Supplier A then quotes $15.40 per sleeve plus a $160 fixture charge for the clarified requirement. Its total is 800 × $15.40 + $160 = $12,480. The preliminary indication was 800 × $15 = $12,000, but it was conditional and incomplete. The $480 difference is a change from an indication to a complete offer, not automatically a supplier overcharge or a procurement loss.
Supplier B quotes $15.55 per sleeve with the same fixture scope included, totaling $12,440. Both offers now refer to the clarified requirement. If both meet the other mandatory conditions, the buyer has a $40 outlay difference to consider alongside timing and commercial terms.
The technical question closes when the approved clarification is released, received, and reflected in the responses. Supplier selection remains open until the buyer makes and records the decision. If either supplier proposes a different tolerance instead, that offer returns to technical review; the buyer cannot erase the exception to make the prices comparable.
Handle unanswered and conflicting responses
If two internal reviewers disagree, record the conflict and route it to the designated decision owner. Do not send both views as if the supplier should choose. A supplier-selected interpretation can create an order nobody intended to place.
If the supplier's revised quote still uses the old revision, request correction and retain the old response as superseded. If it acknowledges the revision but adds an exception in a footnote, send that specific exception for review. A new document number alone does not prove the issue is resolved.
If the answer depends on a test or sample that is not yet complete, describe the offer as conditional and identify the remaining acceptance step. Technical uncertainty should remain visible at the buying decision. It should not be converted into a false “approved” state merely because a price has arrived.
Close the loop and measure the source of delay
Use separate timestamps for supplier question received, complete packet assigned, approved answer released, supplier receipt, and revised response obtained. Measure internal decision time separately from supplier repricing time. Otherwise the team may blame suppliers for days spent waiting on its own answer.
Count open questions with an owner and a specific next action, and review questions reopened because the answer was ambiguous or the wrong revision was sent. State the population and period when reporting completion rates. Ten answered questions from one RFQ do not mean ten sourcing events were completed.
Closure needs an approved disposition, the released wording or document, the recipient record, and evidence of the supplier response it enabled. The RFQ template can prevent recurring omissions, while the quote follow-up process tracks the remaining commercial gaps.
Mandel's sourcing and quoting work can coordinate this loop and bring the precise question to its owner. Technical judgment stays with the team; the operational work is making sure that judgment reaches the supplier and becomes a usable offer.