How do you structure and govern the RAID log (risks, assumptions, issues and dependencies)?

Espria uses a structured RAID log to ensure risks, assumptions, issues and dependencies are identified early, actively managed and governed throughout the transition.

The RAID log provides a single, authoritative view of factors that could impact onboarding delivery.

It is used to:

  • Identify and assess risks before they materialise
  • Surface assumptions that need validation
  • Track active issues requiring resolution
  • Manage dependencies across teams and third parties

This ensures potential problems are addressed proactively rather than reactively.

How the RAID log is structured

Each entry in the RAID log is clearly defined and categorised. Typically, each item includes:

  • Description and category (risk, assumption, issue or dependency)
  • Impact and likelihood assessment
  • Ownership and accountability
  • Mitigation or resolution actions
  • Status and review date

Risk weighting and prioritisation

Risks are assessed using agreed impact and likelihood criteria. This allows the Transition Team to:

  • Prioritise risks that threaten service continuity or go-live readiness
  • Focus remediation effort where it adds the most value
  • Escalate high-risk items early

Weighting ensures governance attention is proportionate to risk.

Ownership and accountability

Every RAID item has a named owner. Owners are responsible for:

  • Progressing mitigation or resolution actions
  • Providing updates through governance forums
  • Escalating where actions are blocked or delayed

This prevents risks or issues becoming unmanaged or overlooked.

Governance and escalation

The RAID log is reviewed as a standing agenda item in onboarding governance meetings. This ensures:

  • Changes in risk profile are visible
  • New items are captured promptly
  • Escalation routes are applied where thresholds are breached

High-impact or time-critical items are escalated to leadership in line with agreed governance.

Transition to BAU governance

As onboarding completes, relevant RAID items are either:

  • Closed where resolved
  • Accepted and documented
  • Transferred into BAU risk and improvement registers

This ensures continuity of risk management beyond transition.

Key takeaway

Espria governs onboarding through a live, structured RAID log that provides transparency, accountability and early risk detection.

By actively managing risks, assumptions, issues and dependencies throughout transition, we reduce uncertainty and ensure onboarding remains controlled, predictable and auditable.

Related questions

  • How is governance run during onboarding?
  • How are complaints or issues escalated to leadership during transition?
  • What prerequisites and success criteria are identified at inception?

Not sure where to start?

Book a consultation and we will recommend the quickest route to improvement

Book a discovery call