How to Write a Government Proposal: Sections L and M, Compliance Matrices and Page Limits

How to write a government proposal: start with Sections L, M and C

Most negotiated federal solicitations follow the Uniform Contract Format, a fixed sequence of lettered sections. Three of them drive your proposal: C says what the government is buying, L says how to write and submit your response, and M says how it will be scored.

What the FAR overhaul changed

The Revolutionary FAR Overhaul rewrote FAR Part 15 in plainer language, and agencies began using the new text through class deviations in late 2025 and 2026. The Defense Department’s deviation took effect March 16, 2026. The Uniform Contract Format survived: in the overhauled text it sits at FAR 15.109 instead of 15.204, and the section letters and their purposes are unchanged. Formal rulemaking to write the overhaul into the codified FAR is moving in stages, so the solicitation in front of you is the best guide to which rules apply.

When an RFP doesn’t use Sections L and M

Plenty of solicitations skip the format. Commercial purchases are built on the SF 1449, with instructions and evaluation criteria usually added as addenda to FAR provisions 52.212-1 and 52.212-2. Requests for quotations, GSA Schedule buys and task orders often use a short custom layout. Find the paragraphs that say what to submit and how you’ll be judged, and treat them as your L and M. Unfamiliar terms are defined in the government contracting glossary.

Shred the RFP before you write a word

Shredding means breaking the solicitation into individual, numbered requirements. You read Sections C, L and M, every attachment and every amendment, and pull out each sentence that tells you to do, provide, describe or comply with something. The words to hunt for are “shall,” “must,” “will,” “should” and “is required to.”

1. Collect the full package. Download the solicitation, all attachments and every amendment from the SAM.gov notice, and note the date of each file.
2. Pull the instructions from Section L. Volume structure, page limits, fonts, margins, file types, naming rules and required forms.
3. Pull the evaluation criteria from Section M. Each factor and subfactor, their order of importance, and whether award is a best-value tradeoff or lowest price technically acceptable (LPTA).
4. Pull the work requirements from Section C and the attachments. Every task, deliverable, standard and deadline in the statement of work or performance work statement (PWS).
5. Give each requirement an ID and a source. Keep the RFP paragraph number on every line so any reviewer can trace it back.

Shredding is also your best bid/no-bid check. If the RFP requires a facility clearance, a license, a cybersecurity certification level or a set-aside status you don’t have, you’ll find out before writing. Set-aside eligibility is explained in small business set-asides.

How to build a compliance matrix

A compliance matrix is a table that lists every requirement from the shred and shows exactly where your proposal answers it. It keeps a proposal team honest: if a row has no proposal location, the evaluator won’t find an answer either.

Keep it in a spreadsheet or your proposal tool, and update it whenever the outline, the draft or the RFP changes. Here is a simplified example for a help-desk support RFP:

Make the matrix earn its keep

• One requirement per row. Split compound sentences: “develop, maintain and deliver” is three requirements if each can be missed on its own.
• Map L, M and C to the same place. The strongest sections answer the instruction, the evaluation criterion and the work requirement together.
• Use statuses that mean something. Missing, drafted, in review and compliant tell you where to spend the last week. Percentages don’t.
• Add rows for every amendment. Amendments change requirements after you’ve started writing, and they’re the easiest thing to miss.

If you include the matrix in the submission as a cross-reference, first confirm that Section L allows it and whether it counts against your page limit.

Outline the proposal to mirror Section L

Evaluators score with a checklist built from Sections L and M. Make their job easy: organize your RFP response in the same order, with the same numbering and headings the RFP uses. If L.3.4(b) asks for a staffing approach, the reader should find a heading called “Staffing Approach” where they expect it, not a creative title three pages later.

The usual volumes

Section L sets the structure, but most federal proposals break into some version of these:

• Technical. Your approach to the work in Section C, often with management in the same volume.
• Management. Organization, key personnel, staffing, transition and quality control, sometimes as its own volume.
• Past performance. Reference contracts and, often, questionnaires your customers send directly to the contracting officer.
• Price or cost. Pricing in the government’s template, following the CLINs in Section B.
• Administrative. The signed SF 33 or SF 1449, amendment acknowledgments, representations, certifications and any required plans.

Turn the outline into an annotated outline

Under each heading, paste the matrix rows that section must answer, its page budget, and the one or two points you want the evaluator to remember. Writers then draft against a plan, and page budgets set now prevent the night-before scramble to cut six pages.

Write the technical and management volumes

The technical volume is where most proposals win or lose on merit. Evaluators record strengths, weaknesses and deficiencies (a deficiency is a failure to meet a material requirement), so every paragraph should either earn a strength or close off a weakness.

Technical approach

• Explain how, not just that. “We will provide 24/7 coverage” earns nothing. “Three shifts, a tiered escalation path and a 15-minute response standard tracked in our ticketing system” gives the evaluator something to credit.
• Tie each choice to the evaluation criteria. Use Section M’s words, and say why the choice lowers risk or improves results for this agency.
• Prove your claims. Back statements with numbers, named tools, examples from past work and the résumés of the people who will do it.
• Don’t parrot the statement of work. Restating the requirement in different words is the most common filler in government proposal writing, and evaluators notice it.

Management approach

