Home / Case Studies / Restoring Control to a Failing Account

Most relevant to civilian assurance roles

Restoring Control to a Failing Account

How systematic control design transformed an unsatisfactory account to full compliance, with three control artefacts adopted beyond the original unit.

Role Account Owner & Control Designer
Timeline May 2024 – September 2026
Scope One front-line warship's account; three controls adopted beyond the unit
Outcome Full Compliance Achieved

TL;DR

Situation

Took over a front-line warship's supply chain account rated unsatisfactory by fleet logistics inspectors, with no standardised controls and no audit trail.

Action

Root-caused each inspection finding, then designed control artefacts, validation aide-memoires, auditable voucher reports, standardised loss packs and an action grid, built for handover from day one.

Result

Account restored to full compliance, with three of those artefacts adopted beyond the original unit and a Navy-wide policy instruction proposed.

Civilian relevance

Control design, audit remediation and process improvement that survives a change of owner.

3
Control Artefacts Adopted Beyond Unit
100%
Compliance Achievement
Proposed
Navy-Wide Policy Instruction
40+ → Single Figures
Open Inspection Findings, From Unsatisfactory to Full Compliance

The Challenge

In May 2024, I took over the supply chain account for a front-line warship that had been assessed as unsatisfactory by fleet logistics inspectors. The account had systematic compliance failures across inventory control, financial reconciliation and loss investigation processes.

The previous system was person-dependent rather than process-driven. When personnel rotated, institutional knowledge left with them. There were no standardised first-line controls, no audit trail for decisions, and no regeneration matrix to prevent the same failures from recurring under the next account holder.

The Core Problem

An account assessed as unsatisfactory does not fail because nobody worked hard enough. It fails because the controls that should make compliance routine either do not exist or cannot be followed consistently by whoever happens to hold the role.

Context & Stakes

The supply chain account manages:

  • Thousands of line items across multiple NATO Stock Numbers
  • High-value and attractive items
  • Financial accountability for expenditure and asset holdings
  • Compliance with Defence Equipment & Support (DE&S) policy and audit requirements
  • Readiness to deploy on short notice with verified inventory

An unsatisfactory rating means the account cannot assure what it holds, what it has spent, or whether losses have been investigated to the standard required for continued operations. That risk extends beyond the ship to fleet-wide confidence in supply chain data.

Approach

Rather than attempting to fix individual findings in isolation, I built the account around first-line controls: tools and processes that make compliance the default path, not the exceptional effort.

1. Root Cause Analysis

I mapped each inspection finding back to the missing control that should have prevented it:

  • Financial variances occurred because there was no validation step before commitment
  • Loss investigations stalled because there was no standardised pack structure
  • Audit trails were incomplete because there was no single source of truth for decisions

2. Control Design

For each gap, I designed a control artefact that:

  • Required minimal training – A new account holder could pick it up and use it immediately
  • Built the audit trail automatically – Compliance became a by-product of normal work
  • Scaled beyond this platform – Generic enough to apply to any similar account

3. Implementation & Testing

Each control was tested in live operations, refined based on real-world friction, and documented so it could be handed over intact. I also created a regeneration matrix: a lessons-learned framework that links findings to controls, so future inspections do not surface the same issues.

Controls Designed

Validation Aide-Mémoires

Checklists embedded into the financial commitment workflow that force verification of key data points before expenditure is authorised. Each check corresponds to a regulatory requirement, and the completed aide-mémoire becomes the audit evidence.

Auditable Voucher Reports

Standardised reporting templates that extract voucher data from the Defence ERP system and present it in a format optimised for inspection. Instead of investigators querying multiple systems, the report consolidates what they need to see, pre-validated.

Standardised Losses Packs

A structured template for loss investigations that ensures every required element (witness statements, physical search records, financial impact assessment, corrective actions) is captured in a consistent sequence. This pack structure has been adopted by another unit and by the wider organisation for all loss cases.

Action Grid for High-Risk Findings

A prioritisation matrix that maps inspection findings to risk level and assigns mitigation actions with accountable owners and deadlines. This grid became the single source of truth for remediation progress, visible to leadership and inspectors alike.

Defence ERP
Excel (Advanced)
Audit Frameworks
Process Mapping
Lean Six Sigma Principles

Who I briefed and what they decided

I presented the control-redesign recommendations to the Logistics Officer, who consolidated them alongside the misallocated-expenditure findings into a submission to the Navy's procurement policy directorate for their review. That review is ongoing; no decision has been communicated back yet.

Outcomes

  • Full Compliance Achieved – Open fleet logistics inspection findings reduced from 42 (Unsatisfactory) to 9 with one still red-rated (Satisfactory revisit), to single figures with no red-rated findings, the remaining minor pickups corrected within two weeks, by the most recent inspection, at which point the account was assessed fully compliant
  • 3 Control Artefacts Adopted Beyond Unit – Standardised losses pack adopted by another unit and by the wider organisation; S82 financial template adopted for upkeep cycles; standardised stores robbery form now in use fleet-wide
  • Process Improvement, Not Person Dependency – The controls were embedded in the workflow rather than individual expertise, designed to be handed over intact, and were handed over in September 2026
  • Navy-Wide Policy Instruction Proposed – Control design lessons informed a proposed policy update to prevent similar failures across the fleet
  • 80% Reduction in Financial Liability – Delivered through two workstreams on this account: closing 15 loss cases through asset verification and internal investigation, and the inspection-finding reduction above. A separate initiative from the £2.4M finding, which came from a review of annual inventory demands on an adjacent account rather than asset verification

The Inspection Trajectory

An early inspection rates the account Unsatisfactory, with 42 open findings across stock-taking, loss-reporting and consignment-discrepancy controls. A revisit some months later rates the account Satisfactory, with open findings down to 9, one of them still red-rated. By the most recent inspection, only a handful of actions remain, none red-rated, the outstanding minor pickups corrected within two weeks, and the account is assessed fully compliant. Alongside that, 15 loss cases are closed through asset verification and internal investigation over the same period. Resolving those findings is what held the account's stock-taking, loss and consignment-discrepancy KPIs steady, and together with the closed loss cases accounts for the 80% fall in financial liability.

Transferable Impact

The controls built for this account are now in use beyond the original unit, which is the real measure of success: enterprise-level process improvement, not localised firefighting.

Lessons Learned

Design for Handover From Day One

If a control cannot be used by a successor without its designer in the room, it is personal knowledge rather than a control. Every artefact I designed was tested by asking: "Could the next person pick this up and run with it?"

Compliance Should Be the Path of Least Resistance

People do not fail to comply because they are careless. They fail because compliance is harder than non-compliance. If a process makes the compliant action the easiest action, compliance becomes automatic.

Build Once, Apply Widely

The controls that fixed this account were generic by design. Two different classes of vessel have different inventories, but the control logic (validate before commit, standardise investigation packs, maintain an audit trail) applies to both. That generalisability is what made these artefacts adoptable beyond the original context.

Document the "Why," Not Just the "How"

Every entry in the regeneration matrix carries the reasoning: why the control exists, which finding it mitigates, and what happens if it is not followed. That context is what allows future account holders to make informed decisions when circumstances change.

Civilian Relevance

Control design, audit remediation and process improvement that survives a change of owner: the same discipline a controls-assurance, internal audit or third-party risk function is built around, whatever the account happens to hold.

Inspection findings and financial figures drawn from official appraisal records and correspondence are described here in general terms only; no internal documents, other individuals, or classified detail are reproduced.

Get in touch

If this evidence is relevant to a role you're hiring for, I'd welcome a conversation now.

Full CV with your direct number, or to discuss a role: start a conversation here.