Building a compliance matrix from Sections L and M

The document that keeps a proposal honest

A compliance matrix is a single table that lists every instruction and every evaluation factor in a solicitation, and says where in your proposal each one is answered and who owes the content. It is the first thing a serious proposal team builds, and most small firms never build one. They read the statement of work, write what seems right, and find out at the debriefing that they missed a required subfactor.

The matrix turns a long solicitation into a checklist you can finish. It tells you what is missing while there is still time to write it. It also tells you when a page limit will not hold everything the evaluator expects, which is a problem you want to discover in the first week.

How a federal solicitation is laid out

The FAR Overhaul model text keeps the uniform contract format for negotiated procurements, saying contracting officers should prepare requests for proposals using it. The format groups the solicitation into four parts and lettered sections, and three of those sections do most of the work for a bidder.

Section	What it holds	Why you care
Section C	Description, specifications and requirements, often a statement or performance work statement	What you will have to do if you win
Section L	Instructions, conditions and notices to offerors	How you must submit, including volumes, format and method
Section M	Evaluation factors for award, significant subfactors and relative importance	How you will be scored

The other sections matter as well. Section B holds supplies or services and prices. Section E holds inspection and acceptance. Section F holds deliveries or performance. Section H holds special contract requirements, and Section K holds representations and certifications. Requirements hide in all of them.

When there is no Section L or M

The format is not universal. The model text says agencies do not need to use it for construction and architect-engineer contracts, subsistence contracts, streamlined requests for proposals, and certain others. Commercial buys typically arrive on Standard Form 1449 with instructions and evaluation language in the commercial provisions and addenda instead. Agencies are putting the Overhaul text in place through class deviations, so read what your solicitation actually says.

Where the format is not used, the model text still requires a competitive solicitation to describe the requirement, the anticipated terms, the information required in the proposal, and the factors and significant subfactors used for evaluation and their relative importance. The same content exists. Your job is to find it, and the same matrix works when the instructions sit in a narrative or an attachment.

The columns that matter

A matrix can have dozens of columns. Five carry the load, and the rest are usually a sign that someone is enjoying the spreadsheet.

Column	What goes in it	Example
Requirement	The exact words from the solicitation	"Describe the plan to maintain operations during phased occupancy"
Source paragraph	Section and paragraph number, amendment number if changed	L.4.2(b), as revised by Amendment 0002
Volume and page	Where the answer lives in your proposal	Volume I, section 3.2, page 9
Owner	One person accountable for the content	Project executive
Status	Not started, drafted, reviewed or final	Drafted

A plain spreadsheet does the job, and a shared spreadsheet is better, because everyone working the bid can see what is open. Keep one tab for the rows and one for amendments and questions. Freeze the header row and filter by owner, so each person sees only what they owe.

Use the solicitation's exact words in the first column. Paraphrasing is where meaning slips. "Shall describe" and "may describe" are different instructions, and a summary will lose that distinction.

Build it in this order

The work takes hours, not days, even on a long solicitation, if you go in sequence.

1. Read the entire solicitation once without marking anything, including every attachment and amendment.
2. Go through the instructions and pull each direction into its own row: every "shall," "must," "will provide," page limit, format rule, form and required attachment.
3. Pull every evaluation factor and subfactor into its own rows, with the words that state its relative importance.
4. Pull requirements from the work statement that an evaluator would expect you to address.
5. Link each evaluation factor to the instruction that asks for it. Note any factor with no matching instruction, and any instruction with no matching factor.
6. Assign each row to a volume, a page budget and one owner.
7. Turn the rows into your proposal outline, using the solicitation's own headings and numbering.

Step five is where the value is. Instructions and evaluation factors are often written by different people, and they do not always line up. When the evaluation section grades something the instructions never ask for, answer it anyway, in the most logical place, and label it clearly. The federal rule requires agencies to evaluate proposals based solely on the factors and subfactors in the solicitation, so the factors decide what scores.

Instructions and evaluation factors are often written by different people, and they do not always line up.

The matrix writes your question list

Building the matrix surfaces the problems in a solicitation: a form that is referenced but not attached, two different page limits, a factor with no instruction behind it, or a work requirement that contradicts a drawing. Add a questions column or a short separate list, and mark each item the moment you find it.

Send questions in writing, by the stated deadline, to the person the solicitation names, and quote the paragraph you are asking about. Ask only what changes how you will write or price. The answer usually comes back as an amendment visible to every offeror, so frame a question so that the answer helps you without giving away your approach. Log each answer against the row it affected, because a posted answer can change a requirement as surely as a numbered amendment does.

Read the weights before you budget pages

The solicitation must state the relative importance of the evaluation factors, and, with a narrow exception, the model text requires it to say, at a minimum, whether the non-price factors combined are significantly more important than price, approximately equal to it, or significantly less important. That statement tells you how hard the technical writing has to work.

Divide your page budget by importance. If technical approach is the most important factor and management is third, the pages should reflect that, and the owner of the technical section should know it before drafting. A firm that spends the same space on every factor has given away its most valuable pages.

Format rules are requirements

Page limits, fonts, margins, file types, file-name conventions, volume separation and the method of submission all go into the matrix as their own rows. The model text says offerors may be instructed to submit proposals in a specific format or severable parts to facilitate evaluation, and agencies can require organization into sections such as technical, past performance and price.

Treat each one as a pass or fail check. Note whether pricing must stay out of the technical volume, whether resumes count against the limit, whether a cover letter or a table of contents is excluded, and whether the portal has a file size cap. Evaluators may simply decline to read beyond a limit, and you may never be told.

• Building the matrix from the work statement alone and missing the instructions
• Combining several requirements in one row so that one of them is never answered
• Leaving the owner column blank, or naming a department instead of a person
• Writing section headings in your own words so the evaluator cannot find the answer
• Treating the matrix as finished when the first draft starts

Amendments change the matrix

Each amendment is new content, and it may quietly change a page limit, a due date, an evaluation factor or a clause. Under the standard provisions, offerors must acknowledge receipt of any amendment to the request for proposals by the date and time specified in the amendment, and bidders in sealed bids must acknowledge amendments by the time and at the place specified for receipt of bids.

Keep a simple amendment log at the top of the matrix: number, date, a one-line summary and the rows it changed. When a row changes, update the words, put the amendment number in the source column and move the status back to not started if the answer needs rewriting. The acknowledgment itself gets a row, with a signature owner, because a missed acknowledgment is a preventable way to lose.

Use the matrix as your final check

A few days before the close, give the matrix and the finished proposal to someone who has not written any of it. They go row by row, confirm that the answer exists at the stated page, and read it as an evaluator would. Anything they cannot find gets moved to where it can be found.

• Every requirement has a page number that is correct in the final file
• Every evaluation factor has a heading an evaluator can spot in seconds
• Every form, certification and amendment acknowledgment is present and signed
• Page counts and file formats meet the rules for each volume
• Page references were checked after the last edit, and the final file is the one you reviewed

Frequently asked questions