Request for Information (RFI) in Procurement: The Complete Canadian Guide with Templates

What is a request for information (RFI) in Canadian public procurement?

A plain-language definition of an RFI

A request for information is a structured way for a public organization to ask suppliers about products, services, capabilities or market conditions. It is generally used to learn and plan, not to select a supplier or make an award. The buyer describes an area of interest and asks questions about what may be available.

For example, a municipal team exploring a new records-management approach might ask about hosting options, implementation needs and accessibility features. The responses can help the team consider possible approaches before deciding whether to proceed with a formal solicitation.

Why public buyers issue requests for information

Early research can help a team test assumptions, identify knowledge gaps and write clearer requirements. Suppliers may describe service models, technical needs, delivery constraints or potential risks. This input can help a buyer avoid describing a solution too narrowly before understanding available options.

A planned process also gives suppliers a consistent way to share information. The buyer should explain the purpose, set response instructions and manage communications fairly. An RFI does not replace the organization’s procurement policies or appropriate advice when a specific situation raises questions.

Where the RFI fits in the procurement lifecycle

An RFI usually belongs in the planning and market-research stage, before a formal solicitation such as an RFP or RFQ. The team can review responses to refine its needs, assess whether a procurement is feasible and decide which process may be suitable. The RFI itself does not commit the organization to a purchase.

In Canadian public procurement, buyers should follow the rules and procedures that apply to their organization and the specific opportunity. Clear records of questions, communications and findings help explain how early research informed later planning. Suppliers should be told how their responses may be used and whether the process could lead to a later competition.

RFI vs RFP vs RFQ: choosing the right request for the job

What makes each request type different

The main difference is what the buyer needs from the market. An RFI gathers information. An RFP asks suppliers to propose an approach to a defined need, often with evaluation criteria that consider more than price. An RFQ asks for pricing against requirements clear enough for suppliers to quote on a comparable basis. Terminology and procedures can vary across organizations, so check the applicable procurement policy.

When to use an RFI instead of an RFP or RFQ

Choose an RFI when the team needs to learn before defining a suitable competition. Use an RFP when the need is understood but suppliers may offer different ways to meet it. An RFQ may fit when the requirements are clear and the buyer needs pricing that can be compared against them.

Ask what decision the responses must support. If the team needs to understand service models, supplier capacity or technical options, information gathering may be the right step. If it is ready to evaluate proposed solutions or priced offers, a formal solicitation may be more appropriate under the organization’s rules.

Common mix-ups and how to avoid them

A common mistake is using an RFI title while asking suppliers to submit binding prices or compete for an award. That can blur whether the process is exploratory or evaluative. Another is treating an RFP as a simple price check when the buyer needs to compare delivery approaches.

State the purpose plainly, describe whether the process could lead to a later solicitation, and explain how responses will be handled. Match the document to the maturity of the need and the decision ahead. Clear language helps the buying team and suppliers understand how to participate.

How to write a request for information: a step-by-step guide

Writing a useful request for information starts with a clear learning goal, not a lengthy document. The process should gather market knowledge while giving suppliers consistent instructions and a fair opportunity to respond. Follow your organization’s procurement policies, approval steps and records-management practices throughout.

Step 1: Define what you need to learn

Write down the decision the responses will support. Your team might need to understand service models, implementation requirements, supplier capacity or delivery risks. Identify what is known and where information gaps remain. Keep the scope exploratory: if the team is ready to evaluate suppliers for an award, use the formal process required by your organization instead.

Step 2: Plan the process, timeline, and fair treatment of suppliers

Decide who will approve the document, where it will be posted, how long suppliers will have to respond and who will manage questions. Set a reasonable timeline for useful answers. Plan to share clarifications consistently with interested suppliers, and keep a record of notices and communications. State that the exercise is for information gathering and explain whether a future competition may follow.

Step 3: Draft the document and include key elements

