Railway Project RAID Log
This is a practical guide to building a raid log for a railway project project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of building or upgrading rail infrastructure.
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 railway project project it plays the same role, tuned to this kind of work.
Why it matters for a Railway Project project
Railway Project projects live or die on building or upgrading rail infrastructure. 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 railway project projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Railway Project-specific considerations
Tailor the raid log to the risks that most often derail railway project projects:
- Possession/access windows
- Safety approvals
- Multi-stakeholder coordination
Example
On a real railway project project, the raid log would be shaped by building or upgrading rail infrastructure. In particular, it should explicitly account for the project’s biggest risks — possession/access windows, safety approvals, multi-stakeholder coordination — rather than treating them as afterthoughts.