The compliance matrix
How to build a compliance matrix: extracting every shall, must and will from a solicitation, mapping each to a response section, and proving coverage before submission.
A compliance matrix maps every requirement in a solicitation to the place in your response that answers it. It is the cheapest insurance in proposal work, and the thing most often skipped when a deadline gets close.
What it is, and what it is for
A compliance matrix is a table with one row per requirement. Each row records where the requirement came from, what it demands, where in your proposal it is answered, and who is responsible for that answer.
It has two audiences and they want different things from it. Internally it is a checklist that turns "did we answer everything" from a memory exercise into a lookup. Externally — when the solicitation asks for one, and many do — it is a navigation aid that tells an evaluator exactly where to find each item, on the page where they are already deciding whether you addressed it.
The second audience is why format matters. An evaluator working through a scoring sheet under time pressure is not hunting for your answer. If they cannot find it, the score is the same as if you had not written it.
The columns that earn their place
| Column | Holds | Why it matters |
|---|---|---|
| Reference | Section and paragraph number from the solicitation | The evaluator’s index. Use their numbering, not yours. |
| Requirement | The requirement, quoted or closely paraphrased | Paraphrasing loses the modal verb. “Shall” and “should” are different obligations. |
| Type | Mandatory, evaluated, or informational | Mandatory failures are disqualifying. Evaluated ones are where points live. |
| Response location | Volume, section and page | The column the evaluator actually uses. Page numbers must be final. |
| Owner | The person accountable for that content | Turns the matrix into an assignment list rather than a report. |
| Status | Not started, drafted, reviewed, final | Makes the gap visible while there is still time to close it. |
Where the solicitation prescribes a format for the matrix, use theirs exactly — including column order and headings. A better table that does not match the instruction is a deviation.
Building one
Read the whole package first, including the attachments
Requirements are distributed on purpose. The statement of work carries scope, Section L carries instructions, Section M carries evaluation criteria, and the attachments carry forms and certifications that are as mandatory as anything in the body.
Extract every obligation, not every sentence
Look for the modal verbs — shall, must, will, is required to — and for anything phrased as a submission instruction. “Offerors shall submit” is a requirement. “The Government intends” usually is not.
Split compound requirements
A single paragraph demanding a schedule, a staffing plan and a risk register is three rows. Left as one, it gets one answer covering whichever part the writer noticed.
Classify by consequence
Mandatory items fail you if missed. Evaluated items score you. Informational items shape the response but earn nothing directly. Time spent should follow that order.
Assign an owner to every row
An unowned row is the one nobody writes. Assignment before drafting is what makes the matrix a plan rather than an audit.
Fill in page numbers last, and verify them
They shift with every edit. A matrix pointing at the wrong page is worse than none: it sends the evaluator somewhere the answer is not and tells them you did not check.
What goes wrong
Built after the proposal
A matrix produced at the end is a report on gaps you no longer have time to close. Built first, it is the outline.
Requirements paraphrased into vagueness
“Shall provide 24/7 support with a 15-minute response” becomes “responsive support”. The obligation is now unmeasurable, and so is your compliance with it.
Attachments never read
Forms, certifications and representations are requirements. They are also the ones most often discovered the night before submission.
Amendments not folded back in
An amendment can add, delete or change requirements. A matrix built against the original document is a matrix for a solicitation that no longer exists.
Cross-references instead of answers
“See Section 3.2” inside a response is a redirect the evaluator may not follow. Where a requirement is evaluated in two places, answer it in both.
The last-day check
Common questions
- Do we submit the matrix even when it is not requested?
Usually yes, unless page limits make it expensive or the instructions prohibit additional material. It costs a page or two and makes the evaluator’s job easier, which is rarely a disadvantage. Check whether it counts against your page limit before including it.
- How do we handle a requirement we cannot fully meet?
Address it directly rather than leaving the row blank or answering an adjacent question. State what you do provide, how the gap is mitigated, and by when it closes if it does. An evaluator who finds an unanswered mandatory requirement has an easy decision; one who finds a candid answer has to weigh it.
- Should the matrix live in a spreadsheet?
A spreadsheet works and is where most teams start. The limitation shows up on amendments and on page numbers — both change, and a spreadsheet has no link back to the document, so both have to be re-checked by hand every time.
Related
Requirements and evaluation criteria extracted, with citations.
Deciding what not to bid, and writing down why.
Plan the outline, draft each section, compose the document.
See what you are not bidding on.
Connect a source, describe what your company does, and look at the opportunities that come back before deciding whether any of this is worth your time.