1. [Home](/)
2. [Guides](/guides)
3. How to Respond to a Government RFP: SAM.gov, Sections L and M

GuidesOctober 7, 2026

# How to Respond to a Government RFP: SAM.gov, Sections L and M

Register in SAM.gov before you submit, outline from Section L, write to Section M, acknowledge every amendment. Checked against the 2026 FAR overhaul.

## The short answer

To respond to a federal government RFP, get an active SAM.gov registration first (it’s free and renews every 365 days), then read the solicitation in this order: Section C for the work, Section M for how you’ll be scored, Section L for how to package it. Build your outline straight from L, put your page budget where M puts its weight, and keep a compliance matrix that maps every “shall” to a page. Acknowledge every amendment, upload a day early, and request a debriefing within 3 days of the award notice.

## Key takeaways

- **Registration is a gate, not a formality:** the overhauled FAR requires an active SAM registration when you submit and at award, so start it the day you decide to bid.
- **L sets the structure, M sets the emphasis:** mirror L’s volumes and numbering exactly, then size each section by the relative importance M assigns.
- **Your FAR citations may be out of date:** most agencies now run Part 15 under a model deviation with new section numbers, and a proposed rule published September 18, 2026 would renumber it again.
- **Amendments are a compliance item:** provision 52.215-1 requires you to acknowledge each amendment by the date it specifies, so log them like requirements.
- **Debriefings have a 3-day fuse:** miss the written request window and you can lose the right to one.
- **The catch:** none of this beats knowing the customer. A compliant proposal for an agency you met for the first time at the industry day rarely wins against an incumbent who shaped the requirement.

## First, check which FAR you’re reading

The FAR isn’t one stable text right now. Under the FAR overhaul (RFO) that began in 2025, the FAR Council issued model class deviations part by part, and agencies adopted them. The [acquisition.gov deviation guide](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide) dates Part 15 (contracting by negotiation) to September 30, 2025\. Part 4 came out August 14, 2025\. Part 52 followed on October 28, 2025, with an update on July 1, 2026\. Meanwhile the codified FAR on acquisition.gov still shows the old numbering under FAC 2026-01.

