How to Write an RFI: Market Research and Response Management

A Request for Information (RFI) helps a buyer learn about suppliers, available solutions, capabilities, constraints, and market conditions before deciding what to procure or how to proceed. Use one when market input could change the requirement, procurement route, or next research step.

For example, a facilities team that does not know whether suppliers can meet a building’s energy target could ask about technical approaches, deployment conditions, performance evidence, and planning-level costs. An RFI does not promise a purchase, a later solicitation, or an invitation to bid.

An RFI is one market research method, not a compulsory first step in every procurement. U.S. federal guidance describes RFIs as a way to gather market, price, delivery, and capability information for planning. Industry events, technical discussions, site visits, sources-sought notices, and other methods may also be appropriate. See FAR Part 10 and FAR Subpart 15.2. Other buyers should check their own rules.

What is an RFI?

A Request for Information is a document or engagement through which a buyer asks suppliers for information that helps define a need, understand solution options, assess feasibility, or plan a later procurement. It may use written responses, structured forms, supplier meetings, or technical discussions. The buyer should state what the information will be used for and what may happen next.

Use this decision test: if you cannot yet describe the realistic supplier landscape, solution categories, or important constraints, market research such as an RFI may help. If the requirement and competitive process are already clear and you are ready to request offers, a formal solicitation may be more appropriate. The RFI’s terms govern how responses are handled, and participation alone does not guarantee an invitation or award.

When should you use an RFI, and when should you skip it?

Use an RFI when a defined decision still depends on information from the market. Typical unknowns include whether a technical approach is feasible, what types of suppliers can deliver it, what implementation dependencies exist, or which performance measures are realistic. An RFI can also help the buyer learn supplier terminology so later requirements are clearer.

Before drafting, write one decision question in a planning brief. For example: “Should we refine the scope, test feasibility, or compare solution categories before choosing a procurement route?” If no plausible response could change the team’s understanding or next action, reconsider issuing an RFI. An industry day, supplier meeting, sources-sought notice, or other research method may better suit the question, subject to applicable rules.

RFI vs. RFP vs. RFQ

These names describe common procurement patterns, not universal legal definitions. Terminology and process vary by jurisdiction, organization, funding source, and solicitation. Confirm the purpose and terms of the specific document rather than inferring them from the acronym.

Document	Typical purpose	Buyer should clarify
RFI	Explore the market, capabilities, options, or constraints.	What decision will the information support, and is the response for research or another stated purpose?
RFP	Request proposals for a defined opportunity, often assessed against stated requirements and criteria.	What scope, response rules, evaluation method, and terms apply?
RFQ	Commonly request quotations, often with a defined need or pricing focus.	What items, quantities, delivery conditions, and pricing basis should be quoted?

An RFI may lead to revised requirements, more research, discussions, a later RFP or RFQ, another procurement route, or no further action. The CanadaBuys procurement glossary provides terminology examples, but its RFI entry is old and is not a complete statement of current Canadian policy.

What to include in an RFI

Make the document answerable by separating what every respondent must provide from information that is preferred, optional, or out of scope. A practical structure includes:

• Buyer and contact: identify the issuing organization and the official channel for questions.
• Purpose and background: explain the decision the research will inform and give enough context for suppliers unfamiliar with the project.
• Problem and boundaries: describe the need, scope, assumptions, dependencies, capabilities of interest, and what is not being sought.
• Questions and requested evidence: identify the answer format and any supporting evidence, examples, or references requested.
• Response instructions: state permitted file types or forms, submission channel, deadline with time zone, and the process for questions and amendments.
• Response handling: explain the intended use of responses, confidentiality or public-record conditions, and possible next steps.

Do not assume an RFI must exclude commercial information. If it supports the research decision, ask for a price range, cost drivers, estimated delivery, savings assumptions, or financing options. State whether these are planning estimates or binding quotations. FAR guidance permits requests for price and delivery information for planning, and a 2021 GSA and DOE supporting presentation includes costs, savings, and financing among its considerations.

A response matrix makes answers easier to compare. For each question, include a requirement ID, buyer question, response type, evidence requested, and required status. Use the same core prompts for all respondents, with a clearly marked optional section for additional relevant information.

How to write an RFI step by step

Build questions from the decision need, not by copying a generic RFP. For each proposed question, record what answer could change in the buyer’s understanding or next action. Remove questions that do not support a decision.

1. Define the decision. List unresolved questions and name the owner who will use the findings.
2. Explain the problem. Give suppliers enough organizational and project context to respond without guessing at the need.
3. Set the boundaries. State assumptions, dependencies, capabilities of interest, exclusions, and known constraints.
4. Design comparable questions. Specify response types, requested evidence, required or optional status, and whether estimates are permitted.
5. Publish the process. Set the submission route, deadline and time zone, contact for questions, amendment method, and possible next steps.
6. Review before release. Have the appropriate procurement owner check clarity, equal access to information, response handling, and consistency with applicable rules.

How to collect and review RFI responses

Use a controlled intake process whether submissions arrive through a procurement portal, a monitored inbox, or another channel named in the RFI. The channel should feed a designated system of record, such as the organization’s approved procurement record or document repository. The workflow below is a proposed operating model, not a claim that a particular product provides a ready-made RFI integration.

