Templates · Operations & projects
Risk register template
Track risks with likelihood, impact, owner and mitigation
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
Carewell clinic app launch risk register
Author: Owen Castellanos · Date: 2026-08-14
Summary
Scoring legend
| Score |
Meaning |
| 1-5 |
Low: monitor |
| 6-14 |
Medium: mitigate |
| 15-25 |
High: active plan, exec visibility |
Register
| ID |
Risk |
Likelihood |
Impact |
Score |
Owner |
Mitigation |
Status |
| R1 |
App store review flags health-data permissions, delaying launch past Sept 15 |
4 |
4 |
16 |
Mia Torres |
Submit a TestFlight build for pre-review on Aug 20; prepare a reduced-permission fallback build |
Open |
| R2 |
EHR vendor sandbox is unstable, so integration tests are flaky and real bugs slip through |
3 |
4 |
12 |
Dev Patel |
Record vendor responses and replay them in CI; weekly call with vendor support |
Open |
| R3 |
Clinic front-desk staff are not trained before go-live, causing check-in queues |
3 |
3 |
9 |
Grace Lin |
Two training sessions per clinic in the week before launch |
Open |
| R4 |
Push notification provider rate limits during appointment reminders at 8am |
2 |
3 |
6 |
Dev Patel |
Stagger reminders across a 30-minute window |
Open |
| R5 |
Accessibility audit finds blocking issues late |
2 |
4 |
8 |
Mia Torres |
Audit booked for Aug 25; fixes budgeted in sprint 18 |
Open, mitigation overdue (audit slipped once) |
| R6 |
Key iOS engineer on leave in September |
2 |
2 |
4 |
Owen Castellanos |
Pair-handover in August |
Open |
Closed risks
| ID |
Risk |
Resolution |
Closed date |
| R7 |
HIPAA BAA with hosting provider not signed |
Signed by legal on Aug 6 |
2026-08-06 |
| R8 |
Design system not ready for dark mode |
Dark mode moved out of launch scope |
2026-08-09 |
Review log
| Date |
Reviewer |
Notes |
| 2026-07-31 |
Owen, Mia, Dev |
Initial register, 8 risks |
| 2026-08-14 |
Owen, Mia, Dev, Grace |
Closed R7 and R8, R1 escalated to the COO, R5 audit date slipped |
The template
Show the blank template
Risk register
Author: [your name] · Date: [date]
Summary
Refresh these at each review. The trend is the story: is exposure going down?
Scoring legend
Likelihood × Impact, each 1 (low) to 5 (high). A score above 15 should have a named owner and an active mitigation, not just a row.
| Score |
Meaning |
| 1-5 |
Low: monitor |
| 6-14 |
Medium: mitigate |
| 15-25 |
High: active plan, exec visibility |
Register
Write each risk as cause, event, effect. One owner per risk.
| ID |
Risk |
Likelihood |
Impact |
Score |
Owner |
Mitigation |
Status |
| R1 |
|
|
|
|
|
|
Open |
Closed risks
Keep resolved risks visible. It shows the register is actually maintained, not a graveyard nobody revisits.
| ID |
Risk |
Resolution |
Closed date |
|
|
|
|
Review log
When this register was last reviewed and by whom. A risk register that's never revisited is decoration.
Questions
- How often should it be reviewed?
- Every two weeks for an active project, and before any go or no-go decision
- What makes a good risk statement?
- Cause, event and effect, for example a vendor delay causes a missed launch date
- When do we close a risk?
- When it can no longer happen or has happened and moved to an issue log
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "Risk register" with search_docs, then read it with read_doc. Propose new or updated risks from the project plan, recent status updates, incident notes and open blocker tickets I point you to, each scored with a suggested owner and mitigation, and refresh the summary numbers. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (uncertain scores, risks with no clear owner) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
All-hands agenda
Run of show for a company all-hands: timed segments with presenters, Q&A collection, and follow-ups owed afterwards
ExecutiveFounderOperationsCommunicationsManagerOffsite agenda
Team or leadership offsite plan: goals, pre-reads, day-by-day schedule, sessions with owners, decisions to make, logistics and outcomes
ExecutiveFounderManagerEngineering managerOperationsProject kickoff
Align a new project on goals, scope, roles and cadence
ManagerProduct managerOperationsRACI matrix
Who is Responsible, Accountable, Consulted and Informed
ManagerOperationsProduct managerRetrospective
What went well, what didn't, and what we'll change
ManagerOperationsEngineerProduct managerSecurity policy starter
An information security policy skeleton in the SOC 2 and ISO 27001 style, with roles, policy statements, exceptions, review cadence and sign-off
OperationsEngineering managerExecutiveFounderStart with this template →Sign in