Building a compliance matrix: trace every requirement to your proposal

A compliance matrix is the single list of everything a solicitation asks for, each item mapped to the person who owns it and the place in your proposal that answers it. It protects you from the most avoidable way to lose: an evaluator who cannot find your response to a requirement. Under FAR 15.305, agencies evaluate proposals solely on the factors and subfactors the solicitation specifies, so a proposal that traces every instruction and evaluation criterion to a clear answer starts ahead.

Where requirements hide#

A good matrix pulls from the whole solicitation, not just the instructions:

• Section L (or the FAR 52.212-1 addendum on commercial buys): volumes, page limits, formatting, required content, forms and submission rules
• Section M (or the FAR 52.212-2 addendum): every evaluation factor and significant subfactor, their relative importance and the basis for award, which FAR 15.304 requires the solicitation to state
• Section C, the PWS, SOW or statement of objectives: every "shall" and "must" that describes the work
• Section B: the CLIN structure the price volume must follow
• Sections H and I: special requirements and clauses with proposal impact, such as key personnel, CMMC level (DFARS 252.204-7021 and 252.204-7025), NIST SP 800-171 assessment currency (DFARS 252.204-7019 and 7020) or Limitations on Subcontracting (FAR 52.219-14)
• Section J attachments: CDRLs, the DD Form 254, the QASP, pricing templates and past performance questionnaires
• Section K and SAM.gov: representations and certifications, including any the solicitation adds
• Amendments and questions and answers: each one can add, delete or change requirements

The columns that matter#

Build it step by step#

1. Shred the solicitation. Extract every instruction, evaluation criterion and "shall", "must" and "is required to" statement. Read "will" statements carefully: some describe the Government's actions, others the contractor's obligations.
2. Keep the source's numbering. Your IDs should let anyone find the original text in seconds.
3. Build the outline from Section L, using its order, numbering and headings, and label where each Section M factor is addressed. When L and M disagree or leave gaps, ask in the Q&A period rather than guessing.
4. Map every performance requirement from Section C or the PWS to the technical section that answers it. Requirements with no home in the outline are your gaps.
5. Assign owners and dates, including teammates who supply resumes, past performance or technical inputs.
6. Re-shred every amendment and record the amendment number against each changed row.
7. Use it in every review. Pink and Red Team reviewers should work from the matrix, asking where each requirement is answered and how well.
8. Run a final compliance check against the matrix before production locks.

Final compliance checks#

Common pitfalls#

• Paraphrasing requirements. Rewording a requirement can change its meaning. Quote it.
• Building the matrix once. A matrix that is not updated with amendments and Q&A answers gives false confidence.
• Skipping the attachments. CDRLs, the DD Form 254 and the QASP often contain requirements the main document does not repeat.
• Mapping to Section L only. Following the instructions without addressing the evaluation criteria produces a compliant proposal that scores poorly.
• Confusing compliance with winning. Compliance gets you evaluated; strengths and proof win. See the proposal process.

How TeamingIndex helps#

• Draft a first-pass compliance matrix with the AI analyst: paste Section L and M or the PWS and get a requirement-by-requirement matrix in which each row cites its source, so your team can check it against the solicitation. Never paste CUI or export-controlled text: inputs pass TeamingIndex's Zero-CUI guard, which rejects marked text (see CUI and Zero-CUI practices).
• Start from a notice in Live RFPs and keep the pursuit's gates, such as CMMC level or facility clearance, in the Team Builder.
• Check that your partners meet the clause-driven gates before you write them into the proposal: see NIST SP 800-171 assessment currency.