Project Risk Register and 2-Week Action Plan

Create a ranked risk register, early warning signs, and a two-week action plan for a project. Supports the go/no-go and resourcing decision at the next checkpoint.

You get: Decision summary, risk register table and two-week action plan

More like this

The prompt

project-risk-register-and-2-week-action-plan.md
Role: You are an experienced program manager who runs risk reviews for small and mid-sized teams.Context: The project is {project_name} with goal {goal}, deadline {deadline}, and team {team_composition}. The decision to support is whether to proceed as planned, adjust scope or timeline, or escalate for resources at {checkpoint_date}.
Task: Build a risk register and a two-week mitigation plan from the information I provide.Constraints: Base risks on the inputs, not generic project lists. Label each risk as Observed (evidence given) or Potential (inferred). Do not assign probabilities with false precision; use Low/Medium/High with a reason. No invented dates or budget figures.

Inputs:
- Project description and scope: {project_description}
- Milestones and dependencies: {milestones}
- Team capacity and constraints: {capacity}
- Budget or resource limits: {budget}
- Stakeholders and their expectations: {stakeholders}
- Past issues or near-misses: {past_issues}

Workflow:
1. Restate the goal, deadline, and decision in two sentences.
2. List assumptions and missing information that affect the risk picture.
3. Identify risks across scope, schedule, resources, dependencies, quality, and stakeholders.
4. Rate likelihood and impact, then rank by exposure.
5. For the top 8 risks, define the early warning sign, mitigation, contingency, and owner role.
6. Build a two-week plan with actions sequenced by dependency.
7. Give a go/adjust/escalate recommendation with reasoning.

Output format:
- Decision summary
- Assumptions and open questions
- Risk register table (ID, risk, type: Observed/Potential, likelihood, impact, exposure, warning sign, mitigation, contingency, owner role)
- Two-week action plan (table: day range, action, owner role, dependency, done-when)
- Recommendation and conditions to revisit
- Information to collect before the checkpoint

Acceptance criteria:
- The top risks connect to the specifics I provided.
- Each mitigation is a concrete action with a done-when condition.
- The recommendation states what evidence would change it.

Quality checks:
- Remove duplicate or overlapping risks.
- Check that no action depends on something not yet available in the plan.
- Check that the owner roles exist in {team_composition}.

Example output

AI-written example

Decision summary
Migrate 1,200 customer accounts from legacy invoicing to the new Harbor Billing Portal by 30 September. At the 12 June checkpoint, decide whether to proceed, adjust scope or timeline, or escalate for resources.

Assumptions and open questions

  • Assumed: the payment gateway sandbox will be available (unconfirmed).
  • Assumed: QA stays at 50% allocation.
  • Unknown: legacy data quality and Finance's report requirements.

Risk register (ranked)

IDRiskTypeLIExposureWarning signMitigationContingencyOwner
R1Gateway sandbox access delayedObservedH (vendor slow last time)HHighNo credentials by Day 3Escalate to vendor contact; done when test payment succeedsMock gatewayPM
R2Legacy data errorsObservedH (duplicates in past migration)HHighOver 2% rejects in dry runDry-run 100 accounts; done when rejects are loggedCleanup sprintDeveloper
R3QA shared with another projectObservedMHHighTest backlog over 5 daysFix weekly QA hours; done when agreed in writingDeveloper peer testingPM
R4One developer knows billing logicPotentialMHHighReviews wait on one personPair on billing module; done when a second developer merges a fix
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Best used a week or two before a milestone. Update the register by pasting new status and asking ChatGPT to re-rank the risks and flag changes.

Questions about this prompt

More in ChatGPT

Custom GPT Blueprint: Instructions, Knowledge Files, and Test Cases

Plan a custom GPT before building it. Produces the instruction text, knowledge file plan, conversation starters, and a test set so you can decide whether to build, narrow, or skip it.

Market Size Triangulation: Top-Down vs Bottom-Up with Source Grading

Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.

Monthly KPI Variance Review with Drivers and Action Plan for Leadership

Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.

Vendor Shortlist Decision Memo with Weighted Scoring and Source Citations

Guides a source-backed evaluation of software or service vendors against weighted criteria. Ends with a decision memo covering risks, open questions, and verification steps before purchase.

Weekly Operating Review: KPI Variance Diagnosis and Action Plan

Analyzes weekly KPI data against targets, separates signal from noise, proposes ranked root-cause hypotheses, and produces owner-assigned actions and an escalation list for a team operating review.

Agent Workflow Decomposition with Autonomy Levels and Stop Rules

Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.

Side Hustle Matcher Ranked by Cost, Speed and Realism

Get five side hustles matched to your skills and weekly hours, ranked by startup cost, time to first $100 and realism, each with a first step.

Trending

Developmental Edit Memo for an Essay Draft With Revise-or-Cut Decisions

Gives a draft essay a structured developmental edit: thesis check, paragraph-by-paragraph audit, and a prioritized revision plan so you can decide what to keep, rewrite, or cut before line editing.

30-60-90 Day Plan for a New Job With Early Wins and Questions for Your Manager

Turns a new role and what you know about the team into a 30-60-90 day plan: learning goals, relationships to build, one early win, and questions to agree with your manager in week one.

30-Minute Moderated Usability Test Script with Tasks and Notes Template

Produces a timed 30-minute moderated usability script with task scenarios, neutral follow-up questions and a ready-to-use notes template.

4-Week Small Business Launch Plan: $0 and Small-Budget Versions

Builds a 4-week launch plan for a product or service in a specific market, with channels and weekly tasks in a $0 version and a small-budget version.

60-Minute Lesson Plan with Checks for Understanding and Differentiation

Builds a timed, objective-aligned lesson plan with formative checks, differentiation, and a teach-or-revise readiness verdict. It asks for missing inputs first and keeps assumptions separate.