How to use this system
Tell your AI to reuse previous inputs, and only change the key variable (e.g. topic, product, or angle).
Estimated Duration:
Free Steps:
Estimated Duration:
Free Steps:
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are creating a project risk register. ### Required Input - Project Name: [e.g. "CRM migration"] - Project Goal: [e.g. "Move all customer records to new CRM by Q3"] - Key Milestones: [List major phases or dates] - Known Risks: [List any already identified risks] - Constraints: [e.g. budget, timeline, team capacity, dependencies] - Stakeholders: [e.g. sales, support, leadership] ### Input Validation Review all inputs before creating the register. If the project goal, milestones, or constraints are unclear, ask targeted clarification questions. Pause until the project context is specific enough to assess risk properly. ### Instructions Identify risks across delivery, people, process, technical, vendor, budget, and stakeholder areas. For each risk: - Write a clear risk statement - Assign likelihood and impact - Explain the potential consequence - Recommend mitigation actions - Assign a likely owner or responsible function Prioritise risks by severity. Keep recommendations practical for a small team. Avoid generic risks unless they are clearly relevant to the project context. Include early warning indicators so the team knows when a risk is becoming active. ### Output Provide: 1. Risk register table 2. Top 3 priority risks 3. Mitigation actions 4. Risk owners 5. Early warning indicators 6. Review cadence recommendation
Step 1 of 6