Quick answer
A simple risk register needs seven columns: risk, likelihood (1 to 3), impact (1 to 3), score, owner, response and status. Multiply likelihood by impact to get the score, act on anything scoring 6 or more, and review the register every week. That is enough for most small project teams.
Most project teams know they should track risks. Many start a risk register and abandon it within a month because it becomes a long list nobody reads. The fix is to keep it small, score it the same way every time and look at it every week. Monica Leigh Burkhardt, a project manager in New York, NY, maintains a risk register on every project she runs, including a $450,000 initiative across five departments that finished within its approved budget.
The seven columns

| Column | What goes in it |
|---|---|
| Risk | One event, written as “X happens, causing Y.” |
| Likelihood | 1 = unlikely, 2 = possible, 3 = likely |
| Impact | 1 = minor, 2 = noticeable delay or cost, 3 = threatens a milestone or budget |
| Score | Likelihood × impact (1 to 9) |
| Owner | One named person, not a team |
| Response | The action you will take now, or the trigger for acting later |
| Status | Open, watch or closed |
How to write a useful risk
“Training” is not a risk. “The vendor delivers training materials late, causing staff to go live untrained” is. Writing each risk as an event with a consequence makes it obvious who should own it and what to do about it.
Scoring without arguments
A 1 to 3 scale is deliberate. Five-point scales invite long debates about whether something is a 3 or a 4. With three points, teams decide quickly and move on to the response, which is what matters.
- Score 6 to 9: act now and report it in the weekly update.
- Score 3 to 4: assign an owner and a trigger for acting.
- Score 1 to 2: watch it; close it if it stops being relevant.
The weekly habit
A risk register is only useful if it is current. Spend ten minutes on it before each weekly status meeting:
- Update scores that have changed.
- Add any new risks raised during the week.
- Close risks that no longer apply.
- Copy the top three into your status report.
Common mistakes
- Too many risks. Twenty open risks means none of them get attention. Merge duplicates and close stale items.
- Team owners. “IT” cannot own a risk. A person can.
- No response. A risk with no planned action is just a worry.
- Hiding it. Share the register with sponsors. Early warnings build trust.
A free copy of this format is on the project management resources page, alongside a weekly status report outline. You can also find Monica on Crunchbase and X.


