Section L and Section M: How to Use an RFP's Own Instructions to Build a Winning Proposal

Federal solicitations above the simplified acquisition threshold of $250,000 for negotiated acquisitions follow a standard document structure called the Uniform Contract Format (UCF), defined in FAR 15.204-1. The UCF divides a solicitation into four parts and thirteen sections, labeled A through M. Two of those sections determine more than any other whether your proposal wins: Section L and Section M.

They have separate jobs — and conflating them is the first mistake contractors make.

Section L tells you the rules of submission. Section M tells you the rules of scoring. You need both. A proposal that violates Section L — wrong page count, missing volume, wrong font — can be rejected outright before evaluation begins. A proposal that complies perfectly with Section L but ignores Section M is technically acceptable and competitively useless.

Under FAR 15.304(d), agencies are required to include price or cost to the government in every source selection. Technical quality and past performance are typically also required. FAR 15.304(c)(3) requires that solicitations disclose the relative importance of all evaluation factors — whether one factor is more important than another, or whether they're roughly equal. That disclosure is in Section M. Reading it before you write a single word of your proposal is not optional. It's the baseline.

It's also worth noting that Section L content is often a combination of agency-specific instructions and incorporated clauses — including FAR 52.215-1 (Instructions to Offerors — Competitive Acquisition), which provides standard language about proposal preparation, amendments, and late proposals. Agencies then layer their own specific instructions on top of or in place of the standard clause provisions. Always read what's actually there — don't assume the standard language applies unchanged.

One structural fact most contractors don't know: upon contract award, Part IV of the UCF — which contains Sections K, L, and M — is not incorporated into the resulting contract. Per FAR 15.204-1, the contracting officer retains Part IV in the contract file. These sections exist solely to govern the competition. Once you win, the contract is defined by Parts I-III. This is why you cannot rely on Section M language to resolve a post-award performance dispute — Section M governed the selection, not the work.

Section L is the rules of engagement for your submission. Violate them and your proposal may be rejected without evaluation — regardless of how strong your technical approach is. The GAO has repeatedly upheld agency rejections of proposals that failed to comply with Section L requirements, even when those failures were minor in the grand scheme of a 500-page submission.

Most contractors scan Section L for obvious format requirements — font size, page limits, margins — and stop there. That's not reading Section L. Reading Section L means extracting every requirement that governs your submission and converting it into a checklist before you start writing.

What to extract from Section L

The compliance matrix you build from Section L is the backbone of your proposal process. Every requirement gets a row. Every row gets a column for the proposal location where it's addressed, and a column for the person responsible. Nothing should be left unaddressed. Our guide to building a compliance matrix walks through how to build one that actually works — not just a reference document that nobody checks.

One often-missed Section L element: page limit definitions. Some solicitations count a page as one side of a standard 8.5" x 11" sheet. Others count each unique page number. Still others exclude pages containing only figures or tables. Read the definition explicitly. Misunderstanding the counting method has caused contractors to submit proposals that are technically over the page limit without realizing it — and the agency to either reject the proposal outright or simply stop reading after the stated limit.

Section M is the government's scoring rubric — made public. No other aspect of federal procurement gives you this kind of transparency into how you're being judged. Most contractors underuse it.

Under FAR 15.304, every Section M must do three things. It must identify the evaluation factors and significant subfactors that will be used. It must state the relative importance of those factors. And it must indicate whether the evaluation is conducted on a best value basis or lowest price technically acceptable (LPTA) basis. Each of those three elements changes how you should write your proposal.

The evaluation factor hierarchy

Section M organizes evaluation into factors, then subfactors. A typical best-value RFP might look like this:

The importance ranking of factors tells you where to concentrate your writing effort. When Section M says Technical is more important than Past Performance, which is more important than Price — that's telling you to go deep on your technical approach. Price still matters, but marginal technical differentiation is worth more than marginal price reduction. Invert that weighting and you've built the wrong proposal.

Pay close attention to how subfactors are weighted relative to each other. FAR 15.304(d) requires that solicitations disclose whether price is more or less important than technical factors, but agencies have flexibility in how they describe subfactor relationships. A statement like "Subfactor 1a is the most important subfactor under Factor 1" means your understanding of the requirement needs the strongest content in the technical volume — not your staffing plan, even if staffing gets more page count.

How adjectival ratings work

Most source selections use adjectival ratings to score proposals. The DoD Source Selection Procedures (updated in April 2016 and still the primary DoD guidance) defines the standard scale as Outstanding, Good, Acceptable, Marginal, and Unacceptable for non-cost factors. Understanding what differentiates those ratings tells you exactly what evaluators are looking for when they read your proposal.

The practical implication: an Acceptable rating is almost never enough to win a competitive best-value source selection. You need to demonstrate strengths — specific, evaluator-recognized advantages — to score Good or Outstanding. Section M is the document that tells you what strengths the agency is actually looking for. Build your win themes from its subfactors, not from your own view of what's impressive.

The compliance matrix is where Section L and Section M stop being two separate documents and become one integrated proposal blueprint. Most contractors build compliance matrices from Section L only — tracking whether they've followed the submission instructions. That catches disqualification risks but misses scoring risks entirely.

A full compliance matrix maps both: every Section L requirement (to avoid rejection) and every Section M factor and subfactor (to earn scores). Anything that appears in Section M but is not explicitly addressed somewhere in your proposal is a scoring gap — a place where evaluators have no evidence to give you credit.

How to build the matrix

The compliance matrix is not a document you build and file away. It should be the live control document throughout the proposal development process — updated as sections are drafted, used to run the Pink Team compliance review, and verified at the Red Team review against actual draft content. At Gold Team, the matrix should show every row green before you submit.

