How do you baseline and report on the current state, and what evaluation outputs do we receive?

Current-state reporting is designed to support onboarding decisions, risk management and long-term service delivery. Espria ensures that environment baselining results in practical, decision-ready outputs, not raw data or opaque reports.

Translating discovery into a usable baseline

Once discovery and assessment activities are complete, findings are consolidated into a structured current-state baseline.

This baseline provides:

• A clear view of what exists today
• How services are configured and interconnected
• Where risks, gaps or constraints exist
• What assumptions have been validated or challenged

The emphasis is on clarity and relevance, not volume.

Core baseline outputs

Depending on scope and environment, baseline outputs typically include:

Current-state environment overview

A structured summary of platforms, services and components in scope.

Architecture and dependency views

Diagrams or written descriptions showing key services, integrations and dependencies.

Asset and service inventory

Visibility of systems, devices, platforms and third-party services relevant to support.

Risk and gap identification

Highlighted risks, unsupported configurations or documentation gaps identified during assessment.

These outputs establish a shared understanding between Espria and the customer.

Evaluation and assessment insights

In addition to factual baselining, Espria provides evaluative insight where appropriate.

This may include:

• Supportability and operational risk observations
• Security or resilience considerations relevant to service delivery
• Areas where configuration or process maturity may impact SLAs
• Dependencies that require careful management during transition

Insights are framed to inform decisions, not prescribe change.

Reporting format and accessibility

Baseline outputs are documented in a format appropriate to onboarding governance.

This ensures:

• Information is accessible to technical and non-technical stakeholders
• Outputs can be referenced during transition and BAU delivery
• Documentation supports auditability and future change
• Where required, outputs are stored within agreed documentation repositories.

Use of baseline outputs during onboarding

The current-state baseline directly informs:

• Transition planning and sequencing
• Remediation and risk mitigation priorities
• Acceptance criteria and go-live readiness
• Ongoing service delivery and improvement planning

Baselining is therefore an active input into onboarding, not a static report.

Ongoing relevance beyond onboarding

Baseline documentation is not discarded after go-live.

It provides:

• A reference point for incident investigation and change
• Context for service reviews and improvement planning
• A foundation for future transformation or optimisation

This ensures value extends beyond transition.

Key takeaway

Espria baselines and reports on your current environment through clear, structured outputs that support onboarding decisions, risk management and long-term service delivery.

By translating discovery into practical, accessible evaluation outputs, we ensure onboarding is informed, governed and aligned from day one. This then informs ongoing monthly service reporting. 

Related questions

• How is our current environment baselined, and what assessment tools are used?
• How is knowledge transfer handled with the outgoing provider?
• How do you ensure undocumented systems or dependencies are identified?