Consistency through travel
Workout completion, check-in context, Marci's edit, publication, Jane's reply, and follow-up remain separate evidence.
Drafted · edited · waiting for approval All requested capabilities
Client + coach view · read-only preview
The system can prepare the handoff. Marci still owns the message.
Messages stay connected to the coaching decision that produced them, while draft, edit, approval, publication, reply, and follow-up never collapse into one automated action.
Fabricated presentation. The conversation and delivery states are fabricated. No message provider is connected, and no draft can send without human approval.
Capability preview
Human reviewClient messaging
System draftWeekly feedback prepared
Not publishedWorkout and check-in packet attached
Coach editPersonal context added
SavedMarci changed the next-session wording
PublicationReady for Marci
Approval requiredClient delivery is a separate action
Inside the experience
Useful state, not another disconnected tool.
The system prepares the handoff; the coach decides what the client receives.
Weekly feedback prepared
Workout and check-in packet attached
Personal context added
Marci changed the next-session wording
Ready for Marci
Client delivery is a separate action
One connected workflow
The handoffs remain visible.
Each step is separately reviewable so people, permissions, and future providers can change without hiding what happened.
- 1Prepare
The system organizes relevant evidence.
- 2Edit
Marci edits tone, context, and next action.
- 3Approve
Only an approved artifact may publish.
- 4Continue
Reply and follow-up become visible work.
What this preview proves
Client messaging has a place in the system—not just a place on a feature list.
The system prepares the handoff; the coach decides what the client receives. This page uses static fabricated configuration and cannot read or change an operational record.