Reading Section L and Section M of a US Federal RFP

If you bid into the US federal market, the single most expensive sentence you’ll ever read is in Section L of your RFP, paragraph 2 or 3, and it goes something like this:

“Proposals failing to comply with the format and content requirements of this section may be eliminated from consideration without further evaluation.”

Translation: the technical excellence of your proposal is irrelevant if you didn’t follow the typesetting rules. Section L is where federal contracting officers separate the ~30% of proposals that go into the evaluation pile from the ~70% that don’t.

This is a primer for engineering practices entering the US federal market — the same conventions apply to many state DOTs and large infrastructure RFxs that adopt FAR-style structures. If you already work US Federal daily, this won’t be new; it’s written for the international engineering firm that just won a SAM.gov registration and is staring at its first 200-page solicitation.

The five sections that actually matter

US federal RFPs follow the Uniform Contract Format — a standardised structure laid out in FAR 15.204. Every solicitation has 13 sections labelled A through M; for bid response purposes, five of them carry all the weight.

Section	Name	What’s in it for you
C	Statement of Work / PWS	What the agency wants done. Your technical approach answers C.
H	Special contract requirements	Insurance, security clearances, drug-free workplace, the lot.
J	Attachments + exhibits	Past performance forms, specifications, drawings. The DD250s.
L	Instructions to Offerors	HOW to format and submit your response.
M	Evaluation criteria	HOW the evaluator will score you.

Section L is the “rule book” for proposal preparation. Section M is the “answer key” telling you what gets points. You write your proposal to comply with L and to maximise on M. Sections A, B, D-G, I, K are mostly contracting boilerplate.

What Section L typically mandates

The format constraints in Section L vary by agency but cluster around the same vocabulary. Things you’ll commonly see explicitly written in:

• Volume structure: “The proposal shall consist of three volumes: Volume I — Technical, Volume II — Past Performance, Volume III — Cost.” Each volume often has its own page limit.
• Page limits per volume: “Volume I shall not exceed 50 pages, excluding the cover page, table of contents, and acronym list.” Read the exclusions carefully — they vary by RFP.
• Font and type size: “Times New Roman 12 point or Arial 11 point. Footnotes may be 10 point. Tables and graphics may be 8 point provided text is legible to evaluators.”
• Margins: typically 1” all sides; sometimes 0.5” for tables.
• Line spacing: single or 1.15; rarely double.
• Page format: 8.5×11 portrait, sometimes 11×17 landscape allowed for foldout drawings within the page count.
• File format and submission method: PDF/A-1b, single bookmarked PDF per volume, uploaded to specific portal by specific deadline Eastern Time.
• Naming convention: [Solicitation#]_[CompanyName]_VolumeI.pdf.
• Mandatory sections: a list of subsection headings the proposal must include in that order.

The disqualification rate on these constraints is enormous. A 51-page volume on a 50-page limit doesn’t get a warning — it gets the COTR removing your proposal from the technical evaluator’s stack.

What Section M tells you

Section M lists the evaluation factors and their relative importance. A typical pattern:

“Award will be made based on best value, considering Technical Approach (35%), Past Performance (25%), Personnel Qualifications (15%), Small Business Participation (10%), and Price (15%). Non-price factors when combined are significantly more important than price.”

This tells you exactly where to spend your effort. If technical approach is 35% and price is 15%, the marginal page on technical methodology is worth 2.3× the marginal page on cost narrative.

Sub-factors usually have descriptive paragraphs explaining what counts as “Outstanding,” “Good,” “Satisfactory,” etc. Treat these paragraphs as the rubric you’re writing to. Lift the language verbatim into your proposal headings — evaluators reading 30 proposals are scanning for their own keywords.

How L and M fit together

The most common rookie mistake on first-time federal bids is to read Section C (the SOW), write a beautiful technical response, and then discover too late that:

1. Section L mandated a section called “Risk Mitigation Approach” that you never wrote (auto-deduction or worse).
2. Section M weighted “Past Performance” 25% but you put 4 pages of past performance and 30 pages of methodology (you maximised the wrong factor).
3. Section L’s page limit was 50 pages and your TOC + cover + appendix are excluded from the count, so you actually had room for 50 pages of content (you under-utilised).

The standard pre-bid task is to build a compliance matrix that maps every “shall” / “must” requirement from C, H, L, and M to a section in your proposal. Federal contracting offices publish this expectation explicitly — see for example the GSA’s proposal preparation guidance.

What this looks like in TenderWright

When you upload a US Federal RFP, TenderWright’s parser extracts:

• The sections (A through M)
• Section L format constraints — page limits per volume, font, margins, file naming, submission portal, deadline
• Section M evaluation factors — name, weight, sub-factor descriptions
• Section C “shall” requirements — every mandatory technical element

These populate the compliance matrix automatically. At export time, the format-rule enforcement compares your generated DOCX against the Section L constraints and flags violations before download — page over limit, font wrong, naming convention off. Same engine, different defaults, per the regions breakdown.

If you’re a non-US engineering firm thinking about the US federal market, the workflow shouldn’t be a leap of faith — it should look like every other tender response your team already runs. That’s the goal we’re building toward.

---

Want a walkthrough on a real Federal RFP? Book a demo or read about concierge setup if you’d rather hand us the data and have us configure the workspace.