Industrial RFQ Intake Checklist: What Sales Needs Before Quoting

An enquiry can be worth pursuing before it is ready to quote. The intake process needs to tell sales which situation they have, without asking the buyer to complete the engineering work at first contact.

For an equipment manufacturer or technical supplier, the practical distinction is between enough information to assign and qualify a request, and enough information for a responsible technical quotation. A single list of mandatory fields tends to blur those stages.

Collect information when it becomes necessary

This is a proposed structure, not a universal specification. A pump, a control panel and an engineering service require different technical evidence. Have the responsible specialist approve the fields and the meaning of quote readiness.

Preserve what the buyer already sent

Keep the original enquiry, attachments, source page and stated requirements together. If the request arrived through a distributor, retain that route and the account relationship. Avoid asking the buyer to retype information the team can already inspect.

For multiple line items, keep quantities, units, requested dates and document references attached to the correct item. A summary that moves a requirement from one item to another can be worse than an incomplete record.

Make unknown values explicit. “Not supplied”, “awaiting confirmation” and “not applicable” are different states. None should be silently replaced with a plausible default.

Work through an incomplete request

Received

The buyer identifies the application and delivery location but has not confirmed the duty point or medium.

Initial decision

Sales can review commercial fit and assign the relevant application engineer. The request is not ready for equipment selection.

Next question

Ask for the missing operating conditions or arrange a technical clarification if the buyer cannot supply them.

After an attachment arrives

Compare it with the stated request, record its revision and flag any conflict. Do not assume the attachment supersedes everything else.

Readiness change

The responsible reviewer decides whether the information supports quotation and records any remaining qualifications.

The important improvement is a visible next action. The form does not need to reject a potentially useful enquiry merely because the buyer is still developing the specification.

Ask sales and engineering different questions

Can we respond?

A reply route and a description of the application are present. If either is missing, request clarification rather than inventing it.

Can we assign?

Product family, relevant territory and account relationship identify an owner, or an exception is explicitly queued.

Can we quote?

The responsible specialist has checked the product-specific requirements and resolved material conflicts. A completed form alone does not answer this question.

For a process-pump enquiry, flow, head, medium and temperature are examples of information engineering may need; they are not a complete or universally sufficient specification. Existing installation details, materials and applicable requirements may change the review. Use the short stage checklist with sales first. The detailed data contract below is for implementation, not a list of compulsory public-form fields.

Sales needs to know whether the opportunity fits, who owns the response and when the next action is due. Engineering needs the conditions, standards, interfaces and limitations relevant to technical assessment. Putting both teams' entire wish lists into the public form makes the buyer reconcile internal responsibilities.

Use the downloadable checklist as an internal review aid, then select the small subset that belongs at first contact. Do not copy every column into mandatory fields.

Explain how submitted information will be used. Treat a request for a response separately from optional future marketing. Confidential drawings or sensitive specifications may need a controlled transfer route agreed with the buyer.

Test the receiving process as carefully as the form

Submit labelled test requests with an attachment, missing context and an ambiguous route. Check the notification, CRM record and owner assignment. Confirm that corrections preserve earlier information and that retries do not create duplicate opportunities.

Then inspect authorised examples of real enquiries with the receiving team. Record clarification loops, misroutes and time spent reconstructing context. Separate wrong-fit leads from relevant requests that need more information; otherwise a stricter form can appear successful simply by discouraging early-stage buyers.

AI can help extract and prepare a draft once this process is clear. It should not fill missing requirements or decide technical suitability without authority. The reviewed enquiry workflow shows where that boundary belongs.