Proposals · 12 Min Read · Includes Free Template And Checklist
How To Build A Compliance Matrix For An RFP
A step-by-step method for turning a federal solicitation into a compliance matrix your team can write from, with the columns to use, a worked example, a shredding test and a checklist.
Quick Answer
A compliance matrix is a table that lists every requirement in a solicitation, where it comes from (Sections C, L and M, attachments, amendments and Q&A answers) and exactly where your proposal answers it. Build it before anyone writes, give every row an owner and a status, and update it for every amendment. Used that way, it becomes your outline, your work plan and your final compliance check.
What Is A Compliance Matrix?
A compliance matrix (also called a requirements compliance matrix or RFP compliance matrix) is a working table with one row for each requirement in a solicitation. Each row records the requirement word for word, where it came from, which part of your proposal answers it, who owns it and how far along that answer is.
It answers one question for your team, at any point before submission: have we answered everything the government asked for, in the place and format it asked for?
| Term | What it means | Who sees it |
|---|---|---|
| Compliance matrix | Your internal tracker: every requirement, its owner, its status and where it is answered | Your proposal team |
| RFP shred | The raw list of requirements pulled out of the solicitation, one per line. It becomes the first columns of the matrix | Your proposal team |
| Cross-reference matrix | A short table that tells evaluators where to find each requirement in your proposal | Evaluators, only if Section L allows or asks for it |
In engineering, "compliance matrix" can also mean a table of technical specifications for a product. This guide is about the proposal version.
Why It Matters: Compliance Is Checked First
Evaluators can only score what you submit in the way they asked for it. A proposal that misses a required section, goes over a page limit or ignores a format rule can lose points or be set aside before anyone reads your solution. Offerors are responsible for format errors even when they are easy to fix.
Being compliant does not win on its own. It gets you into the competition. That is why a good matrix also records which Section M factor each requirement is scored under, so you can spend your pages where the points are.
Where Requirements Hide In A Federal RFP
Most federal RFPs follow the uniform contract format in FAR 15.204-1, which the overhauled FAR Part 15 keeps at 15.109. Requirements are spread across it. Your matrix needs all of these, not just the work statement:
| Where | What you find there | Easy to miss because |
|---|---|---|
| Section C (work statement) | Tasks, deliverables, performance standards | Requirements sit inside long paragraphs and tables |
| Section L (instructions) | Volumes, order, page limits, fonts, file formats, due date and method | Teams treat it as admin, but breaking it can cost the bid |
| Section M (evaluation) | Factors, subfactors and their relative importance | It holds few "shall" statements, so shredding tools skip it |
| Section H (special requirements) | Key personnel, security, staffing or reporting conditions | It reads like contract terms, not proposal content |
| Section J attachments | Work statements, deliverables lists, pricing templates, forms | They are separate files, often added late |
| Amendments | Changes to any of the above, including due dates | Each one can change a requirement you marked complete |
| Q&A answers | The government's answers to offerors' questions | They clarify or quietly change what is required |
RFQs, GSA schedule orders and task orders often skip the uniform format. Find the equivalents instead: the instructions, the basis for award and the work statement.

