How does the Get Fit process identify gaps and trigger improvement projects before go-live?

Rather than discovering gaps after go-live, Get Fit identifies issues early and provides a controlled mechanism to address them before services enter business-as-usual delivery.

Get Fit acts as a formal health check before service take-on. Its purpose is to:

• Validate readiness against managed service requirements
• Identify gaps that could impact support, security or continuity
• Prevent avoidable incidents during early life support
• Ensure services meet agreed acceptance criteria

Get Fit provides assurance that onboarding has delivered a stable foundation.

What Get Fit assesses

The Get Fit process reviews readiness across multiple dimensions, including:

Technical readiness

Monitoring, access, backup, security controls and support tooling.

Operational readiness

Service Desk enablement, escalation paths, runbooks and documentation.

Governance readiness

Reporting, review cadence, ownership and escalation routes.

Risk and dependency status

Outstanding risks, assumptions or dependencies that could affect delivery.

Assessment is proportionate to scope and service criticality.

Identifying gaps and risks

Where Get Fit identifies gaps, these are clearly documented and categorised.

Examples include:

• Missing or incomplete documentation
• Unsupported or non-standard configurations
• Gaps in monitoring or alerting coverage
• Unclear ownership or escalation paths

Each gap is assessed for impact and urgency.

Triggering improvement or remediation actions

Not all gaps require immediate resolution before go-live.

The Get Fit process distinguishes between:

• Blocking issues that must be resolved before take-on
• Non-blocking improvements that can be scheduled post-go-live

Blocking issues are remediated as part of onboarding. Non-blocking items are logged as improvement actions.

Governance and decision-making

All Get Fit findings are reviewed through onboarding governance.

This ensures:

• Clear visibility of readiness status
• Informed decisions on go-live readiness
• Formal acceptance of residual risk where required

Decisions are documented and auditable.

Transition into BAU improvement planning

Post-go-live, Get Fit outputs feed directly into BAU governance.

This ensures:

• Improvement actions are tracked and prioritised
• Readiness insights inform service reviews and roadmaps
• No issues identified during onboarding are lost or forgotten

Get Fit therefore bridges onboarding and continuous improvement.

Key takeaway

The Get Fit process ensures services are genuinely ready before go-live by identifying gaps, distinguishing between blocking and non-blocking issues, and triggering controlled improvement actions.

By embedding Get Fit into onboarding governance, Espria reduces early-life risk and ensures services enter BAU delivery in a stable, supportable state.

Related questions

• What testing and validation is performed before go-live?
• What documentation do we receive during onboarding?
• How are lessons learned captured after sign-off?