Client project - Compliance software

Building SAM into a complete driver compliance and DSP operations platform.

SAM needed a connected web and mobile compliance system for driver onboarding, evidence, documents, payments, scheduling, vehicles, incidents, and daily DSP operations.

Client SAM
Core product Compliance platform, web dashboard, and driver mobile app
Users DSP managers, account teams, compliance teams, and drivers
Business growth Roughly 60-65% growth supported during the engagement
SAM compliance platform screens showing a scheduling dashboard and mobile driver app views.
SAM web and mobile product screens, adapted for the Codtronix case study.

System delivered

One product layer for onboarding, compliance, scheduling, and field operations.

Instead of treating SAM as separate dashboard and app screens, the work connected the operational journey from manager setup to driver activity in the field.

01

Driver onboarding

Structured profile, evidence, contract, and readiness flows that move drivers from invite to operational status.

02

Compliance evidence

Document capture, OCR-assisted checks, DVLA and right-to-work workflows, and management review states.

03

Scheduling and DSP control

Depot-level planning, weekly schedules, route assignments, availability, no-shows, standby, and operational adjustments.

04

Driver mobile app

Field-ready app screens for clocking, schedule visibility, invoices, deductions, incident reporting, and communication.

05

Payments and account operations

Management views for invoices, deductions, payments, documents, exceptions, and exportable operational records.

06

Support and wellbeing

Driver-facing support journeys that keep help, updates, and wellbeing touchpoints inside the product loop.

Driver invited Evidence uploaded Checks reviewed Contract signed Schedule assigned Shift completed Incidents reported Payments visible

The challenge

Why the obvious build path was too risky.

Driver compliance and DSP operations involve many moving parts: document collection, licence checks, right-to-work evidence, payroll inputs, deductions, vehicle records, scheduling, incidents, and communication. When those workflows are split across paper, spreadsheets, calls, and disconnected tools, managers lose visibility and drivers wait longer before they can start work.

The approach

How the work was made smaller, clearer, and more accountable.

  1. Mapped the driver lifecycle from first onboarding step through compliance, contracts, scheduling, payments, incidents, deductions, and ongoing support.
  2. Designed connected web and mobile journeys so DSP, compliance, and account teams could manage evidence while drivers had simple field-ready app flows.
  3. Built the product around practical compliance workflows including OCR-assisted document handling, DVLA and right-to-work checks, reports, vehicles, shifts, messages, payslips, and wellbeing support.

The outcome

What the team gained beyond shipped code.

  • A complete compliance and operating layer for DSP driver management across web and mobile.
  • Roughly 60-65% growth in the business supported during the engagement, with day-to-day operational time and manual effort cut by around 30%.
  • Clearer manager visibility over driver progress, compliance status, operational documents, vehicles, payments, incidents, and reports.
  • A driver app experience for submitting documents, signing contracts, viewing schedules and payments, reporting issues, and communicating with management.

Discuss your context

Building software around real operational complexity?

Tell us which users, workflows, evidence, and systems need to connect. We will help turn the operating reality into a product your team can actually run.

  • See what should be built, simplified, or avoided
  • Leave with risks, constraints, and a credible next step
  • Talk to senior product and engineering people, not a script
It could be yours Show us the workflow, product idea, or system constraint you want to turn into an advantage.

We will help you decide what to build first, what to avoid, and how to move from messy context to usable software.