Manuall Trade Library Run your shop on Manuall

Centralize Dispatch and Office or Keep It Local: Decision Tree

Troubleshooting Expansion Updated Jul 24, 2026

Why this matters

When you run more than one crew or site, every office function faces the same fork: run it once from a central hub, or run it separately at each location. Centralize the wrong thing and a distant crew loses the local judgment and speed that made customers love them. Leave the wrong thing local and you pay for duplicate staff, get inconsistent service, and lose the leverage of buying and booking as one shop. This is not an all-or-nothing choice. It is decided function by function, and this tree walks the main ones.

Start here: what problem are you actually solving?

The whole decision turns on one question asked per function: is this function better when it is consistent and efficient, or better when it is fast and locally aware?

  • If the function benefits most from consistency, leverage, and not paying twice, it leans central.
  • If the function benefits most from local knowledge, speed, and relationships, it leans local.
  • When both matter, the answer is usually a hybrid: central for the standard and the system, local for the judgment call in the moment.

Run each function below through that lens rather than deciding the whole office at once.

Function 1: scheduling and dispatch

The daily call of who goes where. This one splits.

  • If you mean the system, the rules, and the after-hours or overflow desk, centralize it. One scheduling standard and one place to catch spillover beats every location reinventing it.
  • If you mean the in-the-moment reshuffle when a job runs long or a customer needs a same-day squeeze, keep the judgment local. A dispatcher who knows the crews, the traffic, and the customers makes a better real-time call than a distant hub reading a screen. Central owns the system; local owns the day.

Function 2: customer intake and phones

The first impression and the booking.

  • If volume is high and consistency matters (every call answered, booked to the same standard, nothing dropped after hours), a central intake desk usually wins. Missed calls are lost jobs, and a shared desk covers gaps a small local office cannot.
  • If the value is a local person who knows the market, the repeat customers, and the neighborhood by name, keep intake local or blend it (central catches overflow and after-hours, local handles the relationships). Match this to how much your customers value being known.

Function 3: purchasing and stock

Buying materials and keeping trucks stocked.

  • If you are buying the same things across locations, centralize the buying to get the leverage of one larger order and consistent pricing. Buying as one shop beats buying as three small ones.
  • If it is the day-to-day "we are out of X, grab it now," keep that local. Central negotiates the deal and sets the stocking standard; local pulls the trigger on the daily replenishment so a crew is never stuck waiting on a distant approval.

Function 4: back-office (billing, payroll, records)

Invoicing, collections, payroll, the books.

  • This one centralizes almost every time. Billing, accounts receivable and payable, payroll, and the financial records get cheaper, cleaner, and more consistent run once. Duplicating them per location wastes money and scatters the numbers you need to see the whole business. There is little local judgment in cutting a payroll run or sending an invoice, so there is little reason to keep it local.

When to lean which way

Lean central Lean local
Consistency across locations matters most Local knowledge and relationships matter most
The function has buying or booking leverage at scale Speed of the in-the-moment call matters most
Little local judgment is involved Real-time judgment about crews and customers is involved
Paying for it twice is pure waste A distant hub would be slower or blind to local reality

Decision summary

  1. For each function, ask: is it better consistent and efficient, or fast and locally aware?
  2. Scheduling and dispatch: central for the system and overflow, local for the real-time judgment.
  3. Intake and phones: central when consistency and coverage rule, local or blended when being known matters.
  4. Purchasing: central for the buying leverage and standard, local for daily replenishment.
  5. Back-office: centralize it, almost without exception.

Do not centralize the office to feel in control, and do not keep it local out of habit. Decide function by function on whether consistency or local speed serves the customer more.

References

  • U.S. Small Business Administration (SBA): multi-location operations and back-office management
  • Trade-standard practice on centralized dispatch and purchasing leverage
  • See related: What to Centralize and What to Leave to Each Location; Dividing Territory Between Crews Without Creating Turf Wars

Related articles