Create a risk analysis document

Create a detailed risk analysis document with insights and team actions for stakeholder review.

  • Verified
The approach in this prompt has been verified by the Government Project Delivery Professionals. You must still check the results from this prompt for accuracy, as AI can make mistakes.

What this prompt does

This prompt is suitable for any AI assistant (for example, Microsoft Copilot or Gemini). 

The prompt will:

  • generate a professional risk analysis document for stakeholders and the project team
  • align the analysis with official UK government guidance (Teal Book, Green Book, and Orange Book)
  • provide three key outputs: an Executive Summary, a Risk Register table, and a team action plan

Before you start

Before you use this prompt, replace text in square brackets:

  • [DESCRIBE THE TYPE OF PROJECT] for example [digital transformation]
  • [BRIEFLY DESCRIBE THE MAIN OBJECTIVE] for example [improve access to digital services and connectivity for underserved rural populations across the UK]
  • [PROJECT PHASE] for example [feasibility]
  • [DELIVERABLES] for example [pilot scheme and final digital product]
  • [MILESTONES] or key decisions
  • [DESCRIBE PROGRAMME] for example [government digital transformation programme aimed at improving digital inclusion]

You can also add your project brief and any other relevant information (for example, risk appetite statements or policies) when you submit the prompt.

Do not upload any personal or official information to free tools, or any tool not advised by your department. If you are unsure, check with your digital team.

After the prompt has run, use follow-up questions to refine risks, add new ones or adjust strategies.

The prompt

Copy prompt Create a risk analysis document 
                //Goal

Generate a professional evidence-based risk analysis document for a \[DESCRIBE PROGRAMME]. The document should be suitable for presentation to project stakeholders and for use in the next team meeting.

//Context

You are a high-performing quantitatively minded Risk Manager supporting the programme. You understand the importance of risk insight for decision-making and are tasked with producing a clear, actionable risk analysis.

Project details:
* Project Type: [DESCRIBE THE TYPE OF PROJECT]
* Project Goal: [BRIEFLY DESCRIBE THE MAIN OBJECTIVE]
* Current Project Phase: [PROJECT PHASE]
* Key Deliverables: [DELIVERABLES]
* Upcoming Milestones Key Decisions: [MILESTONES] 

//Source 

* The Teal Book Chapter 20. Risk management - Government Project Delivery (https://projectdelivery.gov.uk/teal-book/home/part-e-planning-and-control/chapter-20-risk-management/)
* Business case and supporting project data (attached or summarised)
* Risk register fields from the Project Data Standard (https://www.gov.uk/government/publications/project-data-standard-government-project-delivery)
* The Green Book (https://assets.publishing.service.gov.uk/media/6645c709bd01f5ed32793cbc/Green_Book_2022__updated\_links\_.pdf)
* The Orange Book – Management of Risk – Principles and Concepts (https://assets.publishing.service.gov.uk/media/6453acadc33b460012f5e6b8/HMT_Orange_Book_May_2023.pdf)

//Expected Output

A document with the following three sections:

1. Executive Summary: One paragraph framing the analysis as a proactive measure, highlighting the most critical risks, (including their overall impact on project time, cost, benefits).  Reassure stakeholders that mitigation plans are in place and working as intended. 

2.Risk Register Table: Use all fields from the Project Data Standard. 

3. Team Call to Action: Write a motivating message directly to the project team.  Explain the importance of risk analysis, especially when team engagement is low.  Include relevant excerpts from the Teal Book to reinforce the message.  Encourage the team to review, identify new risks, assess risk indicators and suggest improvements to mitigation strategies.

Provide a list of:

* actionable insights: e.g. every risk should have a mitigation strategy

* any assumptions you made

//Style and tone

Audience: includes the project manager, project team, and executive stakeholders. 

The tone should be professional and in plain UK English, providing clear, actionable insights and recommendations.

Content created: 18 November 2025 | Last updated: 23 November 2025

Support and Resources

Here are the relevant guidance pages for using prompts:

Get in touch

Email ai-knowledge-hub@dsit.gov.uk to share feedback about this prompt.