Section M Evaluation Factors: Writing to the Score, Not the Page Count

The Paragraph That Cost a Win

A small 8(a) firm submitted a 40-page technical volume for a DHS task order. Their solution was sound. Their past performance was strong. They lost the technical factor by one adjectival rating, dropping from Good to Acceptable. The debrief showed why: the evaluator could not find explicit evidence that the offeror understood the key personnel qualification requirements spelled out in Section M. The information existed, buried in a staffing narrative on page 31. The evaluator never connected it to the rating criteria because the proposal never made that connection explicit.

That is the core problem. Proposal teams write to fill the page limit. Winning teams write to earn a specific adjectival rating on each factor. Those are fundamentally different disciplines.

How Section M Actually Works

Section M of a federal RFP, governed by FAR 15.304, tells you exactly what the Government will evaluate and how much each factor matters. Most RFPs use either an adjectival rating system (Outstanding, Good, Acceptable, Marginal, Unacceptable) or a color-coded equivalent. Some use a point scale. Either way, the agency publishes the definitions, and those definitions contain the exact language your proposal must satisfy.

The DoD Source Selection Procedures (2016, updated 2022) define Outstanding as a proposal that, among other things, contains multiple significant strengths and no deficiencies. An Acceptable rating means the proposal meets requirements with no deficiencies but also no significant strengths. The gap between those two ratings is not about word count. It is about documented, specific, discriminating strengths that the evaluator can cite in the source selection decision document.

If you do not hand the evaluator a strength, they cannot record one. If they cannot record one, you cannot score above Acceptable. It is that mechanical.

Build a Section M Compliance Matrix Before You Write a Word

The first operational step is to extract every evaluation criterion from Section M and map it to a rating threshold. Do this in a spreadsheet with four columns: Factor, Sub-factor, Rating Threshold Language, and Proposal Section Responsible.

For a typical best-value acquisition, your matrix might look like this:

• Factor 1, Technical Approach: To achieve Outstanding, the proposal must demonstrate a thorough understanding of requirements AND identify innovative approaches that exceed performance requirements.
• Factor 2, Management Approach: To achieve Good, the proposal must demonstrate a sound management plan with few weaknesses and no deficiencies.
• Factor 3, Past Performance: Evaluated as Substantial Confidence, Satisfactory Confidence, or Unknown. Substantial Confidence requires recent and relevant contracts with ratings of Very Good or Exceptional in CPARS.

Once you have this matrix, every section lead knows exactly what they are writing toward. The technical volume writer is not filling pages. They are building a case for Outstanding on Factor 1 by documenting specific innovations and tying them to measurable performance outcomes.

Strength Statements Are Not Bragging. They Are Evidence Packages.

An evaluator recording a strength needs three things: a feature of your proposal, the benefit that feature delivers to the Government, and the reason that benefit exceeds the minimum requirement. Proposal teams routinely provide the feature. They rarely complete the benefit-and-discriminator chain.

Compare these two passages:

Weak: "Our program manager has 15 years of experience managing federal IT programs."

Strength-ready: "Our proposed PM, [Name], holds a PMP and has managed five FISMA High systems through ATO under NIST SP 800-37 Rev. 2, including two concurrent ATOs under compressed 90-day timelines for CBP. This direct experience with the agency's ATO process reduces ramp-up risk and positions the program to achieve initial ATO within the PWS-required 120 days, rather than the typical 180-day industry average."

The second version gives the evaluator a citable strength: specific experience, a direct benefit (reduced ramp-up risk), and a quantified discriminator (120 days vs. 180-day average). That is what moves the needle from Acceptable to Good or Outstanding.

Use Section L as the Structure, Section M as the Scoring Guide

Section L tells you how to organize your proposal. Section M tells you how to score it. Most teams treat Section L as the primary guide and Section M as a checklist to verify at the end. Flip that priority.

Start with Section M. Identify the rating you are targeting on each factor. Then use Section L to determine where in the document each piece of evidence must appear. Write the Section M compliance argument first, then build the Section L narrative around it.

This approach also protects you against a common trap: burying discriminating information in a section the evaluator is not scoring. If your key personnel qualifications are evaluated under Factor 2 but you describe them in depth only in your staffing plan appendix, you have hidden your strength from the evaluator at the moment they are making their rating decision.

Past Performance: CPARS Language Is Your Source Material

On the Past Performance factor, the evaluator is comparing your submitted references against the relevancy and recency criteria in Section M. Substantial Confidence under the DoD framework requires contracts that are recent (typically within three to five years) and relevant (similar scope, dollar value, and complexity).

Pull your actual CPARS narratives. If a contracting officer wrote "Contractor consistently delivered ahead of schedule and proactively identified a critical integration risk that saved the program an estimated $240K," that language belongs in your proposal, attributed and quoted. Do not paraphrase a strong CPARS rating into generic language. Use the evaluator's own vocabulary: the source selection team reads CPARS every day and recognizes its cadence.

Also address relevancy explicitly. If Section M defines a relevant contract as one with a value above $5M involving cloud migration for a civilian agency, state that your reference contract was a $7.2M cloud migration for USDA. Do not make the evaluator infer relevancy. Spell it out in the first sentence of the reference narrative.

Color-Code Your Draft Against Section M Before Final Review

One of the most effective compliance checks is a color-coded annotation pass. Print your draft technical volume and Section M side by side. For each evaluation criterion, highlight the paragraph in your proposal that satisfies it. If a criterion has no highlighted paragraph, you have a gap. If a criterion has only one highlighted sentence buried in a 400-word block, you have a visibility problem.

This exercise routinely surfaces two failure modes: missing coverage (a sub-factor was never addressed) and diluted coverage (the relevant content exists but is surrounded by so much narrative that an evaluator skimming under time pressure will miss it). Both are fixable before submission. Neither is fixable after.

For teams using Winrove, a product of IT Custom Solution LLC (available at winrove.com, plans from $49/mo), the compliance matrix generation and gap analysis steps can be accelerated significantly during the shred phase, freeing your writers to focus on the strength-building work that actually changes scores.

One More Thing: Read the Rating Definitions Out Loud

Before your final review, read the Section M adjectival definitions out loud to your proposal manager. Then ask: does our technical volume contain multiple significant strengths with no deficiencies? Can we point to the paragraph for each one? If the answer to either question is uncertain, you are not ready to submit.

The page limit is a constraint. The Section M rating is the target. Write to the target.

Takeaway

Extract every Section M criterion before writing begins. Assign a target adjectival rating to each factor. Build explicit strength statements that include a feature, a benefit, and a discriminator. Verify coverage with a color-coded annotation pass. The evaluator can only score what they can find and cite. Make their job easy and your score will reflect it.

If your team wants a structured walkthrough of the compliance matrix process or help pressure-testing a Section M response strategy, reach out for a brief consult with the IT Custom Solution team.