An RFQ intake checklist should tell an estimator what is known, what is missing and which work can safely begin. A folder full of attachments does not answer those questions on its own. Neither does a form with every field filled in if some entries are guesses.
This guide is for the supplier receiving a request for quotation and preparing a technical offer. It is a starting point for sales engineering and estimating teams, not a procurement template for comparing suppliers. Adapt the checks to your equipment, services and approval rules.
Define the next task before deciding whether the RFQ is complete
Complete enough for an initial budget estimate can be different from complete enough for a firm technical offer. Record what the customer is asking for, and what your team has agreed to prepare. A request for a revised layout may need a different review from a request to price an unchanged design.
Then ask a practical question: which missing fact could change the next calculation or technical decision? That is more useful than treating every empty field as an equal reason to stop. A named engineer decides which gaps block work and whether a bounded assumption is acceptable. Intake prepares that decision; it does not authorise a bid or a price.
Six checks before handing the request to estimating
1. Identify the request and the response expected
Record the customer, project reference, site, contact for clarification and quotation deadline. Keep the requested delivery date separate from the date the offer is due. State whether this is a budget estimate, a firm quotation, an alternative or a revision. Link any previous quotation explicitly so an estimator knows what is being replaced or retained.
2. Establish which documents apply
List the received specifications, drawings and other relevant files with their revision identifiers. Preserve the original email or portal reference. If a message refers to a newer drawing that is not attached, record that gap. If two documents conflict, identify both sources and ask for a decision rather than silently choosing the newer-looking file.
3. Describe the technical scope and its boundaries
Capture the requested function, quantities, performance requirements and interfaces. Make supply boundaries explicit: equipment, controls, installation, commissioning or training may sit with different parties. A phrase such as “complete system” should become a question if it leaves responsibilities unclear. Product-specific checks belong here, agreed with the engineers who will use them.
4. Separate customer requirements from cost inputs
A required delivery date is a customer requirement. A supplier lead time is an input that purchasing may still need to obtain. Keep those separate. Identify the materials, labour assumptions, bought-in items and current costing references needed for the next estimate. Mark missing supplier prices or expired quotations for follow-up; do not replace them with an unlabelled figure from an old project.
5. Capture delivery and commercial constraints for review
Record the destination, installation conditions, requested milestones and commercial requirements that affect the offer. Assign questions about access, installation windows, quotation validity or payment terms to the responsible person. Capturing a requested term is not the same as accepting it. Pricing exceptions and commitments remain with the authorised commercial reviewers.
6. Give each unresolved issue an owner and a consequence
“Awaiting clarification” is too vague to hand over. Write the question, who will obtain the answer, when it is needed and which task depends on it. Distinguish the person chasing the answer from the person approving the technical interpretation. They may not be the same person.
A compact record your team can reuse
For each requirement or open point, use the following fields in your existing spreadsheet, CRM or document. This is an illustrative template, not a mandatory software format.
- Requirement or question: one specific statement, with units where relevant.
- Source: document, revision and section, or the dated customer message.
- Status: confirmed, missing, conflicting, proposed assumption or not applicable.
- Impact: the estimate, scope item or decision that depends on it.
- Owner and needed-by date: who obtains the answer and when the dependent work needs it.
- Review decision: who accepted the answer or assumption, and which work may proceed.
A proposed assumption stays visibly different from a customer-confirmed requirement. Record its limits and approval before using it in an estimate. “Not applicable” also needs a reason where omitting the field could affect the scope.
Illustrative example: the throughput requirement is unclear
Imagine a system integrator receives an RFQ for a conveyor extension. The email asks for higher throughput, while an attached layout shows connection points but gives no required peak rate. This is a fictional example, not a Cifral customer result.
The intake record links the email and layout revision, records the missing peak rate and assigns the customer question to the sales engineer. The technical reviewer identifies which equipment selection and cost calculations depend on that answer. The team may be able to check installation boundaries in parallel, but it should not present a capacity-dependent estimate as confirmed.
If the customer asks for a budget figure before replying, an engineer may propose a clearly bounded assumption for approval. The record should show the assumption, its effect on the estimate and the condition that would require recalculation. When the answer arrives, the owner updates the requirement and routes the affected work for review. Filling the gap does not automatically validate the previous estimate.
Agree what happens at handover
The estimator should receive a controlled set of inputs and a decision about the next task. Useful outcomes include proceeding with confirmed inputs, proceeding only with explicitly approved assumptions, or holding the affected work for clarification. Your team defines the criteria and who can approve each outcome.
Keep the decision to pursue the opportunity separate. A technically complete RFQ may still be a poor commercial fit. Conversely, an attractive opportunity may need clarification before estimating capacity is assigned.
What automation can prepare
A tailored workflow can capture information from agreed sources, structure a request, compare it with your checklist and prepare a list of open questions. It can also route questions and make outstanding answers visible. Engineers still validate interpretation, approve assumptions and decide whether the inputs support the next task. Commercial prices and final proposals require human approval.
The guide to RFQ automation around existing tools explains how intake can connect to later stages. Cifral Custom scopes these capabilities around your process and systems, individually or together. They are not prebuilt modules that every team must adopt.
Try the checklist on one recent request
Choose a quotation that required repeated clarification. Reconstruct what the estimator received, which missing input caused work to stop and who eventually resolved it. Add the checks that would have exposed those specific gaps. Test the revised checklist on another request before making it the default.
Record active preparation time separately from time waiting for answers. The quotation cost calculator can help explore the internal labour cost using your own figures; it does not predict savings. If you want to assess whether intake is a useful first stage to automate, book a 30-minute quotation workflow diagnostic. No preparation is required.