Daily workflow
Multi-day and follow-up jobs
Handle work that takes more than one visit — a job scheduled over several days, or a return visit after the first is done.
Owner: Dispatcher or operations managerJobsServicesSchedule
Walkthrough video
Multi-day and follow-up jobs walkthrough
A short product video or annotated screenshot showing this workflow from the operator's point of view.
What happens
Follow this routine when your team is doing this work for real.
- 1Book the first visit as a normal job (Jobs → New job): pick the service, a time, the crew, and the site.
- 2On that job's detail page, find the 'Needs more than one day?' card and choose Make multi-day. This creates a group and makes the job its first day — there is no separate 'create a group' step.
- 3Click Open all days to reach the group page. This is where you add and see every visit.
- 4To add another visit, use the Add-a-day panel: pick the date and time (any date — the next day, or a week out for a return trip), and optionally a different service if the follow-up is different work. The customer, site, and crew are copied from the last visit.
- 5Each visit you add is an ordinary job: open it to set its own status, tick its own checklist, and it produces its own timesheet.
- 6Choose how the group is billed on the Billing card: per day (each completed visit charged at its service price) or one fixed price for the whole engagement. View invoice shows the rolled-up bill.
- 7To make a service ALWAYS require a return visit (diagnose then repair, treat then re-treat), set a Follow-up visit window on the service itself — see the note below.
- 8For a multi-visit job you run repeatedly, build a Service package (Packages in the sidebar): name the sequence of services and their gaps once, then in Jobs → New job pick 'a package' instead of a single service to scaffold the whole group in a click. Templates come in two modes: follow-up (book the first, the rest unlock as each completes) and scheduled-together (all visits booked up front, each within a day-range after the previous).
What this uses
The records Flowdexa connects behind the scenes.
- Where the group starts
- A group is created from a job, not set up in advance. Book one job, then Make multi-day. Deleting a group only removes the grouping — every scheduled visit survives as a standalone job.
- Same or different service
- A follow-up day can keep the same service or use a different one — pick it in the Add-a-day service dropdown. The day takes that service's checklist and price, and the per-day invoice bills each visit at its own service.
- Time gaps
- The next visit's date is free — tomorrow for a continuing job, or weeks later for a return trip. Nothing forces consecutive days.
- Follow-up window (on the service)
- Set Earliest and Latest days on a service to make it require a return visit. Then booking it starts a group that waits: the next visit is locked until the first is completed, and its date is constrained to the window. The earliest is enforced; past the latest it is flagged overdue but still bookable. The window is read from each completed visit's service, so it chains through a mixed group. Leave both blank for one-off services.
- Billing
- Per-day bills each completed visit at its service price and can be sent partway through (unbooked visits are not charged). Fixed price bills the engagement once; its individual days do not invoice separately.
- Packages (reusable)
- A Service package is a named, reusable recipe for a multi-visit job — the services in order and their gaps. Booking one from New job scaffolds the group with the right services, so you do not rebuild the sequence each time. Follow-up mode books the first visit and fixes each next service; scheduled-together mode books every visit up front, each within a day-range after the previous. Deleting a package leaves already-booked groups untouched.
- Payroll
- Because every visit is a normal job, timesheet hours split into regular and overtime per day against each person's work schedule — more accurate than one long block spanning days would be.
Before you call it done
Run these checks to make sure the workflow is actually working end-to-end.
- The responsible role can complete the workflow without owner access.
- Required customer, service, schedule, resource, or payroll records are connected.
- Blocked work has a visible reason and a named next owner.
- Managers can see the status in daily operations or reports.
Next
Keep learning daily workflows
Use the workflow index when training another role or moving to the next part of daily operations.