Platform Documentation

Resolt On-Demand is an end-to-end logistics execution platform designed for fleet operators, third-party logistics providers, and service organisations that manage large volumes of daily field tasks. The platform covers every stage of the logistics workflow — from inbound order ingestion through to proof-of-delivery capture and exception management.

The system is organised into three interconnected layers:

Before the system can generate its first route, the following data must be in place. Work through these steps in order — each depends on the previous.

Accounts represent the customers or clients on whose behalf deliveries and collections are performed. Every order is linked to an account, enabling per-client reporting and filtering throughout the platform.

Key Fields

• Account Name — the trading name displayed throughout the platform.
• Account Code — a unique short reference used for integrations and reporting.
• Account Type — classifies the account (e.g. Retail, Wholesale, Internal) for filtering and analytics.
• Contact Details — email, phone, and primary contact name.

Usage

When creating orders, the account is selected to associate the delivery or collection with the correct client. Account-level filtering is available in the analytics and order modules.

An order is the commercial instruction that drives task creation. Each order is linked to an account and a delivery or collection location, and generates one or more tasks that are ultimately assigned to routes.

Order Lifecycle

Consolidation

Multiple tasks destined for the same physical location can be consolidated into a single stop. When a consolidated task is actioned (failed or reassigned) from the dashboard, all tasks sharing the same location are automatically actioned together.

Task Types

Every task requires a location with precise GPS coordinates. Locations are reusable across orders and are the unit of consolidation when multiple tasks share the same stop.

Key Fields

• Name — a human-readable label for the stop (e.g. "Sandton City Mall").
• Address — the physical street address shown on the driver app and map views.
• Latitude / Longitude — GPS coordinates used for route optimisation and mapping.
• Location Group — optional grouping (e.g. by region or city) for filtering and reporting.
• Location Type — classifies the stop (e.g. Retail, Warehouse, Residential).

Tips

• Ensure coordinates are accurate to within ~10 metres for reliable route quality from the optimisation engine.
• Use Location Groups to organise large location sets by region — this makes filtering in the planning module much faster.

The Route Planning module is where daily operations are constructed. The planner reads all pending tasks for the selected depot and date, and uses the Navora Fleet Matrix Routing API to produce optimised routes across the available fleet.

Planning Workflow

Master Routes

For recurring operations with fixed stop sequences, Master Routes store a reusable template of locations. Instead of re-planning from scratch each day, a master route can be activated to pre-populate tasks for the planner.

The Dashboard is the real-time operational view for dispatchers and fleet managers. It provides an at-a-glance KPI summary at the top, a live vehicle map, and a detailed active routes table below.

KPI Cards

The four KPI cards at the top of the dashboard show live counts of active vehicles, active drivers, total deliveries (with done / pending / failed breakdown), and total collections. Each card includes a mini donut chart that updates automatically as routes progress.

Live Vehicle Map

The vehicle map plots current driver positions using live GPS telemetry. Vehicles are colour-coded by status: On Route Idle Alert. Click a marker to see driver and job details.

Active Routes Table

Each row in the active routes table represents one route. The columns show route number, driver, vehicle, execution date, route status, task counts, and a progress bar. Click any row to expand the task sub-table for that route.

Task Sub-Table

The expanded task list shows the sequence, location, task type, and current status for every stop on the route. For Failed tasks with a recorded exception, the exception name replaces the word "Failed" in the status badge. For Completed tasks, an info icon opens the captured results panel.

Route Map Modal

The map icon at the end of each route row opens the Route Map modal. This full-screen modal shows:

• All task stop locations plotted as colour-coded pins on an interactive Leaflet map.
• The planned route polyline (blue dashed) stored from the optimisation engine.
• The live tracking polyline (green solid) drawn from real-time GPS breadcrumbs.
• A stop list sidebar showing sequence, location name, and status badge. Failed stops display their exception name below the location name in red.

For any task that is not yet completed, failed, or cancelled, a dispatcher can take action directly from the dashboard task sub-table using the icon at the end of the row.

Fail a Task

Marks the task (and all tasks at the same location on the same route) as Failed. A exception reason must be selected from the categorised dropdown before the action can be confirmed. The exception is stored against each affected route task and:

• Displayed in place of "Failed" in the task sub-table status badge.
• Shown in the Route Map modal stop sidebar beneath the location name.
• Delivered to the driver's mobile app as a silent push notification containing the affected task IDs, location ID, and exception ID — enabling the app to update its local state without displaying an intrusive alert.

Reassign a Task

