Project Management

Please login or join to subscribe to this thread

AI-Assisted Project Risk Register and 30-Day Response Plan

linkedin twitter facebook   Artificial Intelligence  
avatar
Zahid Islamli Senior IT Business Analyst| MPAY Baku, Azerbaijan

A reusable prompt that transforms anonymized project information into a prioritized risk register, practical response strategies, early warning indicators, ownership recommendations, and a focused 30-day action plan.

Act as a senior project manager and risk management specialist. Analyze the anonymized, non-confidential project information provided below and create a decision-ready project risk assessment and response plan.

Before starting:

* Review the information for missing or unclear details.
* If critical information is missing, ask up to five concise clarifying questions.
* If answers are unavailable, continue using clearly labeled assumptions.
* Use only the information provided. Do not invent project facts.
* Do not request personal, proprietary, confidential, or security-sensitive information.
* Separate existing issues from uncertain future risks.
* Consider both threats and opportunities.

Assess relevant risk categories, including scope, schedule, cost, resources, technical dependencies, integrations, quality, security, compliance, vendors, stakeholders, and operations.

Present the output in the following structure:

1. Executive Summary

Provide a concise overview of the project’s overall risk exposure, the most urgent concerns, and the recommended management focus.

2. Risk Register

Create a table with these columns:

* Risk ID
* Risk category
* Risk type: threat or opportunity
* Risk statement in cause–event–impact format
* Probability score (1–5)
* Impact score (1–5)
* Overall score: probability × impact
* Priority: Low, Medium, High, or Critical
* Early warning indicators
* Recommended response strategy
* Preventive or mitigation actions
* Contingency or fallback plan
* Suggested risk owner
* Review frequency

Use the following scoring thresholds:

* Low: 1–5
* Medium: 6–12
* High: 13–19
* Critical: 20–25

3. Priority Analysis

* Highlight the five highest-priority risks.
* Explain why each requires management attention.
* Identify relationships or dependencies between risks.
* State which risks require escalation.

4. Assumptions and Information Gaps

List all assumptions, missing information, dependencies, and items requiring expert or stakeholder validation.

5. 30-Day Action Plan

Recommend specific actions for the next 30 days. For each action, include:

* Action
* Intended outcome
* Suggested owner
* Target completion period
* Related risk ID

6. Monitoring Recommendations

Recommend an appropriate risk review cadence, key indicators to monitor, and conditions that should trigger escalation or reassessment.

Project information:

* Project name or type:
* Business objective:
* Current project phase:
* Scope and major deliverables:
* Key milestones and timeline:
* Budget or cost constraints:
* Main stakeholders and vendors:
* Technical systems and integrations:
* Known issues or concerns:
* Security or regulatory requirements:
* Resource constraints:
* Other relevant non-confidential information:

[Insert anonymized, non-confidential project details above before running the prompt.]
Show more Copy Try prompt on PMI Infinity

Please login or join to reply

Content ID:
ADVERTISEMENTS

"A thing worth having is a thing worth cheating for."

- W.C. Fields

ADVERTISEMENT

Sponsors