Skip to main content

What can dispatch timestamps tell me that the schedule board cannot?

ServiceTitan Published October 15, 2026
Short Answer

The board shows intent; the timestamps show what happened. Comparing scheduled window, dispatch time, arrival time and completion time reveals where the day actually goes: late starts, long drives, jobs that consistently overrun their allotted time, and technicians whose on-site duration for the same job type differs sharply. Those gaps are where capacity is lost, and none of them are visible on the board.

Four timestamps, three intervals, three different problems

Every appointment produces a chain: scheduled window, dispatched, arrived, completed. The intervals between them each measure something distinct.

Dispatch to arrival is travel and readiness. Arrival to completion is on-site work. Completion to next dispatch is the slack in the day, and it is usually the biggest and least examined number in the whole chain. Most companies can name their average ticket precisely and have no idea what their average gap between jobs is, even though the second number sets a hard ceiling on how many jobs a day can hold.

What each interval tells you

  • Window versus arrival. Your real on-time rate, as the customer experiences it. This is a marketing asset when it is good and a review problem when it is not.
  • Dispatch to arrival by time of day. Rising mid-afternoon travel time is a routing and geography problem, not a technician problem.
  • On-site duration variance within a job type. High variance between technicians on identical work is either a training gap or a coding gap, and separating those requires looking at what was actually sold on the long visits.
  • Gap time between jobs. The difference between capacity you paid for and capacity you used.

The trap in on-site duration

A technician with long on-site times is not automatically slow. Long visits often correlate with higher tickets because the technician is inspecting, explaining and selling. Judging duration without revenue attached produces exactly the wrong coaching.

Plot on-site duration against revenue per visit for the same job type and the picture separates into useful quadrants: fast and productive, slow and productive, fast and unproductive, slow and unproductive. Only one of those four needs an efficiency conversation.

Timestamps only work if they are honest

The whole analysis depends on technicians actually pressing the status buttons at the right moments. In many shops arrival is tapped from the driveway and completion is tapped in bulk at the end of the day. Before drawing conclusions, check the distribution of completion times: heavy clustering in one late hour means the data records paperwork, not work.

Fixing that is a habit problem with a small technical assist, and it is worth doing because dispatch data underpins nearly every capacity decision. We treat it as a prerequisite when connecting scheduling data into operational AI workflows, and it feeds the capacity lines in daily briefs.

Topics: dispatch · capacity · timestamps · operations

Have a version of this question about your own business?

The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.

Related Answers

People who read this also asked

Browse the Answer Hub →

AI is easy to access. Making it useful is hard.

Bluefrog makes AI useful by integrating it with the way your business actually works — your software, your calls, your customers, your marketing and your revenue.

Technology development since 1997 · AI integration platforms since 2001