RAID log template for Excel, free
A RAID log is a project’s list of Risks, Assumptions, Issues and Dependencies, kept in one place.
Each item gets an owner, a RAG status, an action and a due date, and the log is reviewed every week.
This template is an Excel workbook with the four sheets, a worked example and a summary of what is still open.
- RRisksWhat might happen and would hurt the project, scored by likelihood and impact.
- AAssumptionsWhat the plan takes as true without proof, and who checks it by when.
- IIssuesWhat has already happened and needs an owner and an action now.
- DDependenciesWhat the project needs from someone outside it, or owes to them.
RAID log example
One project filled in on all four sheets: moving a 120-person office to a new building, move weekend 20 March 2027. The rows point at each other the way a real log does: the electrics running late (I1) is part of what risk R1 warned about, and building control’s sign-off (D3) waits on the fire exit issue (I2).
Risks
Likelihood and impact from 1 to 5; the score is the two multiplied and sets the RAG.
| ID | Risk | Owner | Date raised | Likelihood (1-5) | Impact (1-5) | Score | RAG | Status | Action | Due date |
|---|---|---|---|---|---|---|---|---|---|---|
| R1 | The fit-out of the new floor finishes late | Priya Shah (Facilities) | 11 Jan 2027 | 3 | 5 | 15 | Red | Open | Weekly progress check with the landlord and the contractor; a completion date in the contract | 1 Feb 2027 |
| R2 | The network line is not live on move day | Tom Reid (IT) | 11 Jan 2027 | 3 | 4 | 12 | Amber | Open | Order the line 90 days ahead and book a 4G backup router | 15 Feb 2027 |
| R3 | Staff push back on hot-desking | Aisha Khan (HR) | 18 Jan 2027 | 4 | 2 | 8 | Amber | Open | Two drop-in sessions and a desk-booking trial on one floor | 1 Mar 2027 |
| R4 | The removals firm loses or damages equipment | Dan Price (Office manager) | 18 Jan 2027 | 2 | 3 | 6 | Green | Open | Tagged asset list, photos before packing, check the firm's insurance | 15 Mar 2027 |
| R5 | Furniture lead time runs past ten weeks | Priya Shah (Facilities) | 25 Jan 2027 | 2 | 4 | 8 | Amber | Closed | Ordered from the supplier's stock range, delivery confirmed | 25 Jan 2027 |
| R6 | Repairs owed on the old lease cost more than budgeted | Helen Ward (Finance) | 25 Jan 2027 | 3 | 3 | 9 | Amber | Open | Surveyor's schedule of condition before giving notice | 28 Feb 2027 |
Assumptions
A6 is Red because the check came back: the permits do not transfer, so it needs a decision.
| ID | Assumption | Owner | Date raised | Impact if wrong | RAG | Status | Action | Due date |
|---|---|---|---|---|---|---|---|---|
| A1 | The landlord gives access for the fit-out from 1 February | Priya Shah (Facilities) | 11 Jan 2027 | High | Amber | Open | Get the access date in writing in the agreement for lease | 20 Jan 2027 |
| A2 | Most of the current desks and chairs can be reused | Dan Price (Office manager) | 11 Jan 2027 | Medium | Green | Closed | Condition survey done: 80% reusable | 18 Jan 2027 |
| A3 | Headcount stays at 120 until after the move | Aisha Khan (HR) | 18 Jan 2027 | Medium | Green | Open | Check hiring plans with each head of department monthly | 1 Mar 2027 |
| A4 | The phone system moves without new handsets | Tom Reid (IT) | 18 Jan 2027 | High | Amber | In progress | Vendor to confirm the handsets work on the new network | 8 Feb 2027 |
| A5 | Everyone can work from home on the Friday before the move | Aisha Khan (HR) | 25 Jan 2027 | Low | Green | Open | Announce at the all-hands and check every laptop is issued | 15 Mar 2027 |
| A6 | Parking permits transfer to the new site | Dan Price (Office manager) | 25 Jan 2027 | Low | Red | Open | The council says they do not: decide on a travel allowance instead | 15 Feb 2027 |
Issues
Problems that have happened, each with the action that resolves it.
| ID | Issue | Owner | Date raised | Impact | RAG | Status | Action | Due date |
|---|---|---|---|---|---|---|---|---|
| I1 | The fit-out contractor is two weeks behind on the electrics | Priya Shah (Facilities) | 8 Feb 2027 | High | Red | Open | Recovery plan with weekend working and an agreed cost cap | 15 Feb 2027 |
| I2 | The floor plan does not meet the fire exit rules | Priya Shah (Facilities) | 1 Feb 2027 | High | Amber | In progress | Architect revises the layout for building control to review again | 12 Feb 2027 |
| I3 | Two teams want the same quiet room | Dan Price (Office manager) | 3 Feb 2027 | Low | Green | Closed | Booking rota agreed between the two team leads | 5 Feb 2027 |
| I4 | The removals quote is 20% over budget | Helen Ward (Finance) | 5 Feb 2027 | Medium | Amber | Open | Second and third quotes requested | 19 Feb 2027 |
| I5 | The wifi survey of the new floor shows a dead zone | Tom Reid (IT) | 10 Feb 2027 | Medium | Amber | In progress | Two extra access points ordered | 26 Feb 2027 |
| I6 | Signing the lease is held up by the solicitors' questions | Helen Ward (Finance) | 15 Jan 2027 | High | Green | Closed | Questions answered; lease signed on 22 January | 22 Jan 2027 |
Dependencies
What the move waits on from the landlord, suppliers and other teams.
| ID | Dependency | Owner | Date raised | Impact if late | RAG | Status | Action | Due date |
|---|---|---|---|---|---|---|---|---|
| D1 | The landlord hands over the finished shell of the floor | Priya Shah (Facilities) | 11 Jan 2027 | High | Amber | Open | Weekly call with the landlord's agent | 1 Feb 2027 |
| D2 | The telecoms provider installs the network line | Tom Reid (IT) | 11 Jan 2027 | High | Amber | In progress | Chase the order reference every two weeks | 1 Mar 2027 |
| D3 | Building control signs off the fit-out | Priya Shah (Facilities) | 18 Jan 2027 | High | Green | Open | Inspection booked; waits on I2 | 8 Mar 2027 |
| D4 | The furniture supplier delivers the new desks | Dan Price (Office manager) | 18 Jan 2027 | Medium | Green | Open | Delivery slot confirmed for the week before the move | 10 Mar 2027 |
| D5 | Finance approves the removals purchase order | Helen Ward (Finance) | 25 Jan 2027 | Medium | Amber | Open | Waits for the third quote (I4) | 22 Feb 2027 |
| D6 | The old landlord agrees a date for the exit inspection | Helen Ward (Finance) | 25 Jan 2027 | Medium | Green | Open | Three dates proposed in writing | 30 Mar 2027 |
How to run a RAID log
- Start it at kick-off. Open the log in the first project meeting and ask four questions in turn: what could go wrong, what are we assuming, what is already a problem, and who are we waiting on. Write one item per row on its sheet.
- Give every row one owner and a due date. A person, not a team, and the date the action is due. Without both a row is a worry, not an item someone is working on.
- Score the risks. Likelihood and impact from 1 to 5. The score is the two multiplied, and the RAG follows it: 15 or more is Red, 8 to 14 Amber, below 8 Green. On the other three sheets, pick the RAG yourself: Red means it needs a decision this week.
- Move items between sheets. A risk that happens becomes an issue. An assumption that turns out wrong becomes an issue too. Close the old row and add the new one with the same wording, so the history stays readable.
- Review it every week. Go through the Red and Amber rows in the project meeting, update the status and the action, and close what is done. The Summary sheet shows what is still open on each sheet.
RAID log vs risk register
A risk register is the R of a RAID log on its own: the things that might happen, with how likely and how bad each one is. It answers “what could go wrong”. A RAID log also answers “what are we relying on”, “what has gone wrong” and “who are we waiting for”.
Use the register alone for a small internal project, and the full log when the project depends on suppliers, landlords or other teams. If you want the register on its own, with probability in percent and impact in working days, use the risk register template.
What RAG means
Red, Amber, Green: a traffic-light status. Red needs a decision or help now, Amber is being worked on but could slip, Green is under control. In the Risks sheet the RAG comes from the score; in the other three the owner sets it.
Updated .
Frequently asked questions
What does RAID stand for in project management?
Risks, Assumptions, Issues and Dependencies. A RAID log keeps the four lists side by side, so a project manager can see in one place what might go wrong, what the plan relies on, what has gone wrong and who the project is waiting on.
Does RAID ever mean something else?
Some teams use Risks, Actions, Issues and Decisions instead, keeping assumptions and dependencies elsewhere. The sheet works the same way: rename a tab and its first column if your organisation uses that version.
Is this RAID log template free?
Yes. It is an Excel workbook (.xlsx) you download from this page, with no sign-up and no email. There are no macros.
What is the difference between a RAID log and a risk register?
A risk register is one of the four parts: the list of things that might happen. A RAID log adds what the plan assumes, what has already happened and what the project depends on. A small project often keeps only a risk register; a larger one, or one with outside suppliers, usually needs the full log.
Who owns the RAID log?
The project manager keeps it up to date, and each row has its own owner who does the action. In a programme, a project office often collects every project's log in the same format so the Red items can be read across projects.
Does it work in Google Sheets?
Yes. Open a blank spreadsheet, choose File > Import > Upload, pick the file and choose Replace spreadsheet. The score and RAG formulas, the drop-down lists, the colours and the Summary counts come with it.
Track risks and issues in Onplana
Every Onplana project has a Risks tab and an Issue Log, on the Free plan, next to the tasks they affect. Dependencies are links between tasks on the Gantt chart, so a late task moves the ones after it.
Start free