A component shortage is not usually a surprise. The signal arrives before the shortage is acute — inventory levels declining, supplier confirmation of allocation constraints, demand forecast showing combined site requirements exceeding expected supply. What happens next is where multi-site operations diverge sharply.
In operations with a pre-defined shortage allocation governance model, the signal triggers a structured process: the named allocation owner assesses combined site requirements against confirmed supply, applies the pre-agreed priority criteria, communicates the allocation to both plant managers, and records the rationale. Forty-eight hours later, both sites are running on reduced but predictable inputs. The shortage is managed.
In operations without that model — which is most mid-market multi-site manufacturers — the same signal triggers a different process. Both plant managers escalate independently to the COO, each making the case for why their site's demand should be prioritised. The COO spends two days mediating a negotiation between two operations leaders who both have legitimate needs. The allocation decision that finally emerges is based on whoever argued most effectively, not on the objective priority criteria that should govern the decision. The process itself damages the relationship between sites, creates a precedent for future escalations, and consumes COO bandwidth that should be reserved for decisions that actually require their judgment.
Why shortages are governance crises, not supply crises
The framing that shortages are supply chain problems leads operations leaders to focus their shortage response on supply-side interventions: qualifying backup suppliers, building safety stock buffers, diversifying the supplier base. These are legitimate risk-reduction strategies. They reduce the frequency of shortages. They do not change what happens when a shortage occurs.
When a shortage occurs, the problem is not that there is too little material. The problem is that there is not enough material for all sites and there is no pre-defined governance model for deciding how to allocate what exists. The supply problem is a given — it is the triggering condition. The governance problem is the crisis: how does the organisation make a documented, consistent allocation decision at operational pace, without consuming COO bandwidth in a bilateral negotiation between plant managers?
The supply shortage in this scenario is 700 units short of requirements. That gap was always going to create a problem. What the governance failure adds is: a 2.5-day decision delay, two damaged inter-site relationships, COO time consumed by operational mediation, and a decision with no documented rationale — which means the next shortage starts the same negotiation from scratch.
What a multi-site allocation governance model looks like
A shortage allocation governance model is not a set of rules that determine who gets the material. It is a structured process for making the allocation decision consistently, quickly, with documented rationale, without requiring COO mediation. The criteria within the model — the factors that determine allocation priority — should be defined in advance and agreed to by all sites before any shortage occurs.
The criteria framework typically includes four tiers:
These criteria are agreed to in advance by the COO and both plant managers. When a shortage signal fires, the named allocation owner — typically the supply chain director or central planning lead, not a plant manager — applies these criteria against the confirmed data from both sites and makes the allocation recommendation within a defined SLA. COO involvement is only required if the allocation recommendation falls outside the pre-agreed threshold (e.g., one site receives less than 40% of their requirement). In most cases, it is not required.
What changes when governance is in place
The operational difference is in response time and relationship health. With a pre-defined governance model, a shortage that would previously consume 2–3 days of COO-mediated negotiation resolves in 4–8 hours. Both plant managers receive the allocation decision with documented rationale — the criteria applied, the data used, the outcome — rather than a COO directive that one or both will feel was unfair.
The structural difference is in how future shortages are handled. A governance model that has been applied once creates a precedent and a process. The next shortage is not a negotiation — it is a process execution. The allocation owner has already run the model. The criteria are already understood. The escalation path to COO is already defined. Each shortage handled through the governance model makes the next one faster and less contentious.
This is the broader principle that applies across multi-site operations: most governance failures compound across incidents, while governance models compound in the opposite direction. The investment in building the model pays back faster with each subsequent event.
The data requirement
A multi-site allocation governance model requires one operational capability that many mid-market manufacturers do not currently have: a real-time view of both sites' confirmed order books, inventory positions, and production schedules in a single, accessible format. If the allocation owner has to make phone calls or wait for emails from two plant managers to assemble the data before applying the criteria, the governance model slows the process rather than accelerating it.
For organisations running on Dynamics 365 Business Central across multiple sites, this data is already in the ERP. The question is whether it is surfaced in a format that supports a fast allocation decision — or whether accessing it requires navigating across multiple entity views and running ad hoc queries. The decision infrastructure layer that surfaces the right data at the right moment is the prerequisite for the governance model to function at operational pace.
OpsGrid: multi-site allocation decisions in Business Central
OpsGrid — in live beta — is IntelliconnectQ's decision infrastructure layer for Dynamics 365 Business Central. For multi-site manufacturers on BC, it provides the data surfacing and decision routing that makes a shortage allocation governance model operational: live inventory and order positions across all sites, routed to the named allocation owner with the relevant data context, with a defined SLA and a direct connection to BC execution when the allocation is approved.
The governance model itself — the allocation criteria, the escalation thresholds, the COO trigger conditions — is designed with the operations team before deployment. OpsGrid enforces it. The allocation owner makes decisions with full context; the COO is in the loop only when the pre-agreed criteria require it.
If your multi-site operations currently handle shortages through COO-mediated negotiation between plant managers, start a conversation about what a pre-defined allocation governance model would look like for your operation.