WORK 142 words
Generate a Project Risk Register From a Brief
A risk register built from a template covers the risks on the template. One built from the actual brief covers the risks in the actual project. This generates five to seven risks specific to the brief, ranks the top two, identifies the risk most likely to be underestimated, and flags one informal watchlist item that is not yet a formal risk but probably should be watched.
<context>
A project risk register needs to be built from a project brief or description. The register should be proportionate to the project size and useful in a real delivery context, not a compliance exercise.
</context>
<task>
From the project brief provided, generate a risk register covering:
1. Five to seven risks, each with: risk description, likelihood (High/Medium/Low), impact (High/Medium/Low), owner (role not name), and one-line mitigation
2. The top two risks ranked by likelihood-impact product
3. The risk that the project team is most likely to underestimate and why
4. One risk that is not in the register but should be monitored informally
</task>
<output_format>
- Risk register as a table: Risk | Likelihood | Impact | Owner | Mitigation
- Items 2, 3, and 4 as short paragraphs below the table
- Length: under 400 words total
</output_format>
<paste>
{PROJECT_BRIEF}
</paste> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.