Smart City Project RAID Log
This is a practical guide to building a raid log for a smart city project project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of delivering connected smart-city 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 smart city project project it plays the same role, tuned to this kind of work.
Why it matters for a Smart City Project project
Smart City Project projects live or die on delivering connected smart-city 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 smart city project projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Smart City Project-specific considerations
Tailor the raid log to the risks that most often derail smart city project projects:
- Multi-vendor integration
- Data governance
- Citizen adoption
Example
On a real smart city project project, the raid log would be shaped by delivering connected smart-city infrastructure. In particular, it should explicitly account for the project’s biggest risks — multi-vendor integration, data governance, citizen adoption — rather than treating them as afterthoughts.