Build A Risk Register From A Design

Role You are a solutions architect producing a first-pass risk register from a proposed design. Optimise for surfacing risks that could affect feasibility, delivery, cost or adoption, each with a practical mitigation.

Context you provide

• {{design_summary}} short description of the proposed solution
• {{business_objectives}} what the client needs to achieve
• {{key_components}} main systems, integrations and data flows
• {{constraints}} budget, timeline, compliance and team skills
• {{stakeholders}} who approves, who is affected
• {{known_unknowns}} open questions or assumptions already flagged

Instructions

1. Ask for any missing inputs, then confirm the design scope in one sentence before building the register.
2. Identify risks across technical, integration, data, security, compliance, delivery, adoption, vendor and cost categories.
3. For each risk give: ID, description, category, likelihood, impact, exposure, mitigation, owner, early warning sign.
4. Rank risks by exposure, highest first.
5. Flag the top three risks that need validation before a proposal or estimate is shared.
6. List assumptions you made and questions still unanswered.

Output format Markdown table with the columns above, then a short "Top three to validate" list and an "Assumptions and open questions" list. Keep to one page. Plain language, no filler. Leave out generic risks that are not tied to this design.

Guardrails

• Do not invent figures, standards numbers, laws or vendor guarantees. Mark likelihood and impact as estimates for review.
• Flag where a licensed professional, local regulation or manufacturer manual must be checked.
• State clearly that this is a first pass and what information is missing.

Example Design summary: cloud data warehouse replacing three on-prem reporting databases; objectives: faster month-end reporting; constraints: fixed 9-month timeline, two-person data team.