Convert uncertain events into owned, evidence-based risks with triggers, responses, and review dates
7 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Build a project risk register.
Objectives, scope, phases, dates, stakeholders, and status:
[project]
Assumptions, incidents, dependencies, estimates, constraints, and warning signals:
[evidence]
Scales, appetite, escalation thresholds, owners, and review cadence:
[method]
Write each risk as an uncertain cause-event-consequence, not as an issue already happening or a vague topic. Separate active issues, assumptions, dependencies, and opportunities from risks. For every risk provide ID, statement, evidence, affected objective, likelihood, impact dimensions, score with rationale, proximity, indicators, prevention/mitigation, contingency trigger and response, explicit risk owner or Unassigned, action owners, next review, and residual risk. Use only supplied scales and evidence; do not invent probabilities, owners, budget, or controls. Detect duplicates and correlated risks, show scoring uncertainty, and identify missing information that could change priority.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Project context
Migrate 18 internal reporting jobs to a new data warehouse by 31 January. Phase 1 inventory is complete; build starts 1 November. Finance reporting must remain available and monthly close is 25–31 January. Sponsor is CFO; delivery lead is Imani; data platform and Finance teams participate.
Known uncertainties and evidence
Three jobs have undocumented transformations. Platform load testing has not begun. A vendor connector is scheduled for 15 December based on an email estimate, not a contract. One engineer leaves 20 December; replacement capacity is unconfirmed. The source system had two four-hour outages last quarter. Budget contingency is not stated.
Scoring and governance
Likelihood 1 Rare to 5 Almost certain; impact 1 Minor to 5 Critical. Score=L×I. Scores 15+ escalate to sponsor. Delivery lead facilitates weekly Monday review. Only named accountable owners may be assigned; others remain Unassigned.
Example output
R1 If undocumented transformations are misunderstood, migrated outputs may not reconcile, causing incorrect Finance reports. Evidence: three jobs undocumented. Likelihood 4 rationale: known gap affects 3/18; Impact 5: Finance correctness/close. Score 20—escalate. Owner: Unassigned. Indicators: mapping exceptions and reconciliation failures. Mitigation: document logic and create signed source-to-target tests before build completion; action owner Unassigned. Contingency trigger: any critical reconciliation failure before cutover; keep affected job on source and escalate. Residual score cannot be set until controls are tested.
R2 If the connector misses the estimated 15 December date, dependent builds may compress testing before close. L3 due to non-contractual estimate; I4 schedule/quality; score 12. Owner Unassigned. Confirm contractual status and latest viable arrival; define fallback connector or scope only with approval. R3 if replacement capacity is unavailable after 20 December, defect resolution may slow during cutover. L3/I4=12; evidence and resource plan incomplete. R4 if load behavior is inadequate, reporting may degrade at close; score cannot be responsibly assigned until expected load and tests are defined.
Active issue: three undocumented transformations exist now. Dependency: vendor connector. Correlation: R2/R3/R4 can jointly compress testing. Monday review must assign owners, validate scores, and set dated actions.
Why this works
1
Cause-event-consequence statements distinguish manageable uncertainty from current issues and generic concerns.
2
Triggers and contingencies specify what changes when prevention is no longer sufficient.
Check the result
Is each entry genuinely uncertain and tied to a project objective?
Are scores supported by evidence and the supplied scale?
Are risk ownership, response-action ownership, triggers, and review dates distinct?
ChatGPT