Risk Register
Build or update a project risk register that a team will actually use.
Sample result
How it works
What Risk Register does
Writes each risk as cause, event, and effect; scores probability and impact on a stated 1-5 scale with explicit band cut-offs; adds expected monetary exposure when amounts exist; names a single owner, a response type, a concrete mitigation, an observable trigger with a threshold and date, a residual score, and a review date; separates risks from issues, assumptions, and dependencies; and on updates reports new, changed, closed, and realized risks.
Use it when
Someone asks for a risk register, to log or rescore project risks, what could go wrong with a plan, which risks need an owner or a trigger, or how to refresh a stale register before a steering meeting.
Use something else for
Mapping what depends on what, for a live production incident, or for pricing a scope request.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Risk register, risk scoring table, mitigation plan and review diff
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Risk Register
Updated Oct 20, 2026.
What does Risk Register do?
Build or update a project risk register that a team will actually use. Writes each risk as cause, event, and effect; scores probability and impact on a stated 1-5 scale with explicit band cut-offs; adds expected monetary exposure when amounts exist; names a single owner, a response type, a concrete mitigation, an observable trigger with a threshold and date, a residual score, and a review date; separates risks from issues, assumptions, and dependencies; and on updates reports new, changed, closed, and realized risks. Use when someone asks for a risk register, to log or rescore project risks, what could go wrong with a plan, which risks need an owner or a trigger, or how to refresh a stale register before a steering meeting. Do not use for mapping what depends on what (use dependency-map), for a live production incident (use coordinate-production-incident), or for pricing a scope request (use scope-change-brief).
Who is Risk Register for?
It is designed for project managers, program leads, product owners, sponsors and delivery teams.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Risk Register produce?
Risk register, risk scoring table, mitigation plan and review diff. Results come back with their sources and any open questions for you to check before anything is used.
How much does Risk Register cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt9tdt009i…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Risk Register fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.