Kelroy James / Case Studies / Logistics Movement Capability

Building a Compliant Movement Capability

Designing and delivering movement governance, customs compliance and inventory tracking for high-readiness multinational deployments, built from greenfield.

Role Project Lead & Compliance Designer
Timeline Apr 2017 – Dec 2017 (9 months)
Organisation Royal Navy (high-readiness unit)
Methodology PRINCE2 Project Governance

TL;DR

Situation

A high-readiness unit had no organic capability to track its own equipment or manage customs compliance for international movements.

Action

Built a PRINCE2-governed movement capability from greenfield, integrating HMRC, JSP 800 and JSP 916 requirements into the process itself.

Result

Zero financial liability exposure and full deployment tracking, validated live across four multinational exercises.

Civilian relevance

PRINCE2 project delivery against a live regulatory compliance obligation.

Zero
Financial Liability Exposure
100%
Operational Deployments Tracked
200 Miles
Round-Trip Drive Eliminated Per Consignment
4 Exercises
Multinational Deployments Sustained (Open Spirit, Sea Breeze, Northern Challenge, Joint Warrior)

The Challenge

A high-readiness unit deploying globally shouldn't depend on someone else's systems to know where its equipment is. That dependency created operational risk: when external tracking systems failed or access was delayed, the unit had no organic capability to account for equipment in transit or confirm arrival.

The Strategic Problem

Closing this gap meant building a movement organisation from nothing: governance, infrastructure, procedures, and the customs compliance that underpinned it all. The project had to deliver end-to-end capability within the deployment cycle, not as a future-state aspiration.

The Cost of the Old Way: A 200-Mile Round Trip for a Label

Before this project, when consignment labels were needed to move equipment, the only option was for someone to drive upwards of 200 miles round trip to collect them in person, a full day's tasking, plus fuel and vehicle wear, spent on paperwork rather than diving support. That was the situation before I took over. VITALS, the tracking system this project installed, removed that journey entirely.

The Wider Stakes: Reliable Commitment to Multinational Exercises

A unit's ability to commit confidently to multinational exercises depends on being able to move and account for its own equipment without relying on someone else's paperwork. Building that capability mattered beyond the administrative case for it.

Specific Challenges:

  • No existing infrastructure: Unit had no organic consignment tracking system or movement management capability
  • External system dependency: Relied on external organisations for equipment visibility, creating operational risk
  • Customs compliance gap: International deployments exposed the unit to financial liability without documented HMRC compliance
  • Concurrent deployments: High operational tempo required capability to track multiple concurrent movements across different theaters
  • Multinational context: Deployments involved NATO partners, requiring compatibility with allied tracking systems and customs regimes
  • Contractor integration: Hardware installation required coordination with external contractors while maintaining operational readiness

Rob Jones' Assessment (Project OIC)

Rob Jones (now Project Manager at Thales, then Officer in Charge) described this project context in his LinkedIn recommendation:

"His application of the defence procurement model and capability to network with all stakeholders to achieve the required outcome is second to none. If I needed a supervisor to deliver a general defence task then he could always be relied on to deliver and didn't let the unit down."

This project was the operational proof of that assessment.

Project Governance (PRINCE2)

Project Initiation Document (PID)

Authored comprehensive PID following PRINCE2 methodology, establishing formal governance for the full delivery lifecycle.

PID Components:

1. Stakeholder Mapping (Power/Interest Matrix)

  • High Power, High Interest: Unit Command, HMRC liaison, NATO exercise coordinators
  • High Power, Low Interest: Higher formation command, Defence Equipment & Support (DE&S) procurement
  • Low Power, High Interest: Diving team leaders (end users), contractor project managers
  • Low Power, Low Interest: Wider supply chain community (monitor for lessons learned)

2. PESTLE Analysis

  • Political: NATO interoperability requirements, allied exercise commitments
  • Economic: Budget constraints, contractor cost control, financial liability exposure
  • Social: User adoption, cultural shift from external dependency to organic ownership
  • Technological: Tracking system compatibility, hardware installation constraints
  • Legal: HMRC customs requirements, JSP 800/916 compliance, data protection
  • Environmental: Baltic sea conditions, equipment ruggedisation requirements

3. SWOT Analysis

  • Strengths: Greenfield opportunity, command support, PRINCE2-trained project lead
  • Weaknesses: No existing infrastructure, limited in-house technical expertise
  • Opportunities: Establish best practice for other high-readiness units, reduce financial liability
  • Threats: Deployment schedule pressure, contractor delays, budget overrun risk

4. Technical Risk Management

