Operations · 2026-08-18

Your crew is late because the map is fat

Late arrivals are usually a dispatch problem, not a lazy tech. Here is how to tighten the map and stop apologizing by text.

The apology you send every afternoon

Running late. Traffic. Previous job ran long. The customer has heard it. The tech has typed it. The office has copied it. Nobody fixed the board.

Most late days are not mystery. You sold a map that cannot be driven.

A schedule that looks full on paper can still be empty of time.

Count windshield minutes

For one week, write drive time next to every job. Not the GPS promise. The real door to door. You will find the orphan across the river, the lunch that is really a forty minute crawl, and the two stops that should never share a day.

The travel time calculator and the service area calculator will not flatter you. That is the point.

Windows, not folklore

A two hour window you miss is worse than a four hour window you hit. Give windows you can keep. Put the next job far enough that a talkative homeowner does not wreck the day. Build a buffer after the first stop, not after the fifth.

If Jason books the day, he needs the same rules you would give a new dispatcher. Density first. Heroes later.

Cut the pretty zip codes

A high end neighborhood forty minutes off the cluster is a vanity account. Either raise it until the drive is paid or stop taking it. Fleet habits do not matter if the map is a star instead of a fist.

One dispatcher, one truth

When three people move pins, nobody owns the late. One person owns the board. Techs can ask. They cannot freelance a side stop that blows the afternoon.

Sqyre should show the same board to the office and the truck. Two boards is how you get two stories at 4pm.

The late text that still has dignity

If you will miss the window, say it as soon as you know. Give a new window. Offer to reschedule. Do not invent traffic. Customers forgive a tight shop. They do not forgive a shop that lies about why.

Tighten the map for thirty days. The texts get quieter. That is how you know it worked.

The plain version

Crews run late when the map is a star, not a fist. Density is the schedule.

Read that again without the trade slang. Your crew is late because the map is fat is about a choice a small shop makes on an ordinary weekday. The customer wants a clear answer. You want the truck to come home with money, not only a story. Those two wants can live together if the sentence you say on the phone matches the day you can actually run.

Late arrivals are usually a dispatch problem, not a lazy tech. Here is how to tighten the map and stop apologizing by text.

What the words mean

A quote is a written price the customer can accept. A visit fee is the price to show up and find the truth. A route is the order of houses one truck will reach. A promise is only real when the calendar, the part, and the person line up. If one of those is missing, you have a hope, not a booking.

People get hurt by shops that skip this and say yes anyway. The homeowner waits. The tech arrives late or without the part. The office spends the evening apologizing. None of that shows up as a line on the quote, but it is the cost.

A week you can picture

Monday you write the rule in one sentence. Tuesday you use it on a real lead. Wednesday you look at what the truck actually did, not what you hoped. Thursday you fix the sentence that caused a surprise. Friday you count what was paid before the van door shut.

That week is the whole article. Your crew is late because the map is fat is not a theory. It is that loop, repeated until a new person at the desk can do it without you.

Try a number before you promise one

Change the inputs. Watch what a single job keeps. If the number feels too high to say out loud, your costs are already too high to hide.

quote

  • kind — travel

Walk a lead from the first text to a paid ticket

walk

  • Hear the problem — Ask what is wrong and where the house is. Do not give a firm repair price yet.
  • Check the day — Look at the board. Offer a day you can reach, not the day they hoped for if the truck is already full.
  • Say the money — Say the visit fee, the likely range, and what would make it higher. Write it down.
  • Book and collect — When they say yes, put it on the calendar and take the deposit or the card you already explained.

See the shape

diagram

  • kind — route
  • title — Keep the day in one neighborhood
  • caption — Stops that share a street belong together. The far pin can wait for a day you are already over there.
  • First house — stop
  • Next door — stop
  • Same block — stop
  • Across town — skip

What good looks like in Sqyre

The lead, the quote, the visit, and the payment should be one thread. Scheduling holds the day. Quotes hold the price. Payments happen before you leave. Jason may repeat the sentence you trained. He may not invent a better one at 9pm.

If you want the longer trade version, start at the industries pages and come back to this guide when the rule needs to be said in plain words.

Questions people actually ask

faq

  • Do I have to raise every price tomorrow? — No. Start with the next new customer and the next visit fee. Existing routes can move on the renewal, with a clear note, not a surprise.
  • What if the customer wants a firm price on the phone? — Give the visit fee and a range. A firm repair price before you see the job is how small work becomes free work.
  • Can software say this for me? — It can repeat your rule. It cannot invent a rule you never wrote. Put the sentence in the playbook first.
  • How long before this feels normal? — One week of using the same sentence. The third time you say it, it stops feeling like a script.

Do this before Friday

  1. Write the one sentence your desk is allowed to say about price and timing.
  2. Put the next five jobs on a map and mark the one that does not belong.
  3. Take payment on the next finished job before the truck leaves.