Driver Management &
Compliance Platform
with Real-Time Fleet Compliance

Fleet operators in the private hire and taxi sector manage hundreds or thousands of drivers who each carry a stack of time-sensitive credentials — licenses, insurance policies, permits, medical certificates. When any one of those documents lapses, the driver is non-compliant and the operator faces regulatory exposure. The traditional approach is spreadsheets, calendar reminders and manual follow-ups — a system that works until the fleet scales past the point where a single admin can keep every date in their head.

Our client — a major private hire fleet operator running on a cloud-based taxi dispatch platform — had exactly this problem. Driver records lived partly in the dispatch system, partly in shared drives, and partly in email threads. MVR checks were requested manually through a third-party portal with no connection to the onboarding flow. Trip data sat inside the dispatch platform but was not aggregated in a way that supported workload analysis or payment reconciliation. The brief was clear: build a single platform that owns the driver lifecycle end-to-end, stays in real-time sync with the dispatch platform, automates compliance monitoring, and gives both dispatchers and drivers the visibility they were missing.

Webhooks beat polling — but only if you treat them as infrastructure

The first architectural decision was how to keep the platform in sync with the dispatch system. Polling the dispatch API on a timer would have been simpler to implement, but it introduces latency, wastes API quota on no-change checks, and creates a window where local data is stale. We went with dedicated webhook endpoints that the dispatch platform calls the moment a driver profile, trip status or shift event changes. The trade-off is that webhook infrastructure needs to be robust: idempotent handlers, dead-letter queues for failed deliveries, and replay mechanisms for the inevitable moment when a downstream service is temporarily unavailable. Treating webhooks as first-class infrastructure rather than a convenience feature is what made the bidirectional sync reliable enough for dispatchers to trust it as their single source of truth.

Compliance monitoring is a data problem, not a reminder problem

The operator’s previous system for tracking credential expirations was calendar reminders and shared spreadsheets. That approach fails at scale because it depends on a human remembering to check. We reframed driver document compliance monitoring as a data problem: every credential has an expiration date, and the platform should surface every date that falls within the alert window automatically. The compliance dashboard is a materialized view that recalculates whenever a document is uploaded, an MVR result arrives, or a date threshold is crossed. Dispatchers no longer search for problems — the dashboard pushes problems to them, sorted by urgency. The difference between “we think we’re compliant” and “we know we’re compliant” is whether the system can answer that question without anyone asking.

MVR automation removed the slowest step in onboarding

Before the platform existed, requesting a Motor Vehicle Record through SuperVision meant logging into a separate portal, entering driver details, waiting for the report, and manually attaching the PDF to the driver’s file. That was the single biggest bottleneck in the onboarding flow. We integrated the SuperVision API so the platform programmatically initiates the MVR request the moment a new driver record is created, polls for completion, and stores the result directly in Azure Blob Storage linked to the driver’s profile. Recurring checks follow the same path on a configurable schedule. The dispatcher never touches the SuperVision portal — the report simply appears in the compliance dashboard when it’s ready.

Custom auth was the right call for this use case

Off-the-shelf identity providers like Azure AD B2C or Auth0 are usually the pragmatic choice, and we default to them on most projects. For this platform, the operator needed granular, role-specific views that go beyond standard RBAC: dispatchers with regional scoping, supervisors who can see compliance data but not financial data, and drivers who can only access their own records and trip history. The permission matrix was complex enough that mapping it onto a third-party provider’s role model would have meant fighting the framework. We built a bespoke auth layer with custom claims, and the result is a system where adding a new permission takes a migration and a few lines of policy code rather than a reconfiguration of an external identity provider.

SMS integration earns its keep on operational alerts

Email is the default channel for most notification systems, and it is also the channel most likely to be ignored when a driver is on the road. We integrated TextRequest for the alerts that need to land immediately: credential expiration warnings, shift assignments, and compliance action items. The SMS channel runs through the same event engine as every other notification, which means dispatchers can see delivery status in the admin portal and the platform can escalate to a phone call or a manual follow-up if the SMS goes unacknowledged. The lesson: pick the channel that matches the urgency, not the channel that’s cheapest.

Why this reads differently from most fleet-tech write-ups

Most content on driver management platforms stays at the feature-list level — “compliance tracking, onboarding, reporting” — without explaining how the pieces actually connect or what happens when they don’t. We shared the webhook architecture, the MVR automation pipeline, the custom RBAC reasoning, and the compliance-as-data-problem framing because these are the decisions that determine whether a platform works at scale or collapses into manual workarounds. This system has been running in production for a major private hire fleet running on a cloud-based taxi dispatch platform. At DMexec, we don’t just consult on fleet platforms — we provide the dedicated .NET, React and Azure engineers who design, build and maintain them.

Related use cases: AI Medical Imaging Diagnostic Platform with CNN & Explainable AI • Offline Field Data Capture with D365 F&O & Power Platform