Per-service checklists are how you encode your shop's standards into the tech workflow. Every visit for that service surfaces the checklist on the tech screen; completing the visit requires filling it in.
Creating a checklist
- Go to Services → click a service → "Edit checklist."
- For each item, set: label, kind, required, optional conditional.
- Save. The next visit for this service will show the checklist.
Field kinds
- bool — Yes / No radio. "Gate was unlocked on arrival."
- number — Integer or decimal input. "Mow height (inches)."
- text — Free text. "Notes on unusual growth."
- select — Single-choice dropdown. "Soil condition: [dry / wet / saturated]."
- photo — Triggers the photo-capture flow tied to a specific label. "Before photo of front yard."
Required vs optional
Required items must be filled before the tech can tap Complete. Optional items show but can be left blank. Use required for things that affect billing (chemistry readings, area measured) or liability (weather observation, photos for required-photo services).
Conditional fields
Any item can be configured to show only when a parent item has a specific value. Example: a "weeds present" boolean; a conditional "type of weed" text field that only shows if weeds=yes.
Where the data goes
Every answer is written to visit_field_values tied to the visit. On the client detail page, the answer appears on that visit's card. In reports, you can aggregate: "average mow height over 90 days for this client."
Seeded defaults
Every new Servicio tenant gets sample checklists for common services (pool weekly maintenance has chemistry readings + equipment inspection; lawn weekly has before/after photos + soil condition). You can edit or delete the seeded ones — they are starting points.