Give your estimator an RFQ they can assess.

Preserve the received email, attachments and later clarifications as separate sources. Give each a received date, a recognisable reference and its relationship to the request. A revised drawing may change one dimension without replacing the buyer’s delivery instructions or every line in the spreadsheet.

Name the person preparing the request and the estimator who will accept it for pricing. Preparation can expose a conflict; it cannot resolve that conflict on the buyer’s behalf. Keep the original wording available beside any normalised description so the estimator can check what changed.

Start a question record with a request identifier, line reference, source location, question, status and person responsible for the answer. Use statuses that describe knowledge: unresolved, answered by the buyer or internal assumption awaiting approval. “Reviewed” alone says little about what is known.

Separate the request received from the quotation eventually sent. If a new revision arrives, record which prepared brief and quote version may be affected. The quote follow-up guide continues from the issued version; a later buyer message should not silently rewrite what was originally offered.

First confirm identity. Keep the buyer’s description and code alongside your internal reference. A similar product or familiar description is not approval to substitute. If the match is uncertain, state what needs confirmation and who has authority to accept it.

Then check quantity and unit together. Pieces, packs, metres and kilograms are different quantities; a number without its unit is not ready for pricing. Keep any conversion visible, including pack size, cut length or weight assumption, rather than leaving it inside a formula.

Check the specification and revision. Capture dimensions, material, finish, tolerance and the controlling document where these affect the quote. Do not add requirements simply because a similar previous order used them. A missing tolerance is a question if it matters to feasibility or price.

Separate the quote submission deadline from the requested delivery date. Establish whether delivery means dispatch, arrival or a phased requirement. Record the location and any sequence that affects capacity or freight, without promising a date during preparation.

Finally, identify the commercial questions: currency, validity, payment terms and any requested condition that requires approval. Technical acceptance and price approval may sit with different people. The record should show those decisions separately so a complete-looking line does not bypass either review.

Group questions by line item, followed by those affecting the whole request. Include the conflicting text or document reference, explain the choice that needs resolving and ask for a specific answer. “Please clarify the tube quantity: 24 lengths of 3 m, or 24 m total?” is easier to resolve than “The quantities are unclear.”

Keep internal tasks out of the buyer’s question list. Asking the estimator to confirm a machining allowance is different from asking the buyer which drawing controls. Assign an owner and a due date to each internal decision so it does not disappear while waiting for an external answer.

Where the team chooses to quote with an assumption, record its approver and the quote revision carrying the qualification. An internal assumption is not buyer agreement. The customer-facing quote must make the relevant condition clear through the company’s approval process.

Recheck the whole request after a material answer. A quantity change can affect lead time, freight or price approval. Close the individual question, then identify the dependent decisions that need another review rather than treating a completed checklist as permanent clearance.

Start with the inbox, document storage and product records your team already uses. A workflow can collect attachments, extract proposed line items and prepare this question record with source references. The estimator receives a traceable brief and unresolved questions, with technical acceptance, prices and customer commitments kept with the authorised people.

Test the brief manually with a recent request you are authorised to use. Give the prepared record to a colleague without explaining it. Ask them to trace a quantity to its source, identify the controlling revision and find who owns each open question. Add any context they can obtain only by asking the preparer.

The AI workflow selection guide helps decide whether that preparation is repeatable enough to commission on its own. Include conflicting documents and missing attachments in the acceptance tests, and include estimator review and exception time in the cost estimate.

AI-assisted extraction still needs task-specific review. The NIST AI Risk Management Framework offers a voluntary risk-management framework; it does not certify an RFQ output or replace the company’s technical acceptance and pricing responsibilities.