What goes in the matrix
- Every mandatory (pass/fail) requirement
- Every scored evaluation criterion and its weight, if published
- Submission rules: page limits, forms, certifications, file formats, deadlines
- Amendments that add or change requirements mid-cycle
- Status: not addressed, partially addressed, or addressed - with a pointer to the response section
Why it matters
Agencies often screen for administrative compliance before anyone scores technical content. A missed form, unacknowledged amendment, or unanswered mandatory item can end the pursuit regardless of how strong the team is. The matrix is the operational tool that keeps that from happening.
How Flodoc helps
Flodoc extracts requirements from an uploaded RFP or RFQ and tracks each one's status as you assemble the response - so the team reviews coverage instead of rebuilding a spreadsheet from scratch for every pursuit.
How to build a compliance matrix step by step
Building a compliance matrix is a reading exercise before it is a formatting exercise. Work through the solicitation from front to back and flag every sentence that creates an obligation. Directive language is the signal - words like shall, must, will, required, and responsive point to something the agency expects you to do or provide. Softer words like should or may often carry weight too, so capture them and mark them as recommended rather than mandatory.
- Parse the document for obligations. Read the request for proposal and every attachment, then extract each shall, must, will, required, and responsive statement into its own row.
- Assign a stable ID to each requirement. A short identifier such as C-001 lets the whole team reference the same item without confusion, even after the document is reformatted.
- Record the source location. Note the page and section number so anyone can trace the requirement back to the exact place it came from.
- Assign an owner. Every row needs one named person responsible for satisfying it - not a department, a person.
- Point to the response location. Note where in your proposal the requirement is addressed, whether that is a section, a page, or a specific form.
- Track status. Give each row a state such as not started, in progress, or complete, and update it as the work moves.
A suggested column layout
A compliance matrix does not need to be elaborate to be effective. A simple table that everyone reads the same way is far more useful than a detailed one that only its author understands. The layout below covers the essentials and can be extended with columns for weight or evaluator notes when the solicitation is scored.
| ID | Requirement | Source | Owner | Response location | Status |
|---|---|---|---|---|---|
| C-001 | Requirement text as written in the solicitation | Section and page reference | Named owner | Where the response lives | Not started, in progress, or complete |
| C-002 | Requirement text as written in the solicitation | Section and page reference | Named owner | Where the response lives | Not started, in progress, or complete |
Who owns it and when to start
The compliance matrix belongs to a single person, usually the proposal lead or coordinator, even though many contributors fill in the rows. Central ownership keeps the document consistent and prevents the version drift that happens when several people maintain separate copies. Start the matrix on day one, as soon as the solicitation is in hand, rather than treating it as a final check. Building it early forces an early read of the requirements, surfaces hard obligations while there is still time to respond to them, and gives owners a running view of what remains.
How it prevents disqualification
Administrative compliance is typically screened before any evaluator reads your technical approach. A proposal that misses a mandatory form, exceeds a page limit, or skips a required certification can be set aside before its merits are ever considered - regardless of how strong the underlying qualifications are. The compliance matrix guards against this by making every obligation visible and assigning accountability for each one. When each mandatory item has a named owner and a tracked status, nothing quietly falls through the cracks. This is the difference between clearing the bar to be evaluated and never getting the chance to compete on the merits.
This screening step is separate from how your proposal is scored. For more on that distinction, see evaluation criteria. For a practical walkthrough, the AEC RFP compliance checklist covers the same ground in workflow form.
Keeping the matrix current through amendments
A solicitation rarely stays fixed. Agencies issue amendments that change due dates, add or remove requirements, revise page limits, or answer questions in ways that create new obligations. When an amendment lands, the compliance matrix has to be reconciled against it - add rows for new requirements, revise or retire rows that changed, and reset the status on anything affected. Treat each amendment as a required pass through the matrix rather than an optional update. A matrix that reflects the original document but not the latest amendment can give a false sense of completeness, which is more dangerous than having no matrix at all.
For the broader context of how these documents move through a public agency process, see the government AEC RFP playbook.