# The Factory Control Layer: Managing 25 Sites in One Dashboard

**Category:** PMO
**Author:** John Hotham
**Published:** 2026-05-22
**Read Time:** 4 min read

## Summary
Isambard Brunel did not manage the Great Western Railway from 25 separate offices. He built a control layer. Your multi-site operation needs the same discipline.

## Full Content
Isambard Kingdom Brunel did not manage the Great Western Railway by visiting each station individually and hoping the track gauges matched. He built a system. A control layer that ensured consistency, quality, and progress across hundreds of miles of simultaneous construction.

Your 25-site operation deserves no less. And yet, most multi-site project managers are still running their equivalent of the Great Western Railway from a collection of disconnected spreadsheets, WhatsApp groups, and weekly site visits.

## What Is a Factory Control Layer?

A Factory Control Layer is the unified operational dashboard that sits above individual site-level project management. It does not replace site managers or local decision-making. It provides the single source of truth that allows central governance to function without micromanagement.

Think of it as the bridge of a ship. The engine room runs independently. The navigation team operates independently. But the bridge sees everything, in real time, and can intervene when the heading drifts.

## Why Does Multi-Site Project Management Fail?

Multi-site failure follows a predictable pattern:

**Information lag.** Site managers report weekly. Problems emerge daily. By the time the central team knows about a delay, it has already cascaded.

**Inconsistent reporting.** Twenty-five sites using twenty-five different formats. One uses RAG status. Another uses percentage complete. A third uses "on track" or "off track" with no supporting data.

**No early warning system.** Without standardised signals, the central team cannot distinguish between a site that is genuinely 80% complete and one that is 80% complete on paper but has critical path items outstanding.

**Resource allocation blindness.** If Site 14 has surplus labour and Site 7 has a shortage, how quickly can the central team identify and resolve this? In most operations, the answer is: not quickly enough.

## What Does a Single-Dashboard Approach Look Like?

A proper Factory Control Layer provides:

**Standardised signals.** Every site reports against the same framework. Same milestones. Same RAG criteria. Same evidence requirements. No interpretation required.

**Real-time status.** Not weekly updates. Real-time progress against plan, updated as tasks complete. If a critical path item slips on Site 19 at 3pm, the central dashboard reflects it at 3:01pm.

**Exception-based governance.** The dashboard does not demand attention when things are on track. It escalates when they are not. Green sites stay silent. Amber sites flag. Red sites alert.

**Resource heatmaps.** Labour, materials, and equipment allocation across all 25 sites, visible in one view. Surplus and shortage identified automatically.

**Milestone dependency mapping.** Site 12 cannot pour foundations until Site 8 releases the crane. The system knows this. The site managers might not.

## How Did the Isembard Build Inspire This Thinking?

The Isembard approach, named after Brunel himself, treats multi-site delivery as an engineering problem rather than a management problem. The principles are:

1. **Standardise the unit of work.** Every site delivers against the same Work Breakdown Structure.
2. **Centralise the signal, not the decision.** Local teams retain autonomy. Central governance receives standardised data.
3. **Build for exception.** The system assumes everything is on track. It only activates when deviation is detected.
4. **Evidence over assertion.** "On track" means nothing without evidence. Photographs, completion certificates, and timestamped updates replace verbal assurances.

## How Does Simplif-i Deliver the Factory Control Layer?

Simplif-i provides the unified PMO dashboard that multi-site operations have lacked. Not as a reporting tool that generates pretty charts for board meetings. As an operational control system that drives daily decision-making.

**25 sites. One dashboard.** Every project, every milestone, every resource allocation visible in a single view. Drill down to site level when needed. Stay at portfolio level when not.

**Standardised WBS templates.** Configure once. Deploy across all sites. Every project reports against the same structure, eliminating interpretation and enabling genuine comparison.

**Automated exception alerts.** Critical path slippage, resource conflicts, milestone dependencies at risk. The system identifies them before they become crises.

**Evidence-based progress.** No more verbal assurances. Progress is evidenced through document uploads, photograph capture, and timestamped completions. If it is not evidenced, it is not complete.

**Integrated risk escalation.** Site-level risks that breach threshold automatically escalate to portfolio level. The central team sees emerging problems, not historical ones.

At £149 per month for Founding Members, Simplif-i gives multi-site operators the Factory Control Layer that Brunel would have demanded. Because managing 25 sites from 25 spreadsheets is not project management. It is hope management.

And hope, as every project manager knows, is not a strategy.

---
Source: https://simplif-i.com/api/blog/readable/pmo/factory-control-layer-managing-25-sites-one-dashboard
Web Version: https://simplif-i.com/blog/pmo/factory-control-layer-managing-25-sites-one-dashboard
© Simplif-i - Unified Business Management Platform