GroupChatOnGroupChatOnToolkit
Excel template

Risk, Issue & Change Log (Excel)

Three registers every project needs, in one workbook. Risks are things that might happen: each gets a probability and impact from 1 to 5, a score and a heat colour, a response and an owner, and appears on a 5×5 heat map. Issues are things that have already happened: each has a priority, an owner, a target date and a days-open counter. Change requests record what was asked to change, its effect on cost and time, and who approved it.

Free · no sign-up · opens in Microsoft Excel, Google Sheets, LibreOffice and WPS Office. Files contain no macros.

Preview

Real view of the file with its sample data (yellow cells are where you type).

Risks
IDRaised onRisk (cause → event → effect)CategoryOwnerProbability (1-5)Impact (1-5)ScoreRatingResponseAction to takeAction dueStatus
R-01Oct-26Because the sponsor is travelling in the design phase, design approval may be delayed, which would push back the build.StakeholdersPriya3412HighReduceBook two review slots now; agree a deputy who can approve.Nov-26Open
R-02Oct-26Because only one developer knows the hosting set-up, illness or leave may stop the build, which would delay go-live by weeks.People and skillsVikram2510HighReduceWrite a set-up note; pair a second developer for one day a week.Oct-26Open
R-03Oct-26Because content comes from five departments, pages may arrive late or incomplete, which would delay testing.ScheduleSana4312HighReduceWeekly content deadline per department; send a page template with word limits.Nov-26Monitoring
R-04Oct-26Because the hosting price is in a foreign currency, a currency change may raise the yearly cost, which would exceed the budget line.CostFinance224LowAcceptKeep 5% contingency on the hosting line.Dec-26Open
R-05Oct-26Because the old site has no redirects planned, search engines may drop old pages, which would lose enquiries after launch.TechnicalVikram3412HighAvoidList every old address and map it to a new page before launch.Nov-26Open

What's inside

How to use it

  1. On the Settings sheet type your currency (for example USD, €, ₹ or AED). Change the rating limits only if your organisation uses different ones.
  2. Delete the sample rows on the Risks, Issues and Changes sheets.
  3. For each risk, write it as "Because of [cause], [event] may happen, which would [effect]". Pick its probability and impact from 1 (very low) to 5 (very high).
  4. Choose a response (Avoid, Reduce, Transfer or Accept), write the action, give it an owner and a due date.
  5. When a risk happens, set its status to "Became an issue" and add it to the Issues sheet.
  6. Log every change request as it arrives, fill in its cost and time impact, and record the decision once the sponsor or change board has decided.
  7. Review the Heat Map and the Dashboard in every weekly meeting.

Tips

Questions and answers

How is the risk score calculated?

Score = probability × impact, so it runs from 1 to 25. By default 1–4 is Low, 5–9 Medium, 10–16 High and 20–25 Critical. You can change the limits on the Settings sheet.

What is the difference between a risk and an issue?

A risk is uncertain and in the future: it may or may not happen. An issue is happening now and needs action. When a risk happens it becomes an issue.

Which risks does the heat map count?

Only risks whose status is Open or Monitoring. Closed risks and those that became issues are left out.

Is this a formal risk assessment?

No. It is a working register to help the team think and act. For safety, legal or financial risks, follow your organisation's policies and ask a qualified professional.

More in the Project Management toolkit

Also useful