How to respond to a government RFP (federal, state and local)
Short answer: To respond to a government RFP, first confirm you're eligible and registered (for US federal bids, active in SAM.gov when you submit), then read the instructions and evaluation criteria before anything else: in federal RFPs those are Section L and Section M. Build a compliance matrix that maps every "shall" to where you answer it, ask questions before the deadline, write to the evaluation criteria in the order the RFP asks, acknowledge every amendment, and submit exactly as instructed. Government evaluators score what the solicitation says they'll score, and a late or non-compliant proposal is often not evaluated at all.
Who this is for: proposal managers, capture leads, sales engineers and small-business owners responding to federal, state, county, city or education-sector RFPs.
On this page
- How is a government RFP different from a commercial one?
- How do federal, state and local RFPs differ?
- How do you read Sections L and M?
- What are the steps to respond?
- Example: answering an evaluation factor (fictional bidder)
- Pre-submission checklist
- How Iris helps
- FAQ
How is a government RFP different from a commercial one?
| Commercial RFP | Government RFP | |
|---|---|---|
| Rules | Buyer's preference | Statute and regulation (FAR for federal; state procurement codes) |
| Evaluation | Often informal | Stated factors, weights and method in the solicitation |
| Format | Flexible | Prescribed: page limits, fonts, volumes, file names |
| Questions | Ask your contact any time | Formal Q&A by a deadline; answers published to all bidders |
| Late submission | Sometimes accepted | Usually rejected |
| After award | Little feedback | Debriefs (federal) and public records requests are common |
How do federal, state and local RFPs differ?
| Topic | Federal | State | Local (city, county, school district) |
|---|---|---|---|
| Rulebook | FAR plus agency supplements (for example DFARS) | Each state's procurement code and rules | City or county code; often state law minimums |
| Where posted | SAM.gov Contract Opportunities | State procurement portal | Own website, regional portals, newspapers |
| Registration | SAM.gov registration, with a Unique Entity ID, at the time of offer (FAR 4.1102) | State vendor registration | Local vendor registration, sometimes none |
| Common forms | Representations and certifications (Section K), SF 33 or SF 1449 cover forms, amendment acknowledgments | Non-collusion affidavits, tax and insurance certificates, state-specific certifications | Notarized forms, bid bonds for construction, references |
| Evaluation | Tradeoff or lowest price technically acceptable, stated up front (LPTA vs best value) | Usually weighted scoring; cost points often formula-based | Weighted scoring or lowest responsive bid |
| Preferences | Small business set-asides and socioeconomic programs | In-state, small or diverse business preferences vary by state | Local business preferences common |
| Cooperative buying | GSA schedules, GWACs | State contracts open to local agencies | Piggyback and cooperative contracts |
Rule of thumb: the solicitation document overrides any general guidance, including this page. Read it end to end before planning.
How do you read Sections L and M?
Federal solicitations under FAR Part 15 use the uniform contract format (FAR 15.204-1). Two sections drive your proposal:
- Section L, "Instructions, conditions, and notices to offerors": how to structure and submit (volumes, page limits, formats, what goes where).
- Section M, "Evaluation factors for award": what will be scored and how much each factor matters. FAR 15.304(e) requires the solicitation to state whether non-price factors combined are significantly more important than, approximately equal to, or significantly less important than price.
Use this worksheet for each evaluation factor:
| Section M factor / subfactor | Relative importance | Section L instruction (volume, page limit) | PWS/SOW paragraphs it relates to | Our proof (past performance, staff, method) | Owner |
|---|---|---|---|---|---|
| Technical approach | Most important | Vol I, 25 pages | PWS 3.1–3.6 | [Method, tools, staffing] | SE lead |
| Management approach | Second | Vol I, 10 pages | PWS 4.0 | [Org chart, QA plan] | PM |
| Past performance | Third | Vol II, 3 references | All | [Contracts] | Capture lead |
| Price | Less important than non-price combined | Vol III | CLINs | [Pricing] | Pricing |
When Section L and Section M don't line up, follow Section L's structure and make sure every Section M factor is visibly addressed. Ask a clarifying question if the conflict is material.
What are the steps to respond?
- Qualify the bid. Do you meet mandatory requirements, set-aside eligibility and any required certifications or clearances? Can you win on the stated evaluation method? Use a go/no-go scorecard.
- Confirm registration (SAM.gov for federal; state and local vendor portals).
- Shred the RFP into requirements and build a compliance matrix: every "shall," "must" and "will," with the section that answers it.
- Calendar every date: questions deadline, site visit, proposal due date and time zone.
- Submit questions by the deadline. Answers are published to all bidders, so ask precisely.
- Outline to Section L (or the state's instructions) and assign sections.
- Write to the criteria: lead each section with how you meet the requirement, then proof. Mirror the RFP's terms.
- Price separately as instructed; never let price appear in a technical volume if the RFP forbids it.
- Review against the compliance matrix, ideally with a reviewer who didn't write the response.
- Acknowledge every amendment in the form required, then submit early and keep proof of submission.
Example: answering an evaluation factor (fictional bidder)
A fictional state RFP for a benefits-enrollment call center scores "Approach to quality assurance (15 points)." The fictional bidder, "Stonebridge Contact Services," writes:
3.4 Quality assurance (RFP §5.2.4; evaluation criterion 3)
Stonebridge will meet the State's 90% first-contact-resolution target (RFP §5.2.4(a)) through a three-part QA program: (1) supervisors score 5 calls per agent per week against a 20-point rubric aligned to the State's script; (2) weekly calibration sessions keep scoring consistent across supervisors; (3) the State receives a monthly QA report by the 10th business day (RFP §6.1). On our current [county] contract, the same program has held first-contact resolution at [x]% for [x] months (see Past Performance Reference 2).
Annotations: the heading echoes the RFP section and criterion; the first sentence restates the requirement and commits to it; numbers are specific; the RFP section is cited in-line; the proof points to past performance rather than adjectives.
Pre-submission checklist
- [ ] Registered and active (SAM.gov or the relevant state/local portal) on the submission date
- [ ] Every compliance-matrix row marked answered, with a page reference
- [ ] Page limits, fonts, margins and file-naming rules met
- [ ] Every amendment acknowledged
- [ ] Required forms signed by an authorized person
- [ ] Price volume separate and complete
- [ ] Cover letter includes any statements the RFP requires
- [ ] Submitted before the deadline, with confirmation saved
How Iris helps
- RFP Analyzer: upload the RFP (PDF, Word or Excel) and Iris returns a summary, key dates (one click to add to Google Calendar, Outlook or ICS), contacts, scoring criteria and requirements, each cited to the page it came from. It checks each requirement against your knowledge (met, partial or likely not met, with sources) and scores your go/no-go criteria into a Go, Review or No-Go recommendation.
- Party mapping: Iris works out who "the offeror," "the contractor" and "the agency" are in a solicitation so drafts don't confuse "we" and "they."
- Drafts from your own content, with citations and a confidence label on each answer; where your documents are silent, Iris says "There is not enough information to answer the question."
- Find bids: GovSpend Opportunities (beta) shows public-sector bids matched to your company inside Iris; the full feed requires a GovSpend license.
Corelight's federal sales engineering team uses Iris for RFPs and security questionnaires: they report even straightforward RFPs used to take 60 to 90 hours, and a 360-question RFP was turned around in about 3 hours (customer-reported, from Corelight's case study). Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
Where do I find government RFPs?
Federal: SAM.gov Contract Opportunities. State and local: each state's procurement portal, city and county purchasing pages, and aggregators. Iris customers can also use GovSpend Opportunities (beta) inside Iris.
Do I need to be registered in SAM.gov to bid?
For most federal solicitations, yes: FAR 4.1102 requires offerors to be registered in SAM when the offer is submitted, with limited exceptions.
What's the difference between an RFP, RFQ, RFI and IFB?
An RFP asks for proposals evaluated on several factors; an RFQ asks for quotes; an RFI gathers information and isn't a solicitation for award (government RFI guide); an IFB/ITB uses sealed bids decided on price (ITB and ITT guide).
Can I ask the agency questions?
Yes, through the formal questions process by the stated deadline. Contact only the named contracting officer or procurement contact.
What is a debrief?
After a federal award decision, offerors can request an explanation of how their proposal was evaluated. In negotiated federal buys, FAR 15.506 requires a written request that the agency receives within 3 days after you are notified of the award, and FAR 15.505 lets an offeror excluded from the competitive range request a preaward debriefing within 3 days of that notice. Use it to improve the next bid.
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.
