Supply Chain Optimisation RAID Log
This is a practical guide to building a raid log for a supply chain optimisation project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of improving the efficiency and resilience of the supply chain.
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 supply chain optimisation project it plays the same role, tuned to this kind of work.
Why it matters for a Supply Chain Optimisation project
Supply Chain Optimisation projects live or die on improving the efficiency and resilience of the supply chain. 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 supply chain optimisation projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Supply Chain Optimisation-specific considerations
Tailor the raid log to the risks that most often derail supply chain optimisation projects:
- Data visibility
- Supplier coordination
- Change to established processes
Example
On a real supply chain optimisation project, the raid log would be shaped by improving the efficiency and resilience of the supply chain. In particular, it should explicitly account for the project’s biggest risks — data visibility, supplier coordination, change to established processes — rather than treating them as afterthoughts.