# Onboarding and Follow-up Planner

Clearweft · Week 15 · Practical build

Use your own verified records. Blank fields are intentionally unpopulated. Label demonstrations, unavailable data and assumptions; never present them as actual customer results.

## Onboarding path
- Person and starting event:
- Promise already made:
- First useful result:
- Evidence available: system event / self-report / proxy / unavailable:
- Prerequisites:

## Sequence design
| Message/step | Trigger or timing | One purpose | Useful action | Destination | Evidence | Stop/change condition |
| --- | --- | --- | --- | --- | --- | --- |
| Delivery | | | | | | |
| First-use guidance | | | | | | |
| Obstacle/help | | | | | | |
| Relevant next step | | | | | | |

## Rules and ownership
- Confirmed source event:
- Duplicate-start prevention:
- Current-state check:
- Preferences/unsubscribe handling:
- Cancellation/refund/changed-status handling:
- Human help owner and response expectation:

## Recipient test
| Scenario | Expected experience | Observed experience | Fix/owner |
| --- | --- | --- | --- |
| First delivery | | | |
| First task | | | |
| Repeated trigger | | | |
| Changed or stopped status | | | |
| Help request | | | |

## Review
- Main obstacles observed:
- Change made:
- First-use evidence to collect:
- Review date:

## Completion check

A new recipient can reach the first useful result and request help when needed.

Date:

Owner:

Next review: