The Scenario
A facilities management company operates across seven locations in the Midlands. Each site has its own manager, its own processes, and — critically — its own way of tracking performance. The Birmingham office uses a shared spreadsheet. The Nottingham site emails a weekly PDF to head office. Two smaller locations submit numbers via a form that feeds into a Google Sheet. The remaining three provide updates verbally during a fortnightly call with the regional director.
The regional director is responsible for the performance of all seven sites. He knows how each location is doing in isolation, but he has no way to compare them side by side. If Birmingham’s job completion rate is eighty-two percent this month, is that good or bad? He cannot answer that without manually checking every other site’s numbers, which arrive in different formats at different times.
The CEO wants to open two additional locations next year. The regional director’s concern is straightforward: if managing seven sites with no unified view is already difficult, nine will be unmanageable.
The Problem
The lack of a unified view creates several compounding issues.
Performance comparison is impossible in any meaningful timeframe. By the time the regional director has assembled data from all seven sites into something comparable, the month is already over. He is always looking at lagging indicators and can never intervene in time to change an outcome.
Inconsistent reporting means inconsistent standards. Each site defines and measures things slightly differently. One location counts a job as complete when the work is done. Another counts it as complete only when the client has signed off. The numbers look comparable but they are not, and decisions made on false equivalence are worse than decisions made on no data at all.
Resource allocation across sites is guesswork. The regional director does not know which locations are overstaffed and which are stretched thin until a problem surfaces — a client complaint, a missed deadline, or a resignation from an overworked team. By that point the damage is done.
Best practices stay local. If the Nottingham site has figured out a scheduling approach that reduces overtime by fifteen percent, nobody else knows about it. There is no mechanism for identifying what works well at one location and replicating it across the network.
The Approach
Digital Royalty builds a multi-location operational dashboard that standardises data collection across all sites and presents it in a single unified interface.
The first step is defining a shared set of metrics. Working with site managers, the team agrees on what gets measured and how. Job completion rate, average response time, staff utilisation, client satisfaction scores, and revenue per site become the core metrics. Definitions are standardised so that every location measures the same thing the same way.
Data collection is automated wherever possible. The company’s job management platform, payroll system, and invoicing tool all feed into the dashboard directly. Where automation is not possible — client satisfaction surveys, for instance — a simple input mechanism ensures data arrives in a consistent format.
The dashboard provides three levels of view. A network overview shows all seven sites on a single screen with colour-coded performance indicators. A site detail view lets the regional director drill into any location to see its full metric set. A comparison view places two or more sites side by side to identify performance gaps and outliers.
Threshold alerts notify the regional director when any site’s metrics move outside acceptable ranges. He does not need to check the dashboard constantly. The system tells him when something needs attention.
The Outcome
The regional director gains a capability he has never had: the ability to see all seven locations as a single operation rather than seven separate ones.
Within the first month, the comparison view reveals that two sites are consistently underperforming on response time. Investigation shows they are both using a manual dispatch process that other sites abandoned months ago. Rolling out the better process takes a week and brings both sites in line.
Resource allocation becomes data-driven. The dashboard shows that the Coventry site is running at ninety-three percent utilisation while Leicester sits at sixty-eight percent. A temporary staff rebalance addresses both the overwork risk at Coventry and the underutilisation at Leicester without hiring.
The fortnightly calls with site managers become shorter and more focused. Instead of spending thirty minutes on what happened, they spend five minutes confirming the numbers and twenty-five minutes on what to do next. The regional director estimates he saves four hours per week on data gathering alone.
When the CEO approves the two new locations, the onboarding process is straightforward. New sites plug into the same dashboard with the same metrics from day one. There is no six-month learning curve while the regional director figures out how to get data from them. The system scales because it was designed to.
Six months in, the company identifies that its best-performing site shares three specific process characteristics. These are documented and rolled out as standard operating procedure across the network. Average job completion rate improves by seven percent company-wide.
Who This Applies To
This scenario is relevant to any business operating across multiple physical locations, branches, or regional units. It applies to retail chains, hospitality groups, logistics operations, healthcare networks, professional services firms with multiple offices, and franchise operations. The common thread is that each location generates operational data independently, and the business needs a way to see, compare, and act on that data as a whole.