Skip to main content
Logistics & diversifiedUAEIn build

Designing assignment, leave and document-expiry automation for a Gulf fleet

This programme is in build. We will publish outcomes only after its pilot is complete and the client has cleared them for publication.

A field coordinator and supervisor reviewing a route plan beside an unbranded vehicle.
Client
Diversified group, transport & real estate
Operating scale
Large multi-site fleet and overseas workforce
01 / The starting point

The operating situation

A Gulf group running a large transport operation had two problems that looked unrelated and were not. First, the assignment picture — which driver is on which vehicle, which bus is covering which route, who is on leave — was maintained by coordinators holding it in their heads and in spreadsheets. Second, a largely overseas workforce carried visas, passports and licences with expiry dates that nobody was systematically watching until something lapsed.

02 / Delivery scope

Inside the workflow

  1. 01

    Modelled the real assignment rules, including qualification and route constraints

  2. 02

    Designed assignment and leave-cover coordination against live availability

  3. 03

    Designed document-expiry tracking with escalating reminders

  4. 04

    Specified worker contact by voice and message in the languages they use, rather than an app they would not install

  5. 05

    Defined escalation to a named human coordinator on any exception

The system scope

An operations layer is in build for driver-to-vehicle assignment, leave and replacement coordination, and workforce document-expiry tracking, with worker contact in the languages they use.

An operations lead reviewing a flagged exception in a workflow map.
03 / The published record

Current programme status

This programme is in build. We will publish outcomes only after its pilot is complete and the client has cleared them for publication.

04 / Limits and evidence

The operating boundary

This is a current delivery programme, not a completed deployment. Field automation will succeed or fail on whether people who do not sit at desks engage with it; that is the adoption question the pilot is designed to test.

Read the evidence and publication record
Client disclosure
Identity withheld under confidentiality.
Published status
In build
Result evidence
No outcome is published while this programme remains in build.
Client reference
Shared only with the customer’s permission.

We publish a client name only where the client has approved that disclosure. We publish a number only where it is measured and cleared for public use. A missing number means either we are not authorised to publish it or we do not have a measurement we would defend. References and deeper evidence are shared only with the customer's permission.