Identified and mitigated risks across technology integration, contractor performance, user adoption, and compliance validation:

  • Hardware failure in field conditions → Ruggedised equipment specification, redundancy planning
  • Contractor installation delays → Fixed-price contract with liquidated damages clause
  • User resistance to new procedures → Early engagement, training programme, champion identification
  • Customs compliance uncertainty → HMRC liaison established, legal review of SOPs

Contractor Integration

Managed contractor relationship for hardware installation while maintaining unit operational readiness:

  • Defined technical specifications and acceptance criteria in contract
  • Coordinated installation windows around deployment schedule
  • Conducted Factory Acceptance Testing (FAT) before field deployment
  • Managed change control process for scope variations

Regulatory Controls Design

The Compliance Problem

International movements carry financial liability if customs requirements aren't met. Equipment moving between countries without proper documentation exposes the organisation to tax, duty, and penalty charges. For a high-readiness unit deploying frequently, this risk compounded with every movement.

Regulatory Framework Integration

Designed Standard Operating Procedures (SOPs) that aligned unit movements with three regulatory regimes simultaneously:

  • HMRC Customs Requirements: UK customs authority for international goods movements
  • JSP 800 (Defence Movements): Ministry of Defence movements policy and procedures
  • JSP 916 (Tax and Duty): Financial liability management for international movements

SOP Design Approach

Created SOPs that embedded compliance into the movement process rather than treating it as a separate audit activity:

1. Pre-Movement Compliance Checklist

  • Customs documentation requirements by destination country
  • Duty relief eligibility assessment (temporary export vs. permanent transfer)
  • Commodity classification and valuation
  • Export license requirements (dual-use goods screening)

2. Movement Execution Controls

  • Consignment manifest generation (linking inventory system to customs declaration)
  • Packing list verification (declared vs. actual contents)
  • Seal integrity protocols (tamper-evident packaging for customs inspection)
  • Carrier instruction and documentation handover

3. Post-Movement Reconciliation

  • Receipt confirmation and discrepancy reporting
  • Customs clearance evidence retention
  • Temporary export return tracking (ensuring duty-free equipment returns to UK)
  • Financial liability closure (confirming no outstanding duty exposure)

Outcome: Auditable Compliance Position

The unit gained an auditable compliance position it hadn't previously held. In the event of HMRC or MoD inspection, the unit could demonstrate:

  • Documentary evidence of customs compliance for every international movement
  • Alignment with JSP 800 and JSP 916 policy requirements
  • Zero financial liability exposure from improper movements
  • Segregation of duties and approval controls preventing unauthorised movements

Delivery & Operational Validation

Infrastructure Installation

Installed VITALS (Visibility In Tracking Assets Logistics Systems), the unit's organic consignment tracking system, with contractor support:

  • Hardware deployment: ruggedised tracking units, scanning equipment, mobile connectivity
  • System integration: linking tracking platform to unit inventory database
  • User training: movement coordinators, diving team leaders, command staff
  • Documentation: user manuals, troubleshooting guides, escalation procedures

Field Validation: Four Multinational Exercises

The true test of any movement capability is whether it works under operational conditions. VITALS went live in time to support the unit's exercise programme that autumn, and was validated in the field on Exercise Open Spirit (Latvia) before going on to sustain the unit's deployments to Exercise Sea Breeze (Ukraine), Exercise Northern Challenge, and Exercise Joint Warrior (UK).

Milestone Timeline

  • 15 Jul 2017: Project Initiation Document approved
  • 20 Aug 2017: VITALS hardware and software installed
  • 16 Sep – 10 Oct 2017: Initial training delivered
  • 5 – 10 Oct 2017: Field-tested on Exercise Open Spirit, Latvia
  • 20 – 25 Oct 2017: User Acceptance Testing
  • 28 Oct 2017: Project closure and review

Operational Validation Criteria

  • Real-time visibility: Command staff could track equipment location and status during transit
  • Concurrent deployments: System handled at least two simultaneous movements across different countries, the threshold set as a critical success factor at project initiation
  • Customs clearance: All movements cleared customs without delay or financial penalty
  • User adoption: Diving teams used the system organically, without constant oversight
  • System resilience: Hardware functioned in Baltic sea conditions (salt spray, humidity, temperature variation)

Specific Deployment Scenarios Validated:

  • Exercise Open Spirit (Latvia): multi-vehicle convoy with mixed cargo (diving equipment, vehicles, consumables)
  • Exercise Sea Breeze (Ukraine) and Exercise Northern Challenge: forward deployment through multiple customs regimes
  • Exercise Joint Warrior (UK): return movements, confirming duty-free status maintained
  • Emergency resupply: expedited movement of critical equipment with accelerated customs clearance

Outcome: Organic Capability Delivered

