Section L tells you how to write the proposal. Section M tells you how the government will grade it. Win consistently in federal contracting and you will find the teams that read those two sections together, as a single instrument, rather than treating them as separate chores. Misread the relationship and you produce one of two losing documents: a perfectly compliant proposal that scores poorly, or a brilliant one that gets thrown out for noncompliance before an evaluator reads the good parts.
This guide explains where Section L and Section M come from, what each one actually controls, the mistake almost every new proposal team makes, and the workflow that turns the two sections into your outline and your win strategy.
Where they come from
Both sections live in the Uniform Contract Format, the standard structure for negotiated procurements set out in FAR 15.204. A full RFP runs through sections A to M: the schedule (A through H), contract clauses (I), the list of attachments (J), and the three that the proposal team lives in. Section K holds representations and certifications. Section L is Instructions, Conditions, and Notices to Offerors. Section M is Evaluation Factors for Award. Section C, or an attached statement of work, defines the actual work; for how those work documents differ, see PWS vs SOW vs SOO.
Section L: the instructions
Section L controls the document itself. It governs format, page limits, the number and content of volumes, the order of contents, fonts and margins, the submission method, and the deadline. It is the rulebook for how you package and deliver the proposal.
Section L is pass or fail
Here is what makes Section L unforgiving: noncompliance can make you nonresponsive before anyone evaluates your approach. Go one page over the limit and an evaluator may simply not read the overflow, or worse, your proposal can be rejected. Submit the wrong volume structure, miss a required form, use the wrong font size to cram in more words, or blow the electronic submission instructions, and you can be eliminated on mechanics alone. Strong teams treat every Section L instruction as a checklist item that must be physically verified, not assumed.
Section M: the scorecard
Section M lists the evaluation factors and subfactors, tells you their relative importance, and states the basis for award. It is the government telling you, in advance, exactly what it values and how heavily. Your win themes, your proof points, and your page allocation all have to answer to Section M.
Best value tradeoff vs LPTA
The basis for award shapes your entire strategy. Under a best value tradeoff, the government can pay more for a higher-rated proposal, so non-price factors like technical approach and past performance carry real weight and your differentiators matter. Under lowest price technically acceptable, or LPTA, the government buys the cheapest proposal that clears the technical bar, so once you are acceptable, additional quality does not help and price decides. Reading Section M tells you which game you are playing, and a tradeoff proposal written as if it were LPTA, or the reverse, leaves the win on the table. For a deeper read on decoding the evaluation, see how to read Section M like a winning capture manager.
The mistake: reading them in isolation
The most common failure is treating Section L as the outline and ignoring how Section M weights the work. Section L might ask for a technical volume organized in a particular sequence. Section M might weight past performance heavily and management lightly. A team that writes to L's structure without aligning emphasis to M's weights ends up spending pages on sections that barely score while shortchanging the factor that decides the award.
The two sections are also not always in the same order, and they do not always use the same labels. A subfactor that appears late in Section L might be the most heavily weighted item in Section M. If you do not cross-walk them, you will not notice.
The compliance matrix is the bridge
The tool that connects L and M is a compliance matrix: a single table that lists every Section L instruction and every Section M factor, maps each L requirement to the M factor it serves, and assigns an owner and a location in the proposal. Built well, it guarantees you have addressed every instruction and that your effort is pointed at what scores. Our compliance matrix template lays out the structure, and it is the backbone of a disciplined proposal.
How to use L and M together
- Extract every Section L requirement into a checklist, down to page limits and formatting.
- Extract every Section M factor and its weight, including the basis for award.
- Map each L section to the M factor it supports so you can see coverage and gaps.
- Allocate page count by M weight, not by habit or by which author writes fastest.
- Assign win themes to the highest-weighted factors and make sure every theme is backed by proof, not assertion.
- Pull the staffing requirements early, since key personnel is often its own scored factor; see extracting key personnel requirements.
- Review against both: a Section L compliance check and a Section M scoring check, built into your color team reviews.
What about the rest of the RFP
Section L and M do not exist in a vacuum. Section C or the attached SOW, PWS, or SOO defines the work you are proposing to do and must align with your technical volume. Section H carries special contract requirements, including things like organizational conflict of interest provisions; see OCI explained for why Section H deserves a careful read. Section K reps and certs have to be completed accurately, because errors there can also make you nonresponsive. The proposal team that wins reads the whole package, but builds its outline from L and its strategy from M.
How evaluators actually score: ratings, strengths, and weaknesses
Section M does not just list factors; it implies how evaluators will rate them. Most non-price factors are scored with adjectival ratings, common scales run from Outstanding or Exceptional down through Good, Acceptable, Marginal, and Unacceptable, and evaluators assign them by tallying strengths, significant strengths, weaknesses, significant weaknesses, and deficiencies in your proposal. A strength is a feature that exceeds a requirement in a way that benefits the government. A deficiency is a failure to meet a material requirement, and it can make your proposal unawardable on its own. Writing to Section M means deliberately engineering strengths the evaluator can point to, and eliminating anything that reads as a weakness or a risk.
A worked cross-walk
Suppose Section L asks for a technical volume organized as Management, Technical Approach, and Staffing, in that order, with a 30-page limit. Section M, however, weights Technical Approach most heavily, then Past Performance (evaluated from a separate volume), then Management, with Staffing folded into Management. A team that allocates pages by the Section L order might give each of the three roughly ten pages. A team reading the two together allocates by Section M weight: more pages to Technical Approach, fewer to Management, and it makes sure the heavily weighted Past Performance volume is as strong as the technical one even though Section L listed it elsewhere. Same instructions, very different page strategy, and the second team scores higher. This is exactly the cross-walk a compliance matrix is built to make visible.
Bottom line
Section L keeps you in the competition. Section M wins it. Build your outline from L, allocate your effort by M, and review against both before you submit. The proposal that is fully compliant and weighted toward what actually scores is the one that wins, and the teams that do this consistently are the ones that read the two sections as a single instrument from day one.
For the surrounding workflow, see how to evaluate an RFP in under 10 minutes, understand the early-stage notices in Sources Sought vs RFI vs RFP, and learn the document types you will be responding to in SOW vs SOO.