Free Template
Get The Compliance Matrix Template
An Excel workbook with a Start Here guide, 200 ready rows with dropdowns, a coverage box that counts compliant items and gaps for you, and a filled example built on a fictional RFP.
Get The Free Template →The Columns Every Compliance Matrix Needs
Keep it simple enough that people actually update it. These ten columns cover what most small business proposals need:
| Column | What goes in it | Why it matters |
|---|---|---|
| ID | A tracking number such as C-014 or L-003 | Lets reviewers talk about one row without confusion. Never renumber once drafting starts |
| RFP section | C, L, M, H, J, amendment or Q&A | Shows the type of requirement at a glance |
| Paragraph reference | The exact paragraph number | Lets anyone check the source in seconds |
| Requirement text | The words copied exactly | Writers answer what was asked, not what someone remembers |
| Shall/must flag | Yes if it says shall, must or will | Separates the mandatory items from the helpful ones |
| Proposal volume and section | Where you answer it, using your outline numbering | Turns the matrix into your outline |
| Section M factor | The factor this row is scored under | Shows where the points are |
| Owner | One named person | A row owned by "the team" is owned by nobody |
| Status | Not started, drafting, drafted, in review, compliant or gap | Shows progress and problems early |
| Final page reference | The page where an evaluator will find the answer | The last check before you submit |
How To Build A Compliance Matrix In 7 Steps
- Collect Every Document. Download the full solicitation package: every section, attachment, amendment and Q&A release. Note the latest amendment and Q&A you included at the top of the matrix.
- Read The Whole Thing Once Before You Extract Anything. You will understand how the sections relate, spot conflicts between L and M, and find requirements hiding in attachments.
- Shred Sections L, M And C Into Rows. Copy every requirement word for word, one per row. Start with Section L, because it decides your outline, then Section M, then Section C, then H and the attachments.
- Split Compound Requirements. If one sentence holds two "shall" statements, give it two rows. Each needs its own answer and its own status.
- Map Each Row To Your Outline. Build the outline from Section L's order and wording, then give every row a proposal section. Any row without a home is a gap in your outline.
- Assign An Owner And A Status. One person per row. Review the status at every team meeting, and treat "gap" as a call for help, not a failure.
- Keep It Live Until Submission. Add rows for every amendment and Q&A answer, re-check rows they affect, and fill in final page references during the last review.
Every requirement should travel this whole path before you submit.
How To Shred A Requirement Properly
The most common shredding mistake is putting several requirements in one row. Here is the same sentence shredded two ways. The example is fictional.
"The contractor shall provide Tier 1 and Tier 2 IT help desk support from 7:00 a.m. to 6:00 p.m. Eastern, Monday through Friday, and shall resolve Tier 1 tickets within four business hours."
C-001: Provide help desk support and resolve tickets.
It paraphrases, drops the hours and the four-hour standard, and gives two requirements one status. One can be finished while the other is missing, and the matrix will not show it.
C-001 (C.3.1): "The contractor shall provide Tier 1 and Tier 2 IT help desk support from 7:00 a.m. to 6:00 p.m. Eastern, Monday through Friday."
C-002 (C.3.2): "...and shall resolve Tier 1 tickets within four business hours."
Each requirement has its own words, reference, owner and status. The four-hour standard can now be tracked and checked on its own.
Example: A Compliance Matrix For A Fictional RFP
These rows come from the example tab in our free template, built on a fictional IT help desk RFP. Notice the amendment row: it changes a requirement the team had already drafted.
| ID | Source | Requirement (shortened here) | Proposal section | Owner | Status |
|---|---|---|---|---|---|
| L-001 | L.2.1 | Volume I shall not exceed 15 pages | All of Volume I | Proposal Manager | Compliant |
| C-001 | C.3.1 | Provide Tier 1 and Tier 2 help desk support, 7 a.m. to 6 p.m. | 2.1 Help Desk Operations | Technical Lead | Compliant |
| C-002 | C.3.2 | Resolve Tier 1 tickets within four business hours | 2.2 Ticket Resolution | Technical Lead | Gap |
| L-005 | L.3.3 | Provide resumes for the Help Desk Lead and Tier 2 Engineer | Appendix A Resumes | Program Manager | Gap |
| M-001 | M.2 | Technical approach is the most important factor | 2.0 Technical Approach | Technical Lead | Drafted |
| A-001 | Amendment 0001 | Changes the Tier 1 resolution standard from four to three business hours | 2.2 Ticket Resolution | Technical Lead | In review |
Two lessons from this example. First, the amendment turned C-002 from finished into a gap, because section 2.2 still promised four hours. Without a row for the amendment, nobody would have caught it. Second, L-005 shows a required resume that is not ready yet. The matrix surfaced that staffing problem weeks before submission, while there was still time to fix it.
How To Use The Matrix In Reviews
| Review | When | What to check in the matrix |
|---|---|---|
| Kickoff | Before writing starts | Every row has a section, an owner and a page budget |
| First draft review | When a full draft exists | Every row is drafted; gaps have a plan and a date |
| Final review | Before production | Every row is compliant; final page references are filled in |
| Submission check | The day you submit | Format, file names and delivery rules from Section L are met |
Give reviewers the matrix with the draft. They should score the proposal against Section M and check it against the matrix, not just read it for flow. An independent proposal review does exactly this.
Spreadsheet, Software Or AI?
For most small businesses, a spreadsheet is enough. It is free, everyone can open it and it works for proposals with a few hundred requirements. Proposal software and AI tools can pull "shall" statements out of a long RFP much faster. If you use them, check the output against the solicitation yourself: tools can miss requirements in tables, attachments and Section M, and they can paraphrase text you should copy exactly. Keep sensitive solicitation material out of public AI tools.
Common Mistakes That Cost Points
- Shredding only Section C and missing the instructions in Section L
- Skipping Section H, attachments, amendments and Q&A answers
- Paraphrasing requirements instead of copying them
- Putting two or more requirements in one row
- Building the matrix after writing has started
- Marking rows compliant before anyone has reviewed them
- Leaving final page references blank at submission
- Renumbering rows halfway through, so nobody can follow the history
The Compliance Matrix Checklist
Use this on every proposal. Tick items off as you go, or copy the whole list into your kickoff notes.
Compliance Matrix Checklist
Tip: copy this checklist into your notes at kickoff, and assign an owner to each line.
Key Takeaways
- Build the matrix before anyone writes. It becomes your outline and work plan.
- Shred everything: Sections L, M, C and H, attachments, amendments and Q&A answers.
- Copy requirements word for word, one per row, each with one owner.
- Update it for every amendment and use it in every review.
Frequently Asked Questions
What should a compliance matrix include?
At minimum: a requirement ID, its source and paragraph reference, the requirement text copied exactly, where your proposal answers it, an owner and a status. Adding the Section M factor, a shall/must flag and a final page reference makes it far more useful.
Is a compliance matrix required in a government proposal?
Usually not, unless Section L asks for one. Some solicitations ask offerors to include a cross-reference matrix. Even when it is not required, building one is the most reliable way to make sure you answer every requirement.
What is the difference between a compliance matrix and an RFP shred?
The shred is the list of requirements pulled from the solicitation, one per line. The compliance matrix adds where each one is answered, who owns it and its status, so you can manage the proposal with it.
Can I submit my compliance matrix with the proposal?
Only if the solicitation allows it. Check Section L for whether a matrix is permitted and whether it counts toward the page limit. If it does not say, ask the contracting officer during the question period.
How long does it take to build a compliance matrix?
It depends on the size of the solicitation. A short RFP can take a few hours; a large one with many attachments can take several days. Starting from a template with the columns already set up saves time.
Who should own the compliance matrix?
The proposal manager usually owns the matrix itself, while each row is owned by the person who writes or supplies that part. On a very small team, the same person may do both.
Want A Second Check On Compliance?
Our Proposal Review checks your draft against every Section L and M requirement, scores it the way an evaluator would and ranks the fixes by the points at stake.
Sources
- Acquisition.gov: FAR 15.204-1, Uniform Contract Format
- Acquisition.gov: FAR Overhaul, Part 15, including 15.109 Uniform Contract Format
- SmallGovCon: It's Not Up To Agency To Clarify Layout And Printing Errors In Proposals, Says GAO
Related Guides
Talk To Us About Your Next Bid
Book a free call at a time that suits you. We will come back with a clear view of where to start.