Case study — Orba Enterprise Ltd

Orba Enterprise Ltd is an anonymised illustration. Identifying details have been adjusted; the methodology, formulas, and bands are exactly those of OrbaOS Instruments and The Coordination Capital Doctrine.

1. Executive summary

Headline interpretation. Coordination capital is materially above the structural floor — but not by much. The 2.5-percentage-point gap is dominated by post-merger transition load (1.25pp), with a smaller architectural-debt tail (0.20pp) and a residual ungoverned slice (0.05pp). Three diagnostic triggers fire (AL+DD, AL+RL high, 3+ high), all consistent with a control graph thickening around recently-rotated approvers in the integration boundary.

Recommended response (per the Doctrine cascade Measure → Interpret → Respond):

• Hold CCR steady through Q4 FY26.
• Time-bound the transition load: target floor + 1.0pp by Q2 FY27.
• Address architectural debt as a Q3 FY27 design item (legacy ERP coupling); not appropriate for a cost-cut.

2. About Orba Enterprise Ltd

Why they ran a coordination capital assessment. The Group CFO observed two signals over FY25:

1. The internal audit team flagged growing approval-queue times in three control domains.
2. Closing the consolidated H1 management accounts required eight hours of unscheduled reconciliation work — up from one hour pre-merger.

Both signals are coordination signals — they don't show up in the P&L or in process-mining tools. The CFO commissioned an Orba diagnostic and a measured CCR run as the formal instrument.

3. Step 1 — The Diagnostic

The 30-item OrbaOS diagnostic was run by the Group CFO with three direct reports (Group FC, Head of Risk, Head of Internal Audit) calibrating individually before consolidation. 90-minute working session.

Domain scores

RSI = 0.20·3.0 + 0.22·4.0 + 0.20·3.2 + 0.18·3.8 + 0.20·3.6 = 3.524 CDI = (5/4) · (5 − 3.524) = 1.846 → INTERMEDIATE band

Triggers fired (3 of 15)

The interpretation engine fires structural rules when domain scores cross threshold combinations.

Reading from the doctrine engine, not the analyst. The narratives above are the verbatim outputs from lib/diagnostic/triggers.ts. They are stable across observers; calibration discipline is preserved.

What the diagnostic does not tell us

• It does not quantify the cost (in £). That is the job of the CCR run.
• It does not derive the structural floor. That requires evidence-based three-layer derivation (Step 3).
• It does not classify the discretionary gap. That requires the five-bucket allocation (Step 4).

4. Step 2 — The CCR run

Once the diagnostic surfaced that coordination load was structurally elevated, Orba ran a measured CCR to quantify it.

Sample design

• Population: 2,800 employees across all functions and grades.
• Sample size: 1,200 (stratified by function and grade).
• Period: 4 weeks rolling, weeks 8–11 of FY26 H1.
• Method: activity-coding rubric (executed vs coordinating activities, applied to time-tracker exports + manager attestation).
• Variance handling: hour-weighted means within strata; bootstrap 95% CI.
• Calibration: classification rubric calibrated by 30-respondent pilot at week 7.

Result

• Total labour cost (FY25 baseline): £155 m
• Coordination cost (sampled, period-equivalent): £44.18 m
• CCR: 28.5 % (95% CI 27.6 – 29.4 %)
• Status: CALCULATED, attached to assessment "Group H1 FY26 — Coordination Capital Assessment"

CCR sits firmly in the Coordination-bound band on the OrbaOS framework (25 – 35 %): elevated but not catastrophic. The next question is how much of that is structural vs discretionary.

5. Step 3 — Structural floor derivation

Per the Doctrine's three-layer method (Ch. 7).

Layer 1 — Obligation baseline: 24.5 %

Layer 2 — Topology and interdependence load: +4.5 %

Layer 3 — Stability adjustment: −3.0 %

A negative Layer 3 here means: of the integration-boundary coordination, 3.0 percentage points are transitional and should not enter the steady-state floor. They are real, but they will fall out of the floor when the integration completes.

Resulting floor

Floor = 24.5 + 4.5 − 3.0 = 26.0 % (CI 24.5 – 27.5 %)

Discretionary gap

Gap = CCR − Floor = 28.5 − 26.0 = 2.5 percentage points

In £ terms (at FY25 wage bill): 2.5 / 100 × £155 m = £3.875 m per year of coordination spend that sits above the structural floor.

This is not by itself a cost-cutting target. The next step (classification) decides what kind of governance response is appropriate.

6. Step 4 — Five-bucket classification of the gap

The 2.5pp gap is allocated across the doctrine's five buckets (Ch. 4, 7). Buckets sum to 100 % of the gap.

Governance response by bucket

• Transition (1.25pp): Time-bounded. Will fall out as integration completes. Track via drift baseline.
• Structural (0.75pp): Should migrate into the floor at the next derivation. Update Layer 1 with new compliance driver.
• Strategic (0.25pp): Affirm; document the strategic justification in the audit committee report.
• Architectural debt (0.20pp): Address by design — Q3 FY27 ERP coupling redesign item.
• Ungoverned (0.05pp): Investigate before next assessment; classify or reduce.

No recommendation to cut. The Doctrine is explicit: structural and strategic coordination is governed, not eliminated. Architectural debt is a redesign target, not a redundancy programme. This is the discipline that distinguishes Instruments from a generic cost-cutting consultant.

7. Step 5 — Routing, drift, and reporting

Routing map (excerpt)

Authority topology for material commitments above £5 m capital — published on the Routing Mapper.

Origin (Group FC)
  └─→ Group CFO (review, max 5d)
        └─→ Group ExCo (approve / refer)
              ├─→ Audit Committee  (control-significant)
              └─→ Risk Committee    (risk-significant)
                    └─→ Board       (board-reserved)

Cross-jurisdictional rule: any commitment touching FR or DE entities must include the relevant subsidiary board chair as a named approver (sparse path, single approval, auditable).

Drift baseline

ACTIVE baseline registered 2026-04-15:

• Baseline CCR: 28.5 %
• Threshold: 5 % (drift > 1.4pp triggers an alert)
• Cron: daily; alerts emailed to Audit Committee secretariat

Governance report

One published board-ready report (Ch. 8) for H1 FY26: see docs/marketing/CASE_STUDY_BOARD_MEMO.md for the full text as attached to board papers.

8. What changed six months later (forward look)

The case study reflects H1 FY26. At H2 review, Orba expects:

These are projections, not promises. The Drift Monitor will record what actually happens; the next diagnostic at the end of H2 will re-test the domain scores; the Reports module captures the change.

9. Limitations

OrbaOS Instruments is a self-assessment instrument and decision-support platform. It does not certify regulatory compliance or replace audit procedures. The methodology — RSI, CDI, CCR, three-layer floor, five-bucket classification — is the canonical model published in The Coordination Capital Doctrine. See orbaos.com for the framework underpinning this work.

Orba Enterprise Ltd is an anonymised illustration. Identifying details have been adjusted; no representation is made about any specific company.

— © Rondanini Publishing trading as OrbaOS™.