Moves the task (and all tasks at the same location) to a different driver's route for the same execution date. If the target driver has no existing route for that date, a new route is created automatically. Both drivers receive a visible push notification informing them of the change.

For any Completed stop in the Route Map modal, clicking the info icon opens the Results Panel — a slide-over on the right side of the map that displays every workflow field captured by the driver at that stop.

Supported Capture Types

Master Routes allow you to pre-define a fixed sequence of stops that repeats regularly (e.g. a daily milk-run to the same set of locations). Rather than re-planning from scratch each day, a master route can be activated to instantly generate the task set for the planner.

• Each master route has a name, associated depot, and an ordered list of locations.
• Master routes are not vehicles or drivers specific — they define the stops only. Driver and vehicle assignment happens at planning time.
• Activating a master route creates the necessary pending tasks for the selected execution date, ready for the route optimiser or manual assignment.

Each driver record represents a field team member who executes routes through the mobile app. Driver records control both the operational assignment (route, vehicle, depot) and mobile app authentication.

Key Fields

• Name & Contact — first/last name, phone, and email.
• Driver Status — Active, Inactive, or On Leave. Only Active drivers appear in the planning and dashboard dropdowns.
• Depot — the home depot that determines which routes and plans this driver is visible in.
• Notification Token — automatically registered by the mobile app on first login. Used to deliver push notifications for task assignments, reassignments, and silent data updates.

Vehicles are assigned to routes and carry capacity constraints that the Navora optimisation engine respects when building plans.

Key Fields

• Registration Number — the unique identifier shown on the dashboard and in planning.
• Vehicle Type — classifies the vehicle (e.g. Light Delivery, Heavy Truck, Bike) and maps to capacity profiles.
• Depot — the home depot for this vehicle.
• Vehicle Status — Active or Inactive. Only Active vehicles are available for route assignment.

A workflow is a sequence of data-capture steps that a driver must complete before marking a task as done in the mobile app. Workflows are scoped to a company and assigned per task type (Delivery or Collection).

Field Types

Workflow Items

Each item in a workflow has a name (label shown to the driver), a field type, an optional required flag, and for select/choice fields — a lookup list of allowed values configured under Workflow Item Lookups.

Exceptions are the reason codes a dispatcher selects when marking a task as failed from the dashboard. They are organised into categories that group related reasons together in the dropdown.

Structure

• Exception Category — a grouping label scoped to a company and task type (e.g. "Access Issues" for Delivery tasks).
• Exception — an individual reason under a category (e.g. "Gate Locked", "Customer Not Present", "Wrong Address").

Each exception can optionally define a resulting task status — if set, the system applies that status automatically when the exception is selected. An optional Microflow can also be linked to trigger additional automated steps.

Usage in the Dashboard

When a dispatcher clicks the action icon on a task row and selects Mark as Failed, the exception dropdown is populated with all categories and exceptions configured for the company and that task's type. The selected exception is stored on the route task and visible throughout the platform.

Microflows are lightweight automation sequences that can be triggered when a task reaches a specific state — for example, sending a customer notification when a delivery is completed, or creating a follow-up task when an exception occurs.

Microflow Items

Each microflow is made up of an ordered list of items, where each item represents one automated action. Actions can include HTTP webhooks, notification dispatches, or status transitions.

Each depot can be configured with its own set of operational defaults including opening and closing times, default address, GPS coordinates, and default workflow assignments per task type.

Default Workflows

The Depot Default Workflow configuration maps a workflow to a task type at the depot level. When an order is created without an explicit workflow, the depot default is used — ensuring drivers always have the correct capture steps regardless of how the task was created.

The Route Analysis module provides post-execution reporting across all routes for a selected depot and date range. It surfaces performance metrics that help managers identify inefficiencies, exception patterns, and driver performance trends.

Available Metrics

• Completion Rate — percentage of tasks completed successfully per route and per driver.
• Exception Rate — frequency and type of failures across the fleet, broken down by exception category.
• Planned vs Actual Distance — compares the planned route distance (stored at publish time) with the actual GPS track distance.
• On-Time Performance — measures adherence to planned time windows where configured.

The Resolt Driver App is a purpose-built mobile application that guides drivers through their daily route. It connects to the platform in real time and operates fully offline — buffering all events locally and syncing them reliably when connectivity is restored.

Core Capabilities

Data Sync Architecture

The mobile app uses a guaranteed delivery consumer pattern. All outbound events (task completions, captures, telemetry) are placed on a durable message queue and processed by the server-side consumer service. Even if the network drops mid-upload, the consumer retries until every event is persisted — ensuring the platform always holds a complete and accurate execution record.