1. Publish and version the RFI. Save the released document and every amendment with a version identifier. Record the deadline and time zone in the intake record.
2. Preserve each submission. Save the received file unchanged, assign a submission ID, and record supplier identity, RFI version, receipt time, and an immutable file reference. Do not replace the original with extracted text.
3. Run deterministic checks. Validate receipt time, permitted file type, required sections, units and currency where relevant, and whether the submission is a duplicate or amendment. Route failures to an exception queue.
4. Normalize answers with evidence links. Map each response to an RFI question and retain the supplier’s wording, document reference, and page or section. Separate administrative completeness from substantive review.
5. Document findings and next action. Use only review methods stated in the RFI and permitted by the applicable process. Record whether the team will refine requirements, research further, solicit, or stop.

One response record should represent one supplier submission for one RFI version. A supplier may submit an allowed amendment or supplement, so do not identify a record using only supplier name plus RFI ID. A proposed identity is RFI ID, RFI version, supplier ID, and submission sequence. Also assign an immutable submission UUID or file hash. If amendments are permitted, create a new linked record rather than overwriting the earlier submission.

{
  "rfi_id": "RFI-2026-014",
  "rfi_version": "2",
  "response_id": "SUB-illustrative-0081-02",
  "supplier_id": "SUP-0081",
  "submission_sequence": 2,
  "received_at": "2026-10-13T14:22:00Z",
  "original_file_ref": "immutable://submission/illustrative-id",
  "file_sha256": "illustrative-hash-value",
  "requirement_id": "Q-04",
  "evidence_reference": "page 6",
  "reviewer_status": "needs_review"
}

The identifiers above are illustrative. Enforce uniqueness in the database or use a transactional upsert when concurrent intake is possible. A read-then-create check can allow duplicate records when two workers process the same submission at once. Keep extracted or normalized values separate from the source file and record reviewer corrections.

Simple rules are better than AI for deadlines, allowed file types, required fields, units, and duplicate detection because these checks have explicit conditions. If AI is used later, limit it to suggesting categories, locating candidate answers, or drafting summaries for review. A human should verify the source passage and resolve uncertain or conflicting claims before exclusion, ranking, publication, or transition to a solicitation.

Use distinct review statuses so gaps are not silently interpreted as negative findings: not provided, not applicable, not verified, conflicting, and clarification requested. An assigned evaluator owns evidence review. A procurement administrator handles late, corrupted, duplicate, or incomplete submissions and records the disposition. If the process includes scoring or shortlisting, use only criteria and review methods disclosed in the RFI or otherwise permitted by the applicable process.

Proposed response-intake decision table

Trigger	Optional AI job	Validation	Action or fallback
New file received	None required	Check timestamp, file type, hash, and RFI version	Create an immutable submission record; route late or corrupted files to the procurement administrator
Required answer detected	Locate a candidate passage	Reviewer confirms wording and page or section	Link the answer to the response matrix; mark not provided or clarification requested when unresolved
Possible duplicate or amendment	Suggest related records	Use database uniqueness, hash comparison, and human confirmation	Create a linked amendment record; never overwrite the original
Conflicting claim or attachment	Flag the conflict	Evaluator compares the source documents and records status	Mark conflicting or request clarification; do not convert the conflict into a negative score automatically

Organizations considering workflow tracking can explore ClickUp setup and automation as an operational option. The page should not be read as a claim that a specific RFI template, procurement control, or integration is included.

Examples: what real RFIs can ask for

Real examples show that RFI questions can be focused and practical without becoming a request for binding offers.

• GSA and DOE building technology research: The 2021 supporting presentation grouped input into high-performance and low-carbon technologies, onsite energy generation and storage, and greenhouse-gas or carbon-reduction technologies. It considered measurable success criteria, performance, costs or savings, deployment potential, and technical risk. The practical lesson is to define comparison dimensions before collecting responses. The presentation is supporting material, not the original RFI landing page.
• NASA Orbiter placement: A verified NASA-hosted follow-up RFI asks about facilities, delivery capability, funding for preparation and transportation, organizational experience, and intended use. These prompts reveal operational readiness and logistical constraints. This document concerns Space Shuttle Orbiter placement and explicitly does not address Space Shuttle Main Engines. It is not necessarily the same as the historical PDF once cited elsewhere. Read the NASA follow-up RFI.
• FY2024 GSA building technology application: A later GSA application includes fields for technical function, deployment, performance, costs, validation, readiness, and financing. It is a separate example from the 2021 GSA and DOE material.

HubSpot also describes a Government of Canada financial-planning-software RFI and a University of Ottawa ERP integration discussion process. The cited Canada PDF now redirects, and the MERX page for the University of Ottawa example was not independently accessible during research. Treat those as reported examples, not as current, verified templates or instructions.

Common RFI mistakes to avoid

• Questions are too vague. Ask for a defined response type and useful evidence, such as deployment examples, assumptions, or cost ranges.
• Submission rules are incomplete. State the deadline with a time zone, submission channel, contact for questions, and amendment method.
• The next step sounds guaranteed. Explain possible uses of the information without promising a shortlist, later invitation, or contract.
• Responses are treated like bids without warning. Keep market research distinct from a formal evaluation or award process unless the document and applicable rules establish otherwise.
• Confidentiality is assumed. State relevant handling and public-record terms, and tell suppliers how to identify sensitive material if the process permits it.
• Missing evidence is treated as failure. Distinguish not provided from not applicable and not verified before drawing conclusions.

Procurement terminology and rules depend on jurisdiction, organization, funding source, and solicitation. Public-sector teams should confirm applicable requirements before publication. As a final measure of usefulness, document whether the responses resolved the stated unknowns and what decision changed as a result.