Google's LSA Load-Time Rule Turns Dispatch Into Cost Driver

Google announced in early September 2026 that Local Services Ads for moving companies will now track load time accuracy—the delta between the estimated truck arrival window you communicate and the moment your crew actually pulls up. Miss by more than 15 minutes consistently, and your cost-per-lead climbs 40–60%. This is not a soft ranking factor buried in algorithm tea leaves. It is a hard cost penalty tied to operational execution.

For moving companies, this changes the economics of customer acquisition. LSA performance is no longer just about reviews, response speed, or geographic coverage. Google is now auditing whether your dispatch system can deliver on the promise your sales team made. The platform treats on-time arrival as a proxy for operational reliability, and it prices leads accordingly.

The implication: dispatch precision is now a margin line item. If your process cannot consistently land trucks within the communicated window, you pay more for every inbound call. If you pad estimates so wide that you never miss, you lose bookings to competitors who quote tighter ranges and sound more confident. The only path forward is instrumentation—real-time routing, client notification workflows, and buffer calibration that adapts to actual performance data.

Why Google Cares

Google's Local Services Ads business model depends on trust. Homeowners pay nothing to request quotes; advertisers pay per lead. If leads convert poorly because service providers fail basic operational commitments, the marketplace degrades. Homeowners stop using it. Advertisers churn. Google loses revenue.

Load time is one of the few operational metrics Google can observe without manual human review. Moving companies already communicate estimated arrival windows through LSA's booking interface and follow-up messages. Google can compare that timestamp to GPS data from the truck, check-in signals from the mover's app, or even client-reported arrival times if the platform prompts for feedback post-job.

For moving companies, this metric is particularly vulnerable. Unlike a plumber arriving for a one-hour service call, a move involves coordinating crew schedules, vehicle availability, prior job overruns, traffic, parking access, and client-side delays like elevator reservations or building access. The surface area for variance is large, and most moving companies manage dispatch with a combination of spreadsheets, group texts, and gut feel.

Google's 15-minute threshold is tight but not arbitrary. It reflects the tolerance window most consumers expect. A truck arriving 10 minutes late feels on time. A truck arriving 25 minutes late without warning feels like broken trust. By penalizing movers who cross that line repeatedly, Google is enforcing the operational standard the market already holds.

The Penalty Mechanics

When your moving company LSA account consistently misses load time windows by more than 15 minutes, Google raises your cost-per-lead. The reported range is 40–60%, which means a lead that cost you $35 under normal performance now costs $50–$55.

This is not a manual review or a one-time flag. It appears to be an automated adjustment tied to your account's rolling performance data. If you course-correct and bring your on-time rate back above Google's threshold, the penalty reverses over time. If you remain out of compliance, the premium persists.

Google has not published the exact calculation window—whether it's trailing 30 days, 50 jobs, or a weighted blend. What matters for operators is that variance compounds faster than averages. Missing by 20 minutes on half your jobs is worse than missing by 40 minutes on 10% of jobs. Consistency matters more than occasional heroics.

The cost impact scales with volume. A moving company running 120 jobs per month through LSA at a $40 average cost-per-lead spends $4,800. A 50% penalty pushes that to $7,200—an extra $2,400 per month with zero additional bookings. Over a season, that is $14,400 in wasted acquisition spend, or roughly two additional trucks' worth of operating margin.

For smaller operators running 30–40 jobs per month, the dollar figure is lower but the margin impact is identical. A 50% LSA cost increase without compensating revenue growth forces either price hikes, crew cuts, or margin compression. None of those paths sustain growth.

The Trap

The instinctive response to Google's load-time penalty is to widen your arrival windows. Quote a four-hour range instead of two. Build in buffer. Never be late.

This solves the penalty but breaks conversion. Homeowners booking a move want certainty. A competitor who offers a two-hour window sounds more professional, more in control, more worth the premium. When your estimate says "We'll arrive sometime between 8 a.m. and noon" and theirs says "10 to 11 a.m.," you lose the booking—even if your price is lower.

Padding also degrades operational efficiency. If you quote a four-hour window and your crew shows up in hour one, the client is often unprepared. If you show up in hour four, the client has burned half a day waiting. Neither scenario builds trust or referrals. Wide windows are a signal of operational immaturity, and homeowners read that signal clearly.

The only sustainable answer is to make your estimates accurate and then hit them. That requires instrumentation: dispatch software that models real job duration, routing logic that accounts for traffic and prior-job overrun risk, client notifications that update in real time as conditions shift, and feedback loops that refine your buffer assumptions based on actual performance.

Dispatch Infrastructure

Most moving companies dispatch jobs using a shared calendar, a whiteboard, or a manager's mental model of crew availability. This works when volume is low and jobs are local. It breaks when you scale past two trucks or operate across a metro area with variable traffic.

Moving company dispatch software should answer four questions for every job on the board:

1. Which crew is assigned, and what is their current location and estimated finish time?
2. What is the drive time from their current job to the next load site, accounting for real-time traffic?
3. What is the expected duration of the next job, based on historical data for similar moves (square footage, floor count, item volume, distance)?
4. What buffer is required to absorb variance without missing the quoted window?

These are not exotic. They are the same questions a rideshare platform answers thousands of times per second. The difference is that moving companies run lower volume and higher stakes—each job is worth $800 to $3,500, and a single miss can cost the client's trust and the company's LSA cost structure.