Use plain language and organize the document so suppliers can find instructions quickly. Include an introduction and purpose, background on the organization’s need, the scope of information sought, specific questions, response format, submission method and closing date. Explain response-length limits, optional information and how the organization may use material received. Avoid asking for detailed proposals when seeking early market insight.

Questions should be focused and open enough to invite useful detail. For a records-management service, a buyer could ask which implementation dependencies are common, what accessibility considerations to plan for and which hosting approaches are available. Ask suppliers to distinguish general information from assumptions specific to their response.

Step 4: Issue the document and manage supplier questions

Publish the document through the channel and process approved by your organization. Identify one contact for questions and set a deadline for submitting them. Share answers that could affect responses through the stated communication channel so participants receive the same information. Maintain a log of questions, answers, updates and dates to document how the process was managed.

Step 5: Review responses and document what you learned

Review submissions against the learning questions rather than treating them as bids. Group findings by topic, such as service options, implementation needs, dependencies and unresolved questions. Record the limits of the information, including gaps or differing supplier assumptions. A short findings note can show how market input informed the next planning decision without suggesting that any supplier has been selected.

Working check: Before closing the exercise, confirm that the purpose was stated, communications were recorded, responses were handled consistently and the team documented its conclusions. Follow internal policy and seek appropriate organizational guidance when a process raises legal or procurement concerns.

RFI template and checklist for Canadian public-sector buyers

This adaptable request for information template gives a buying team a practical starting structure. Tailor each field to the organization’s needs and follow its policies for approvals, publication, supplier communications and records. The template is for information gathering, not a substitute for a formal solicitation or organization-specific review.

A fill-in-the-blank template structure

Copy and complete the headings below. Keep the wording direct, remove fields that do not apply, and make the intended use of responses clear.

Title: [Topic or service area]
Organization: [Public organization name]
Purpose: [What the organization hopes to learn]
Background: [Relevant context and current information]
Scope: [Topics, needs or boundaries for this inquiry]
Questions:
1. [Question about available approaches or capabilities]
2. [Question about implementation, timing or dependencies]
3. [Question about risks, constraints or assumptions]
Response instructions: [Format, length and submission method]
Questions deadline: [Date and contact channel]
Response deadline: [Date, time and time zone]
Use of responses: [How the information may inform planning]
Next steps: [State whether a later process may be considered]

Pre-issuance checklist

Use this review before publication to catch unclear instructions and missing process details. A colleague who did not draft the document can identify confusing terms or questions that invite inconsistent answers.

• Does the purpose explain what the organization wants to learn?
• Are the background and scope accurate, relevant and understandable?
• Can suppliers answer each question without guessing what the buyer means?
• Are the submission method, deadlines and contact details complete?
• Does the document explain how responses may be used and whether a later competition is possible?
• Have required reviews, approvals and publication steps been completed?
• Is there a plan to record questions, shared answers and findings?

An illustrative example of an RFI in practice

Hypothetical learning example: A Canadian public organization is exploring options for managing digital records. Its team has not settled on a service model or detailed requirements. It issues an inquiry asking suppliers to describe available hosting approaches, typical implementation dependencies, accessibility considerations and information the organization should gather before defining its needs.

The team gives all participants the same submission instructions and records clarifications in one place. It reviews responses for themes and unanswered questions, then documents what it learned for internal planning. The exercise does not score suppliers or promise a contract. This example is educational only; for a specific procurement, consult the relevant official guidance, organizational policies and a qualified professional.

Best practices, common pitfalls, and building your RFI skills

A well-run RFI gives the buying team market insight and sets clear expectations for suppliers. Keep the purpose focused, communicate consistently and treat responses as planning information rather than offers for an award. Follow your organization’s procurement policies and approval processes. These habits support accountability and help the team decide what to do next, including when more research is needed.

Five habits that lead to useful responses

Use these habits to improve the clarity and usefulness of supplier input:

