Check-in types
Configure visit types, attach forms, and set required evidence rules.
Audience: Admin
Check-in types (visit types / activity types) classify what field users do on mobile. Each type defines which forms appear, whether GPS or photos are mandatory, and how visits show up in Visit control.
What a visit type controls
| Area | Examples |
|---|---|
| Label & icon | "Delivery", "Audit", "Maintenance" shown on mobile |
| Forms | Zero, one, or many forms attached; order and required flags |
| Place rules | Must select registered place vs. free location |
| GPS | Require coordinates at start/end |
| Photos / comments | Minimum evidence before closing visit |
| Notifications | Alerts on visit complete |
| Tracking profile | Link to GPS schedule (if module enabled) |
Attach forms to a visit type
Two equivalent paths—use whichever you prefer:
- Visit type settings → Forms → pick published forms, mark required, set order.
- Form settings → Linked visit types → enable for this type.
Both must agree. A form linked only on the form side but not enabled on the visit type may not appear on mobile.
Required vs. optional
| Flag | Behavior |
|---|---|
| Required form | Visit cannot finish until submission is valid |
| Optional form | User may skip unless supervisor policy says otherwise |
Stacking many required forms slows capture—see Common mistakes.
Relationship to places
Some types require a registered place (customer site from Places module). Others allow ad-hoc GPS for patrol or emergency jobs. Mismatch causes mobile users to get stuck at place picker—validate with one test route.
Duplicate types
Avoid near-duplicate names ("Inspection" vs. "Inspection 2"). Duplicates split reporting and confuse Workflows filters. Consolidate to one type per real activity.
Workflows and automation
Visit type is a common Workflow filter alongside form_submitted. Example: only "Complaint" visits create escalation tasks. See Automations on form submit.
Tips
- Name types the way field staff speak, not internal ERP codes (codes can live in place metadata).
- Document which types are customer-facing (trigger client notifications).
- When changing required forms, communicate before mobile sync—not mid-shift if avoidable.
- Retire unused types by disabling before delete to preserve historical visit labels.