Section M is not just an evaluation document — it's an organizational tool. The factors and subfactors in Section M are a direct signal of what the agency wants to read about, in what order, and with what emphasis. The smartest proposal writers use Section M to design their document structure, then use Section L to validate that structure against submission requirements.

The principle: make it easy for evaluators to find the evidence they need to give you credit. Evaluators are reading dozens of proposals under time pressure. If your Section M Subfactor 1b content is buried across three different sections of your technical volume with no clear signposting, the evaluator either misses it or has to work to find it. Neither outcome serves you.

The mirror structure method

The most effective structural approach is to mirror Section M in your proposal organization. Each major section of your technical volume corresponds directly to an evaluation factor. Each subsection corresponds to a subfactor. Evaluators following Section M can move directly to the relevant section in your proposal to find the evidence for each criterion.

Some agencies specify their own required structure in Section L — and where that conflicts with a pure mirror of Section M, follow Section L. But where Section L gives you latitude in how you organize content within a volume or section, use Section M as your organizing principle.

Beyond structure, Section M tells you where to invest writing time. If Subfactor 1a (Understanding of the Requirement) is the most important subfactor, it deserves your most specific, most detailed content — not a paragraph-long affirmation that you've read the PWS. Outstanding ratings come from specific evidence: named programs, quantified performance metrics from prior work, concrete examples of how you've handled exactly this kind of requirement before.

CapturePilot's proposal tools help you track coverage across Section M subfactors throughout the writing process — so you can see which factors have strong content and which ones are thin before the Red Team finds it.

Section M will tell you which source selection method the agency is using. That single sentence — often easy to miss in a long document — changes the entire proposal strategy.

Under FAR 15.101-1, a best value tradeoff allows the agency to select a technically superior offer at a higher price, if the additional value justifies the difference. Under FAR 15.101-2, an LPTA(Lowest Price Technically Acceptable) source selection awards to the lowest-priced offer that meets the minimum technical requirements. The evaluation method is not a detail — it's the entire decision framework.

Congress has repeatedly pushed DoD to limit LPTA use. The FY2017 and FY2018 NDAAs directed DoD to restrict LPTA for specific categories, and DFARS 215.101-2-70 (effective October 2019) now prohibits DoD from using LPTA "to the maximum extent practicable" for IT services, cybersecurity services, systems engineering and technical assistance, advanced electronic testing, knowledge-based professional services, and certain training and logistics services. The FY2018 NDAA added an outright prohibition on LPTA for engineering and manufacturing development on major defense acquisition programs (MDAPs). If you're bidding DoD work in any of these categories and the solicitation uses LPTA, that could be a protest ground.

For a deeper look at pricing strategy across both source selection types, our LPTA vs. best value guide covers how to calculate a competitive price and how to position your technical approach depending on which method you're facing. CapturePilot's competitive intelligence tools can pull historical award data to help you estimate what a winning price looks like for a specific agency and contract type.

These aren't hypothetical risks. They're patterns that show up in GAO protest decisions and agency debriefs — the concrete errors that converted competitive proposals into losses.

If you've received a proposal debriefing that cited evaluation findings you didn't expect, most of them trace back to one of these eight patterns. The debrief is the government's best free consulting service — request it every time you lose. Our guide to government contract debriefings walks through how to request one, what questions to ask, and how to translate the feedback into a better proposal on your next pursuit.

Large prime contractors have proposal managers who own Section L and Section M analysis from the day the RFP drops. They build the compliance matrix, brief the writing team, and run reviews against the matrix throughout development. The approach is correct — the question is how a small business with two or three people working the proposal does the same thing.

The good news: the core discipline is not resource-intensive. Reading Section L and Section M carefully takes a few hours. Building a compliance matrix in a spreadsheet takes another few hours. Those hours pay for themselves in the proposal sections they keep from being written wrong.

Prioritizing under time constraints

When you have limited staff and a compressed response timeline, you can't apply equal effort to everything. Section M gives you the priority list. The most heavily weighted factor gets the deepest content and the most writing time. The least weighted factor gets minimum compliant coverage.

This is not a license to be thin — thin content on any factor still risks a Marginal rating, which can be disqualifying depending on the agency's evaluation approach. But it does mean that if you have six hours left before submission and an underdeveloped Technical Approach section, you spend those hours there — not polishing the Management Approach section that carries 10% of the total evaluation weight.

The contractors who develop strong Section L/M analysis skills over multiple proposals accumulate another advantage: they get better at qualifying opportunities before they commit to writing. Reading Section M on an opportunity you're considering tells you whether the agency's evaluation criteria actually favor your strengths. A Section M that heavily weights past performance in contracts you've never performed is a signal to reconsider — or to find a teaming partner who fills that gap before you bid alone.

For the bid/no-bid decision, Section M analysis is one of the most actionable inputs you can have. If the weighted factors don't align with your demonstrated strengths, your probability of win is low regardless of how well you write. Using CapturePilot's pipeline tools to track your past performance profile against the Section M criteria of live opportunities helps you invest proposal effort where you actually have a path to win.

Finally: every proposal you submit — win or lose — is a source of Section L/M intelligence. Which evaluation factors did the winning contractor score highest on? The debrief will often tell you. Over time, you develop pattern recognition for how specific agencies write their Section M language and which factors they consistently prioritize. That institutional knowledge compounds. The contractors winning consistently aren't just reading Section L and M correctly. They're reading it in the context of everything they've learned about how this specific agency makes award decisions.