Request for information: scoping a supply market before you specify

The questions only the market can answer

Useful information requests ask about constraints rather than prices: what part envelopes the process comfortably handles, which material grades are routinely run, what minimum quantities apply and why, what tooling would typically be required and roughly what it involves, what the normal approval sequence looks like, and which of your draft requirements the supplier would push back on. That last question is the most valuable and the least asked. Suppliers see the impractical requirement immediately and will usually say so at this stage, when nothing is at stake commercially. Ask also what typically goes wrong on parts of this type, since the answer maps the failure modes you will spend the programme managing.

Being honest about where you are

Suppliers allocate effort according to how real an opportunity appears. Presenting an exploratory enquiry as an imminent award gets you fast answers and a reputation that costs you on the next round. Say plainly that this is a scoping exercise, give the approximate timing of any real decision, and describe the volume honestly even where it is embarrassingly small. Firms that decline at that point were never going to be your supplier, and firms that engage anyway are telling you something useful about how they view a relationship. Reputation in a specialised process community travels quickly, and a buyer known for speculative enquiries gets slower answers on the round that matters.

What you must not ask for at this stage

Detailed pricing on an undefined part invites a number the supplier will later revise upward, and anchors your internal expectations on a figure with no basis. Full technical proposals are equally unfair, since serious proposal work has a real cost and asking for it speculatively burns goodwill. Keep the effort proportionate: a short set of questions answerable by a knowledgeable person in an hour. Where a rough order of magnitude is genuinely needed, ask for it as such, state that you understand it is not a quotation, and do not treat it as one later.

Turning responses into a specification you can defend

The output of this stage is not a shortlist; it is a better requirement. Responses tell you which of your draft constraints are ordinary and which are exotic, where the minimum quantity cliff sits, what the tooling commitment implies for the business case, and how long the approval path really is. Those findings should be fed back into design and into the programme plan before the enquiry is written. Skipping that loop is how programmes arrive at quotation with a specification the market cannot serve economically. Record what changed in the requirement as a result, because that record justifies the stage to anyone who saw it as delay.

Where the information request is a formality worth skipping

Not every category needs one. Where the part is a standard catalogue item, where your team has bought this process repeatedly, or where an existing supplier could answer the same questions in a conversation, a formal round adds delay without adding knowledge. The stage earns its place when the process is new to your organisation, when the geography is unfamiliar, when the volume sits near a threshold that changes how the work would be done, or when a technology choice remains genuinely open. In those cases a short technical conversation with two or three known plants gives you the same picture in a fraction of the elapsed time.

Frequently asked questions

How is an information request different from an enquiry for pricing?

The information request asks what is possible and under what constraints; the pricing enquiry asks what a defined part costs. The first assumes your specification is still moving and treats supplier feedback as an input to it. The second assumes the specification is fixed and treats supplier responses as comparable offers. Running the second while the specification is still fluid produces prices that change once the design settles, and destroys any basis for comparing suppliers fairly.

Do suppliers take an information request seriously?

They respond in proportion to how genuine and how proportionate the request appears. A short, specific set of questions from a buyer who explains the stage and the timing usually gets thoughtful answers, because suppliers want to shape a specification they will later quote against. A long questionnaire demanding detailed data for an unnamed project with no timeline gets a marketing brochure, which is a reasonable response to an unreasonable request.

Should the information request be sent to suppliers you would never use?

Include firms you are unlikely to award to only where they hold knowledge you lack, and be clear about it. Sending to a wide list purely to appear thorough wastes their time and yours, and the responses from unsuitable firms will distort your picture of what is normal. A better use of breadth is to include one or two suppliers using a different process route to the one you assumed, since the most valuable finding at this stage is often that your assumed route is not the sensible one.