Owners and operations leaders · 6 min read

How to run every location from one screen

What a multi-location command center needs to show, who should see it, and how to roll it out without a rip-and-replace.

Start with the questions, not the software

Most operators already have the data they need. It is spread across a CRM, an accounting package, a scheduling tool and a handful of spreadsheets. The command center is not another system to feed. It is the place those systems report to.

Before you connect anything, write down the five questions you ask every Monday. Which location is behind on revenue? Where are tickets piling up? Which crews are idle? Those questions become the first screen.

Agree on one set of definitions

Two locations rarely count a "lead" or a "job" the same way. If the command center pulls both numbers side by side without a shared definition, the screen creates arguments instead of decisions.

Pick the definitions once, at the group level, and map each location’s systems to them during setup. DojoCOMMAND stores these mappings so new locations inherit them.

  • Lead, opportunity and closed deal
  • Job, visit and work order
  • Revenue recognised vs. revenue invoiced
  • Active customer

Give each role its own view

The owner wants the whole group. A location manager wants their site. Finance wants every number reconciled. One dashboard for everybody ends up serving nobody.

Use roles to decide what each person sees by default, and let them drill down from there. Everyone works from the same data, they just start in a different place.

Roll out one location first

Connect your best-run location first. It gives you a clean baseline and a team that will tell you quickly when a number looks wrong. Once that site is trusted, add the rest in batches.

One hub

Ready to run it as one operation?

Pick the native apps you need, connect the ones you already have, and see your DojoCOMMAND price live. Or start with a fixed-price Blueprint and we'll map it for you.