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

Problem guide

The schedule falls apart by mid-morning

The schedule falls apart by mid-morning because it was built on durations nobody checked, and the first overrun has nowhere to go. One long job, visit or appointment pushes everything behind it, and the office schedule, the worker's phone and the customer's window each hold a different version of the day. In ServiceTitan's capacity planning, for example, a job type with no duration set is simply counted as two hours. Set durations from your own history and keep room for the work that runs long.

A dispatcher's desk with a headset and a pinned wall map

How it actually happens

At seven the schedule looks clean. Each technician has five or six jobs, each booked at the length the job type always gets, each with a customer window that was promised days ago. The trouble is in the lengths. Some were set years ago, some were never set, and some are the system's default. Nobody has compared them to how long the work really takes. A clinic's template, a warehouse's dock plan and a property manager's maintenance board are built the same way.

The first technician arrives at a maintenance call and finds a failed part. The second finds a multi-system house booked as a single unit. Someone writing from the dispatch side on Reddit's r/HVAC described one tech blowing up an entire day because converting and hooking up a residential stove took six hours. By nine thirty the dispatcher knows the first two jobs will run long, and every job behind them on those two schedules is now late.

Then the reshuffle. The dispatcher drags jobs to other people, pushes some to the afternoon and some to tomorrow. Each move is made in the office system. Whether the change reaches the field depends on settings most companies never looked at: is push turned on, is the phone in signal, does the worker read the app or a calendar that syncs twice a day. One HVAC tech on Reddit said his first call was not until ten, and the office was blowing up his phone at six thirty asking him to refresh the app and get to a call an hour away by eight.

While the schedule changes, the promises do not. The customer windows set at booking stay where they were. A capacity number that ignored the morning meeting and double-counted two overlapping jobs told the call center there was room for one more, so a new same-day request is now on the schedule as well.

By eleven the scheduler has stopped planning and is only reacting. Each new urgent request pushes two planned ones. The customers whose appointments moved start calling, and every call takes the scheduler away from the schedule for a few minutes. The day that looked clean at seven is now being run from memory and a phone.

Project work breaks the same way on a slower clock. The look-ahead says the crew starts the third floor, but the material is not there, or the drywall crew is still in the way. The foreman reassigns people on the spot. In Procore, nothing changed in the lookahead writes back to the master schedule, so the plan the project manager reports from still shows the third floor starting today.

The pattern under the chaos

Most broken mornings break at the same hour, on the same types of work. That is good news. A schedule that fails randomly is hard to fix, and one that fails on maintenance calls in multi-system homes, or new-patient visits, every Tuesday is a booking rule waiting to be written.

Signs you have this problem

  • By ten o'clock the scheduler is redoing the afternoon
  • People call in to ask where they are going next because the app does not match what the office said
  • The same few job or appointment types run long every time and get booked at the same short length anyway
  • Every urgent request pushes two or three planned ones to tomorrow
  • Teams on project work stand around waiting on material, access or another group

What usually causes it

  • Booked lengths are guesses or system defaults, so the day is overbooked before the first appointment startsThe exception swamp
  • The office reshuffles the schedule, and the change reaches the worker's phone, the calendar and the customer at different timesThe field-to-office split
  • Look-ahead planning on project work is done in a separate place from the master schedule, so the team plan and the project plan drift apartThe handoff gap

Find your cause

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

  1. Are your booked lengths defaults, or the same number for every job or appointment type?If yes: the day is overbooked before it starts. Set durations from your history first.
  2. Is every person booked solid from start to finish?If yes: the first overrun has nowhere to land. Add a gap to each day.
  3. Do people learn about schedule changes by a phone call rather than from the app?If yes: the change path is broken. Check push settings, calendar syncs and whether each person's role can see the full day.
  4. On project work, is the look-ahead kept separate from the master schedule?If yes: the team plan and the project plan are drifting. Feed look-ahead changes back weekly.

How it breaks in each industry

Residential HVAC service
Maintenance visits are booked as short, identical slots. A multi-system home booked as one unit, or a no-cool call that turns into a compressor job, takes the whole morning, and the next four customers inherit the delay.
Commercial construction crews
The crew shows up to a planned task and finds the area not ready, the material not delivered, or another trade in the way. The foreman reassigns people on the spot, and the master schedule does not learn about it.
Healthcare practices and clinics
Appointment types are booked at fixed lengths, and a new patient, a late arrival or a visit that needs a procedure runs long. Every patient behind it waits, staff skip breaks to catch up, and the same-day slots the front desk promised by phone are gone by ten.
Logistics and third-party warehousing
Dock appointments and delivery routes are planned for the day, and one late inbound truck or a slow unload holds the door. Every appointment behind it slides, drivers wait, and the yard plan on the screen no longer matches the trucks in the lot.

Where it breaks between systems

ServiceTitan Adaptive Capacity
If a job type has no duration, capacity planning counts it as two hours. Non-job events such as meetings or training only consume capacity when the right box is ticked, and two overlapping jobs double-count the overlap. The available-hours number the office books against can be wrong in either direction.[1]
ServiceTitan Dispatch Board and the customer's window
Moving a job by drag and drop on the board updates its start time and leaves the arrival window untouched. Rescheduling from the Job screen resets the tech's status to Scheduled, while a drag keeps it as it was, so two ways of making the same change leave different traces.[3]
ServiceTitan office and mobile
When a tech's phone is out of signal, the office can see Dispatched while the phone shows Working, until the device reconnects. The board the dispatcher uses to rebuild the day can be behind the field by the length of a crawlspace job.[5]
ServiceTitan alerts and accounting
The Running Over alert fires when a job is not marked complete before its scheduled end, and when it fires, the documented fix is to call the next customer or shift the tech's remaining jobs. A day whose appointments are done but whose job is never completed keeps its invoice off the Accounting screen.[6]
ServiceTitan booking and drive time
Until an April 2026 release, customer service reps using Get Adaptive Availability could not see a slot's drive time or which tech was free, so dispatchers reworked routes later. The new preference that shows both is off by default, so shops that never turned it on still book without drive time.[7]
Jobber and Google Calendar
The calendar sync is one way, from Jobber out, and not real time. Jobber says Google Calendar is updated roughly every 12 hours and Google offers no manual refresh, so a tech who works from Google Calendar can be looking at yesterday's plan.[8]
Housecall Pro and Google Calendar
The Google Calendar integration is one way and needs web access, so it is not available to employees in the Field Tech role at all. Changing a time in Google does not change the job.[9]
FieldEdge and ServiceM8 mobile updates
FieldEdge pushes assignment changes to technicians only after an office admin enables push notifications in Global Settings. ServiceM8 relies on push notifications to tell the app to sync, and says jobs take much longer to reach a phone with notifications or background refresh turned off.[10]
Procore lookahead and master schedule
A lookahead reads its tasks from the master schedule, but nothing done in the lookahead edits the master. Subtasks added or removed by the field never reach the schedule the project manager reports from.[12]

By the numbers

FigureWhat it measures
83% vs 15%[13]Contractors reporting emergency resource needs several times a week: 83% of those doing minimal look-ahead planning, against 15% of those planning three weeks or more ahead (FMI 2023 labor productivity study, 259 respondents, self-reported, consultant).
76%[14]Respondents in the same FMI study naming a schedule that was not updated, realistic or coordinated as a top outside factor hurting productivity, second only to poor design documents at 80% (FMI presentation slides).
$30 billion to $40 billion[13]FMI's estimate of what US labor-intensive contractors lose annually to poor labor productivity.
About 32%[15]Share of time on an active construction site that FMI's time studies classify as recoverable lost time: waiting for material, tools, information or access, rework, and unplanned delays (FMI, April 2025, no sample size published).
2.5%[16]Construction firms reporting that projects consistently finish on time and on budget, from 243 executives and 84 project managers (FMI 2025 Project Management Study, Part 1, consultant).
40% and 18.3%[17]Share of jobs that ran over their budgeted labor hours, and share that ran past 150% of budget, across 315,393 jobs from 1,391 companies (Level, May 2025, vendor client data, unaudited).
Nearly half[18]Technicians in a 2025 Salesforce survey of 350 US technicians and tradespeople estimated that 47% of their appointments do not go to schedule (vendor survey, self-estimates).

Rules that apply

AIA A201-2017, Section 3.10.1 and 3.10.3[19]
Under the unmodified A201, the contractor submits a construction schedule promptly after award, revises it at appropriate intervals as the work requires, and performs the work in general accordance with the most recent schedules submitted. A master schedule that never hears about field changes stops being the most recent schedule in practice.
29 CFR 5.5(a)(3)(ii)(A), certified payroll[20]
On Davis-Bacon covered work, the contractor or subcontractor submits certified payrolls weekly. When the morning reshuffle moves a worker between covered and uncovered jobs, the payroll has to show where the hours really went.

Measure it in your own shop

From: Completed jobs with scheduled start, scheduled end, actual arrival and actual completion from your field system, plus reschedule history. In ServiceTitan, the job's Audit Trail shows time and technician changes; Running Over alerts mark the overruns.

  1. Export six weeks of completed jobs with scheduled and actual times, and tag each by job type.
  2. For each job type, compute the median actual time on site and the share of jobs that ran past their booked length.
  3. Count how many jobs were moved on the same day they were scheduled, and note the hour of the first move each day.
  4. Find the job type that most often is the first overrun of the day.

Reading it: The hour of the first move is when your day breaks. The job type that most often overruns first is where to start: fix its booked length, or move it to a slot with room behind it.

What does not fix it

Routing software
Better routes save drive time between jobs. They do nothing about a job booked at one hour that takes three, which is what breaks most mornings.
Telling techs to work faster
Overruns come from the work, not the pace. A compressor replacement booked as a maintenance visit is a booking problem, and pushing the tech to rush it buys a callback.
Adding more jobs to cover cancellations
Overbooking to protect against no-shows makes the full days worse, and full days are the ones that already fall apart.

What to try this week

  1. Measure real durations by typePull the last three months of completed jobs, visits or appointments and compare the scheduled length with the actual time for each type. Change the booked length to the median you actually see, not the one you hope for.
  2. Leave a gap in each person's dayStop booking every person solid. Hold back time in the early afternoon for the work that runs long or the urgent request that always comes. Decide how much from your own history.
  3. Book the hard work firstPut long or unpredictable work, installs, complex visits, new patients, old buildings, at the start of the day when there is room behind it. Put short, predictable work where an overrun matters least.
  4. Make one rule for every changeWhen the office moves an appointment, it moves it in the system, the person doing the work gets a push or a call, and the customer is told. Do the three together so no version of the day goes stale.
  5. Plan project teams three weeks outOn construction and other project work, hold a short weekly look-ahead covering at least three weeks, checked against material deliveries and other trades, and feed what changes back into the master schedule.

Where do-it-yourself stops

These steps make the morning sturdier, but the scheduler is still deciding by hand which three appointments to move when the first one runs long, and telling three different places about it. The lasting fix is a tool built on top of your scheduling system that learns your real durations, spots the overrun early, and pushes one change to the schedule, the worker and the customer together. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why does our schedule always break around ten?

Because that is when the first long job of the day becomes obvious. If every slot was booked at a default length and nothing was left open, every job after the first overrun moves, and the dispatcher spends the rest of the morning rebuilding the board.

How long should we book each job type?

Use your own history. Take the median actual time on site for each job type over the last few months. In Level's vendor data across more than 315,000 jobs, 40% ran over their budgeted hours, so the hopeful number is usually short.

How much of the day should we leave open?

There is no published benchmark for trade contractors. Look at how many same-day and emergency calls you took over the last two months, and hold back about that much time, placed where it can absorb an overrun.

Do look-ahead schedules really make a difference?

In FMI's 2023 study, 83% of contractors doing minimal look-ahead planning reported emergency resource needs several times a week, against 15% of those planning three weeks or more ahead. It is self-reported and a correlation, but the gap is large.

Why is the tech's app different from the dispatch board?

Often because the phone is offline, push notifications are off, or the tech works from a calendar sync that is not real time. ServiceTitan's help names out-of-range phones as the usual cause of office and mobile showing different statuses.

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.