Skip to main content
MethodManagement, People & ProjectsProject managementStarter

Create a project risk register

A risk register with causes, scores, owners, responses and triggers.

This is a practical, copy-paste process for project kickoff or stage gates.. Use it when you want a clear structure, then add your own details and the linked evidence.

Published by Deepstory Research. Reviewed Sep 2026.

How to use this method

  1. 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
  2. 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
  3. 3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.

The prompt

Paste it as-is. The AI will ask for anything still in [BRACKETS].

Download .md
# Create a project risk register
Method by Deepstory Research: deepstoryresearch.com/method/project-risk-register

You are a project risk manager. Follow the method below step by step. Goal: A risk register with causes, scores, owners, responses and triggers.

## My inputs
- Project: [PROJECT]  (example: describe)
- Known concerns: [KNOWN_CONCERNS]  (example: list)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. Identify risks by category.
2. Write as cause → event → effect.
3. Score probability and impact.
4. Assign owners and responses (avoid, mitigate, transfer, accept).
5. Define triggers.

## Deliver the output in this structure
- Risk register table
- Heat map
- Top-5 response plans

## Quality rules
- Risks are uncertain events, not current issues.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

What you need to give the AI

InputPlaceholderExample
Project[PROJECT]describe
Known concerns[KNOWN_CONCERNS]list

Use it when

  • Project kickoff or stage gates.

What you get

  • Risk register table
  • Heat map
  • Top-5 response plans

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

  1. 1

    Identify risks by category.

  2. 2

    Write as cause → event → effect.

  3. 3

    Score probability and impact.

  4. 4

    Assign owners and responses (avoid, mitigate, transfer, accept).

  5. 5

    Define triggers.

Quality checks built into the prompt

  • • Risks are uncertain events, not current issues.
  • • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].

Evidence to use with this method

Methods tell the AI how to think. Evidence gives it sourced numbers to think with. Download a context file and attach it with the prompt.

Run next

Methods that chain well after this one.

Management, People & ProjectsWrite a weekly project status reportA one-page status report with RAG, progress, next steps, risks and decisions needed.Management, People & ProjectsBuild a project plan (WBS and schedule)A work-breakdown structure, milestones, dependencies, schedule and resource plan.Management, People & ProjectsMap stakeholders and a RACIA stakeholder map, RACI matrix and communication plan.

Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.