Key takeaways
- Section L tells you how to respond; Section M tells you how you’ll be scored.
- Structure your response to L, and argue your case against M.
- The compliance matrix should drive the outline, not audit it afterwards.
- Read M first — it tells you where to spend your effort.
Most losing proposals are not badly written. They are badly aimed. The company understood the requirement, described its capability accurately, and produced a document that was never structured to be scored well. The fix lives in two sections of the solicitation that get read too quickly.
What each section does
In the Uniform Contract Format:
- Section C is the statement of work — what the government wants done.
- Section L is instructions to offerors — how to construct and submit your response. Volume structure, page limits, formatting, required forms, submission mechanics.
- Section M is evaluation factors — the criteria the government will score you against, and their relative importance.
The short version: L is how you respond. M is how you win. A response compliant with L but indifferent to M is readable, submittable, and average.
Read Section M first
Reading order matters more than most teams realise. Section M tells you where the points are. Read it before you read anything else, and read it for three specific things:
- What the factors are, and in what order of importance.
- The relationship between technical merit and price. “Technical significantly more important than price” and “price and technical approximately equal” call for completely different bids.
- The language used. If M rewards demonstrated experience, unsupported assertion of capability will score badly no matter how well written.
Only then read L, and only then C. You want to be reading the requirement already knowing how the response to it will be judged.
Building the compliance matrix
The compliance matrix is the single artefact that most reliably distinguishes a disciplined pursuit from an anxious one. In its simplest useful form it is a table with one row per requirement:
- The source reference (section and paragraph).
- The requirement itself, quoted — not paraphrased.
- Where in your response it is addressed (volume, section, page).
- Who owns writing it.
- Its current status.
Quoting rather than paraphrasing matters. Paraphrasing is where requirements quietly change meaning, and the changed version is the one your writer responds to.
Include everything: instructions in L, criteria in M, requirements in C, and the representations and certifications that have nothing to do with your technical approach but will still make you non-responsive if unsigned.
Turning the matrix into an outline
This is the step that gets skipped. The matrix should generate your response outline, not audit it afterwards.
Structure your volumes in the order Section L specifies, using the headings Section L uses. Evaluators frequently score with a checklist built from the same source. Making them hunt for your response to a requirement is a self-inflicted wound — and where L and your preferred narrative structure conflict, L wins every time.
Within that structure, write to Section M. Each section should make an argument the evaluator can score, supported by evidence, rather than describing your company.
Common failures
- Responding to C and forgetting M. A technically excellent answer that ignores the evaluation criteria.
- Reorganising L’s structure because your narrative flows better. It doesn’t, for the person scoring it.
- Treating page limits as a target. They are a constraint. Filling them with lower-value content lowers your average.
- Building the matrix at the end as a compliance check. By then the outline is set and the expensive errors are structural.
- Ignoring the administrative volume. Unsigned representations end bids that would otherwise have scored well.
None of this requires unusual talent. It requires reading two sections carefully, writing down what they say, and letting that drive the document.
