Recovering a Non-Compliant Account at NATO SHAPE

The Challenge

I took over as Unit Application Administrator (UAA) at the European Joint Support Unit (EJSU), a tri-service support unit based at NATO's Supreme Headquarters Allied Powers Europe (SHAPE), during the period when the unit had to rectify shortfalls found in a prior assurance inspection ahead of a mandatory revisit.

The unit's logistics account, including ammunition accounting, had been assessed as non-compliant against the Army's own logistics assurance framework, a different standard to the Royal Navy's own stores-accounting regulations. As the only Royal Navy rating in a tri-service unit, I held the account's day-to-day accounting responsibility as UAA under segregation of duties, while formally listed as second-in-charge, a reflection of unit structure rather than a lesser share of the work.

Context & Stakes

EJSU provided firm-base logistics support to UK military and MOD civilian personnel and their dependants serving with NATO and the EU, across 31 locations in Europe and Turkey. The account under review covered general stores, uniform and specialist clothing, and ammunition, for a diverse and demanding tri-service population.

A mandatory revisit was already scheduled. Failure to close the shortfalls identified at the first inspection risked a second non-compliant finding, with the accountability gap it exposed left open across the unit's full footprint in the meantime.

Approach

Rather than closing individual findings in isolation, I focused on the structural gaps that had produced them: inconsistent naming conventions, no single source of truth for records, and no standard template tying the account's data to the tri-service systems it was being assessed against.

I worked with the unit's RQMS (Regimental Quartermaster Sergeant) to make sure the fixes held up against Army assurance expectations specifically, not just against what I was used to from Royal Navy stores accounting, and to embed the new practice across a unit where every other rating and rank came from a different service.

Artefacts Created

Restructured Asset Naming Conventions

Rebuilt the unit's asset-in-use naming conventions from the ground up, so that every item could be traced consistently across the account rather than relying on ad hoc local naming that varied by who had entered it.

Central Records Branch

Established a new Central Records Branch to hold a single, consistent source of truth for the unit's accounting records, replacing a position where records had been dispersed and inconsistently maintained.

MIR Template

Created a new MIR template that brought the unit's records in line with MJDI (the tri-service inventory system) and DLF policy, so the account's data mapped cleanly onto the systems and standards it would actually be assessed against.

Outcomes

• Account Recovered to Full Compliance – The account moved from non-compliance to full compliance at the scheduled revisit, in approximately nine months
• Three Artefacts Created and Adopted – The naming convention restructure, Central Records Branch, and MIR template were all built personally and remained in use as the account's standard practice
• Recognised at the Inspection – The inspecting Senior Warrant Officer singled me out during the revisit, described in my Logistics Inspection feedback as being "of infallible character with impeccable attention to detail"
• Rated Against a Wider Peer Group – Placed first of five Leading Hands and Corporals reported on by my First Reporting Officer for that tour

Lessons Learned

A Title Doesn't Always Describe the Work

Being formally listed as second-in-charge, because I was the only Royal Navy rating in a tri-service structure, said nothing about where the actual accounting responsibility sat. As UAA, that responsibility was mine under segregation of duties regardless of where the org chart placed me.

Different Frameworks, Same Underlying Discipline

An account found non-compliant against Army assurance standards and an account found non-compliant against Royal Navy stores regulations are the same underlying problem: the record does not match what is actually held, and the audit trail cannot prove otherwise. Learning to close that gap under someone else's framework, rather than my own, is the same skill applied further from home.

Structural Fixes Outlast the Person Who Built Them

None of the three artefacts here depended on me personally to keep working. That was deliberate: a naming convention, a records branch, and a template are all things a successor can pick up without the context I had in my head.