ERP Implementation RAID Log
This is a practical guide to building a raid log for an erp implementation project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of replacing or deploying an enterprise resource planning system across the whole organisation.
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 erp implementation project it plays the same role, tuned to this kind of work.
Why it matters for an ERP Implementation project
ERP Implementation projects live or die on replacing or deploying an enterprise resource planning system across the whole organisation. 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 erp implementation projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
ERP Implementation-specific considerations
Tailor the raid log to the risks that most often derail erp implementation projects:
- Under-estimated data migration
- Business-process change resistance
- Customisation over-reach
Example
On a real erp implementation project, the raid log would be shaped by replacing or deploying an enterprise resource planning system across the whole organisation. In particular, it should explicitly account for the project’s biggest risks — under-estimated data migration, business-process change resistance, customisation over-reach — rather than treating them as afterthoughts.