When a tree removal runs long: audit the customer update handoff

The late job is the test, not the root cause

A removal was meant to wrap at 11:30. At noon, the climbing crew is still tied up. The chip truck is waiting on a disposal run, the next crew order no longer makes sense, and dispatch is moving blocks around while a CSR answers, “Are they still coming today?”

Nobody caused that moment by being careless. Tree work moves when access is worse than expected, equipment changes the pace, or conditions are not safe to work in. OSHA, for example, says line-clearance tree workers must not work in hazardous weather such as high winds, icing, thunder, or lightning, and requires a new job briefing when expected conditions change. Safety can move the plan.

The missed homeowner is the visible cost. The hidden cost is the handoff that broke before anyone called them.

This audit is for finding the first weak link in a tree service dispatch workflow, not finding someone to blame.

Rebuild the delay minute by minute

Pick one removal that ran long in the past two weeks. Use a normal bad day, where the repeatable problem is easier to see.

Pull timestamps from the board, crew notes, GPS, call log, and text record. Mark any time that exists only in memory as unclear.

Moment	Time	What changed?	Who knew?	Record checked	Customer told?
Planned finish				Board
First warning				Crew note or call
Overrun confirmed				Board or dispatch note
Board changed				Schedule history
Customer contact				Text or call log
Actual arrival				GPS or job record

Now circle two gaps:

The minutes between field knowledge and office knowledge.
The minutes between office knowledge and the customer notice.

Then mark the first moment a useful update could have gone out. Not the moment the new ETA became perfect. Perfect ETAs are rare by 1:15 on a changing removal. A useful update can say the crew is delayed, give a revised window if one is real, and promise the next update at a specific time.

Check 1: Was the schedule usable before it slipped?

A copied two-hour block is not a duration estimate. For the delayed job, answer yes, no, or unclear:

Was the duration based on job facts, including access, rigging, haul distance, disposal, permits, weather exposure, and equipment?
Did complex removals have a buffer rule and an arrival window that allowed normal field variation?
Do similar jobs run long with this estimator, crew mix, job type, or service area?
Did dispatch have enough detail to see the risk to later stops?

A narrow window can look precise on the board, but it does not make arrival more precise. And yes, a board can still look perfect after reality has left the chat.

Diagnostic label: schedule accuracy failure

Check 2: Did the right signal fire early enough?

The crew should not manage customer messages from a driveway, but it needs a fast way to signal a changed plan.

Find the first reliable signal: a longer job, moved finish, delayed chip truck, equipment issue, or board resequence. A warning signal and confirmed ETA should trigger different actions.

Audit question	Evidence to inspect
What signal showed the job might run long?	Crew status, radio note, job note, GPS, or board move
When did dispatch see it?	Time-stamped note, call, or status change
Was there time for the next customer to adjust?	Planned arrival compared with signal time
What confirmed the revised window?	Crew update, route change, or dispatch decision

Earliest useful trigger time: ____________

Use a verified field report or visible job-status change. A notification setting cannot rescue a late signal.

Diagnostic label: trigger timing failure

Check 3: Did one role own the update?

Assign a primary owner, backup, and escalation contact for each delay handoff. Names may change by shift; the designations should not.

Responsibility	Primary owner	Backup	Escalation role	Field crew role
Receive and record a job-status change	Dispatch	Designated dispatch backup	Operations manager	Report status facts
Confirm queue order and revised window	Dispatch	Designated dispatch backup	Operations manager	Provide facts
Send routine delay notice	Dispatch	CSR	Operations manager	No customer messaging
Handle a reply or customer-specific request	CSR	Designated CSR backup	Operations manager	Provide facts
Escalate safety, access, or major schedule impact	Dispatch	CSR	Operations manager	Start alert

Dispatch owns the queue and revised order. The CSR owns replies requiring judgment or a customer conversation. The crew supplies status facts; it should not compose updates while managing a difficult removal.

Diagnostic label: ownership failure

Check 4: Can the workflow handle exceptions?

Use these branches during the audit:

If the customer can’t meet the revised window, confirm whether access can proceed; otherwise reschedule or escalate.
If a text gets no reply, follow the call rule before the crew arrives.
If crews or equipment arrive separately, update for the next customer-facing arrival.
If the job moves again, replace the old window and state the next-update time.
For a safety stop, weather hold, breakdown, or disposal delay, do not invent an ETA; give the next-update time.
Use an approved alternate contact path for unverified details or text opt-outs, and escalate access, safety, or high-value-job risks.

For text programs, the FCC says robotexts are generally treated as telephone calls under TCPA rules. FCC guidance cautions against treating a phone number as blanket permission. CTIA says appointment reminders and alerts are informational messages and calls for purpose-specific permission, sender identity, opt-out instructions, and retained consent and opt-out records. Read the CTIA guidance.

Diagnostic label: exception-path failure

Check 5: Can anyone see what the customer was told?

When dispatch says, “We already sent that,” the next question is simple: where is it?

A shared message history prevents duplicate updates, conflicting windows, and a CSR having to reconstruct a conversation while a homeowner is on hold. It also gives dispatch a quick way to check the live schedule change before sending the next notice.

Check whether your record shows:

The correct job and customer
The sent time and channel: text, call, or email
The exact wording or call note
The sender
Delivery result, when available
Customer replies, visible to both dispatch and the CSR
The revised service window
The next-update promise, if no firm ETA was available

At minimum, retain consent and opt-out details for your messaging program, as CTIA recommends. The wider job-linked log lets the next person see what happened quickly.

Diagnostic label: message-history failure

Score the handoff, then fix the first break

Score each point from the delayed job. Green means the evidence was clear and timely. Yellow means it worked through manual effort or luck. Red means the handoff broke.

Audit point	Green	Yellow	Red
Schedule accuracy
Trigger timing
Ownership
Exception path
Message history

Start with the first red point in the timeline: improve the duration rule, early status signal, owner/backup assignment, exception branch, or shared log that failed first.

Test one change for a week. Track notice lead time, inbound ETA calls, missed access, duplicate contacts, and manual touches.

If manual ETA relay is the weak point, Queue Up can send repeatable routine notices once schedule data and triggers are sound, leaving the CSR to review messages and handle replies. It does not fix bad data, late signals, or unclear ownership.

Repeat the audit and keep the change only if timestamps show earlier notice, clear office ownership, and a record of what was said.