Office Relocation RAID Log
This is a practical guide to building a raid log for an office relocation project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of moving an office to new premises.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On an office relocation project it plays the same role, tuned to this kind of work.
Why it matters for an Office Relocation project
Office Relocation projects live or die on moving an office to new premises. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how office relocation projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Office Relocation-specific considerations
Tailor the raid log to the risks that most often derail office relocation projects:
- Minimising downtime
- IT and telephony cutover
- Staff communication
Example
On a real office relocation project, the raid log would be shaped by moving an office to new premises. In particular, it should explicitly account for the project’s biggest risks — minimising downtime, IT and telephony cutover, staff communication — rather than treating them as afterthoughts.