Risk Register Template for Software Projects
Updated: Oct 18
A common state for a risk register halfway through a project: forty rows, every one marked Open, nothing updated in two months, and the risk that eventually derails the project isn't on the list at all. A register like that is worse than none, because it turns "we stopped thinking about risk" into "we have a process". It lets everyone feel covered.
A useful register is short, current, and judged by one thing: did it warn you about what actually happened? This post shows how to check whether yours does, how to find the risks that tend to be missing, how to write entries someone can act on, and where the familiar likelihood × impact score gets the ranking wrong.
Audit what your register caught
Before changing the template, test the register you have. Take one current or recent project and check three things:
Capture rate. List the last five problems that cost the project real time or money. How many were in the register before they happened? This is the number that matters most, and it's rarely measured.
Staleness. How many rows haven't been updated in four weeks or more?
Real responses. How many mitigations say "monitor" or "monitor closely" with no trigger and no pre-agreed action?
A low capture rate means the problem is how risks get found, not how they get scored, and the next section deals with that. Lots of stale rows mean the register has no review rhythm or has grown too long. And "monitor" with nothing attached means the register records worries rather than decisions.
The test: if fewer than half of your last five problems were in the register beforehand, spend your effort on finding risks before you touch the template.
Find risks with a pre-mortem
Teams usually build a register by asking "what could go wrong?" That tends to produce generic worries: schedule, resourcing, scope. The risks that sink projects are usually more specific, and a different question brings them out.
A pre-mortem asks the team to imagine the project has already failed and explain why. The idea rests on what Mitchell, Russo and Pennington called prospective hindsight: explaining a future event as if it had already happened. In their experiments, people explaining an outcome treated as certain wrote longer explanations with a higher proportion of episodic reasons, meaning specific events rather than general factors. A register needs exactly those specific reasons.
The tail matters too. Flyvbjerg and Budzier analysed 1,471 IT projects. The average cost overrun was 27%, but one project in six was a "black swan", with an average cost overrun of 200% and a schedule overrun of almost 70%. So the pre-mortem shouldn't stop at "we slipped a few weeks". Ask the question that finds the tail too: "It's a year from now, the project cost three times the budget. What happened?"
Two other good sources of entries: the assumptions in your design documents (an assumption like "volumes stay under 10,000 a day" is a risk with an owner and a signal, as Documenting Constraints Without Drowning the Doc explains), and every external dependency with a date attached. The pre-mortem facilitation kit has a script for the session.
The test: after the pre-mortem, how many of the new risks were already in the register? If most were missing, run one at every major milestone, not just at kickoff.
Write each risk as cause, event, effect
"Schedule risk" is an anxiety, not a risk. A useful entry has three parts: the cause (what's true now), the event (what might happen because of it), and the effect (what it would do to the project). Then add the two things that make it manageable: a signal that it's starting to happen, and a date by which you'll know.
Weak: "Okta integration risk."
Strong: "Because the Okta API rate limits are undocumented (cause), bulk invite testing may be throttled (event), delaying beta by one to two weeks (effect). Signal: any 429 response in staging. Resolves by: 3 June, when vendor support confirms the limit."
The resolves-by date is what makes a risk feed your reporting. A risk due to resolve within the next two weeks belongs in the status report, and its outcome can change the forecast.
The test: could someone outside the project read the entry and say what would happen, how bad it would be, and when you'll know? If not, rewrite it in cause, event, effect form.
Don't let the score rank your worst risks
The standard register scores likelihood and impact as High, Medium or Low (3, 2 and 1) and multiplies them. That's fine for sorting a long list. It goes wrong at the top, which is the part that matters most.
Cox's analysis of risk matrices found that they can assign identical ratings to quantitatively very different risks ("range compression"), and can assign higher ratings to quantitatively smaller risks. Typical matrices can correctly compare only a small fraction of randomly chosen pairs of hazards, and he found that where likelihood and severity are negatively correlated, they can be "worse than useless". A review of risk matrices in the oil and gas industry by Thomas, Bratvold and Bickel concluded that they "produce arbitrary decisions" and that these problems are inherent in their structure.
Here's what that looks like in a software register. In the composite worked example below:
R3, "the back button confuses users after switching workspace", is Medium likelihood × Medium impact = 4.
R5, "a user who loses access mid-session can still see the old workspace's data", is Low likelihood × High impact = 3.
The matrix ranks the usability annoyance above a possible data exposure. When you write each impact as a range, the difference is obvious. R3 costs a few days of UI rework. R5 is a security incident, with customer notification and weeks of work.
So use the score to sort the long list, but don't let it decide the top. Any High-impact risk gets its impact written as a range in days or money, and goes on the review list whatever its likelihood score.
The test: take your three highest-scoring risks and your three highest-impact risks. If they aren't the same six, look at the ones that differ. That's where the matrix is steering your attention.
A response is a decision, not a verb
"Monitor" isn't a response. The useful responses each force a specific decision:
Response | Use it when | The entry must say |
Avoid | You can change the plan so the risk can't happen | What changed in the plan, and what it cost |
Reduce | Work now lowers the likelihood or the impact | The task, its owner and its date, and the expected effect |
Transfer | Someone else can carry it: vendor, contract, insurance | Where the transfer is written down, and what stays with you |
Accept with contingency | Acting now costs more than the risk, but you know what you'd do | The trigger, and the action you've already agreed if it fires |
Accept | The impact is small and absorbable | Who accepted it, and when it will be looked at again |
"Monitor" becomes legitimate when it's written as "accept with contingency": a named signal, plus an action agreed in advance. For example: "If staging returns a 429, switch bulk invites to the fallback flow; agreed with the product lead." Monitoring with no trigger and no action just means nobody has decided anything.
The test: for each open risk, can you name the decision behind the response? If the answer is "we'll keep an eye on it", the decision hasn't been made yet.
Keep it short and alive
The register stays useful when it has a rhythm and a way to close things:
Every week: the owner of each top risk confirms its status and signal. Anything past its resolves-by date gets resolved: it happened, it passed, or it gets a new date with a reason.
At every milestone: run a short pre-mortem, add what's new, and close what has passed.
When something surprises the team: add it the same day. Don't wait for the review.
When a risk happens: mark it Realised and move it to the issue list. It's no longer a risk.
Keep the active list short enough that the weekly review covers every row. If it doesn't, either the project needs a programme-level register with separate project registers underneath, or some rows are worries that should be closed. Closed risks should stay visible, marked closed, so the register shows what the team saw coming.
The test: sort by the date each row was last updated. Anything untouched since the last milestone is either closed and not marked, or nobody is managing it.
The template
Column | What goes in it |
ID | Stable identifier (R1, R2...). Never reused |
Risk | Cause, event, effect, in one or two sentences |
Likelihood / Impact | High, Medium or Low each, used for sorting |
Impact range | For High-impact risks: days or money, low to high |
Signal | What you'd see first if it's starting to happen |
Resolves by | The date you'll know either way |
Response | Avoid, reduce, transfer, accept with contingency, accept, plus the decision |
Owner | One named person |
Status | Open, Realised (moved to issues) or Closed |
Updated | The date of the last real review |
For risks on the top list, keep a fuller entry alongside the table:
R5 Permissions: stale access after removal
Cause: Session tokens are cached for 15 minutes after a workspace
switch
Event: A user removed from a workspace mid-session still sees its
data until the token expires
Effect: Data exposure to a removed user; customer notification;
estimated 3-8 weeks of work and review
Signal: Any audit-log read by a user after their removal timestamp
Resolves: 2026-06-12 (spike result)
Response: Reduce. Spike to revoke tokens on removal (Pat, week 3).
Until then, accept with contingency: if the signal fires,
force-expire all sessions for that workspace (agreed with
the security lead).
Owner: Pat
A worked example
Here is a composite register for a workspace-switching project in a multi-tenant product. The figures and people are illustrative.
ID | Risk | L | I | Score | Impact range | Resolves by | Response | Owner | Status |
R2 | Undocumented Okta rate limits throttle bulk invite testing, delaying beta | M | H | 6 | 1-2 weeks | 3 Jun | Accept with contingency: fallback invite flow if staging returns a 429 | Sam | Open |
R5 | Cached tokens let a removed user see a workspace's data | L | H | 3 | 3-8 weeks, plus customer notification | 12 Jun | Reduce: revocation spike; contingency: force-expire sessions | Pat | Open |
R3 | Back button confuses users after switching workspace | M | M | 4 | 2-4 days | 1 Jul | Reduce: user testing in week 7 | Riley | Open |
R1 | Session-scoped deep links break on switch | M | M | 4 | 3-5 days | 29 May | Reduce: week 1 spike to list the cases | Pat | Closed |
R4 | One engineer on call in week 6 reduces capacity | H | L | 3 | 2 days | 20 May | Accept: cover confirmed | Sam | Closed |
Sorted by score, R5 comes last of the three open risks. Sorted by impact range, it comes first, and that's how the team reviews it every week. The pre-mortem that produced R5 asked "a customer has emailed to say a removed contractor still saw their data; what happened?" Nobody had raised it when the question was "what could go wrong?"

What to do this week
Run the three audit checks on your current register, starting with the capture rate. Hold a 30-minute pre-mortem on the project, including one round on the "three times the budget" question. Rewrite your top risks in cause, event, effect form with a signal and a resolves-by date. Give every High-impact risk an impact range, and compare your top list by score with your top list by impact. Replace each bare "monitor" with a decision. The Pre-Mortems Beat Post-Mortems post explains why the pre-mortem works.
Final takeaway
A risk register is worth keeping only if it warns you about what actually happens, so measure that first. Find risks by imagining the failure has already happened, including the version where the cost triples. Write each one as cause, event and effect, with a signal and a date you'll know by. Use likelihood × impact to sort the long list, but rank the top by impact range, because the matrix can put a usability annoyance above a data exposure. Make every response a decision someone can point to. Keep the list short enough that the whole thing gets reviewed every week.
A risk register works best next to an agreed scope, and the Project Charter Template for Technical Initiatives is where that scope gets written down.
Sources
Cox, L. A., "What's Wrong with Risk Matrices?", Risk Analysis 28(2), 2008, pp. 497–512: poor resolution (typical matrices correctly compare only a small fraction of random pairs of hazards), range compression, higher ratings for quantitatively smaller risks, and "worse than useless" results for negatively correlated frequency and severity. https://doi.org/10.1111/j.1539-6924.2008.01030.x
Thomas, P., Bratvold, R. B. and Bickel, J. E., "The Risk of Using Risk Matrices", SPE Economics & Management 6(2), 2014, pp. 56–66: a review of 30 SPE papers; risk matrices "produce arbitrary decisions", and the problems are inherent in their structure. https://doi.org/10.2118/166269-PA
Flyvbjerg, B. and Budzier, A., "Why Your IT Project May Be Riskier than You Think", Harvard Business Review, September 2011 (also SSRN 2229735): 1,471 IT projects; average cost overrun 27%; one in six a "black swan" with an average cost overrun of 200% and a schedule overrun of almost 70%. https://doi.org/10.2139/ssrn.2229735
Mitchell, D. J., Russo, J. E. and Pennington, N., "Back to the future: Temporal perspective in the explanation of events", Journal of Behavioral Decision Making 2(1), 1989, pp. 25–38: prospective hindsight; explanations for certain outcomes were longer and contained a higher proportion of episodic reasons. https://doi.org/10.1002/bdm.3960020103


