Risk And Compliance Committee Report
# 30. Risk and Compliance Committee Report
**Domain:** Board Reporting
**Level:** Advanced
## Use Case
Produce a structured risk and compliance management report for Risk Committees, ExCo, Operating Committees, or Audit Committees. Covers the reporting period's key developments, risk position, compliance status, incidents, and actions required.
## Variables
| Variable | What to Enter | Example |
|----------|--------------|---------|
| `[REPORT_TYPE]` | The committee or audience this report is for | e.g. Risk Committee, Audit Committee, ExCo, Operating Committee, Compliance Committee |
| `[ORGANISATION]` | Organisation name | e.g. Nationwide Building Society |
| `[REPORTING_PERIOD]` | The period this report covers | e.g. Q3 2025 (1 July to 30 September 2025) |
| `[KEY_DEVELOPMENTS]` | Significant events, changes, or issues during the period | e.g. Two P2 incidents, one regulatory request for information from FCA, DORA programme milestone achieved, new AI system deployed |
| `[RISK_AND_COMPLIANCE_METRICS]` | Current metrics and status figures | e.g. Open risks: 14 (3 Red, 6 Amber, 5 Green); Overdue actions: 7; Policy exceptions: 2; Incidents this period: 4 |
| `[ACTIONS_AND_DECISIONS_REQUIRED]` | What the committee needs to approve, note, or decide | e.g. Approve revised risk appetite statement, note the FCA response timeline, escalate overdue remediation to ExCo |
## The Prompt
Copy everything below this line. Replace all `[VARIABLES]` with your specific information. Paste into Claude, GPT-4o, Gemini, or any capable LLM.
---when to use it
Community prompt sourced from the open-source GitHub repo KunalCyber/GRC-Prompts-Library (MIT). A "Risk And Compliance Committee Report" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
KunalCyber/GRC-Prompts-Library · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions