Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

Staff and crew assignments change without telling anyone

Assignment changes miss people because the notices documented in common scheduling and field software mostly go to the person added, and everyone else is assumed to find out. ServiceTitan's answer to notifying a technician who was unassigned is an alert someone has to build in Settings, and Fieldwire sends no notice when tasks are reassigned in a batch. Make the person who moves a worker responsible for telling the worker, both supervisors and payroll, in one message.

Two coffee cups, a phone and a notebook on a table by a morning window

How it actually happens

A move has one person who decides it and four who need to know: the worker, the supervisor losing them, the supervisor getting them, and whoever keys time. The move usually reaches one of the four.

It starts with a short crew. A superintendent on a rush job calls another superintendent on Tuesday evening and borrows an apprentice for two days. They agree on the phone. The apprentice gets a text and drives to the new site Wednesday morning. The board in the office still shows him on the original job, because neither superintendent touched it. A warehouse lead pulling pickers onto a busy client's orders, or a restaurant manager covering a call-out from another location, makes the same trade the same way.

Service businesses move people on the board itself, which looks safer and often is not. A dispatcher drags a call from one tech to another as the morning runs long. The software tells the tech who got the call. Whether it tells the one who lost it depends on settings. In ServiceTitan, notifying an unassigned technician is an alert someone has to build in Settings. Housecall Pro's help describes a push to the employee assigned and an updated text to the customer, and no notice to the employee removed. P3 is the exception that proves the point: its default texts the tech when a call is removed from his day.

Bulk changes are the quietest. At four in the afternoon a scheduler reshuffles tomorrow for three crews at once. Fieldwire sends nothing for batch reassignments. Jobber's reschedule prompt goes to the client, for visits moved one at a time. A technician on r/HVAC put the result plainly in 2024: if you change my board last minute, text or call, so I do not drive to the wrong site.

The supervisor on the original job finds out at seven when the helper does not show. He calls the office. The office looks at the board, which is wrong, and cannot say where the apprentice went.

Then the paperwork follows the old plan. The apprentice's hours go to the original job because that is what the board said. In ServiceTitan, a past timesheet edited later does not re-sync job costing until payroll for that period is updated again. On Davis-Bacon work the certified payroll lists him on the wrong contract. In a warehouse that bills labor by client, the hours land on the wrong invoice. Nobody notices until the cost report looks off two weeks later, and by then nobody remembers the phone call.

Removals need their own notice

When you test your system, test the removal, not the addition. Assign a test worker to a job or shift, then take them off, then move a batch of work to another day, and see who gets told each time. If your setup matches the help pages above, the person added hears quickly and everyone else hears late, sometimes from the customer.

Signs you have this problem

  • A supervisor waits for someone who was moved to another job, site or shift the night before
  • Two supervisors each think the same person is theirs today
  • Someone drives to a site or shows up for a shift that was taken off their schedule
  • Hours land on the old job, client or location because the timecard follows the original assignment
  • The whiteboard, the scheduling system and the group text each show a different lineup

What usually causes it

  • Supervisors trade people by phone, and the change never reaches the shared scheduleThe handoff gap
  • The schedule lives in several places, so updating one leaves the others wrong, and timecards are keyed from the stale oneThe re-entry trap
  • No one can see a list of today's changes, so no one knows what to double-checkThe invisible queue
  • The software notifies the person added, while the person removed and the supervisor left short hear nothingThe field-to-office split

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Do people get moved by phone or text between supervisors without anyone touching the schedule?If yes: the schedule is not the truth. Make a move official only once it is on the schedule.
  2. Does your software notify the person who was removed, not only the one added?If yes: check the supervisors and payroll next. If no, turn on the unassign notice or make the mover send it.
  3. Are moves often made in bulk at the end of the day?If yes: bulk moves are the quiet ones. Jobber and Fieldwire both document sending less for bulk changes than for single ones.
  4. Do cost reports show hours on jobs, clients or locations the person had left?If yes: timecards follow the old assignment. Reconcile timecards to the final schedule before payroll.

How it breaks in each industry

Residential HVAC and plumbing service
Moves happen on the dispatch board all day as calls run long. A technician on r/HVAC in 2024 asked dispatchers to at least text or call when they reshuffled his board last minute, so he would not drive to the wrong site. Another described a 6:30 a.m. call telling him to refresh the app and head to a job an hour from home, when his first call had been set for 10.
Electrical and mechanical construction crews
Superintendents borrow people between jobs by phone. Crew time is often entered later from a crew sheet: in Trimble Vista, hours go into a crew timesheet, are locked, approved and sent to a payroll batch, so a move nobody recorded lands on the original job.
General contractors and their subs on Fieldwire or Procore
Task reassignments and schedule updates drive who shows up. Fieldwire sends no notification for batch reassignments or for start, end or manpower changes made in a task's attributes, and Procore emails schedule changes only to users whose Directory record has that box checked.
Logistics and third-party warehousing
A shift lead moves pickers from one client's account to another when volume spikes. The move is made on the floor, while labor is billed to clients from the hours recorded against each account, so a move nobody logs puts the hours on the wrong client's bill.
Restaurants and hospitality
Shifts get swapped between staff and moved between locations by text. The posted schedule keeps the old names, the manager on duty plans the floor around someone who is not coming, and the hours post to the location on the schedule rather than the one worked.

Where it breaks between systems

ServiceTitan unassignment alerts
ServiceTitan's help answer to getting technicians notified when they are unassigned is to add a Technician Unassigned alert under Settings, Integrations, Alerts, with Job Related Technicians checked. A companion Technician Assigned alert covers assignment and reassignment. Both are alerts someone has to set up.[1]
ServiceTitan dispatch board notifications
The Dispatch Board's notification dropdown shows only actions a technician triggered; office-triggered dispatches appear in Dispatch Messaging as SMS instead. Dispatch notifications are available only on the Daily Board.[3]
ServiceTitan text messages
A properly configured default outbound SMS number is a prerequisite for any text notification. Without it, ServiceTitan says, all SMS notifications silently fail, so a shop can believe techs are being told when nothing is sent.[4]
ServiceTitan timesheets and job costing
Editing a past timesheet does not re-sync payroll data, so job costing keeps showing the pre-edit numbers until payroll for that technician and period is updated again. The article covers the legacy job costing model.[5]
Jobber push and reminders
Schedule-change pushes cover the current workday, fire one minute after the last edit, are sent only when someone else made the change, and can be turned off by non-admin users.[6]
Jobber rescheduling
Rescheduling a visit prompts a notification to the client, not the team, and the prompt appears only for visits moved one at a time, not on bulk reassignments.[7]
Housecall Pro employee and customer notices
Employees get a push when a job is assigned and scheduled to them, plus a reminder an hour before, if their phone allows notifications. The help pages do not describe a notice to the employee taken off the job.[9]
FieldEdge assignment push
Technicians get push notifications for assignment changes affecting their day, and for upcoming weekend assignments, once an office admin enables it. The setting sends notices for assignments occurring within a number of hours the admin enters.[11]
ServiceM8 mobile
ServiceM8 pushes a notice when a job is scheduled to a staff member, or a booking changes, for later that same day, or when a job is allocated to them. A change to a booking on a future day is outside that description.[12]
simPRO mobile
simPRO's mobile push appears only for changes made on the current day. Nothing arrives while the phone is offline, and on reconnect only the most recent push shows, so a tech who was out of signal can miss an earlier change.[13]
P3 schedule change texts
P3's default, Immediately, texts a technician when a call is added to or removed from his current-day calendar or its start time changes. A setting added in 2024 lets shops switch to Manually, sending one mass text after bulk changes, or Never.[14]
Procore schedule notifications
Schedule-change emails go only to users with Upon Schedule Changes checked on their project Directory record. The weekly email does not send on its own when there are no open tasks for the period.[15]
Procore schedule change requests (2022 help)
Procore's 2022 help for its Schedule tool said that approving a schedule change request does not update the schedule. The change had to be made in the integrated scheduling software and the new schedule uploaded before the team could see it.[16]
Fieldwire task notifications
Changing the assignee of a single task sends a notification. Batch reassignments do not, nor do start date, end date or manpower edits made in the task attributes; the same edits made through a task message do notify. Watcher emails go out five minutes after an update, at most one per hour, and never to the person who made the edit.[17]

By the numbers

FigureWhat it measures
5.5, 4.7 and 3.9 hours[19]Hours a week construction professionals said they spent looking for project data and information, resolving conflicts, and dealing with mistakes and rework (PlanGrid and FMI, Construction Disconnected, 2018; 599 leaders, 500 in the US, mostly general contractors; sponsored by a software vendor).
48% and 26%[19]Share of US rework respondents attributed to miscommunication and poor project data together, and to poor communication between team members alone, in the same 2018 PlanGrid and FMI report. Respondent attributions applied to a modeled rework total.
58% and 56%[20]Contractors in FMI's 2023 labor productivity survey (259 respondents) who named poor planning and communication by field management, and by project management, as challenges to productivity. Shares of respondents naming each, not measured losses.
15% and 8.5%[21]Share of project activities performed out of sequence, and the average labor productivity drop associated with a 5% rise in out-of-sequence work, across 42 projects and 88 experts (Construction Industry Institute RT-334, December 2018). CII lists poor communication between project parties among its top ten causes. Mostly large industrial and owner projects.
45%[22]Respondents to the AGC and NCCER 2025 Workforce Survey (1,342 individuals, July and August 2025) who reported project delays from shortages of their own or subcontractors' workers. Short crews are why people get moved between jobs in the first place.

Rules that apply

40 CFR 82.161(a)(1) and (a)(2), refrigerant work[23]
Technicians who could open the refrigerant circuit must hold Type I, II, III or Universal certification for the equipment, and an apprentice is exempt only while closely and continually supervised by a certified technician. A swap that pulls the certified tech changes whether the work is legal.
29 CFR 1926.20(b)(4), qualified operators[24]
On construction work the employer may let only employees qualified by training or experience operate equipment and machinery. If the qualified operator is moved, someone has to check who now runs the machine. The standard does not require a notification method.
29 CFR 5.5(a)(3)(i)(B) and (a)(3)(ii)(B), Davis-Bacon records[25]
On covered federal work, payroll records must show each worker's classification of work actually performed and daily and weekly hours on each covered contract, and certified payrolls must set that information out completely. Hours booked to the job a worker was moved off are wrong on that record.
29 CFR 3.4(a), certified payroll timing[26]
Weekly certified payroll statements are due within 7 days after the regular payment date of the payroll period. A crew sheet nobody corrected goes out wrong on that schedule.

Measure it in your own shop

From: Your schedule or dispatch history for two weeks, the group texts and call notes where moves were arranged, and the timecards for the same days.

  1. List every assignment change in the period: who moved, from which job, shift or site, to which, and when the change was made.
  2. For each, find out when the worker, the losing supervisor, the gaining supervisor and payroll each heard. Mark any who heard only on arrival or not at all.
  3. Count changes that produced a wasted trip, a short-staffed shift or idle time.
  4. Compare timecards with the final schedule and count hours booked to the wrong job, client or location.

Reading it: The share of moves where someone heard late shows which of the four people your process leaves out. Wasted trips, short shifts and idle time are the operating cost. Hours on the wrong code are the office cost, and they surface weeks later as a cost report nobody trusts.

What does not fix it

Letting only one person change assignments
It stops the phone trades for a while, then turns that person into the bottleneck, and supervisors go back to trading people directly.
A company group text
It reaches everyone fast, but it mixes old and new plans, cannot be searched by job, and never updates the timecard or the cost code.
Assuming the software notifies everyone
The help pages mostly describe notices to the person added. Removals, bulk moves and changes for a future day are where the documented notices thin out or need a setting turned on.

What to try this week

  1. Log every move for two weeksAsk everyone who moves people to note each change: who moved, from which job, shift or site to which, starting when, and who was told. Count the changes the worker, the supervisor or payroll heard about late or not at all.
  2. Name one schedule as the truthPick the single place that shows who is working where today and tomorrow. A move does not count until it is on that schedule, whoever made it.
  3. Turn on the notices your software already hasCheck what your system sends when someone is removed, not just added. In ServiceTitan that means building Technician Assigned and Technician Unassigned alerts; in FieldEdge an admin has to switch assignment push notifications on; in Procore each user's Upon Schedule Changes box has to be checked.
  4. Send one message to four peopleWhoever makes the move tells the worker, the supervisor losing them, the supervisor gaining them, and whoever keys time. A short template keeps it under a minute: who, from, to, starting when, replacing whom.
  5. Reconcile timecards to the schedule each afternoonAt a set time, compare today's timecards to today's final schedule, not this morning's. Fix the job, client or location codes before payroll, because a past timesheet edited later may not flow through to costing on its own.

Where do-it-yourself stops

These steps make changes visible and catch the timecard errors before payroll. They still depend on a busy supervisor remembering to send the message and update the schedule every time, and the software still tells the added worker more than it tells anyone else. The lasting fix is a staffing board built around your own schedule, timecards and work records, so moving a person notifies everyone affected and carries the right code to payroll. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why do crew changes never reach the crew?

Because the change is made between two people, by phone or on the board, and the software notices described in vendor help pages mostly go to the person newly assigned. The removed worker, the foreman left short and whoever keys time are often not told at all.

Does ServiceTitan tell a technician when he is unassigned from a job?

Only if someone sets it up. ServiceTitan's help says to add a Technician Unassigned alert in Settings, Integrations, Alerts, and check Job Related Technicians so it goes to the technicians on that job.

Does Jobber notify my team when a visit moves to another day?

Jobber's push for schedule changes covers the current workday, and its reschedule prompt is a message to the client. Team reminders are emails set per visit, from at the start of the task up to 24 hours before.

What should a crew change message include?

Who is moving, from which job to which job, starting when, and who replaces them. Send it to the worker, both foremen and whoever enters time, in one message.

How much does poor communication cost on site?

No source measures the cost of a missed crew change. The closest figures are broader: in the 2018 PlanGrid and FMI survey, respondents attributed 26% of US rework to poor communication between team members, and CII lists poor communication among its top causes of out-of-sequence work.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.