Compliance matrix template: map every RFP requirement to your answer
Short answer: A compliance matrix is a table that lists every requirement in an RFP, one per row, with your compliance status (Comply, Partial, Exception), where in your response it's answered, and who owns it. Build it the day the RFP arrives, before anyone writes, and use it to make sure nothing is missed. Many teams submit a version of it with the response so evaluators can find each answer quickly.
Who this is for: proposal managers, bid managers and capture teams responding to commercial RFPs or government solicitations.
On this page
- What is a compliance matrix?
- Why does a compliance matrix matter?
- What columns should a compliance matrix have?
- Filled-in compliance matrix example
- How do you build a compliance matrix step by step?
- How do Section L and Section M fit into a compliance matrix?
- Free compliance matrix template
- How Iris helps
- FAQ
What is a compliance matrix?
A compliance matrix (also called a requirements matrix or, in a more detailed form, a requirements traceability matrix) is the master list of everything an RFP asks you to do, provide or confirm. Each row is one requirement. The columns record what the requirement says, whether you comply, where your response addresses it, and who's responsible.
It has two audiences:
| Version | Audience | Purpose |
|---|---|---|
| Internal (working) matrix | Your bid team | Tracks ownership, status, drafts and gaps through the response |
| Submitted matrix | The buyer's evaluators | Shows, requirement by requirement, where the answer is in your response |
The internal version has more columns (owner, due date, status, notes). The submitted version is usually trimmed to reference, requirement, compliance and response location. Submit it only if the RFP asks for or allows it.
Why does a compliance matrix matter?
- Nothing gets missed. Requirements hide in scope sections, attachments, terms and conditions, and addenda. A missed "shall" can make a response non-compliant.
- Evaluators can score you faster. If they can find each answer, you're less likely to lose points for something you did answer.
- It's your go/no-go evidence. Counting Comply, Partial and Exception rows tells you how well you fit. See the go/no-go scorecard.
- It drives the work. Every row has one owner and a due date, which turns a large RFP into an assignable list.
- It keeps the story consistent. The cover letter's compliance statement and the executive summary's compliance line come straight from it.
What columns should a compliance matrix have?
| Column | What goes in it | Internal | Submitted |
|---|---|---|---|
| Req ID | Your unique ID for the row (e.g. R-001) | ✓ | Optional |
| RFP reference | Section, page and paragraph, exactly as numbered in the RFP or attachment | ✓ | ✓ |
| Requirement text | The requirement copied verbatim. Don't paraphrase | ✓ | ✓ |
| Type | Mandatory (shall / must) · Desirable (should / may) · Instruction · Evaluation factor | ✓ | Optional |
| Compliance | Comply · Partial · Exception · N/A (with reason) | ✓ | ✓ |
| Response location | Volume, section and page of your answer | ✓ | ✓ |
| Owner | One named person | ✓ | |
| Due date | Internal deadline for a draft | ✓ | |
| Status | Not started · Drafted · In review · Approved | ✓ | |
| Evidence | Attachment, policy, certificate or reference that supports the answer | ✓ | Optional |
| Notes / alternative | For Partial or Exception: the workaround or alternative offered | ✓ | ✓ for Partial/Exception |
Tip: treat "shall", "must", "will" (when describing the vendor) and "required" as mandatory, and "should", "may" and "preferred" as desirable, unless the RFP defines its own terms. Check the definitions section first.
Filled-in compliance matrix example
A fictional vendor responding to a fictional county RFP for a records-management system:
| Req ID | RFP ref | Requirement (verbatim) | Type | Compliance | Response location | Owner | Status | Notes / alternative |
|---|---|---|---|---|---|---|---|---|
| R-001 | §3.1.1 | The system shall support role-based access control. | Mandatory | Comply | Vol I §4.2, p.12 | Security lead | Approved | |
| R-002 | §3.1.4 | The system shall retain records for the periods in Attachment B. | Mandatory | Comply | Vol I §4.6, p.18 | Product lead | In review | Attachment B mapped in Appendix C |
| R-003 | §3.2.2 | The vendor should provide on-site training. | Desirable | Partial | Vol I §6.1, p.24 | Delivery lead | Drafted | Live virtual training offered; on-site at additional cost |
| R-004 | §3.4.1 | Data shall be hosted within the state. | Mandatory | Exception | Vol I §4.8, p.20 | Security lead | In review | US-region hosting proposed; see alternative and data-protection controls |
| R-005 | §5.2 | Proposals shall not exceed 40 pages excluding appendices. | Instruction | Comply | Whole of Vol I | Proposal manager | Approved | 38 pages |
| R-006 | Addendum 2, Q14 | Vendor shall provide two municipal references. | Mandatory | Comply | Vol II §2, p.3 | Sales lead | Drafted | References confirmed with permission |
| R-007 | §7.1 (Eval) | Technical approach, 40% of total score | Evaluation factor | N/A | Vol I §4 | Proposal manager | Approved | Highest weight; lead with it in exec summary |
What to notice: R-004 is a mandatory requirement the vendor can't fully meet. The matrix forces that decision early: either it's a knockout (No-go), or the team offers an alternative and says so plainly. R-005 and R-007 show that instructions and evaluation factors belong in the matrix too, not just technical requirements. R-006 came from an addendum, which is where requirements most often get missed.
How do you build a compliance matrix step by step?
- Collect every document: the RFP, all attachments, forms, the draft contract, and every addendum and Q&A response.
- Read for requirement words. Highlight every shall, must, will, required, should and may, plus every instruction about format, page limits and submission.
- One requirement per row. If a sentence contains two requirements ("shall encrypt data and shall log access"), split it into two rows.
- Copy text verbatim and record the exact reference. Paraphrasing is how requirements get subtly changed.
- Classify the type (mandatory, desirable, instruction, evaluation factor).
- Decide compliance honestly. Partial and Exception are legitimate answers. A false "Comply" is the most expensive mistake in the matrix.
Assign one owner and a due date per row.
Map your outline to the matrix. Every row should point to a section of your response; every section should trace back to at least one row.
- Update it as addenda arrive. Add rows; don't overwrite.
- Do a final check before submission: filter for rows without a response location or with status other than Approved.
How do Section L and Section M fit into a compliance matrix?
In US federal solicitations that use the uniform contract format, Section L is "Instructions, conditions, and notices to offerors or respondents" (how to structure and submit the proposal), and Section M is "Evaluation factors for award" (how proposals will be scored). Section C usually holds the statement of work, the source of most technical requirements. (FAR 15.204-1.)
A strong federal compliance matrix cross-references all three:
| Column | Source |
|---|---|
| Requirement | Section C (statement of work) and attachments |
| Proposal instruction | Section L: which volume, page limit, format |
| Evaluation factor | Section M: which factor or subfactor it's scored under |
| Response location | Your volume and section |
Organize your response in the order Section L prescribes, and make sure every Section M factor has a clearly labelled place in it. Commercial RFPs rarely use these labels, but most have equivalents: a "submission instructions" section and an "evaluation criteria" section. Map them the same way.
Free compliance matrix template
Copy this into a spreadsheet.
COMPLIANCE MATRIX
Buyer: [ ] RFP no.: [ ] Title: [ ] Due: [date]
Addenda included: [Addendum 1, date] [Addendum 2, date]
Matrix owner: [name] Last updated: [date]
Req ID | RFP ref | Requirement (verbatim) | Type | Compliance | Response location | Owner | Due | Status | Evidence | Notes / alternative
R-001 | [§x.x] | [text] | [Mandatory/Desirable/Instruction/Eval factor] | [Comply/Partial/Exception/N/A] | [Vol, §, p.] | [name] | [date] | [Not started/Drafted/In review/Approved] | [doc] | [ ]
R-002 | ...
SUMMARY
Mandatory requirements: [n] · Comply [n] · Partial [n] · Exception [n]
Desirable requirements: [n] · Comply [n] · Partial [n] · Exception [n]
Rows without a response location: [n] Rows not yet approved: [n]
How Iris helps
Iris is AI software for RFP, security questionnaire and DDQ responses. Two parts of it map directly onto building a compliance matrix:
- Question and requirement extraction. Upload the RFP (Excel, Word, PDF or CSV). Iris pulls out every question and requirement, keeps the document's hierarchy, and makes each numbered sub-item its own row. Rows are checked word-for-word against the source, and anything it can't verify is flagged for a reviewer rather than silently rewritten.
- Requirement fit before you commit. Iris's RFP Analyzer checks each requirement against your own content and marks it met, partial or likely not met, with sources, so your first-pass Compliance column has evidence behind it.
- Then the work. Assign rows to owners, draft from your approved content with sources on every answer, and export back into the original file or your branded Word template.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is a compliance matrix in an RFP?
A table listing every RFP requirement with your compliance status and where in your response it's answered. It makes sure nothing is missed and helps evaluators find your answers.
What's the difference between a compliance matrix and a requirements traceability matrix?
They overlap. A requirements traceability matrix usually traces each requirement further, for example through design, delivery and testing after award. In proposal work the terms are often used interchangeably.
Should I submit the compliance matrix with my proposal?
If the RFP asks for it, yes, in the format it specifies. If it's silent, submitting a trimmed version usually helps evaluators, but check page limits: some RFPs count it.
What do I put when we don't fully comply?
Mark it Partial or Exception and describe the alternative in the notes. Honest partial compliance with a workaround is better than a "Comply" that an evaluator, or the contract, later proves wrong.
What are Section L and Section M?
In US federal solicitations, Section L contains proposal instructions and Section M contains evaluation factors for award (FAR 15.204-1). Your matrix should map requirements to both.
How detailed should each row be?
One requirement per row, copied verbatim. If a sentence contains two "shall" statements, split it.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
