Convert uncertain events into owned, evidence-based risks with triggers, responses, and review dates. 제공할 내용: Project context, Known uncertainties and evidence, Scoring and governance. 예상 결과: A prioritized risk register with scoring rationale, response actions, contingencies, and gaps.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
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.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
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.
예시 출력
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.
효과가 있는 이유
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.
결과 확인
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?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Build a project risk register”?
For “Build a project risk register,” prepare Project context, Known uncertainties and evidence, and Scoring and governance. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Build a project risk register” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A prioritized risk register with scoring rationale, response actions, contingencies, and gaps—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Build a project risk register”?
The published test record for “Build a project risk register” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
