---
title: Scope, Timeline, and Customer Communications
description: Align wave scope, timeline constraints, and customer communication plans, including cutover and hibernate procedures.
sidebar:
  label: Scope, timeline, and communication
  order: 5
source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/migration-factory-setup/scope-timeline-and-communications/"
source_file: "docs/migration/design-and-mobilize/migration-factory-setup/scope-timeline-and-communications.mdx"
---

## Objective

Wave operations need a synchronized control model for scope, timing, and stakeholder communication.
This is especially critical in cutover and hibernate windows where technical and business risks converge.

## Scope and Timeline Baseline

<CardGrid>
  <Card title="Wave scope boundaries">
    Define in-scope workloads, deferred items, blocked dependencies, and explicit exclusions.
  </Card>
  <Card title="Timeline architecture">
    Define freeze windows, implementation windows, validation windows, and rollback windows.
  </Card>
  <Card title="Change control model">
    Specify who can approve scope changes and until which cut-off point.
  </Card>
  <Card title="Delivery commitments">
    Align throughput assumptions and confidence levels with partner and customer stakeholders.
  </Card>
</CardGrid>

## Customer Communication Model

- **Audience segmentation**: Separate communication streams for executives, business owners,
  operations, and impacted users.
- **Event-driven templates**: Predefine messages for schedule confirmation, cutover start,
  rollback activation, and service restoration.
- **Decision checkpoints**: Communicate go/no-go status at agreed milestones.
- **Single source of truth**: One authoritative status channel to avoid conflicting updates.

## Cutover and Hibernate Planning

<Steps>

1. Define cutover objective, outage tolerance, and acceptance criteria with the customer.
2. Align hibernate criteria for services that must pause during transition.
3. Establish reactivation sequence and service validation steps for business restart.
4. Rehearse communication timing with technical run checkpoints.
5. Validate rollback communication as rigorously as success-path communication.

</Steps>

## Common Risks

- Scope changes accepted too late in the wave lifecycle.
- Communication cadence misaligned with actual technical decision points.
- Hibernate duration underestimated relative to data validation effort.
- Rollback path documented technically but not communicated operationally.