Request for Information

A company knows it needs a new warehouse system but has not decided which features or delivery model are realistic, so it asks several suppliers about capabilities and implementation timelines before writing a formal specification. New Zealand government procurement guidance calls an RFI a market-research tool and distinguishes it from a request for offer under its rules, which is a public-procurement requirement and not automatically a rule for private buyers elsewhere.

US federal acquisition guidance says RFIs may seek market information for planning and that responses under that rule are not binding offers, which is also specific to its legal setting. State the purpose by telling suppliers whether the buyer is testing feasibility, building a shortlist or preparing a later tender, and avoid suggesting an award is imminent if it is not.

Ask clear questions, since capabilities, certifications, locations, integration methods, lead times and indicative price models may be useful, but questions should inform the decision, not create unnecessary paperwork. Provide enough context, such as expected volume, locations and constraints, without disclosing sensitive internal data beyond the approved purpose.

Separate facts from marketing, because a supplier's claim that it supports an integration can be checked in a demo or reference later and an RFI response is not independent verification. Use consistent evaluation by summarising answers against the same needs and marking unknowns, so that a polished brochure does not outrank a specific, verifiable answer.

Set a reasonable deadline, since a detailed response takes effort and a timeline that is too short may mean the buyer hears only from incumbents or vendors with generic material ready. Clarify confidentiality and use, because suppliers may share proprietary approaches while the buyer may need to compare options, and state how responses will be handled.

Avoid premature price precision: indicative ranges can help budget, but a real quote needs defined scope and terms, so do not treat an RFI estimate as a binding offer. Invite a relevant market cross-section, since known vendors may not show every alternative, and record clarifications, because if one vendor receives material new information a fair process may require giving the same detail to others, particularly in regulated procurement.

An illustrative RFI response coverage measure is suppliers answering a key question with specific evidence divided by suppliers responding, so if six of eight do, coverage is 75%, though it does not rank solution quality. Plan the next step, as an RFP, tender, demo or pilot may follow if the need remains, while in some private purchases the buyer might stop after learning the market cannot meet the budget.

Distinguish RFI from RFP, since an RFP usually asks for a proposal against a defined requirement and an RFI helps shape that requirement, although local terminology can vary. Set ownership, because procurement, operations, security and finance may need to review different answers and one person should coordinate the comparison and decisions.

Respect supplier effort by not requesting a full custom design merely to collect free consulting without a real procurement intent, and scope questions to what the buyer genuinely needs at this early stage. Preserve the record by saving the issued questions, answers, clarifications and version dates; for owners, an RFI reduces uncertainty before a formal purchase and works when it asks focused questions and does not mistake early market claims for final commitments.