1. Ask about decisions ahead. Connect each question to a knowledge gap the team needs to resolve.
2. Use neutral wording. Avoid questions that assume a particular product, service model or supplier capability is preferred.
3. Invite relevant detail. Ask suppliers to explain assumptions, dependencies and constraints that could affect planning.
4. Keep communications consistent. Use the stated contact and process for questions, clarifications and document updates.
5. Record the learning. Summarize themes, differing views and unanswered questions, then note how the findings informed planning.

These practices help the team compare information without turning an exploratory exercise into an informal competition.

Common challenges and how to overcome them

Vague questions often produce broad answers that are difficult to use. Break a large question into a specific topic, such as implementation dependencies, service assumptions or information needed to define requirements. If suppliers seem uncertain about the process, review the purpose statement and instructions for language that could imply a future award or evaluation.

Uneven access to information can undermine confidence. Keep a communication log, share material clarifications through the stated channel and retain records of changes. If the team has concerns about supplier engagement, confidentiality, intellectual property or a possible later competition, consult the appropriate internal procurement or legal resource. The right response depends on organizational policy and the circumstances.

RFI questions answered: quick FAQ

Does an RFI select a supplier?

It is generally used to gather information, not to make an award. Explain the purpose and intended use of responses in the document.

Can suppliers share pricing?

A buyer may ask for general pricing information when it supports planning, but should distinguish estimates or market context from a formal quotation. Follow the organization’s rules and state what the response will and will not mean.

Can an RFI be followed by a competition?

A later process may be considered. Do not promise a competition or imply that participation will give a supplier an advantage. Describe possible next steps accurately and consistently.

Benefits and limits of an exploratory process

Next steps for learning Canadian public procurement

To build your skills, review your organization’s procurement policies and note how they address early market research, supplier communications and records. Identify one capability to practise, such as drafting neutral questions or documenting findings. Training can help individuals and teams develop a shared foundation in ethical procurement and contract management. Want to keep learning? Explore The Procurement School’s training programs and review the course outlines for a suitable next step.

Frequently Asked Questions

What is an RFI in Canadian public procurement?

A request for information (RFI) is a structured way for a public organization to ask suppliers about products, services, capabilities or market conditions. It is used to learn and plan, not to select a supplier or make an award. The buyer describes an area of interest and asks questions about what may be available.

How do I respond to a request for information?

Responding to a request for information means answering the buyer’s stated questions clearly and within the set timeline. Describe your capabilities, service models, delivery constraints or market knowledge as requested. Remember that an RFI is exploratory, so no award decision will be made from your response.

What is a request for information in contract law?

In contract law, a request for information is generally treated as an exploratory inquiry rather than a formal solicitation. It does not create a binding commitment to purchase or award work. Public buyers should still explain the purpose of the process, set clear response instructions and manage communications fairly.

How long is an RFI or RFP usually open for responses?

Response timelines vary by organization and the complexity of the opportunity, so buyers should set a reasonable timeline that allows suppliers to give useful answers. Simpler requests may allow a few weeks, while complex proposals often need more time. Always check the dates stated in the posted document.

When should I use an RFI instead of an RFP or RFQ?

Use an RFI when your team needs to learn before defining a suitable competition, such as understanding service models or supplier capacity. Choose an RFP when the need is understood but suppliers may propose different approaches. An RFQ fits when requirements are clear and you need comparable pricing.

Does issuing an RFI commit a public organization to buy anything?

No, a request for information does not commit an organization to a purchase. The RFI sits in the planning and market-research stage, before any formal solicitation such as an RFP or RFQ. Buyers should tell suppliers how responses may be used and whether a later competition is possible.

What is a common mistake to avoid when writing an RFI?

A common mistake is using an RFI title while asking suppliers to submit binding prices or compete for an award, which blurs whether the process is exploratory or evaluative. State the purpose plainly, describe whether the process could lead to a later solicitation, and explain how responses will be handled.