What does the generated assessment include?

For each risk it produces an identified event with its root cause, likelihood and impact scores on your chosen scale, a combined score, a concrete mitigation, an owner role, and the residual risk remaining after mitigation.

Which scoring scale should I use?

A 1 to 5 likelihood-times-impact matrix is the most common and gives finer ranking. Use 1 to 3 or Low/Med/High when you want a simpler, faster register that non-specialists can read at a glance.

Why does it ask for categories?

Prompting per category forces breadth. Without it, models cluster on the two or three most obvious risks. Naming technical, security, schedule, and vendor categories ensures coverage across the project.

Can I export the output as data?

Yes. Choose the JSON format and the prompt instructs the model to return a structured array with scores and residual values, ready to load into a spreadsheet or risk tool.

Does the tool perform the analysis?

No. It assembles the prompt in your browser. You run it in ChatGPT, Claude, or any model and review the output, since risk judgement should always have a human in the loop.

Risk Analysis Prompt Builder

Risk analysis prompt builder

Ask a model to “list the risks” and you get five generic bullet points. A useful risk assessment names specific events and their causes, scores them consistently, proposes concrete mitigations, and tracks what risk remains afterward. This builder encodes that discipline into a prompt so the output is something you can paste straight into a planning doc or risk register.

How it works

You describe the scenario, list the risk categories to cover, choose a likelihood and impact scale, and pick an output format. The tool builds a prompt that walks the model through a five-step method — identify, score, mitigate, estimate residual risk, and assign an owner — and requires at least two specific risks per category. The output is formatted as a Markdown table sorted by score, a full risk register, or structured JSON, with a “Top 3 risks” summary and an overall posture statement appended.

Tips and notes

Be specific about scope. “Weekend database migration” yields sharper risks than “the project.”
Pick categories deliberately. They drive breadth — add a compliance or financial category if those matter to you.
JSON for tooling, table for humans. Use JSON when you will import the result; use the table when stakeholders will read it.
Keep a human in the loop. Models miss context-specific risks; treat the output as a thorough first pass, not a final sign-off.