Reading a Federal RFP: Sections L and M for Software Companies

2026-10-05#saas #federal-market

By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.

A federal request for proposals can run to a hundred pages or more, and most of it is contract language that will matter only if you’re awarded the work. For a software company deciding whether to bid, and then writing the proposal, two parts matter most: the instructions that say what to submit, and the evaluation criteria that say how the submission will be judged.

In the traditional federal format these are Section L and Section M. This guide explains where they sit in a solicitation, what each one asks for and how to build a proposal around them.

Where L and M sit in a solicitation

Negotiated federal procurements under FAR Part 15 have long used the uniform contract format, which divides a solicitation into lettered sections:

Sections A to H describe the requirement and the contract terms: the supplies or services and prices (B), the statement of work or performance work statement (C), packaging, inspection, delivery, contract administration and special requirements.
Section I lists the contract clauses.
Section J lists attachments, which often hold the detailed technical requirements, pricing templates and security documents.
Section K holds representations and certifications.
Section L gives instructions, conditions and notices to offerors.
Section M sets out the evaluation factors for award.

Not every solicitation follows this layout. Commercial acquisitions under FAR Part 12 often use a shorter format, and orders placed under existing vehicles such as a GSA Schedule or an IDIQ contract follow that vehicle’s ordering procedures. The labels change, but almost every competitive solicitation still separates the two questions: what to submit, and how it will be evaluated. Find those two parts first, whatever they’re called.

Section L: what to submit

Section L is the instruction set for the proposal. It typically specifies:

Volumes. How the proposal is split, such as technical, management, past performance and price, and what belongs in each.
Format. Page limits, font size, margins, file types and naming. Pages beyond a limit are often not read.
Content requirements. The specific topics each volume must address, sometimes mapped to paragraphs of the statement of work.
Questions and deadlines. When and how to submit questions, and the exact due date, time and delivery method for the proposal.
Oral presentations or demonstrations. Some agencies ask for a live demonstration of the product instead of, or alongside, a written technical volume.

Read Section L line by line and treat every “shall” as a requirement. A proposal that ignores an instruction can be found noncompliant before anyone evaluates its substance. Deadlines are strict: late proposals are generally not considered, and electronic submission problems are rarely accepted as an excuse.

Section M: how it will be judged

Section M tells you how the agency will choose. It lists the evaluation factors, any subfactors and their relative importance. Common factors for software buys include technical approach, management approach, past performance and price.

Under the FAR, price or cost must be evaluated in every source selection, and past performance is usually evaluated in competitive negotiated buys as well. (Our guide to past performance covers how evaluators weigh it, including for first-time bidders.)

Section M also states the basis for award, which usually takes one of two forms:

Best-value tradeoff. The agency may award to a proposal that isn’t the lowest priced if its technical merit justifies the difference. Section M says whether non-price factors together are more important than, equal to or less important than price.
Lowest price technically acceptable. Proposals are rated acceptable or unacceptable on the non-price factors, and award goes to the lowest-priced acceptable proposal. Technical strengths beyond acceptability earn no extra credit.

Which basis applies changes how you write. In a tradeoff, describe strengths and the benefit they bring to the agency’s mission. In a lowest-price buy, show clearly that you meet every requirement, then compete on price.

Section M may also say whether the agency intends to award without discussions. If it does, your initial proposal may be your only chance, so it should be your best offer.

Building the proposal around L and M

Experienced bidders build a compliance matrix before they write anything. It’s a table that lists every instruction in Section L and every evaluation factor in Section M, maps each to the relevant requirement in the statement of work, and assigns it to a section of your proposal and an owner.

A few practices help software companies in particular:

Mirror the structure. Organize each volume in the order Section L requests, using its headings. Evaluators score against Section M with the solicitation open next to them, and they shouldn’t have to search for an answer.
Answer the requirement, not the product tour. Describe how your software meets each stated requirement, rather than its full feature set. Features the agency didn’t ask for use pages the agency did set limits on.
Address security and accessibility directly. Software solicitations often require evidence of FedRAMP authorization or a path to it, Section 508 conformance documented in an accessibility conformance report, or, on Department of War work involving controlled unclassified information, CMMC status. Say what you hold and what is in progress. Self-attested compliance is not the same as a third-party assessment or an authorization, and evaluators can tell the difference.
Price the way the template asks. Use the pricing attachment exactly as provided. Software licensing models such as subscriptions, users, cores or tiers need to fit the agency’s line items, so explain any mapping clearly.
Watch for amendments. Agencies change solicitations through amendments, often in response to questions. Acknowledge every amendment as instructed and check whether it changed Section L or M.

Before you commit to a bid

Reading L and M closely is also the fastest way to decide whether to bid at all. If the evaluation leans heavily on past performance you can’t show, on a vehicle you don’t hold or on a security authorization you don’t have yet, that tells you something. It may make more sense to pursue the work through a prime as a teaming partner or subcontractor, or to shape future requirements earlier through sources sought notices and RFIs.

To see where your company stands on the factors evaluators tend to look for, score your company’s federal readiness.

The CMMC brief

What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.