Building a Compliance Matrix
The Compliance tab turns your shred into a Ref / Requirement / Type / Where-addressed matrix — the artifact that keeps you from getting eliminated on a technicality.
The short answer
The Compliance tab turns your shred into a matrix: every requirement gets a row with Reference, Requirement text, Type (shall / must / will / format), and a Where-addressed column you fill in as you write. It is the artifact that prevents technical eliminations.
Why compliance eliminations happen
Contracting officers eliminate on the easy stuff first. Wrong page count. Missing SF-33. Volume submitted in the wrong file format. A required attestation you skipped because Section L.4.2 sub-bullet iii didn't feel important. A technically superior proposal gets thrown out at the gate every day of the week over exactly this.
How the matrix prevents them
Every shall in the RFP becomes a row. Every row has to point somewhere in your proposal by the time you submit. Rows that don't have a home are the shortlist of things that will disqualify you. Run compliance the day you decide to bid, not the day before submission.
Related help
Shredding an RFP
The Shred tab breaks a solicitation into requirements, Section L instructions, and Section M evaluation criteria — and flags the red flags.
ReadThe Bid/No-Bid Brief
The Evaluate tab produces a bid/no-bid recommendation with cited rationale, strengths, and gaps.
ReadCapture Plan, Pricing & Competitor Intel
The workspace tabs that turn a bid decision into a plan: capture, pricing intel (Pro), and competitor intel (Pro).
Read