The table that maps every requirement in Sections L, M, and C/PWS to where you answer it, who owns it, and whether it's done. The spine of the proposal — and the thing that loses you the bid if a single “shall” goes unanswered.
When you reach for it. Day one after RFP drop, before anyone writes a word. It's the first artifact built and the last thing checked before submission.
Copy, paste into your document, fill the brackets.
| Req ID | Source (L/M/C + ¶) | Shall statement (one testable obligation) | Response location | Owner (name) | Status | Win theme / proof link |
|--------|--------------------|--------------------------------------------|-------------------|--------------|--------|------------------------|
| | | | | | | |Copy, paste into Claude, add your own inputs.
You are a proposal manager building a compliance matrix.
I will paste raw text from Sections L, M, and C/PWS.
For each requirement:
1. Atomize compound “shall” statements into one testable obligation per row.
2. Tag the source section and paragraph.
3. Note whether it is a WRITE instruction (L), an EVALUATION factor (M),
or a WORK requirement (C/PWS) — and flag any C/PWS requirement that
Section M scores, since those carry the most weight.
4. Leave response location, owner, and status blank for me to fill.
Return a markdown table. Do not invent requirements not in the text.| Req ID | Source | Shall statement (atomized) | Response loc. | Owner | Status | Strategy link |
|---|---|---|---|---|---|---|
| C.5.1a | PWS 5.1 | Contractor shall migrate all production workloads to a FedRAMP High environment. | Vol I §3.2 | Okafor | compliant | WT-2 (blue-green) |
| C.5.1b | PWS 5.1 | Contractor shall maintain continuity of citizen-facing services during migration. | Vol I §3.2 | Okafor | drafted | WT-2 |
| M-2 | Sec M | Approach evaluated on transition risk mitigation. | Vol I §3.4 | Reyes | reviewed | WT-2, PP-1 |
| L.3.2 | Sec L | Submit transition plan not to exceed 10 pages. | Vol I §3.4 | Reyes | not started | — |
Every shall is atomized to one testable obligation. M is mapped, not just L. Owners are people. The matrix is the meeting agenda, not a document generated at the end to look compliant.
Compound requirements left whole (“shall provide and maintain and report…”). Only Section L mapped. “Various” in the owner column. Built after the proposal instead of driving it.
Grab it here when you’ve got it handled. When the bid matters more than the afternoon, a senior operator builds it — right, on deadline, as part of the pursuit.
Start with the Sprint →