Institutional Command and Control (iC2)

SYNOPSIS

Modern defence institutions face a growing structural paradox. Operational decision cycles increasingly run at machine speed, enabled by advanced sensing, analytics and decision systems, while the institutions responsible for resourcing, sustaining and governing those operations continue to function at bureaucratic speed. A defence organization can generate operational insight in seconds and then require weeks or months to mobilize the institutional action needed to act on it. This paper names that space the institutional execution gap, and argues that Institutional Command and Control is the command function required to close it.

WHAT iC2 IS

Institutional Command and Control is the enterprise command function through which defence institutions align and direct authorities, resources and industrial capacity in response to operational demand. It translates operational intent into synchronized enterprise action across current operations, force regeneration and future capability development.

It is not an additional layer of governance, and it does not consolidate or override the functional authorities that exist precisely because cyber, safety, financial and personnel risks require independent expert judgement at arm's length from operational pressure. It ensures those authorities operate in synchronization rather than in isolation. Unlike a standing committee or a project governance structure, it is not convened in response to a decision; it is continuously active.

KEY FINDINGS

1. 1

   The gap is structural, not a matter of inefficiency. Two command cycles, operational and institutional, run at fundamentally different speeds and serve distinct but interdependent purposes. The problem is not that they exist separately, which they must, but that they are not synchronized. The gap is the predictable consequence of an enterprise in which authority, resources and accountability are distributed across structures that were not organized to function as a coherent command system.

2. 2

   The levers have migrated out of the commander's span of control. Historically many of the functional authorities required to generate and sustain military capability sat within it. They have since moved into specialized functional structures across the enterprise, leaving commanders accountable for operational outcomes while the means of delivering them operate outside the operational chain of command. The ability to influence and synchronize those enterprise systems is no longer ancillary to command; it is integral to it.

3. 3

   Enterprise tempo collapses to the slowest process in the chain. Where institutions apply a uniform standard across distributed processes optimized for governance rather than tempo, that is the result. And because the functional offices' requirements are in many cases asynchronous or directly contradictory, a reconciliation problem is added on top of the coordination one.

4. 4

   A system's label does not determine the operational consequences of its failure. In an interconnected defence enterprise, every system that enables a commander to resource, sustain, adapt or regenerate forces is an operational system. The administrative and operational distinction obscures that, and the institutional arrangement through which a system is delivered does not change it either.

5. 5

   Institutional execution must be exercised before it is required. Commanders routinely wargame operational plans, yet the institutional systems required to sustain those plans are rarely exercised with the same rigour. The institution that has not exercised its execution architecture in peacetime will discover its limits in conflict, when the cost of doing so is highest.

6. 6

   Institutional execution is a form of readiness, and should be measured like one. Defence institutions track operational readiness through force availability, equipment readiness and training status. Comparable measures rarely exist for the institutional processes that let those forces adapt and sustain operations. The paper proposes two dimensions, execution velocity and execution coherence, and argues that where execution cannot be measured it cannot be controlled, and where it cannot be controlled it cannot be aligned to operational tempo.

7. 7

   Governance is not the constraint. How it is applied is. Cyber accreditation, supplier onboarding, export controls and security vetting are expressed through small p policy calibrated for a different operational tempo. Defence digital strategies that address data integration while leaving those mechanisms unchanged will accelerate the visibility of institutional failure without improving the capacity to resolve it.

THE SCENARIO

The paper works the argument through a Royal Canadian Navy task group on a multinational maritime operation. Electronic warfare sensors aboard several Halifax-class frigates detect previously unobserved adversary emissions capable of degrading combat system performance. The Fleet Commander determines that a modification to the combat system software and the associated procedures would mitigate the threat.

The operational decision cycle may take hours. Executing it requires combat system configuration offices to approve the modification, cyber and safety accreditation bodies to validate the software update, the Halifax-class program office to authorize the revised configuration baseline, industrial partners to prepare the update, fleet sustainment organizations to distribute it to ships at sea, and personnel staffs to ensure operators and technicians are trained on it. Each of those intervals is governed by a separate office and process, and in current structures they routinely extend from days to weeks. Throughout, the vulnerability remains unmitigated and adversary systems continue to adapt. The execution gap is not a single delay. It is the cumulative effect of unsynchronized cycles.

MEASURING INSTITUTIONAL EXECUTION

If institutional execution is a strategic capability it must be measurable. Defence institutions track operational readiness through force availability, equipment readiness and training status; comparable measures rarely exist for the institutional processes that let those forces adapt and sustain operations. The paper frames institutional execution as institutional readiness, resting on two factors: execution velocity, the speed at which institutional action occurs, and execution coherence, the degree to which that action is synchronized across authorities, systems and organizations.

It proposes concrete indicators: the time to authorize mission-critical changes; the time from identified operational need to funded experiment; the cycle time from industry proposal to live operational trial; the time from operational feedback to fielded software modification; and the time to accredit new capabilities and onboard industrial partners into secure production environments. These belong inside existing defence reporting rather than in a separate analytical exercise, and responsibility for tracking them has to be assigned explicitly. Without assigned ownership they remain advisory. With it, they become a command instrument rather than an administrative one.