A functional dispatch system pulls crew location from GPS, models job duration using past jobs with similar attributes, calculates drive time via a routing API, and surfaces a recommended arrival window. The dispatcher confirms or adjusts. The system then monitors progress in real time and flags variance early—before the 15-minute threshold is breached.

This does not require custom software. Off-the-shelf field service platforms and moving-specific tools already offer most of these features. The gap is adoption. Many moving companies treat dispatch as an art, not a science, and resist instrumenting it because "every job is different." Every job is different, but patterns are detectable, and variance is manageable if you measure it.

Client Communication Loops

Even with perfect dispatch logic, variance happens. A prior job runs long because the client added last-minute items. Traffic spikes due to an accident. The building delays elevator access. A crew member calls in sick and you reshuffle trucks mid-morning.

When variance is inevitable, communication becomes the release valve. A truck arriving 20 minutes late with no warning feels like negligence. The same truck arriving 20 minutes late after a text update 40 minutes prior feels like professionalism under pressure.

Client notifications should trigger automatically based on dispatch system data:

• 24 hours before the move: Confirm the estimated arrival window, crew size, and any client prep steps (parking, building access, packing status).
• Morning of the move: Narrow the window if possible ("Our crew will arrive between 9:15 and 9:45 a.m.") and provide crew lead name and truck number.
• When the prior job is finishing: Send an updated ETA based on actual drive time and current location ("We're wrapping up our current job and expect to arrive at 10:05 a.m.").
• If delay exceeds 10 minutes beyond the quoted window: Proactive alert with revised ETA and brief explanation ("Traffic on I-95 is heavier than expected—new arrival time is 10:30 a.m. We'll have you loaded and on the road quickly.").

This sequence does two things. First, it sets and resets expectations so the client is never surprised. Second, it creates a documented communication trail that Google's system may ingest when evaluating your on-time performance. If the client receives a timestamped update revising the window and you hit the revised target, that may count as on-time in Google's eyes—though Google has not confirmed this mechanic publicly.

What matters more is client perception. A homeowner who receives proactive updates is far less likely to report the move as late, even if the original window was missed. Client-reported feedback likely feeds Google's LSA scoring, so managing perception is managing cost.

Buffer Calibration

The hardest part of hitting quoted windows is choosing the right buffer. Too little buffer and you miss windows whenever minor variance occurs. Too much buffer and you either quote uncompetitive windows or waste crew idle time.

Buffer is not a fixed number. It should vary based on:

• Time of day. Morning jobs have tighter variances than afternoon jobs, because there is no prior-job overrun risk. A 9 a.m. start can safely quote a 30-minute window. A 2 p.m. start after two prior jobs needs 60–90 minutes unless you instrument handoff precision.
• Job complexity. A one-bedroom apartment move has lower duration variance than a four-bedroom house with a piano and a hot tub. Complexity increases tail risk, which requires wider buffer or more conservative scheduling.
• Crew experience. A senior crew with three years together will complete jobs faster and more predictably than a crew mixing seasonal hires. Your system should track crew-level performance and adjust arrival windows accordingly.
• Geographic density. Urban jobs with parking and elevator coordination have higher variance than suburban jobs with driveway access. Route density also matters—if you run three jobs in the same neighborhood, you can tighten windows because drive time variance is low.

To calibrate buffer, you need historical performance data. Track actual arrival time versus quoted window for every job, tagged by day of week, crew, job type, and start time. After 50–100 jobs, patterns emerge. You will see that your Tuesday morning crew hits 95% of windows but your Saturday afternoon crew hits 70%. You will see that three-story walkups run 20% longer than estimated, while single-family suburban moves run on time.

Use this data to build buffer rules into your dispatch system. A Saturday afternoon job for a crew with 70% on-time performance and a three-story walkup should automatically get an extra 30–45 minutes of buffer compared to a Tuesday morning job with a proven crew and ground-floor access.

This is not guesswork. It is operations research applied to a low-margin, high-variability service business. The moving companies that instrument this will win LSA cost efficiency. The ones that rely on intuition will pay the Google tax.

The Compounding System

Google's LSA load-time rule is one forcing function. It will not be the last. As platforms gain access to operational data—through integrations, GPS signals, client feedback loops, and payment timestamps—they will continue to price and rank service providers based on execution, not just marketing.

This trend rewards companies that treat operations as infrastructure, not overhead. Dispatch precision, client communication workflows, and buffer calibration are not tactics. They are the revenue engine in a world where platforms audit promises.

For moving companies, the path forward is clear:

Instrument dispatch. Replace spreadsheets and group texts with software that models job duration, tracks crew location, and surfaces variance in real time.

Automate client communication. Build notification sequences that update arrival windows dynamically as conditions change, so clients are never surprised and variance is managed through expectation, not perfection.

Calibrate buffers using data. Track on-time performance by crew, job type, time of day, and geography. Use that data to set arrival windows that are tight enough to win bookings and wide enough to hit consistently.

Treat cost-per-lead as an operational metric. Your LSA performance is not a marketing problem. It is a dispatch problem. The companies that connect acquisition cost to operational execution will compound margin while competitors burn budget on penalties they cannot see.

Google's load-time accuracy rule does not create a new capability gap. It makes an existing gap expensive. Moving companies that already run tight dispatch and proactive communication will see cost-per-lead drop as competitors get penalized. Moving companies that operate on feel and firefighting will watch acquisition costs climb until margin disappears.

The moat is not in the ad spend. It is in the system that delivers what the ad promised.