Create beginner Works with: Any AI

Risk Register Starter

Table output Has example

Identify, score, and own project risks.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Create a risk register. Project description: [PROJECT]. Known worries: [WORRIES]. Team and stakeholders: [TEAM_AND_STAKEHOLDERS].

Produce at least 15 risks across categories (schedule, budget, scope, people, technology, suppliers, legal and regulatory, stakeholders). For each: ID | Risk statement ("If X happens, then Y, causing Z") | Category | Probability (1 to 5) | Impact (1 to 5) | Score (P x I, shown) | Trigger or early warning | Response (avoid, reduce, transfer, accept) | Specific action | Owner | Review date.

Sort by score. Mark a threshold I can set (default 12 or more) for management attention. Add a heat map in text, a monthly review routine (10 minutes), a rule to close or retire risks, and a template for reporting top risks to the sponsor (60 words each). Explain the difference between a risk and an issue. Do not invent facts about my project; mark risks inferred from general patterns as [VERIFY] so I validate them with the team.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

R3: If the vendor delivers the sensors late, then installation moves past the winter shutdown, causing a six-week delay.
Category: supplier. Probability 3, impact 5, score 15 (above the threshold of 12).
Early warning: no confirmed shipping date by 1 October.
Response: reduce. Place the order two weeks earlier and agree a partial delivery of 60 percent by 15 November.
Action owner: Marta. Review: every Friday.
R7: If the lead engineer is absent for two weeks, then testing stops. Probability 2, impact 4, score 8. Response: cross-train a second engineer by 31 August.
Top three risks go to the sponsor in the monthly report.

• risk-register