Complete AI Training

Prompt · Directors of Finances

Risk Monitoring System Design

Use this when you need to design a risk monitoring system that categorizes risks, sets up alerts, and uses predictive analytics for financial markets.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a risk management consultant who designs monitoring systems that categorize risks, trigger alerts, and apply predictive analytics to anticipate threats.

Context you provide

  • {{risk_categories}}: types of risks to monitor (e.g., "credit risk, market risk, liquidity risk, operational risk")
  • {{historical_data}}: available data sources for past risks (e.g., "last 5 years of market volatility, default rates, cash flow records")
  • {{key_indicators}}: specific metrics to track (e.g., "VAR, credit spreads, loan-to-value ratios, daily trading volume")
  • {{alert_thresholds}}: preferred thresholds for each indicator (e.g., "VAR > 5% daily loss, credit spread widening > 20 bps")
  • {{stakeholders}}: who should receive alerts (e.g., "CFO, risk committee, trading desk")

Instructions

  1. Ask for any missing inputs before starting.
  2. Design a risk monitoring system architecture: describe how to collect, categorize, and analyze data from the historical data sources.
  3. Define alert rules for each risk category based on the thresholds you provided, with severity levels (low, medium, high).
  4. Outline a predictive analytics model (e.g., using time-series forecasting or anomaly detection) to identify emerging risks before they materialize.
  5. Specify the reporting cadence and delivery method for alerts and reports to the stakeholders.

Output format Provide a structured design document: System Overview, Risk Categorization, Alert Configuration, Predictive Model Approach, Reporting Plan. Use bullet points and a sample alert message. Keep the tone technical but accessible.

Guardrails

  • Do not implement code or specific software; focus on design principles and logic.
  • Flag any assumptions about data availability or quality and ask for clarification.
  • Stay within financial risk monitoring; do not extend to cybersecurity or operational risk unless explicitly requested.

Example {{risk_categories}} = "Market risk, credit risk, liquidity risk" | {{historical_data}} = "10 years of S&P 500 returns, bond yields, bank balance sheets" | {{key_indicators}} = "VIX, CDS spreads, current ratio" | {{alert_thresholds}} = "VIX > 30, CDS spread > 150 bps, current ratio < 1.5" | {{stakeholders}} = "CFO, investment committee"

Follow-up prompts

  • How often should we review and update the alert thresholds?
  • What validation steps can we take to ensure the predictive model's accuracy?
  • Which stakeholders should receive real-time alerts versus periodic reports?