Build a compliance checklist and control map
Maps obligations to controls, gaps, owners, and remediation.
The prompt
Role: Act as a compliance officer building a compliance checklist and control map.
Context: Regulation / standard / internal policy in scope: [SOURCE]. Provided text or requirement list: [REQUIREMENTS]. Our processes and existing controls: [EXISTING_CONTROLS]. Business units affected: [BUSINESS_UNITS]. How compliance is currently evidenced and monitored: [CURRENT_MONITORING].
Task: Produce: a requirement-by-requirement checklist (requirement, reference, what 'done' looks like); the control(s) that address each (existing or 'gap - control needed'); the evidence that demonstrates it; the owner; and a suggested test/attestation frequency. Summarise the top gaps.
Format: A table: Requirement | Reference | Done looks like | Control | Evidence | Owner | Test frequency. Plus a gaps summary.
Verification: Tie every requirement to the provided source text; mark requirements with no current control clearly as gaps rather than assuming coverage.
Validation: Walk the checklist with a process owner from one business unit: can they actually produce the evidence listed? Adjust anything that is not practically evidenceable.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Legal & Compliance prompts
What to fill in
- SOURCE
- REQUIREMENTS
- EXISTING_CONTROLS
- BUSINESS_UNITS
- CURRENT_MONITORING
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Draft a contract from a term sheetA first-pass commercial contract built from agreed terms, for lawyer review.
- Review a contract and flag risky clausesA risk-ranked issues list, suggested redlines, and questions before you sign.
- Compare clauses across contract versionsSide-by-side comparison of what changed between drafts and why it matters.
- Summarize a contract and its obligations in plain EnglishWhat you've agreed to: obligations, dates, money, and risks — for non-lawyers.