Consent form and arrival check-in
Workflows · Workflow 6 of 6
Not synced yet
Not connected
Once Vik approves a booking, the client fills in the consent and release form on their phone: health questions, acknowledgements, a photo of their ID and a drawn signature (plus a parent or guardian's for under-18s). On the day, Vik reviews it, checks the ID against the person and checks them in. The Worker's check_in_client tool won't check anyone in until every step is done. Off until INTAKE_FORM_ENABLED and its key are set; the wording gets matched to Vik's own form (no lawyer review needed).
Step (built)DecisionForm / booking stateEmail to the clientNot built yet
Yes / No branches◷ timing
1 · The client fills in the form A private link, single use, valid until the session ends.
2 · Arrival: Review & check in Dashboard only: Today page → the booking's "Review & check in".
Who sees what Privacy
Answers, the typed name and the note are AES-256-GCM encrypted; signatures and ID photos sit encrypted in private storage. The full form and the ID photos open only on the dashboard, and every opening is logged. The assistant gets the form status and health flags yes/no, never the answers or which flags.
Records Kept
Kept forever by default (Vik's choice). If he sets a retention period, the daily cron deletes signed forms and ID photos that many days after the session. The print view is the export.
Not built yet Later
Google Drive backup of the records (needs his Google login) and a generated PDF.
Wide diagram: scroll sideways, or pinch to zoom on a phone.