The RAID log we use on every S/4HANA programme
Six-column format · escalation triggers · linked to SAP Activate phases.
Why most RAID logs fail
Half the RAID logs I see are just a risk register in disguise. They confuse severity with probability, they don't link items back to the SAP Activate phase they threaten, and they die the first time someone forgets to update them. This template solves all three.
The six columns that matter
Type (Risk/Assumption/Issue/Dependency), Description, Impact, Probability, Owner, Mitigation. Anything more is noise, anything less is undercooked. We colour-code Type and let the impact-probability score drive escalation.
How it links to SAP Activate
Every RAID entry references the SAP Activate phase it threatens (Prepare/Explore/Realize/Deploy/Run). At phase gates, the log auto-produces a filtered view for the steering committee — no more Sunday-night deck rebuilds.
Escalation triggers baked in
When an item's impact × probability crosses 12 (out of 25), the row lights up amber; above 20 it auto-flags for the next steering committee. This is what turns a spreadsheet into a live governance instrument.
Run this template live inside Capittance
The Capittance Harmonizer platform ships with every template on this page as a live, autosaving module — no downloads, no version drift, exports to PDF/Word/PPT with one click.