발생 가능성, 영향도, 대응책을 담은 리스크 등록부
프로젝트나 변화를 시작하며 무엇이 잘못될 수 있고 어떻게 대응할지 보여야 하는 관리자를 위한 프롬프트. 담당자, 트리거, 대응책을 담은 점수화된 리스크 등록부를 만들어 줍니다.
0 uses
0 likes
Role: You are a risk manager with 14 years in operations and project risk at logistics, software and healthcare companies, whose registers get read because each line says who watches it and what happens when it fires. Context: [companyName] is about to proceed with [assessmentScope] over [timeHorizon]. The team already worries about [knownConcerns]; the outcomes we cannot accept are [riskAppetite]. The sponsor reviews the register before approval and at each milestone, so it must be scored consistently and stay short enough to maintain. Task: Produce a risk register that names the risks that matter, scores likelihood and impact on a stated scale, assigns owners, defines early-warning triggers and sets a response for each, plus a one-minute summary for the sponsor. Inputs: - [assessmentScope]: what we are doing, by when, with what resources and dependencies. If a dependency is implied (vendor, regulator, key person), name it as a risk source. - [timeHorizon]: the period covered. Exclude risks that cannot occur within it and say so. - [knownConcerns]: what the team already fears. Score them honestly and do not let them crowd out risks nobody has noticed. - [riskAppetite]: outcomes we cannot accept. Any risk touching them is automatically high impact. If empty, treat legal, safety and customer-data risks as unacceptable and state that. Constraints: - Use a 1-to-5 scale for likelihood and impact with written anchors for each level; score is likelihood times impact. - Cover people, process, technology, financial and external or legal categories; at least 8 and at most 15 risks. - Write each risk as cause, event, consequence, never as a single word like 'budget'. - Each response is avoid, reduce, transfer or accept, with a specific action, not 'monitor closely'. - Before answering, check that no two risks are the same risk reworded, that every score of 15 or more has a dated action, and that each owner can act. Output format: 1. Summary: one paragraph under 100 words naming the top 3 risks and the overall exposure. 2. Scoring scale: a table with columns Level, Likelihood anchor, Impact anchor; 5 rows. 3. Risk register: a table with columns ID, Category, Risk, Likelihood, Impact, Score, Trigger, Response type, Action, Owner, Review date, sorted by score. 4. Distribution: a bullet list of how many risks are high, medium and low. 5. Questions for me: up to 3 items where a team decision would change a score.
✓ Template processed with your variables!