The unit gained end-to-end inventory visibility and the ability to sustain concurrent high-readiness deployments on its own infrastructure, with regulatory assurance built into the movement process rather than checked after it.

This meant:

  • Operational independence: No longer dependent on external systems for equipment visibility
  • Command confidence: Real-time situational awareness of equipment location and status
  • Financial assurance: Zero liability exposure from non-compliant movements
  • Scalability: Capability to handle increased operational tempo without infrastructure failure

Outcomes

  • Zero financial liability exposure achieved: All international movements compliant with HMRC, JSP 800, and JSP 916; no duty charges or penalties incurred
  • 100% operational deployment tracking: Every movement from project go-live tracked through organic system, proving capability under operational pressure
  • 200-mile round trip eliminated: VITALS removed the previous requirement to drive to collect consignment labels in person, freeing personnel time for diving support instead
  • Multinational exercise validation across 4 exercises: Field-tested on Exercise Open Spirit and sustained through Exercise Sea Breeze, Exercise Northern Challenge, and Exercise Joint Warrior, demonstrating interoperability and resilience, and sustaining the unit's ability to commit to Defence Engagement exercises
  • PRINCE2 project governance delivered on time and budget: PID-documented scope delivered within 9-month timeline and approved budget envelope
  • Contractor integration successful: Hardware installation completed without operational impact; FAT and UAT acceptance criteria met
  • SOP suite adopted as unit policy: Customs compliance SOPs embedded in unit standing orders, ensuring sustainability beyond project closure
  • Organic capability independence: Unit no longer dependent on external systems for equipment visibility during deployments
  • Concurrent deployment capability: Infrastructure scaled to handle multiple simultaneous movements across different theaters

Rob Jones' Validation

From Rob Jones' LinkedIn recommendation (OIC during this project):

"Of all the logistics specialists I worked with over 12 years if I could select one to support my engineers on the ground it would be Kelroy. He could always be relied on to deliver and didn't let the unit down."

This project was the proof: greenfield capability delivery, from governance to operational validation, with zero failures.

Civilian Relevance

Skills Demonstrated

PRINCE2 Governance
Capability Delivery
Customs Compliance
Risk Management
Stakeholder Mapping
PESTLE Analysis
SWOT Analysis
Contractor Integration
SOP Design
Regulatory Alignment
Process Design
User Training

Civilian Sector Applications

Supply Chain Manager / Logistics Operations Manager:

  • Designing movement capabilities for organisations with international operations
  • Building customs compliance processes for cross-border trade
  • Implementing inventory tracking systems with regulatory requirements integration
  • Managing contractor relationships for infrastructure projects

Project Manager (Infrastructure / Systems Implementation):

  • PRINCE2 project governance for greenfield capability delivery
  • Stakeholder management using power/interest matrix and structured engagement
  • Risk management through PESTLE, SWOT, and technical risk registers
  • Contractor integration and acceptance testing (FAT/UAT)

Compliance Manager (Trade / Export Control):

  • Designing SOPs that embed regulatory requirements into operational processes
  • Aligning multiple regulatory regimes (customs, tax, trade policy) into coherent controls
  • Building auditable compliance positions with documentary evidence trails
  • Managing financial liability exposure from international movements

Management Consultant (Capability Development):

  • Diagnosing dependency vulnerabilities (reliance on external systems)
  • Designing organic capabilities that reduce operational risk
  • Delivering complex projects with PRINCE2 methodology in high-pressure environments
  • Validating capability under real-world conditions, not just trial scenarios

Why This Project Matters for Civilian Transition

This project demonstrates the full lifecycle of capability delivery in a regulated, high-stakes environment:

  • Greenfield delivery: Built from nothing to operational capability in 9 months
  • Regulatory complexity: Integrated HMRC, JSP 800, JSP 916 into coherent SOPs
  • Stakeholder management: Navigated command, contractors, NATO partners, customs authorities
  • Operational validation: Proved capability under real-world pressure, not just trial conditions
  • Financial assurance: Delivered zero liability exposure through systematic compliance design

For civilian employers, this translates directly to:

  • Infrastructure project delivery (systems implementation, process re-engineering)
  • Trade compliance programmes (export control, customs, duty management)
  • Supply chain resilience (reducing external dependencies, building organic capabilities)
  • PRINCE2 governance (formal project management in regulated sectors)

The skills are commercial-grade. Only the sector differs.

Nine Years On: A Fleet-Wide Priority

In my own professional experience, the Royal Navy circulated a fleet-wide call for volunteers to build "movements" specialism in early 2026. The unit-level fix this project delivered in 2017, an organic movements function that didn't depend on borrowing capacity from elsewhere, anticipated that same need years before it became a fleet-wide priority.

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.