Use this guide to understand the differences between Multi-Day, Ongoing, Callback Split, Copy, and Repeats jobs.
Quick comparison
Type | Best used for | Jobs linked together? | Shared fields? | Job numbers |
Multi-Day | Work scheduled across consecutive days | Yes | Mostly shared | Same job number across all visits |
Ongoing | Return visits that are not necessarily planned as consecutive days | Yes | Mostly shared, with more flexibility per visit | Same job number across all visits |
Callback Split | Follow-up visits that should remain separate | Yes, but fields are not shared | No | Different job numbers |
Copy | Creating a new job based on an existing one | No | No | New job number |
Repeats | Recurring work on a set frequency, such as daily, weekly, or monthly | Yes | Some fields can be updated per visit or for all following visits | Different job numbers |
1. Multi-Day Jobs
Use case
Use Multi-Day when you need to set up work that runs over consecutive days.
How to create
On the job, enable the Multi-Day Job checkbox, then set:
Multi-Day Start Date
Days or Multi-Day End Date
Scheduler behavior
Most fields are shared across the entire series.
Shared behavior
Changes to these fields generally update all jobs in the series:
Job Notes
Job Types
Items > Inventory
Multi-Day Start and End Date
Important exception
These can be unique per visit:
Technician
Units
Unscheduled flag
Notes
Dragging and dropping one visit in the scheduler moves the entire series
Updating the nth job in the series can still update all jobs
Updating the visit date manually on the job may cause confusing results in the calendar
It is better to adjust the Multi-Day Start Date / End Date instead of manually changing visit dates
Timesheet associations may remain tied to the original visit date even after moving visits
Mobile behavior
When technicians update job fields in mobile, the changes may update all jobs in the series.
Tested fields:
Tech Notes
Hours
Products
Job numbers
All visits share the same job number.
Example:
1st visit: 42
2nd visit: 42
3rd visit: 42
Asset tests
Asset Test status and progress are shared across all jobs in a Multi-Day series.
SWMS
You can assign SWMS to the primary job, and it will apply to each visit.
Technicians must sign the SWMS each day
This creates 1 signed SWMS per day
Job status
If Ongoing jobs have individual statuses is enabled in:
Misc > Scheduling
then each visit can have its own status.
If that setting is off, changing the status may update the whole series.
Note: A Multi-Day setup that later has Ongoing added may be treated as one job.
2. Ongoing Jobs
Use case
Use Ongoing when a technician may need to return to site again, often unexpectedly.
This is usually better than Multi-Day if you want more flexibility, because each visit can be managed more independently.
How to create
On the job, click:
Add Ongoing
Scheduler behavior
Most job information is shared, but ongoing visits are more flexible than Multi-Day.
Key behaviors
You can update the date/time for an individual job card without affecting the others
Moving one visit to another scheduler only moves that job
Technician and Unit assignments can be saved per visit
Job numbers
All visits share the same job number.
Example:
1st visit: 42
2nd visit: 42
3rd visit: 42
Asset tests
Asset Test status and progress are shared across all jobs in an Ongoing series.
If you need to share an incomplete Asset Test, use Ongoing instead of Callback Split.
Job status
Controlled in:
Misc > Scheduling
Relevant settings:
Enable ongoing jobs — allows the Add Ongoing option
Ongoing jobs have individual statuses — allows each visit to have its own status
Mobile behavior
Not fully tested yet, but it may behave the same as the Scheduler.
3. Callback Split
Use case
Use Callback Split when you need to return to a site, but the follow-up visit should remain separate from the original in terms of fields and progress.
How to create
On the job, click:
Callback (Split)
Scheduler behavior
Fields are not shared
Each visit is treated independently
Job numbers
Each job in the series gets a different job number.
Example:
Original job: 42
2nd job: s42-1
3rd job: s42-2
4th job: s42-3
Asset tests
Asset Test status and progress are not shared across Callback Split jobs.
Mobile behavior
Fields are not shared
4. Copy
Use case
Use Copy when you want to create a new job based on an existing one, but with no relationship between the two jobs.
How to create
On the job, click:
Copy
Behavior
Jobs are not related
Fields are not shared
Asset Tests are new
The copied job gets a new job number
5. Repeats
Use case
Use Repeats when you need to create recurring jobs on a schedule, such as:
Daily
Weekly
Monthly
You can also specify:
Repeat interval, such as every 2 days or every 2 weeks
End date, or set it to never end
How to create
On the job:
Select a value from the Repeats dropdown
Choose the repeat type
Set the repeat variation
Choose whether the series ends never or on a specific date
Scheduler behavior
When updating fields, the system prompts:
Only this job
All Following
This is similar to Multi-Day behavior.
Drag and drop behavior
Only this job: updates just the selected visit
All Following: updates the selected visit and moves all following visits
Mobile behavior
Still being confirmed.
22 Jan 2026 note: when updating Tech Notes in mobile, the note only saves for that visit.
Job numbers
Each visit has a different job number.
Example:
1st job: 42
2nd job: 42-2
3rd job: 42-3
4th job: 42-4
Asset tests
Asset Test status and progress are not shared across repeated jobs.
Field sharing summary
Field / Area | Multi-Day | Ongoing | Callback Split | Copy | Repeats |
Technician Assigned | Unique per visit | Unique per visit | Unique per visit | New job | Can vary by visit |
Asset Assigned | Shared | Shared | Not shared | New job | Varies |
Job Status | Can be individual depending on settings | Can be individual depending on settings | Not shared | Not shared | Per visit / all following |
Asset Tests | Shared | Shared | Not shared | New | Not shared |
Job Number | Same | Same | Different | New | Different |
Important notes for support teams
Why “All Following” may not update all visits
In a Multi-Day job series, most fields are shared across the series except:
Technicians
Units
Because of this, changing many fields on one visit will update the whole series regardless of whether the user selects:
Only this job
All Following
That prompt is mainly relevant for Technicians and Units.
If the account is also configured for individual status per visit, then status changes may still apply only to the selected visit, which can make the prompt feel inconsistent.
Recommended workaround
If the goal is to update the status for all visits, use a bulk status change from the All Visits tab.