Formal rulemaking started in 2026\. A [proposed rule covering Part 15 and six other parts](https://www.govinfo.gov/content/pkg/FR-2026-09-18/html/2026-19162.htm) (FAR Case 2026-003) was published September 18, 2026, with comments due October 19, 2026\. It says the phase one model deviations stay operative while rulemaking proceeds, and it moves some sections again (the uniform contract format sits at 15.108 in the proposed text, versus 15.109 in the deviation).

So this guide cites the **Part 15 model deviation text** on acquisition.gov as read in October 2026, with the old FAR number in brackets where people still search for it. The practical rule: cite what’s in your solicitation. Section I and Section K list the clauses and provisions that actually apply, with their dates, and agencies such as DoD publish their own deviations.

| Topic                                     | Old FAR cite           | RFO model deviation cite           |
| ----------------------------------------- | ---------------------- | ---------------------------------- |
| SAM registration required                 | 4.1102                 | 4.203-1(b), provision 52.204-7     |
| Uniform contract format, Sections C, L, M | 15.204-1               | 15.109-1 to 15.109-4               |
| Exchanges before receipt of proposals     | 15.201(f)              | 15.101(d), 15.201(c)(1)            |
| Amending the RFP                          | 15.206                 | 15.106                             |
| Late proposals                            | 15.208, 52.215-1(c)(3) | 15.107(b), 52.215-1(c)(3)          |
| Past performance evaluation               | 15.305(a)(2)           | 15.104(b)(3), 15.202(c)            |
| Discussions and final revisions           | 15.306, 15.307         | 15.204-2 (now called negotiations) |
| Debriefings                               | 15.505, 15.506         | 15.206-2, 15.301-1                 |

## Before the RFP drops: SAM.gov and the notice

**Register early.** The [Part 4 model deviation](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-4) says offerors must have an active federal contracts registration in SAM when they submit an offer and at award, with exceptions for things like purchase-card micro-purchases and urgent sole-source awards. Provision [52.204-7](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52) tells you to allow for processing time and to put your Unique Entity ID (UEI) on the cover page of the offer, and it asks for CAGE codes for you, your immediate owner and your highest-level owner.

Two housekeeping facts save grief. [SAM.gov](https://sam.gov/content/entity-registration) says you must renew every 365 days, and [GSA states](https://content.govdelivery.com/accounts/USGSA/bulletins/358af1f) that registration is always free. Anyone emailing you an invoice to “activate” it isn’t the government.

**Watch the right feed.** The Governmentwide point of entry is SAM.gov, per the [Part 2 definitions](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-2). Under the [Part 5 deviation](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-5), presolicitation notices go up for actions expected to exceed $20,000, and for commercial buys above the simplified acquisition threshold ($350,000) there is no fixed minimum response time unless a trade agreement applies. Translation: some RFPs give you very little time, so the work starts at the draft RFP or request for information stage. RFI responses aren’t offers, but they’re where you shape requirements and get a feel for the customer.

## Read the solicitation in the order the evaluator thinks

Under the uniform contract format in the [Part 15 deviation](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-15), the parts you care about most are:

- **Section C (description, specifications, requirements):** what the contractor must do. Every “shall” here is a requirement your technical volume must answer.
- **Section L (instructions and notices to offerors):** how to submit, and often a mandated format split into volumes such as technical, management, past performance and price.
- **Section M (evaluation factors for award):** every significant factor and subfactor, their relative importance, and one of three statements about non-price factors combined: significantly more important than price, approximately equal to price, or significantly less important.
- **Section K and Section J:** representations and certifications, and the attachment list (often where the performance work statement, pricing template and past performance questionnaire live).

Read C, then M, then L. C tells you what the job is. M tells you what wins. L tells you how to wrap it. Reading L first produces a perfectly formatted proposal about the wrong things.

One exception worth knowing: the deviation says agencies don’t have to use the uniform contract format for construction and architect-engineer contracts, so federal construction solicitations often look different. The [construction prequalification guide](/guides/construction-tender-prequalification) covers that world.

## Outline from L, win themes from M

**Decision rule for the outline:** your table of contents copies Section L’s volume, section and paragraph numbering, in L’s order, using L’s words for headings. If L says “Factor 1, Subfactor 1a: Transition Approach,” that is your heading. Evaluators score with a checklist built from L and M, and you want them to find each item without hunting.

**Decision rule for emphasis:** allocate pages in proportion to M’s relative importance, then adjust for how much you have to prove. A factor described as “most important” gets the biggest share, and the price narrative gets only what L allows.

**Win themes come from M, not from your brochure.** For each M factor, write one sentence that pairs a feature with a measured benefit to this agency, then back it with a proof point (a past contract, a named person, a metric you can cite). If you can’t find proof, it’s a wish, not a theme.

## Worked example: An illustrative L/M pair, turned into an outline

Say an illustrative RFP for help desk services has this Section L: Volume I Technical, 25 pages maximum, covering Factor 1 Technical Approach (Subfactor 1a Transition, Subfactor 1b Staffing and Retention) and Factor 2 Management Approach. Volume II Past Performance: up to three contracts performed in the last five years. Volume III Price, using the Attachment J-3 pricing workbook.

Its Section M says: Factor 1 is more important than Factor 2, which is more important than past performance. Within Factor 1, the subfactors are equal. All non-price factors combined are significantly more important than price.

Here’s a defensible page budget for Volume I. Take 25 pages, hold 1 for a cover letter if L counts it (check whether it does) and 1 for an executive summary, leaving 23\. Weight Factor 1 at roughly two thirds because M puts it first: 15 pages, split 7.5 and 7.5 between the equal subfactors. Factor 2 gets the remaining 8.

| Proposal section             | Source in L | Scored under M            | Pages | Owner              |
| ---------------------------- | ----------- | ------------------------- | ----- | ------------------ |
| Executive summary            | L.4.1       | Not scored directly       | 1     | Capture lead       |
| 1a Transition approach       | L.4.2.1     | Factor 1 (most important) | 7.5   | Transition manager |
| 1b Staffing and retention    | L.4.2.2     | Factor 1 (most important) | 7.5   | HR lead            |
| 2 Management approach        | L.4.3       | Factor 2                  | 8     | Program manager    |
| Past performance (Volume II) | L.5         | Third in importance       | Per L | Contracts          |
| Price (Volume III)           | L.6, J-3    | Price                     | Per L | Pricing analyst    |

Then the compliance matrix. Each row is one requirement, with a source paragraph you can cite back:

| Req ID | Source      | Requirement (paraphrased)                               | Proposal location      | Owner              | Status       |
| ------ | ----------- | ------------------------------------------------------- | ---------------------- | ------------------ | ------------ |
| L-07   | L.3.2       | 12-point font, 1-inch margins, tables may be 10-point   | All volumes            | Desktop publisher  | Template set |
| L-14   | L.4.2.1     | Describe transition within 30 days of award             | Vol I, 1a.2            | Transition manager | Draft 1      |
| C-22   | C.5.3       | Contractor shall staff Tier 1 from 7 AM to 7 PM Eastern | Vol I, 1b.1            | HR lead            | Not started  |
| M-03   | M.2.1       | Transition evaluated for risk of service disruption     | Vol I, 1a.3 risk table | Transition manager | Draft 1      |
| K-01   | K, 52.204-7 | UEI on cover page                                       | Vol I cover            | Contracts          | Done         |

Every C requirement should land in a row tied to the L section that answers it, and every M subfactor should point at the paragraph where the evaluator will find your strength. The [compliance matrix guide](/guides/rfp-compliance-matrix) goes deeper on column design, and the [requirement extractor](/tools/rfp-requirement-extractor) can give you a first pass at pulling “shall” statements out of a PDF.

## Page limits, Q&A and amendments

**Page limits** are whatever L says, and L also says what counts: covers, tabs, résumés, tables and font sizes in figures. Read those lines twice. Pages beyond a limit are a gift to the evaluator who wants an easy reason to stop reading.

**Questions go to the contracting officer.** The deviation makes the contracting officer the focal point for inquiries from prospective offerors after release (15.201(c)(1)), and if information needed to prepare proposals goes to one offeror, it has to be made public no later than the next general release (15.101(d)). Ask early, ask in writing, cite the paragraph, and propose the answer you’d like. The [clarification questions guide](/guides/rfp-clarification-questions) has wording that gets real answers.

**Amendments change the rules mid-game.** Under 15.106, each amendment states its number and date, describes the change and gives any revised closing date. Provision 52.215-1(b) says terms not amended stay unchanged and that you must acknowledge receipt of each amendment by the date and time it specifies. Keep an amendment log with four columns: amendment number, date, what changed, and where your proposal now reflects it. Then re-run the compliance matrix against it.

**Late is late.** Under 15.107(b) and 52.215-1(c)(3), a proposal received after the exact time is late and won’t be considered unless it arrives before award, accepting it wouldn’t unduly delay the acquisition, and one of a few exceptions applies. The electronic exception requires receipt at the Government’s initial point of entry by 5:00 PM one working day before the due date. If L names no time, the default is 4:30 PM local time at the receiving office. Set your internal deadline a full working day early, and treat portal outages as your problem until proven otherwise.

## Past performance: Write for an evaluator who also reads CPARS

The deviation requires past performance to be evaluated in every competitive source selection unless the contracting officer documents why not (15.104(b)(3)). The RFP must let you identify similar contracts, including federal, state, local and private sector work, and describe problems you hit and how you fixed them. Offerors with no relevant record can’t be rated favorably or unfavorably on it (15.202(c)(1)).

Evaluators don’t rely on your write-up alone. The [Part 42 deviation](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-42) names CPARS as the official source for past performance information and tells agencies to use evaluations within 3 years of completion (6 years for construction and architect-engineer work). You get 14 calendar days to comment on each evaluation of your own work, so answer them. A rebuttal you wrote last spring is part of today’s proposal.

In the narrative, pick references that match M’s definition of relevance (scope, size, complexity), state the outcome with a number the customer would recognize, and own any problem before the evaluator finds it in CPARS. If teaming partners carry part of the work, their contracts may count, so collect their past-performance records on the same schedule as your own and keep the contact details current.

## Clarifications, negotiations and revisions

The overhauled Part 15 changes the vocabulary, which matters when you read your RFP:

- **Clarifications** (15.202(a)(2)) let the government resolve minor errors or ambiguities. They can’t be used to revise your proposal or cure a deficiency. Answer exactly what was asked.
- **Competitive range** (15.204-1) is the group of proposals the contracting officer picks for further negotiation, and it can be narrowed for efficiency.
- **Negotiations** (15.204-2, formerly discussions) must at least tell each offeror in the range about its deficiencies and significant weaknesses. They don’t have to cover every improvement.
- **Proposal revision** (15.204-2(d)) is the closing round: a written revision, equal time for everyone, and notice that award will follow without further revisions. Teams still call it a final proposal revision or BAFO; the [BAFO guide](/guides/bafo-best-and-final-offer) covers pricing moves at that stage.

If the RFP says award may be made without negotiations, believe it. Your initial proposal is probably your only proposal.

## Debriefings: Ask within 3 days, arrive with questions

Under 15.206-2, an offeror excluded before award can request a preaward debriefing in writing within 3 days of the exclusion notice. Under 15.301-1, you can request a postaward debriefing within 3 days of the award notice, and it should happen within 5 days of the request where practicable.

At a minimum you’re owed the government’s evaluation of significant weaknesses or deficiencies in your proposal, the overall evaluated price and technical rating for you and the winner, past performance information on you, the overall ranking if one was developed, a summary of the award rationale, and reasonable answers about whether the agency followed its own procedures. For DoD awards over $100 million, a redacted source selection decision document is included. You won’t get point-by-point comparisons with other offerors.

Also note: accommodating an untimely debriefing request doesn’t extend protest deadlines. If a protest is even a possibility, talk to counsel the day the award notice lands.

Bring three questions: which strengths the evaluators credited, which weaknesses drove the rating, and what the winner’s proposal did better at the factor level. Then update your library and your win themes before the next bid.

## State and local RFPs are a different rulebook

Everything above is federal. The [Part 1 deviation](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-1) describes the FAR as the acquisition regulation for executive agencies, supplemented by agency regulations. State, county, city and school-district buyers write their own codes: registration portals, bid bonds, protest windows and debriefing rights all vary, and many use sealed bids opened in public rather than negotiated proposals. The habits transfer (outline from instructions, write to the evaluation criteria, track addenda), but check each rule in the solicitation itself. Running a [bid/no-bid check](/guides/rfp-bid-no-bid-decision-framework) before you commit saves a lot of weekends.

## Where software helps (and where it doesn’t)

**US GovCon capture-to-proposal is a specialist lane, and the specialists earn it.** If federal bids are your main pipeline, start with tools built for that workflow:

- [GovDash](/govdash) runs one workflow across BD, capture and proposals, with compliance tracking and integrations to GSA eBuy, SharePoint, Slack and Microsoft Teams.
- [Rohirrim](/rohirrim) has a Shred-to-Comply feature that maps Sections L, M and C into a downloadable compliance matrix, plus long-form technical drafting from your own corpus.
- [Sweetspot](/sweetspot) pairs an opportunity engine over federal award data with shredding of Sections C, L and M into a compliance matrix with owners and status. It connects to GovWin (with your own Deltek account) and ingests GSA eBuy notices on request.
- [VisibleThread](/visiblethread) shreds RFPs into a traceable requirements matrix, flags long sentences and passive voice, and connects to SAM.gov and GSA eBuy.
- [AutogenAI](/autogenai) suits long-form narrative bids, with Storyboard drafting from solicitation requirements and Project Inputs that keep win themes in front of every section.

**General response tools help with the reusable parts:** corporate capability statements, résumés, quality and security boilerplate, and past performance write-ups you reuse across bids. A library-first platform like [Loopio](/loopio) or [Responsive](/responsive) does that well for teams that answer commercial RFPs too. The [RFP response software hub](/rfp-response-software) and the [govcon tag](/tags/govcon) list the rest.

**What no tool does:** decide whether to bid, read an agency’s real priorities from an industry day, price against an incumbent, or write a win theme you can prove. Those are judgment calls. And if you bid two federal jobs a year, a spreadsheet compliance matrix and a disciplined amendment log are honestly enough.

## Sources

- [FAR Overhaul (RFO) home page](https://www.acquisition.gov/far-overhaul), Acquisition.gov (GSA), accessed October 2026
- [FAR Overhaul: FAR Part Deviation Guidance](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide), Acquisition.gov, accessed October 2026 (part issuance dates)
- [FAR Overhaul: Part 15](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-15), Acquisition.gov, accessed October 2026 (uniform contract format, evaluation factors, amendments, late proposals, negotiations, debriefings)
- [FAR Overhaul: Part 4](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-4), Acquisition.gov, accessed October 2026 (SAM registration at offer and award)
- [FAR Overhaul: Part 52](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52), Acquisition.gov, accessed October 2026 (52.204-7, 52.215-1)
- [FAR Overhaul: Part 5](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-5), Acquisition.gov, accessed October 2026 (notice thresholds and response times)
- [FAR Overhaul: Part 2](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-2), Acquisition.gov, accessed October 2026 (GPE at SAM.gov, simplified acquisition threshold)
- [FAR Overhaul: Part 42](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-42), Acquisition.gov, accessed October 2026 (CPARS, 3 and 6 year windows, 14-day comment period)
- [FAR Overhaul: Part 1](https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-1), Acquisition.gov, accessed October 2026 (FAR applies to executive agencies)
- [FAR Part 15, Contracting by Negotiation (FAC 2026-01)](https://www.acquisition.gov/far/part-15), Acquisition.gov, accessed October 2026 (old section numbering)
- [Federal Acquisition Regulation: RFO Parts 8, 12, 13, 15, 38, 44 and 51; Proposed Rule](https://www.govinfo.gov/content/pkg/FR-2026-09-18/html/2026-19162.htm), Federal Register Vol. 91 No. 180, September 18, 2026, accessed October 2026
- [FAR Council releases second round of FAR overhaul proposed rules](https://www.nixonpeabody.com/insights/alerts/2026/09/25/far-council-releases-second-round-of-far-overhaul-proposed-rules), Nixon Peabody, September 25, 2026, accessed October 2026 (deviations remain operative during rulemaking)
- [Entity Registration](https://sam.gov/content/entity-registration), SAM.gov (GSA), accessed October 2026 (365-day renewal)
- [Don’t Take the Bait: Beware of Misleading Marketing, Imposters, and Phishing](https://content.govdelivery.com/accounts/USGSA/bulletins/358af1f), GSA, May 4, 2023, accessed October 2026 (registration is free)

Table of Contents

- [The short answer](#the-short-answer)
- [Key takeaways](#key-takeaways)
- [First, check which FAR you’re reading](#first-check-which-far-youre-reading)
- [Before the RFP drops: SAM.gov and the notice](#before-the-rfp-drops-samgov-and-the-notice)
- [Read the solicitation in the order the evaluator thinks](#read-the-solicitation-in-the-order-the-evaluator-thinks)
- [Outline from L, win themes from M](#outline-from-l-win-themes-from-m)
- [Worked example: An illustrative L/M pair, turned into an outline](#worked-example-an-illustrative-lm-pair-turned-into-an-outline)
- [Page limits, Q&A and amendments](#page-limits-qa-and-amendments)
- [Past performance: Write for an evaluator who also reads CPARS](#past-performance-write-for-an-evaluator-who-also-reads-cpars)
- [Clarifications, negotiations and revisions](#clarifications-negotiations-and-revisions)
- [Debriefings: Ask within 3 days, arrive with questions](#debriefings-ask-within-3-days-arrive-with-questions)
- [State and local RFPs are a different rulebook](#state-and-local-rfps-are-a-different-rulebook)
- [Where software helps (and where it doesn’t)](#where-software-helps-and-where-it-doesnt)
- [Sources](#sources)

[Summarize with ChatGPT](https://chatgpt.com/?q=Summarize%20this%20article%3A%20https%3A%2F%2Frfp-software-tools.com%2Fguides%2Fhow-to-respond-to-a-government-rfp)[Summarize with Claude](https://claude.ai/new?q=Summarize%20this%20article%3A%20https%3A%2F%2Frfp-software-tools.com%2Fguides%2Fhow-to-respond-to-a-government-rfp)[Summarize with Perplexity](https://www.perplexity.ai/?q=Summarize%20this%20article%3A%20https%3A%2F%2Frfp-software-tools.com%2Fguides%2Fhow-to-respond-to-a-government-rfp)

Share this article

## Related articles

[**RFP Compliance Matrix: How to Follow Every Buyer Instruction**How to build an RFP compliance matrix: shred every shall and must, track formatting and submission rules, and run a final compliance pass before you submit.RFP Software Tools · October 7, 2026](/guides/rfp-compliance-matrix)[**How AI RFP Software Drafts Answers and Prevents Hallucinations**How AI RFP tools draft from approved content, cite each claim, flag thin evidence, and route those questions to a person before you submit.RFP Software Tools · October 7, 2026](/guides/how-ai-rfp-software-prevents-hallucinations)[**RFP Clarification Questions: How to Ask, Track and Re-Check**How the RFP Q&A window works, why every bidder sees your question, how to phrase questions that don't leak strategy, and what to do after each amendment.RFP Software Tools · October 7, 2026](/guides/rfp-clarification-questions)[**RFP Version Control: Managing Drafts Without Losing Edits**How to run version control on an RFP response: one source of truth, naming rules, section locks, freeze points, a version log and how to recover a lost edit.RFP Software Tools · October 7, 2026](/guides/rfp-version-control)