Published 2026-05-18 · Practical guides · RFQ Operations
Follow Up on the Question Holding Up the Quote
Find the actual blocker, ask the responsible person and keep the production date in view.
Before sending another 'just checking in' email, read the last response. The supplier may already be waiting for something from you.
Identify what is missing
Is the request missing a drawing? Is engineering reviewing an alternate? Has the supplier promised a quote, or is the buyer deciding on an offer already received?
Write one next action with a named owner and response date. Keep the job's original required date separate. Moving the follow-up date does not move the production need.
Ask the specific question
Missing supplier response: 'Can you quote features 1 and 2 on Rev C? Please confirm a response date, or let us know which scope you cannot support.'
Missing application detail: 'The supplier needs material hardness before selecting a grade. Who can confirm it, and by when?'
Alternate awaiting approval: 'Can engineering accept the proposed assembly and the listed process changes for this job?'
Customer decision: 'Is this work proceeding? The offer expires Friday. Is the remaining decision technical, commercial or scheduling?'
Send the relevant drawing, quote or prior answer with the question so the recipient does not need to reconstruct the thread.
Escalate the affected work
If a promised response is late, contact the backup or ask whether another approved source is needed. Prioritize by the production risk, not by how many reminders have been sent.
For a partially quoted job, chase only unanswered scope. A feature already marked no quote needs another source or a closure decision, not another request for the same supplier's price.
Close the loop
Record the answer, next owner and date. Close cancelled or no-longer-needed requests rather than leaving them overdue forever.
A useful open-item list contains the job or feature, blocker, responsible person, promised response date and production need. Anyone taking over the request should be able to send the next useful message from that record.