RFI template procurement
Use an RFI when your organization needs to understand the market before defining a formal competition. A clear RFI template procurement document helps you ask suppliers consistent questions, record what you learn and plan a fair next step.
Key Takeaways
- An RFI helps your organization learn about the market before launching a formal competition.
- Using a consistent set of questions lets you gather supplier information fairly and compare responses with confidence.
- Documenting what suppliers tell you gives you a solid foundation for planning the next step in your procurement process.
- A well-structured template keeps your team organized and supports a fair, transparent approach from the start.
This guide explains the purpose of an RFI, how it differs from other solicitation types and how to prepare a document that supports accountable decisions. An RFI gathers information; it does not replace your organization’s policies or the official rules that apply to a procurement.
What is an RFI in procurement, and when does a Canadian public body use one?
A plain-language definition of a request for information (RFI)
A request for information, or RFI, is a structured way for a public organization to learn about available products, services, suppliers or delivery approaches. The organization describes a need and invites suppliers to share information. It can use responses to develop its understanding before deciding whether, and how, to issue a formal solicitation.
An RFI is generally for learning, not selecting a supplier or awarding a contract. Its neutral questions should focus on what the organization needs to understand, such as available features, implementation considerations, service models or market capacity.
RFI vs. RFP vs. RFQ vs. RFB/ITT: what each stage is for
These documents serve different purposes. The right choice depends on how clearly the organization has defined its need and what it is asking suppliers to provide. Terms and processes can vary by organization, so confirm definitions in the applicable procurement policy before preparing a solicitation.
| Document | Main purpose | Typical use |
|---|---|---|
| RFI | Gather market information | Explore options while the need or solution is still being defined |
| RFP | Invite proposals against stated requirements | Assess proposed approaches and other disclosed evaluation factors |
| RFQ | Request quotations | Seek pricing for defined goods or services, subject to the stated process |
| RFB/ITT | Invite bids or tenders | Request submissions against specified requirements and terms |
When an RFI makes sense before a solicitation
Consider an RFI when the team cannot yet describe the requirement in enough detail to prepare a useful competition. A municipality exploring digital permitting, for example, may need to learn about system capabilities, data migration, accessibility and support models before setting requirements. If the need and specifications are already clear, an RFI may add an unnecessary step.
Fair-competition basics: talking to suppliers before an RFP without crossing a line
Plan supplier engagement so participants have the same opportunity to understand the request and provide information. Use written questions, consistent deadlines and a shared method for issuing clarifications. Keep communication records and avoid giving any supplier an advantage in a later competition. Check your organization’s rules and the trade-agreement requirements that apply; the appropriate process depends on the organization and procurement.
Free RFI template for procurement (download)
What the free download includes
A useful starting document gives the team a consistent structure without assuming every procurement has the same requirements. It can prompt you to state the background and purpose, describe the inquiry’s scope, ask clear supplier questions, set response instructions and explain how the information will be used. Adapt each section to your organization’s policies, project context and applicable rules.
Use the RFI template procurement as a drafting aid, then confirm its wording reflects the actual process. A template cannot determine whether an RFI is appropriate, establish trade-agreement obligations or replace review by the responsible procurement team.
Available in Word and PDF formats
Choose an editable Word document when your team needs to tailor headings, questions and instructions. A PDF can be useful for sharing a fixed version for review. No verified download file or format link is available here, so this page does not provide a downloadable Word or PDF attachment. Before distributing a template, identify its owner and version date so staff can check they are using the current approved document.
For structured learning on public procurement, explore Procurement Training. Individual. Its progressive curriculum covers planning, solicitation, award and evaluation, helping learners build context for preparing procurement documents.
How to build your RFI document step by step
Start with the decision the team needs to make after reviewing supplier input. That purpose guides the background, scope, questions and response instructions. A well-organized RFI template procurement draft helps colleagues review the same information and keeps the file record understandable.
-
Step 1: Write a clear statement of need and context
Describe the service or operational challenge without prescribing a solution prematurely. Include relevant context, such as the users affected, current process and intended outcomes. Separate known requirements from open questions so suppliers can tell what is fixed and what the organization is exploring.
-
Step 2: Define the scope of your inquiry
State which topics are in scope and which are not. If exploring software, you might ask about functions, integration, implementation and ongoing support, while excluding detailed pricing if the team is not ready to compare cost. A defined scope helps suppliers prepare focused responses and limits irrelevant material.
-
Step 3: Draft supplier questions that produce comparable answers
Ask specific, neutral questions and use the same prompts for each respondent. Request concise descriptions of capabilities, dependencies, delivery assumptions and limitations. For measurable details, specify the unit or format. Avoid asking suppliers to solve an undefined problem at length; answers should be practical to review and compare.
-
Step 4: Explain the response format, timeline, and how information will be used
Set out the submission method, deadline, contact point and any page or file requirements. Explain whether the organization may publish clarifications, how it expects to use responses and whether the RFI could lead to a later solicitation. Do not promise confidentiality or future procurement steps unless authorized by your organization’s policies and applicable rules.
Before release, use this short review checklist:
- Does the document explain the information the team needs to learn?
- Are questions consistent, neutral and within the stated scope?
- Are response instructions and key dates easy to find?
- Have the responsible staff reviewed fairness, record-keeping and applicable requirements?
For a guided next step, review Procurement Training. Individual alongside your organization’s official procurement resources. Training can help new practitioners build confidence with planning and solicitation tasks, while organizational policies remain the authority for a specific process.
Annotated RFI template walkthrough for municipalities, agencies, and institutions
Use the sections below to make an RFI understandable to suppliers and useful to your team. The notes are illustrative drafting guidance, not approved clauses or legal advice. Adapt wording to your organization’s procurement policy, records practices and applicable requirements. A consistent document helps staff explain why information was requested and how the inquiry was designed.
Introduction and background section: what to say about your organization
Identify the public organization issuing the request, the department or program leading the work, and a contact for questions. Give enough background for suppliers to understand the operating context, such as the service area, user groups or current process. Avoid sensitive operational details that respondents do not need to prepare useful answers.
Scope and objectives section: stating what you want to learn
Describe the subjects on which the organization is seeking input, then distinguish them from matters outside the inquiry. Objectives might include understanding available service models, implementation dependencies, accessibility considerations, integration needs or support arrangements. State what the organization knows and which assumptions remain open. This gives suppliers a clear boundary and helps prevent the inquiry from becoming an informal request for a complete proposal.
Be precise about the level of detail requested. If the team is exploring broad approaches, ask for concise information about options and conditions rather than detailed designs based on an incomplete specification. Clear objectives also help reviewers decide whether a response addresses the question.
Supplier information request section: capability, experience, and capacity questions
Ask questions that help the team understand supplier capabilities without treating the answers as a scored competition. Useful topics include relevant experience, delivery approach, staffing assumptions, service coverage, technical requirements, implementation risks and known limitations. Ask for context behind claims, such as the type of work performed and the supplier’s role, rather than unsupported statements of excellence.
Use common prompts and response fields so submissions can be reviewed consistently. Ask each respondent, for example, to identify prerequisites, dependencies and typical client responsibilities for an implementation. Make space for suppliers to explain where an answer depends on project scope. Avoid requesting information unrelated to the stated objectives or that your team has no plan to review.
Market and cost context section: gathering pricing and market signals without commitments
If cost information will help with planning, explain the detail sought and the assumptions respondents should use. You might ask suppliers to identify common cost categories, factors that affect price or information needed to prepare a future estimate. Label requested figures as indicative planning information, not a quotation or offer, if that reflects the organization’s intent. Do not imply that a response creates a purchase commitment.
Ask respondents to identify exclusions, dependencies and variables that could change an estimate. This helps staff interpret figures that rely on different assumptions. Check internally before requesting commercially sensitive details, and follow your organization’s direction for receiving, handling and retaining supplier information.
Terms, conditions, and disclaimer clauses commonly used by public bodies
Include clear instructions for the response deadline, submission method, question process and changes or clarifications. Explain how the organization expects to use the information and whether it may inform future planning or a later solicitation. State that the RFI is not itself a contract or promise to proceed, if consistent with the approved process. Do not promise confidentiality or a particular procurement outcome unless authorized.
Clauses about records, intellectual property, costs of responding, amendments and cancellation may also need attention. Their wording and effect depend on the organization’s rules and circumstances. Have the appropriate procurement, legal, privacy or records staff review terms before release. If you are building confidence with these document choices, Procurement Training. Individual offers a learning route for people developing public procurement knowledge. Review Procurement Training. Individual alongside your organization’s policies, which govern the specific process.
From RFI responses to a stronger RFP: a worked example
An RFI is useful when the team can show how supplier input informed its next decisions. Treat responses as market information, not a ranking exercise. Organize material against the questions asked, record where answers differ and note assumptions that affect interpretation. This provides a traceable basis for refining requirements and moving from early research to a later solicitation.
Organizing supplier responses for comparison
Start with a response log recording the supplier, submission date and questions answered. For each topic, summarize the response neutrally and reference the relevant page or section of the original submission. Record unanswered questions, differing terminology and stated dependencies rather than filling gaps with assumptions. If clarification is needed, follow the process described in the RFI and document the question and response. This helps staff distinguish supplier statements from their own analysis.
A hypothetical example: turning RFI findings into a requirements matrix
Hypothetical example: A public organization is exploring a scheduling service for several community facilities. Responses indicate that suppliers describe user access, reporting and implementation in different ways. The team groups findings by topic, then decides what must be a clear requirement, what should remain open to proposed approaches and what needs more internal definition. The matrix below shows a planning method, not a prescribed procurement result.
| RFI topic | What responses revealed | Possible RFP planning action |
|---|---|---|
| User access | Different access models and account assumptions | Define user groups and required access conditions |
| Reporting | Reports vary by configuration and included features | Describe the information and outputs the organization needs |
| Implementation | Supplier timelines depend on data preparation and staff availability | State known dependencies and invite a delivery approach |
Before drafting, confirm that each proposed requirement reflects the organization’s need rather than a single respondent’s preferred design. The matrix can flag matters needing operational, accessibility, privacy, security or budget review before release.
Recording your process so it stands up to audit and information requests
Keep the approved RFI, amendments, questions and answers, submissions, review notes and decisions together in the procurement file, following your organization’s records practices. Record who reviewed the responses, what themes informed planning and why the team changed or retained a requirement. Protect information according to applicable organizational rules, and avoid promising unconfirmed confidentiality. These records help colleagues understand the rationale and support a consistent handoff into the RFP process.
For a learning path covering planning, solicitation, award and evaluation, explore Procurement Training. Individual. Reviewing the RFI template procurement process alongside structured learning can help you build confidence in documenting decisions and preparing the next stage. Consult your organization’s policies and official procurement resources for direction on a specific file.
RFI template questions and answers
Is an RFI required before issuing an RFP?
Not necessarily. Whether an RFI is appropriate depends on the organization’s policies, procurement circumstances and applicable rules. If the need is sufficiently defined, the team may plan a solicitation without first gathering market information. Check official procurement guidance and the internal approval process before deciding.
Can an RFI be used to shortlist suppliers?
An RFI is intended to gather information, not select suppliers for a contract. Do not use responses to create an undisclosed shortlist or give respondents an advantage in a later competition. If supplier qualification or shortlisting is intended, establish the process and criteria through an appropriate, clearly described procurement process under the organization’s rules.
Do trade agreement rules apply to an RFI?
Requirements can depend on the public organization, procurement and applicable agreement. Calling a document an RFI does not settle whether a particular rule applies. Ask responsible procurement staff to review the circumstances and consult relevant official Canadian government or jurisdictional guidance before release.
How long should an RFI response period be?
Set a period that gives suppliers reasonable time to understand the request and prepare a useful response. Consider the document’s complexity, information requested, known deadlines and applicable policy or trade-agreement requirements. State the closing date, time and submission method clearly, then manage changes through the process described in the RFI.
Frequently Asked Questions
What is an RFI for procurement?
An RFI, or request for information, is a structured way for a public organization to learn about available products, services, suppliers or delivery approaches before deciding whether to run a formal competition. It is generally for market research, not for selecting a supplier or awarding a contract.
When should a public body use an RFI instead of an RFP?
Use an RFI when your team cannot yet describe the requirement in enough detail to prepare a useful competition, such as when exploring digital permitting options. If your need and specifications are already clear, an RFI may add an unnecessary step and an RFP or RFQ is likely more appropriate.
What is the standard format for an RFI document?
A standard RFI includes a background and purpose statement, the scope of the inquiry, clear supplier questions, response instructions and an explanation of how the information will be used. A good RFI template procurement draft keeps these sections consistent so colleagues can review the same information and the file record stays understandable.
What should be in an RFI checklist?
A practical RFI checklist covers stating the decision the team needs to make, describing the need and context, defining which topics are in and out of scope, drafting neutral questions that produce comparable answers, setting consistent deadlines and confirming the document aligns with your procurement policies and trade-agreement requirements.
How do you write a good RFI?
Start with the decision the team needs to make after reviewing supplier input, then describe the challenge without prescribing a solution prematurely. Separate known requirements from open questions, keep the scope clearly defined and ask specific, neutral questions using the same prompts for every respondent.
How can you talk to suppliers before an RFP without unfairness?
Plan supplier engagement so every participant has the same opportunity to understand the request, using written questions, consistent deadlines and shared clarifications. Keep records of all communication, avoid giving any supplier an advantage in a later competition and treat the RFI as market research, not an informal evaluation.
Can I download a free RFI template for procurement?
Templates are often available in editable Word and fixed PDF formats, though a template is only a drafting aid that must be adapted to your organization’s policies and applicable rules. Before distributing any template, identify its owner and version date so staff use the current approved document.