Prompt: Create a Risk Assessment

Risk assessments tend to happen after something goes wrong. "We should have seen that coming" is the most expensive sentence in business. Running a proactive risk assessment takes discipline, but AI makes it fast enough to do regularly.

This prompt creates a structured risk assessment you can run quarterly. Use it to prompt create risk assessment ai analysis that catches threats before they become crises.

The Prompt

Create a risk assessment for the following business situation:

BUSINESS: [What you do, size, key dependencies]
SCOPE: [What area to assess - e.g., "Q1 marketing operations" or "New product launch" or "Overall business"]
KNOWN CONCERNS: [Any risks you are already aware of]
RECENT CHANGES: [New hires, new tools, market shifts, competitor moves]

For each risk identified, provide:
1. Risk description (specific, not vague)
2. Category (Operational, Financial, Strategic, Compliance, Reputational, Technology)
3. Likelihood (1-5, where 5 is almost certain)
4. Impact (1-5, where 5 is catastrophic)
5. Risk score (Likelihood x Impact)
6. Current controls (what is already in place to mitigate this)
7. Recommended mitigation (what else should be done)
8. Owner (which role should own this risk)
9. Early warning sign (what would signal this risk is materializing)

Identify at least 10 risks. Organize them by risk score, highest first.

After the individual risks, provide:
- TOP 3 PRIORITIES: The risks that need immediate attention
- QUICK WINS: Mitigations that can be implemented this week
- SYSTEMIC ISSUES: Patterns across multiple risks that point to a deeper problem

Rules:
- Be specific. "Revenue decline" is not a risk. "Losing 3 key accounts due to competitor pricing pressure" is a risk.
- Include risks people do not like to talk about (key person dependency, technical debt, market shifts)
- Every mitigation must be actionable, not "monitor closely" (that is not an action)
- Flag risks where current controls are inadequate

Running the Assessment

Fill in the business context thoroughly. The quality of the assessment depends entirely on how much context you provide. Include your biggest client dependencies, your technology stack, your team structure, and any recent changes.

The Quarterly Cadence

Run this assessment every quarter with updated context. Compare to the previous quarter. Did any risks materialize? Did mitigations reduce scores? Did new risks emerge?

The trend across assessments is more valuable than any single snapshot. A risk that keeps scoring high quarter after quarter despite mitigation efforts needs a fundamentally different approach.

Making It Actionable

Assign every high-priority risk to a specific person. "The team" does not own risk. Sarah in operations owns the vendor dependency risk. Marcus in engineering owns the technical debt risk. Named ownership creates accountability.

Review the early warning signs monthly. When a signal fires, escalate immediately instead of waiting for the quarterly review. The whole point of proactive assessment is acting before the risk becomes a problem.

Build These Systems

Ready to implement? These step-by-step tutorials show you exactly how:

• How to Create Automated Pipeline Health Reports - Generate daily pipeline health reports with deal velocity and risk alerts.
• How to Build a Prompt Template Library - Create a reusable library of tested prompts for every business function.
• How to Create Dynamic Prompt Chains - Chain multiple AI calls together where each output feeds the next prompt.