• Organization and key personnel. An org chart, plus résumés that meet every minimum qualification the RFP lists: degrees, years of experience, certifications.
• Staffing and transition. How you’ll recruit, retain and get people productive on day one, with a transition plan if there’s an incumbent.
• Quality control and risk. How you’ll measure performance against the PWS standards and fix problems before the customer finds them.
• Subcontractor management. Who does what, how you’ll manage teammates and, on a small business set-aside, how you’ll stay within the limitations on subcontracting.

Past performance and price volumes

Past performance

Agencies evaluate past performance in most competitive source selections, and Section L tells you how many references to provide, how recent they must be and what counts as relevant. Relevance usually comes down to size, scope and complexity: a $200,000 janitorial contract won’t carry much weight on a $15 million facilities bid.

• Pick the closest matches. Choose the references that look most like this requirement, and explain the similarity in Section M’s terms.
• Send questionnaires early. When the RFP includes a past performance questionnaire, your customers usually return it directly to the contracting officer. Give them weeks, not days.
• Know your CPARS record. Evaluators can use information from any source, including the government’s Contractor Performance Assessment Reporting System.
• No record isn’t a zero. Under the FAR, an offeror without relevant past performance can’t be rated favorably or unfavorably on it. Evaluators may also consider relevant experience of predecessor companies, key personnel or subcontractors; check Sections L and M for what this RFP accepts.

Building a record from scratch is covered in how to win your first federal prime contract.

Price

• Use the government’s template and CLINs. Don’t restructure the pricing sheet, and price every line item unless the RFP says otherwise.
• Keep price and technical consistent. If the technical volume promises five full-time staff and the price supports four, evaluators will catch it.
• Keep prices out of the technical volume when Section L says to. Agencies often evaluate the volumes with separate teams.
• Avoid exceptions and conditions.Taking exception to the RFP’s terms, or attaching conditions to your price, can make an offer unacceptable. Ask about anything unclear during the Q&A period instead.

Many RFPs say the government intends to award without negotiations, which the FAR long called discussions. Make your initial proposal your best offer.

Page limits, formatting and file rules

Page and format rules come from Section L, and they are not suggestions. Many RFPs state that pages beyond the limit won’t be evaluated, so a requirement you answered on page 26 of a 25-page volume may not exist as far as the evaluator is concerned.

• Know what counts. Check whether the cover, table of contents, acronym list, résumés and any compliance matrix count toward the limit.
• Match the specs exactly. Font, size, line spacing, margins, page size, and any separate rules for tables, graphics, headers and footers.
• Get the files right. File type (often searchable PDF, with Excel for price), naming conventions, size limits for email or portal uploads, and whether the price workbook must keep working formulas.
• Count pages in the final format. A volume that fits in your word processor can run over once it’s converted to PDF with every graphic in place.

Track amendments, questions and deadlines

Solicitations change after they’re posted. Amendments change requirements, extend deadlines or answer industry questions, and they’re posted to the same SAM.gov notice as the original RFP.

• Watch the notice. Follow the SAM.gov notice so you see updates, and check it once more on the day you submit.
• Acknowledge every amendment. Do it the way and by the time the amendment specifies, often by signing the SF 30 or listing each amendment on your offer form. A missing acknowledgment can make your offer unacceptable.
• Update the matrix. Every amendment gets its own rows, even when it seems to change nothing important.
• Respect the Q&A deadline. Questions are usually due well before proposals and must go to the person and address Section L names. Answers typically go to every bidder in an amendment, so phrase questions without revealing your strategy.

Build your schedule backward from the due date: submission, final review, red team, first draft, outline, kickoff. Put the question deadline on the calendar the day you decide to bid.

Run color team reviews before you submit

Color team reviews are an industry convention, not a FAR requirement. Each asks a different question at the right moment. Names vary by company; these are the most common:

A small business doesn’t need a formal program. One fresh reader with Section M in hand, scoring your draft the way an evaluator would, catches most of what a red team finds. Leave a few days after that review to fix what it turns up.

Software can speed up shredding, first drafts and compliance checks; see AI for government proposal writing for what to trust it with.

Submit on time and avoid the common disqualifiers

Section L tells you how to submit: by email to a named contracting officer or specialist, through an agency portal, or occasionally on paper. Defense solicitations increasingly require upload through the PIEE Solicitation Module, which needs an account with the proposal manager role, so set up access early.

• Submit early. Aim for at least a day ahead. Large files, portal outages and email filters that quarantine attachments don’t move the deadline.
• Keep proof of receipt. Save the portal confirmation or the sent email with its timestamp.
• Keep your registration active. Solicitations generally require an active SAM.gov registration when you submit; the SAM.gov registration guide covers renewal.

Late proposals are generally rejected. The FAR’s exceptions are narrow and at the government’s discretion: an electronic proposal, for example, generally must have reached the government’s system by 5:00 p.m. one working day before the due date. Never plan around them.

Common reasons proposals are rejected or lose

• Late submission, or submission to the wrong address or portal.
• Missing signed forms, representations or amendment acknowledgments.
• Pages over the limit, or the wrong font, format or file type.
• A missing required element, such as a résumé, a plan or a priced CLIN, that makes the proposal deficient.
• Exceptions to the RFP’s terms or conditions attached to the price.
• Ineligibility: the wrong size status for the NAICS code, a missing certification for a set-aside, or an inactive SAM.gov registration.
• Technical and price volumes that contradict each other.

Frequently asked questions