Creating Check-In Templates
Define the questions clients answer in periodic check-ins.
trainer guide/clients/[id]
What this is for: Capture structured client feedback (sleep, soreness, mood, photos) on a recurring cadence.
What a template is
A CheckInTemplate is a reusable set of questions you build once and use across multiple clients. Question types:
| Type | What the client sees |
|---|---|
| Text | Free-text answer (notes, descriptions) |
| Scale | 1-10 slider (mood, sleep quality, soreness) |
| Photo | Upload a URL link to a photo (front/side/back) |
| Yes-No | Boolean toggle |
| Number | Numeric input (weight, hours of sleep) |
Each template can have any number of questions in any order.
Create a template (current state)
A template body (sent to the API) looks like:
{
"name": "Weekly Check-In",
"questions": [
{ "type": "scale", "label": "Sleep quality (1-10)", "required": true },
{ "type": "scale", "label": "Energy level (1-10)", "required": true },
{ "type": "text", "label": "Anything weird this week?", "required": false },
{ "type": "photo", "label": "Front photo (optional)", "required": false }
]
}
Once created, templates are owned by you and reusable across all your clients.
Editing or archiving a template
- API:
PATCH /api/check-in-templates/[id]orDELETE /api/check-in-templates/[id]. - A template that's referenced by an active schedule cannot be deleted — archive instead.
What clients see
When you schedule a check-in (next article: Scheduling Check-Ins), an instance is generated on each due date. The client gets a notification (Mailgun email + push if enabled) and a form to answer.
Common pitfalls
Where to find this
- Schedule for client:
/clients/[clientId]→ Forms tab (read existing schedules). - API:
GET/POST /api/check-in-templates,GET/PATCH/DELETE /api/check-in-templates/[id].
Was this article helpful?
