Proposals get eliminated for reasons that have nothing to do with how good the company is. A missing form. A page over the limit. A required topic nobody addressed because it was buried in an attachment. Evaluators work from the solicitation, and if they can't find what it asked for, they can't give you credit for it.
A compliance matrix is how you make sure that never happens. It's a table that lists every requirement in the solicitation, where it came from, where you answer it, and who owns it. It isn't glamorous, and it's the single best habit a small proposal team can build.
What a compliance matrix is (and isn't)
A compliance matrix maps each requirement in a solicitation to the place in your proposal that responds to it. Done well, it does four jobs at once:
- A checklist that proves you addressed everything the government asked for.
- An outline for the proposal itself, built in the order evaluators expect.
- An assignment sheet, where every requirement has an owner and a status.
- A final submission check before anything goes out the door.
It isn't a sales document, and it usually isn't submitted. Some solicitations do ask for a cross-reference table, and when they do, you include one. Otherwise it's your internal control.
Section L vs. Section M: the two sections that matter most
Many negotiated federal solicitations follow the Uniform Contract Format described in FAR 15.204, which splits the document into lettered sections. Three of them drive your matrix:
- Section C: description, specifications, and statement of work. What the contractor must actually do.
- Section L: instructions, conditions, and notices to offerors. How to build and submit your proposal, including volumes, page limits, fonts, file formats, required content, and the deadline.
- Section M: evaluation factors for award. How the government will judge proposals, including the factors, their relative importance, and the basis for award, such as a best-value tradeoff or lowest price technically acceptable.
Section L tells you what to write. Section M tells you what gets rewarded. The two don't always line up neatly. Section L might ask for a staffing plan while Section M evaluates 'management approach,' and the gaps between them are where proposals lose points. Your matrix should cross-walk them, so every L instruction connects to the M factor it supports and the C requirement it shows you can meet.
Reading the language: shall, must, will, should, may
Requirements hide in verbs. Before you start extracting, agree as a team on how you'll treat each one:
- Shall and must: mandatory. Every instance is a requirement that needs a response or a compliance confirmation.
- Will: read it in context. It often describes what the government will do ('the Government will evaluate'), but some solicitations use it for contractor obligations. If it describes something you do, treat it as mandatory.
- Should: a strong preference. Not strictly required, but evaluators may reward it. Track it.
- May: optional. Track it when it gives you a chance to show a strength.
Don't stop at verbs. Tables, notes under tables, attachments, the performance work statement, data deliverable lists, and every amendment can contain requirements written as plain statements, such as 'Resumes are limited to two pages.'
How to build a compliance matrix, step by step
Step 1: Collect the complete package
Download the solicitation, every attachment, every exhibit, and every amendment. Check SAM.gov (or the state or local portal) for amendments again right before you submit. Late amendments are common, and missing one is a classic reason a proposal is found noncompliant. Keep a list of amendment numbers so you can acknowledge each one exactly as instructed.
Step 2: Shred the solicitation
Shredding means pulling out every individual requirement as its own row. Go section by section. Each row gets a unique ID and an exact source reference: section, paragraph, and page. Copy the requirement text word for word. Don't paraphrase at this stage, because paraphrasing is where meaning drifts.
Step 3: Set up your columns
A practical matrix for a small team needs about ten columns:
- ID, for example L-4.2.1 or C-3.5
- Source reference: section, paragraph, page, and the amendment that changed it, if any
- Requirement text, verbatim
- Type: submission instruction, evaluation factor, performance requirement, or format rule
- Related Section M factor
- Proposal volume and section where you respond
- Owner
- Status: not started, drafted, reviewed, final
- Compliance: full, partial, or exception
- Notes and evidence: the proof point, past performance reference, or graphic that supports the answer
Step 4: Cross-walk L, M, and C
Link every Section L instruction to the Section M factor it supports and the Section C requirements it addresses. Where a Section M factor has no matching L instruction, flag it. You still need to address it, and you'll need to decide where.
Step 5: Build the outline from the matrix
Your proposal outline should mirror Section L's order and numbering and use the government's own headings. Evaluators score against the solicitation. Make it easy for them to find each answer exactly where they expect it.
Step 6: Assign owners and track status
Every row gets one owner: a name, not a department. Review the matrix at each proposal check-in. Any row that stays 'not started' for two check-ins gets escalated.
Step 7: Update for every amendment
When an amendment arrives, compare it with the original and update the affected rows, noting which amendment changed what. Amendments can change page limits, due dates, evaluation factors, or the work itself.
Step 8: Run a final compliance check
Before submission, someone who didn't write the proposal walks the matrix row by row against the final document: every requirement addressed, every page limit met, every form signed, every amendment acknowledged, every file named and formatted as instructed. Keep this separate from your quality review. Quality asks whether it's persuasive. Compliance asks whether it's all there.
Common mistakes that get proposals thrown out
These are the failures we see most often, and nearly all of them are preventable with a disciplined matrix:
- Late submission. The government generally can't consider late proposals outside narrow exceptions (see FAR 15.208). Treat the deadline as an hour earlier than stated, and test the submission method before the due date.
- Missing amendment acknowledgments. Acknowledge every amendment in exactly the way the solicitation specifies.
- Exceeding page limits. Pages over the limit may not be read, and some solicitations treat the whole proposal as noncompliant. Check what counts toward the limit; covers, tables of contents, resumes, and attachments are handled differently in each solicitation.
- Ignoring format rules. Font size, margins, file type, file naming, and file size limits are requirements, not suggestions.
- Pricing in the wrong volume. Many solicitations prohibit price information anywhere outside the price volume.
- Missing representations, certifications, or signatures on required forms.
- An inactive SAM.gov registration. Registration generally must be active when you submit an offer (see FAR 52.204-7).
- Answering the question you wish they had asked. Pasting standard capability language instead of responding to the specific requirement in front of you.
- Requirements buried in attachments. The performance work statement, deliverable lists, and other exhibits all contain obligations that belong in the matrix.
How AI speeds this up, safely
Shredding a 120-page solicitation by hand can take a full day. AI can do a first pass in minutes, and it's genuinely good at the tedious part: finding every shall and must, pulling requirements out of dense paragraphs, and grouping them by section. But a compliance matrix is a control, and a control is only as trustworthy as its verification. A few rules keep AI useful instead of risky:
- Every extracted requirement must carry a source reference (section, paragraph, page) so a person can check it against the original in seconds.
- A person reviews every row. AI can miss requirements in tables, scanned pages, or attachments, and it can paraphrase in a way that changes the meaning.
- Run your own spot check: pick ten requirements from the solicitation at random and confirm each one made it into the matrix.
- Never let AI decide compliance status. It drafts; your team confirms.
In Contract Command, this is the job of Checkpoint, one of the Command Agents. Checkpoint reads the solicitation package, drafts a compliance matrix with a source reference on every row, flags shall and must language, and cross-walks instructions to evaluation factors. Nothing it produces is final until a person on your team approves it. The matrix then sits beside the proposal and pricing workspace, so owners and statuses live in one place instead of a spreadsheet emailed back and forth.
The takeaway
- Build the matrix before you write a single paragraph.
- Shred verbatim, with a source reference on every row.
- Cross-walk Section L, Section M, and Section C, or their equivalents in commercial and state or local solicitations.
- Mirror Section L's structure and the government's headings in your outline.
- Update for every amendment, and run a separate compliance check before you submit.
- Use AI for the first pass, and keep a person accountable for every line.