# Customer onboarding pause conditions

Illustrative planning brief; no automatic product import.

Illustrative case: The customer contact goes on leave mid-onboarding.

## Decision

Pause customer-dependent milestones and retain a clear restart package.

## Owned work

- Identify paused inputs
  - Owner role: Onboarding coordinator
  - Acceptance evidence: The outstanding customer decisions are listed.
- Prepare restart context
  - Owner role: Customer enablement contributor
  - Acceptance evidence: Current state and remaining demonstration are documented.
- Agree restart trigger
  - Owner role: Customer readiness reviewer
  - Acceptance evidence: The customer confirms return or substitute-contact timing.

## Workflow

1. List the customer-dependent decisions still open and the work that can safely remain paused.
2. Prepare a restart packet with the last accepted state, pending demonstration and current material revision.
3. Agree the return or substitute-contact trigger and confirm the receiver can resume from the packet without replaying the entire history.

## Judgment

Do not mark paused work as customer rejection.


## Filled illustrative planning example

Synthetic restart packet: customer data scope accepted; sample report review still open; current guide revision B; restart when the returning or authorized substitute contact confirms a review slot. No customer rejection is inferred from leave.


## Working artifact

- Returning customer contact / Current accepted scope, revision B and open report demonstration. / Confirms a return review slot or authorized substitute.
- Enablement contributor / Pending demonstration and required sample preparation. / Confirms material remains usable at restart.
- Readiness reviewer / Pause reason and the explicit opening condition. / Reopens the review only after contact and evidence are available.


## Workflow questions

### Can internal preparation continue?

Yes, where it does not assume the missing decision

### What restarts the plan?

A confirmed customer contact and available review slot

## Product connection

Adapt the stage tasks, owner roles and acceptance evidence to your TeamBoost planning workflow. The example does not create customer records or import an onboarding plan.

Confirm account availability before adopting this manual outline.


## Leave a restartable handover

A restart packet assigns each missing input to the role that can supply or accept it.

### Customer contact

Responsibility: Confirm return or authorized substitute and the next review slot.

Receiving evidence: The enablement contributor receives an agreed restart trigger.

### Enablement contributor

Responsibility: Retain current scope, material revision and pending demonstration.

Receiving evidence: The returning contact can resume without reconstructing the history.

### Readiness reviewer

Responsibility: Keep the customer-dependent milestone pending until demonstrated.

Receiving evidence: The completion label reflects the actual accepted outcome.