How to respond to a government RFI
Short answer: A government request for information (RFI) is market research: the agency wants to learn what's available, what it costs and how industry would approach a need before it writes a solicitation. Under the FAR, RFIs are used when the Government doesn't presently intend to award a contract, and responses aren't offers. Respond anyway when the work fits you: answer every question in the agency's order, show relevant capability and past performance, give realistic ranges if asked about price, suggest requirements that would help the agency get a better outcome, and mark proprietary information. A good RFI response shapes the RFP you'll later bid on.
Who this is for: business development, capture and solutions teams at companies selling to federal, state and local government.
On this page
- What is a government RFI for?
- What is the agency really deciding?
- What should a government RFI response include?
- RFI response outline
- Example answers, annotated (fictional vendor)
- What should you leave out?
- How Iris helps
- FAQ
What is a government RFI for?
The FAR encourages early exchanges of information between government and industry and lists RFIs among the techniques, alongside industry conferences, one-on-one meetings, presolicitation notices, draft RFPs, preproposal conferences and site visits (FAR 15.201(c)). Per FAR 15.201(e), RFIs may be used when the Government doesn't presently intend to award a contract but wants price, delivery, other market information or capabilities for planning, and responses aren't offers and can't be accepted to form a binding contract. RFIs are also one of the market research techniques in FAR 10.002(b)(2). State and local agencies use RFIs the same way, under their own rules.
| Notice | Main question for the agency | Covered in |
|---|---|---|
| Sources sought | Who can do this? Should it be set aside? | Sources sought guide |
| RFI | What's possible, how would you approach it, what does it cost? | This page |
| Draft RFP | Is the solicitation clear and workable? | Comment like an RFI; detail on the draft text |
| RFP / RFQ / IFB | Who should get the award? | Government RFP guide |
What is the agency really deciding?
| The RFI asks | What the agency is likely deciding | How to answer |
|---|---|---|
| "Describe your capabilities" | Whether enough capable vendors exist; which to invite to talk | Specific capabilities mapped to their need, with proof |
| "Describe your recommended approach" | How to write the statement of work | A practical approach, with trade-offs explained |
| "Provide rough order of magnitude (ROM) pricing" | The budget and contract type | Ranges and the assumptions behind them |
| "What contract vehicle would you use?" | Whether to use an existing vehicle | Vehicles you hold, and others that would work |
| "What risks do you see?" | Where the requirement could fail | Candid risks and mitigations |
| "Comment on the draft requirements" | What to change before the RFP | Specific edits with reasons |
What should a government RFI response include?
- Cover page: RFI number and title, company name, UEI and CAGE (federal), size status under the stated NAICS, point of contact.
- Executive summary: two to four sentences: who you are, why you're relevant, the one thing the agency should take away.
- Answers to every question, numbered as the RFI numbers them.
- Relevant experience: two or three similar efforts.
- Approach and assumptions, if asked.
- ROM pricing, if asked, with assumptions, clearly labelled as non-binding estimates.
- Recommendations on requirements, evaluation or contract type, if invited.
- Proprietary markings on any page containing confidential information, using the legend the RFI specifies. If it gives none, you can adapt the proposal legend in FAR 52.215-1(e): a restriction notice on the title page that lists the restricted pages, and a matching legend on each of those pages.
Stay within the page limit and file format. If the RFI offers a one-on-one meeting, ask for one in the response.
RFI response outline
| Section | Length guide | Owner |
|---|---|---|
| Cover page | 1 page | BD |
| Executive summary | 1/4 page | Capture lead |
| Answers to RFI questions (in order) | Most of the page budget | SMEs, solution architect |
| Relevant experience | 1–2 pages | Capture lead |
| ROM pricing and assumptions (if requested) | 1 page | Pricing |
| Recommendations | 1/2 page | Capture lead |
| Attachments (capability statement, if allowed) | As allowed | BD |
Example answers, annotated (fictional vendor)
A fictional state agency issues an RFI for a case-management system. A fictional vendor, "Northfield Civic Software," answers two questions.
Q4. Describe how your solution would integrate with the State's existing identity provider.
Northfield supports SAML 2.0 and OpenID Connect single sign-on and has integrated with [identity provider] at two state agencies ([agency], [agency]) since [year]. (①) For the State, we'd recommend SAML with group-based role mapping so the State keeps control of access in its own directory. (②) Typical integration effort is [x] weeks, assuming the State provides a test tenant and metadata in week one. (③)
Q9. Provide a rough order of magnitude cost for a five-year implementation.
ROM (non-binding): $[x]M to $[y]M over five years, for [x] named users. (④) The range depends mainly on (a) the number of legacy data sources to migrate (we assumed [x]) and (b) whether the State wants a configurable public portal (included in the high end). We'd be glad to refine this after a one-on-one session. (⑤)
Annotations: ① capability plus where it's been done; ② a recommendation the agency can put in the requirement; ③ an estimate with the assumption that drives it; ④ a labelled, non-binding range; ⑤ the cost drivers, which help the agency budget and invite a follow-up conversation.
What should you leave out?
- Marketing brochures in place of answers. Evaluators want the question answered.
- Requirements that only you can meet, unless they genuinely serve the agency. Agencies notice wired suggestions, and competitors will challenge them later.
- Firm prices or commitments you aren't ready to honor. Label estimates as estimates.
- Unmarked proprietary information. Assume anything unmarked may be shared.
- Claims you can't support (certifications, authorizations, past performance). They'll be checked when the RFP comes.
How Iris helps
- Cited answers to RFI questions: upload the RFI as PDF, Word or Excel; Iris extracts the questions and drafts each answer from your approved answers and documents, linking every draft to its source.
- Gaps flagged, not filled: where your documents don't support an answer (an integration you haven't done, a certification you don't hold), Iris returns "There is not enough information to answer the question."
- RFP Analyzer summarizes the RFI and pulls out the response deadline, contacts and requirements, each cited to the page.
- GovSpend Opportunities (beta) surfaces public-sector opportunities, including federal opportunities, matched to your company inside Iris; the full feed requires a GovSpend license.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered, or an RFI you've already submitted.
FAQ
Is responding to a government RFI worth it?
If the work fits you, usually yes: you can influence the requirement and become known to the program office. If you couldn't credibly bid on the resulting RFP, skip it.
Is my RFI response binding?
No. Under FAR 15.201(e), RFI responses aren't offers and the Government can't accept them to form a contract.
Should I include pricing in an RFI response?
Only if asked, and as a labelled rough order of magnitude with assumptions.
Will the agency share my RFI response with competitors?
Agencies generally protect information marked proprietary, but follow the RFI's marking instructions and don't include anything you can't risk disclosing.
How is a government RFI different from a commercial RFI?
Government RFIs follow procurement rules, are posted publicly, and feed a formal solicitation. For commercial RFIs, see how to respond to an RFI.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
