Fitness Questionnaire¶

A client intake questionnaire, long enough that it needs to be broken up. Each section lives on its own page so it can be reviewed, edited and handed around independently.

What this site is

This is the source of truth for the questions — their wording, their answer types, their ordering and the logic between them. It is a static site, so it does not collect answers.

The pages here are what the voice subagents are handed at call time, so a reworded question is asked in its new wording on the next call. See The agentic flow.

Sections¶

#	Section	What it covers	Filled by
1	About you	Identity, contact, household, occupation	Client
2	Health & medical history	PAR-Q+ screening, conditions, vitamins and supplements, family history	Client
3	Systems review	Symptom sweep by body system, digestive and menstrual detail	Client
4	Injuries & movement	Current pain	Client
5	Activity & training history	Current activity, daily lifestyle, attitude to exercise	Client
6	Goals & motivation	Primary goal, obstacles	Client
7	Nutrition & hydration	Food frequency, dietary needs, relationship with food	Client
8	Sleep, stress & recovery	Sleep quality, stressors, energy, recovery habits	Client
9	Measurements & assessments	Anthropometrics, vitals, movement screen, capacity tests	Coach
10	Preferences & logistics	Availability, equipment, likes/dislikes, communication	Client
11	Consent & sign-off	Declarations, waiver, privacy, signatures	Both

How to use it¶

Reviewing the questionsEditing the questionsAdding a sectionHanding it to a clientRunning it as a conversation

Read straight through in nav order. Sections 1–8 and 10 are what the client answers before the first session; section 9 is completed by the coach at the baseline appointment; section 11 is signed by both.

Every question is a row in a table with a stable field ID. Change the wording freely, but treat the field ID as permanent once responses exist — it is what ties an answer back to its question.

Answer types and the notation for conditional questions are defined in Question patterns.

Copy the blank section template into docs/sections/, number it, and add a line to the nav array in zensical.toml. The preview server picks up both without a restart.

Split delivery over two sittings — sections 1–4 (screening) first, so anything that needs medical clearance surfaces early, then 5–8 and 10. Estimated completion times are noted at the top of each page; the whole thing runs to roughly 75 minutes of client time, which is why it should never arrive as one link.

An AI agent can conduct the intake conversationally instead of as a form, which is the difference between a client finishing it and abandoning it at question 40. The interview protocol sets out how — one question at a time, how to voice each answer type, when to stop, and what the agent must never do.

In production this runs as a phone call: ElevenLabs rings the client and a fleet of subagents conducts the intake, one per section. See The agentic flow.

Conventions¶

Field ID: Stable snake_case identifier, unique across the whole questionnaire. Never reuse or repurpose one.
Type: How the answer is captured. See Question patterns for the full list.
Req.: Yes — the questionnaire cannot be submitted without it. No — optional. Cond. — required only when a preceding answer triggers it.
→: Conditional follow-up. → if Yes means the question only appears when the parent question was answered Yes.

Reading this site as an LLM¶

Every page here is also served as its original Markdown, at the page's own path with a .md extension: this page is at /index.md, section 1 is at /sections/01-about-you.md. (Those are deliberately not links — Zensical reads a link ending in .md as a reference to a page in the nav and warns that it does not exist.) The relative links inside those files resolve against each other, so a crawler can walk the whole site without touching the rendered HTML.

/llms.txt indexes all of them in nav order with a one-line description each, and /llms-full.txt is the entire site in one file — around 170 KB, small enough to paste whole into a model's context.

Sources¶

Sections 1, 4–6 and 8–11 were written for this site. Sections 2, 3 and 7 draw heavily on a Hebrew practitioner intake sheet (דף תשאול) supplied as the domain reference — specifically its body-systems review, its food frequency table, its per-relative family history, and its practice of asking whether a client wants to know their weight rather than demanding the number.

That sheet is a naturopathic and nutritional intake, not a training one. The parts adapted here were chosen because they improve screening and referral; the parts that only support treatment decisions a coach cannot make were left out or marked as requiring a licensed practitioner. Where a question's scope is borderline, the page says so.

Not medical or legal advice

The screening questions in section 2 are modelled on PAR-Q+ but this is not a validated reproduction of it. The symptom lists in section 3 are a referral aid, not a diagnostic instrument. The waiver language in section 11 is a placeholder. Have all three reviewed by a qualified professional in your jurisdiction before using them with real clients.