Facility Relocation RAID Log
This is a practical guide to building a raid log for a facility relocation project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of relocating a facility or operation to a new site.
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 a facility relocation project it plays the same role, tuned to this kind of work.
Why it matters for a Facility Relocation project
Facility Relocation projects live or die on relocating a facility or operation to a new site. 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 facility relocation projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Facility Relocation-specific considerations
Tailor the raid log to the risks that most often derail facility relocation projects:
- Downtime minimisation
- Logistics
- Staff and equipment moves
Example
On a real facility relocation project, the raid log would be shaped by relocating a facility or operation to a new site. In particular, it should explicitly account for the project’s biggest risks — downtime minimisation, logistics, staff and equipment moves — rather than treating them as afterthoughts.