Sections L and M are the whole test

Every formal federal solicitation built on the uniform contract format carries the same skeleton, sections A through M, and almost all of the bid-prep work lives in just two of them. Section L, instructions to offerors, tells you what to submit, in what order, in what format, and by when. Section M, evaluation factors for award, tells you how the government will grade what you send. The rest of the solicitation, the statement of work, the pricing schedule, the contract clauses, matters for doing the work. L and M are what decide whether you get the chance to do it.

Section	What it controls	What ignoring it costs
L, instructions to offerors	What to submit, in what shape, by when	Set aside unread, no matter how strong the content
M, evaluation factors	How the government scores what you submitted	A compliant proposal that still loses on substance

Read M before L, and L before anything else

It feels backward to read the grading rubric before the instructions, but that order saves time. Section M tells you what the government actually cares about: which factors it scores, how they weigh against each other and against price, and whether this is a best value tradeoff or a lowest price technically acceptable competition. Once you know what earns points, Section L's formatting demands make sense as the container you have to pour that content into. Read L next, in full, before you draft a single page. Everything else on your team's list, teaming calls, past performance write-ups, pricing, comes after those two sections are understood, not before.

L is pass or fail, not partial credit

In practice, agencies treat Section L compliance as a gate, not a scoring factor. A proposal that runs a page over the limit, uses the wrong font size, submits the wrong file format, or leaves out a required volume can be found nonresponsive and set aside unread, no matter how good the technical content is underneath. Common Section L requirements worth checking twice:

• Page limits, sometimes set per volume rather than overall
• Font, margin, and spacing rules, which some agencies enforce by simply not reading past the cutoff
• Required volumes and how they must be separated, often technical, past performance, and price as distinct files
• File format and file naming convention
• Submission method and deadline, including time zone and whether the portal has its own cutoff behavior

None of this rewards creativity. The safest approach is to turn Section L's numbered requirements straight into a checklist and confirm every item before you submit. See bid mistakes that get you thrown out on page one for the specific ways this goes wrong.

M is where the points actually live

Section M lists the evaluation factors, commonly things like technical approach, management approach, past performance, and price, and usually states how they relate to each other. Two structures show up often:

• Best value tradeoff. The government can pay more for a proposal that scores meaningfully better on the non-price factors. Effort spent sharpening your technical narrative and past performance can pay off here.
• Lowest price technically acceptable, LPTA. Once you clear the technical bar, price decides everything. Polishing your technical volume past "acceptable" buys you nothing, and that effort belongs in your pricing instead.

Knowing which one you are in before you start writing changes where your team's hours should go.

When there are no letters

Simpler, commercial-style solicitations often skip the lettered sections and use plain headings instead, commonly something like "instructions to offerors" and "evaluation criteria" or "basis of award." The content underneath asks the same two questions: what do you submit, and how does it get judged. Read a commercial-format solicitation the same way. You are just hunting for the headings instead of the letters.