Define key risk indicators with thresholds
Creates measurable key risk indicators for my top risks, with data sources, thresholds, escalation paths, and pitfalls to avoid.
The prompt
Help me define key risk indicators (KRIs) for my organization's risks.
Risks to monitor: [LIST, with a short description of each]
Risk appetite or tolerance statements: [PASTE if available]
Data we have access to: [systems, reports, logs, HR data, incident data]
Reporting audience and frequency: [e.g. monthly risk committee]
For each risk, propose 2-3 KRIs and return a table with columns:
- KRI name
- Definition and exact calculation (numerator / denominator)
- Leading or lagging
- Data source and owner
- Frequency
- Thresholds: green / amber / red, with the rationale (link to appetite where possible; otherwise mark [CALIBRATE WITH HISTORICAL DATA])
- Escalation action at amber and at red
Then:
1. Recommend the strongest KRI per risk and explain why.
2. Flag KRIs that would be easy to game, too noisy, too slow, or that just measure activity rather than risk.
3. Suggest how to set thresholds using 12-24 months of history if I have it.
4. Draft a one-page KRI dashboard layout.
Prefer leading indicators (e.g. overdue access reviews, staff turnover in key roles, backlog of unresolved alerts) over counts of past incidents. Do not invent baseline numbers.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Data & Analysis prompts
What to fill in
- LIST, with a short description of each
- PASTE if available
- systems, reports, logs, HR data, incident data
- e.g. monthly risk committee
- CALIBRATE WITH HISTORICAL DATA
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Design an A/B testHypothesis, variants, metrics, sample size, and duration for a valid test.
- Break down my results into the business drivers behind themBuilds a driver tree from your results, sizes how much each driver contributed to the change, and names which ones to act on.
- Identify the leading and lagging indicators for my business or teamSorts your metrics into leading and lagging indicators, links each lead to the outcome it predicts, and fills gaps in early-warning measures.
- Find the 20% of activities driving 80% of my resultsRuns a Pareto analysis to show the few activities, customers, or products producing most of your results, and what to cut or double down on.