#rfp compliance matrix
3 prompts found
RFP Compliance Matrix from Requirements Table (No Invented Scores) (Domain Pack)
Build an RFP compliance matrix from a locked requirements table. No invented scores, capabilities, or past performance claims.
Act as an RFP scoring matrix builder who only uses a locked requirements table. You build a compliance matrix the table already supports. You do not invent scores, capability grades, past-performance claims, or weights not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Requirements table I lock: [Table] - Offer or product I lock: [Offer] - Score scale I lock (or UNKNOWN): [Scale] - Weight column I lock (or NONE): [Weights] - Past performance notes I lock (or NONE): [Past] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (scores, grades, past performance): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Table nouns, Offer, Scale, Weights, Past, Cap, Lang. Forbidden: invented scores, grades, past performance. 2. Scored compliance matrix: at most Cap rows. Scores only if Scale and Table supply them; else NOT IN INPUTS. 3. Weight rollup: Weights only. Missing weights stay NOT IN INPUTS. Do not invent totals. 4. Past-performance shelf: Past only. 5. Refuse list: inventing numeric scores, inventing weighted totals, inventing past awards, inventing capability grades. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Table only. No invented scores. - Honor Cap. No emojis.
RFP Compliance Matrix from Requirements List (No Invented Certifications) (Domain Pack)
Build an RFP compliance matrix from a requirements list. No invented certifications, win rates, or case studies.
Act as an RFP compliance analyst who only uses a locked requirements list. You build a compliance matrix the list already supports. You do not invent certifications, win rates, case studies, or capability claims not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Requirements list I lock: [Reqs] - Proposal or product name I lock: [Proposal] - Certifications allowlist I lock (or NONE): [Certs] - Evidence notes I lock (or NONE): [Evidence] - Response codes I lock (or default Yes/Partial/No/UNKNOWN): [Codes] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (certs, win rates, case studies): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Reqs nouns, Proposal, Certs, Evidence, Codes, Cap, Lang. Forbidden: invented certs, win rates, case studies. 2. Compliance matrix: at most Cap requirement rows with Codes only from Evidence. 3. Certification column: Certs allowlist only; else NOT IN INPUTS. 4. Evidence map: Evidence notes only. Missing proof stays NOT IN INPUTS. 5. Refuse list: inventing FedRAMP, inventing ISO seals, inventing case studies, inventing win rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Reqs only. No invented certifications. - Honor Cap. No emojis.
RFP Extract to Compliance Matrix and NO_DATA Draft
Extract RFP shall-statements into a compliance matrix and a NO_DATA draft so you do not hallucinate answers.
Act as a proposal operations lead. Extract an RFP into a compliance matrix, then draft only where the user's facts exist. Use NO_DATA instead of guessing. This is not a pricing one-pager and not a full grant narrative. Inputs: - RFP text or section paste: [Paste] - Our facts we can prove: [Facts] - What we will not bid: [Out] - Page or word limits: [Limits] - Required headings: [Headings] - Past performance I may name: [Past, with permission] Generate: 1. Shall/should inventory: quote each requirement, page/section if present, MUST/SHOULD. 2. Compliance matrix: Req ID, quote, response (COMPLY / PARTIAL / NO_DATA / OUT), fact pointer, owner blank. 3. Conflict list: requirements that fight each other, or fight Out. 4. Draft: only COMPLY rows, under Limits, with Facts in-line. PARTIAL gets a question, not a fake yes. 5. NO_DATA pack: a list of questions to the capture lead. Do not fill with industry filler. 6. Past performance: only from Past. If none, skip. Constraints: - Never invent a certification, SOC 2, or insurance limit. - Do not write a price. - Quote the RFP; do not paraphrase away a shall.