Most small businesses read Section C of a federal RFP (the statement of work) and skip straight to pricing. That is the wrong order. The contractors who win read Section L and Section M first, then reverse-engineer their entire proposal from those two sections.
Here is what each section does and how to use them.
What Section L is and why it exists
Section L is titled "Instructions, Conditions, and Notices to Offerors." In plain terms: it tells you exactly what to submit, in what format, with what page limits, by what deadline.
A typical Section L will specify how many volumes your proposal needs (Technical, Past Performance, and Price are the standard three), the maximum page count for each, acceptable file formats, font size minimums (usually 12-point), and margin requirements. It will also list any certifications or representations you need to include, and whether you need to submit hard copies in addition to electronic files.
None of this is bureaucratic filler. Contracting officers use Section L as a compliance checklist. If you submit a 30-page Technical Volume when the RFP says 25 pages, the agency can reject your proposal outright without evaluating the content. That is not uncommon. The Government Accountability Office has sustained bid protests where offerors were eliminated for exceeding page limits by a single page.
Read Section L before you write a single word of proposal content.
What Section M is and why it matters more
Section M is titled "Evaluation Factors for Award." This is the scoring rubric. It tells you which factors the agency will evaluate, how they are weighted relative to each other, and in what order of importance they rank.
Under FAR Part 15 (Contracting by Negotiation), agencies must disclose all significant evaluation factors and their relative importance. The law requires it. That means Section M is not boilerplate — it is a legally binding statement of what the agency cares about.
A typical Section M will list factors like: Technical Approach, Management Approach, Past Performance, and Price. It will then tell you whether those non-price factors are weighted equally, or whether Technical outweighs Management, or whether Price is more important than anything else. Some agencies give you a rough percentage breakdown (Technical: 40%, Past Performance: 30%, Price: 30%). Others use ordinal language like "Technical is more important than Past Performance, which is more important than Price."
The specific weighting language matters. "Approximately equal" means price will likely decide close technical competitions. "Significantly more important than price" means you can win on technical merit even if you are not the lowest bidder.
Two scoring systems you will encounter
Agencies use two primary evaluation methods, and you need to know which one applies before you write.
Adjectival ratings assign qualitative labels to each factor: Outstanding, Good, Acceptable, Marginal, or Unacceptable. The definitions for these ratings are standardized in the DoD Source Selection Procedures and widely adopted by civilian agencies. An "Outstanding" rating requires a proposal to "contain multiple strengths" that would benefit the government and have "no weaknesses." A "Good" requires at least one strength with no significant weaknesses. These ratings are narrative-driven — the evaluator writes a justification for each.
Point scoring assigns numerical scores to each factor. An agency might score Technical Approach on a 0-100 scale and Management on 0-50. Point-scored evaluations are more common in task order competitions under GWAC contracts (like GSA OASIS, NASA SEWP, or DHS EAGLE).
Why does this distinction matter? With adjectival ratings, your goal is to generate documented strengths — specific, verifiable claims about your approach that an evaluator can write up as a positive finding. Vague language produces no strengths. Concrete, specific commitments do.
With point scoring, you need to hit every scored element. Agencies often publish a scoring matrix in Section M or in an attachment. If the matrix awards 10 points for describing your quality control process and you skip it, you get zero for that item regardless of how good the rest of your proposal is.
Mapping your proposal outline to Section M
Here is the practical technique: print Section M and build your proposal outline from it.
Each evaluation factor in Section M should become a major heading in your Technical Volume. Each subfactor should become a subheading. If Section M says the agency will evaluate "Technical Approach" with subfactors of (1) Understanding of Requirements, (2) Technical Solution, and (3) Risk Mitigation — your Technical Volume should have three clearly labeled subsections using those exact words.
Evaluators are reading proposals under time pressure, often scoring five or more submissions simultaneously. If they have to hunt for your response to a subfactor, you lose points or get marked as non-responsive. Making it easy for the evaluator to find and score your content is itself a competitive advantage.
After you draft each section, read the corresponding Section M language again and ask: does my response generate a documentable strength? Did I make a specific commitment — a timeline, a staffing ratio, a process step — that the evaluator can quote in the evaluation record?
How to handle price relative to technical factors
Section M will tell you how much weight price carries. Read that language carefully, because it determines your pricing strategy.
If the solicitation is a "best value" procurement where technical factors are "significantly more important than price," you have room to price for margin. The agency is explicitly telling you it will pay more for a better technical approach. In this scenario, a proposal that wins on technical merit at a 15% price premium is a rational outcome.
If the solicitation is "lowest price technically acceptable" (LPTA), the evaluation works differently. The agency evaluates technical proposals only to determine whether they meet minimum standards. Once a proposal clears the technical bar, the award goes to the lowest price. Under LPTA, competing on technical quality above the minimum threshold wastes effort and money.
The FAR limits LPTA use to acquisitions where requirements are clearly defined and risk of unsuccessful performance is minimal (FAR 15.101-2). DoD has additional restrictions under 10 U.S.C. 3241 that require a written determination before using LPTA for acquisitions above certain thresholds. In practice, you still see LPTA used broadly for commoditized services and IT support.
Know which evaluation approach applies before you scope your proposal effort.
A note on Section L page limits and page count strategy
Section L page limits are hard constraints, not suggestions. But they also tell you something about what the agency values. If the Technical Volume gets 25 pages and Past Performance gets 5, the agency is signaling where it wants your attention.
Do not pad sections to fill the limit. Evaluators know filler when they see it, and filler dilutes your strengths. Write to the limit only if you have substantive content to fill it. If your Technical Approach is genuinely strong in 18 pages, submit 18 pages.
Graphics count toward page limits unless Section L explicitly excludes them. Tables of contents, cover pages, and section dividers may or may not count — check the RFP language. Some agencies specify that resumes for key personnel do not count against the page limit; others do. When in doubt, count conservatively.
Three action steps
Before the next RFP you pursue: Pull the Section M from a recent award in your target agency. Most awards are publicly available via USASpending.gov or agency procurement forecast pages. Read the evaluation factors. That tells you what the agency actually cares about, before you see the next solicitation.
On any active opportunity: Build a compliance matrix that maps every Section L requirement (volume, page limit, format) and every Section M subfactor to a corresponding section of your proposal. Review it before submission.
On pricing: Identify whether the solicitation is best value or LPTA before you set your price. The evaluation approach should drive your pricing strategy as much as your cost model does.
