The customer replies to your request for clarification: “Price Level 2 only. All eight are there.” That settles which floor to quote. It says nothing about the color. But once the email thread is marked handled, both questions can look closed to the next person who opens the request.

An RFQ clarification queue tracks each open question on a request for quote, who owns the follow-up, and what the answer changes. For building-products manufacturers, it shows which work can start and which part of the estimate still has to wait.

The technical RFQ intake checklist helps you spot what’s missing. Here’s how to handle what happens after you ask.

Give each RFQ question its own status

Send the buyer one email where practical, but track one entry per question. The buyer shouldn’t get three separate emails from your team, and one reply shouldn’t close three entries.

Give each entry just enough detail that another person can take over:

  • Question and source. Say what needs confirming and point to the drawing, specification section, or message that raised it. If two documents disagree, keep both references and ask which governs the quote.

  • Owner and next follow-up. Give one person responsibility for getting the answer. Set the next follow-up based on when estimating needs the decision, not just when the quote is due.

  • Status and answer. Start with open or waiting on customer. When a reply arrives, save it with the RFQ and update only the questions it actually answers. Mark an ambiguous reply for review rather than treating it as confirmation.

  • Effect on estimating. Record what can proceed, what is blocked, and who made that call. The person following up with the customer may not be the person who can make the estimating decision.

Write questions the customer can answer without reconstructing your review. Instead of “Please clarify Level 2,” ask “Does this quote cover all eight compartments on Level 2 only, or should it include Level 1 as well?” Number the questions so a short reply has something to refer back to.

Work through a partial reply

Take North Hall, a fictional building-products RFQ. The quantity sheet calls for eight compartments, but the drawing package shows two floors, and the color hasn’t been confirmed. The coordinator sends one email with two numbered questions: whether the quote covers Level 2 only or includes Level 1, and which color to price.

The customer confirms the quote is for Level 2 only and all eight are on that floor. The coordinator saves that reply with the RFQ, records the answer against the floor-allocation question, and leaves the color question open. The color entry keeps its owner and next follow-up date. Nobody has to read the whole thread to see what the customer did and didn’t answer.

Now the estimator makes a separate call. For this request, they can start checking the Level 2 layout and hardware quantities. The color may affect price or lead time, so they hold color-dependent pricing and don’t release a firm quote. The coordinator can tell the buyer exactly what the team still needs without asking about Level 2 again.

The handoff could be as short as this: Level 2 only, eight compartments, confirmed in the buyer’s Tuesday reply. Start layout and hardware review. Hold color-dependent pricing and firm quote release. Quoting coordinator to follow up on color tomorrow morning.

Decide what can start before every answer is in

An open question doesn’t always mean the entire RFQ has to sit. It does mean the estimator should make the boundary clear.

  • Hold the estimate when the missing answer can change the product configuration, quantities, or scope enough to invalidate the work.

  • Start the unaffected work when an estimator can separate it from the unresolved part. Name what can move ahead and what still can’t be priced or released.

  • Proceed without the detail only when the estimator confirms it isn’t needed for this estimate. Write down why. If the team sends budget pricing based on an assumption, label it as budgetary and make the assumption visible to the buyer. Don’t present it as a firm quote.

Your process may require a full hold. For example, Twin City Fan’s representative quote guide asks reps to reply in the existing email thread identified by its quote request number and pauses work while required information is outstanding. Set the rule for your team and leave it visible on the request.

Keep the customer’s reply with the RFQ

A queue is useful only if the next person can check what the buyer actually said. In Vsimple, a coordinator can forward a reply to the RFQ record’s email address to log it in the activity stream. When the Outlook integration is connected and a message from the thread is already on the record, later replies can sync there too. The team still decides which question the reply resolves and whether the estimate can move.

Try it on the next RFQ that arrives with two open questions. Send one follow-up, track the questions separately, and record the estimator’s decision before you hand the work over. If a teammate can pick up the request without asking you what’s still missing, the queue is doing its job.

See how Vsimple supports RFQ intake for manufacturers.

Share this article: