Last-mile performance dashboards
We define every measure once and build your delivery performance dashboard for Bahrain, the UAE, Qatar, Saudi Arabia, Oman and Kuwait in three views: daily for operations, weekly for the network and one page for the board. Operations and finance read the same number.
What we do
We tie dispatch, cost and service to one set of definitions and build the reporting your delivery network runs on: a metric dictionary, a daily operations board, a weekly network review and a monthly page for the board. All three views trace back to the ledger.
What you get
- A metric dictionary that fixes each definition, source field and owner.
- A daily operations board covering orders, capacity, waits, exceptions and cost to date.
- A weekly network review by zone, provider and vehicle type, with variances against plan.
- A one-page board view showing cost per drop, contribution, service level and capital in the fleet.
- A reconciliation routine that ties the dashboard to the ledger each month.
What changes
- Operations and finance read one reconciled cost.
- A day's report reaches managers sooner after the day ends.
- The number of metrics with more than one live definition is reported, so every conflict has an owner in the dictionary.
- Managers use the dashboard in weekly reviews.
- Board decisions cite a dashboard figure.
The problem we solve
Dispatch platforms offer many charts and none of them shows cost. Finance sees the cost a month later and cannot place it by zone. The result is two reports that never agree, and a board that is told the network is performing without evidence in money.
Signs you need it
- On-time delivery has three definitions in three reports.
- The daily view cannot be tied to the month-end cost.
- Managers build their own spreadsheets and defend them.
- The board pack has a page on deliveries and none on delivery profit.
- Nobody notices a zone sliding until the month is closed.
Who it is for
Operations heads, finance leads and chief executives of delivery businesses, retail and restaurant groups and 3PL operators, who see different figures for the same week from dispatch, finance and partners.
Why At Par
Qasim Abbas brought more than seven companies at Nexxo Pay and QPay International onto one set of numbers, so every figure on your dashboards reconciles to the ledger.
How we work
We build in the reporting tool the group already runs, on dispatch data including Tookan exports, partner statements and your ledger. See how fees work.
Questions boards ask
- How many measures should the board see?
- One page. The detail sits in the weekly and daily views, and the board page links each figure to the view behind it.
- Can dashboards cover partners as well as our own fleet?
- Yes. Partner data is brought onto the same definitions, which is the basis for the service-level monitoring of each one.
The next step
Put your current delivery report in front of the Managing Partner at a private briefing. We mark the three figures a board would question first and say what it takes to settle them.
Related
- Delivery SLA definition and monitoringMeasurable delivery service levels with defined clocks, tolerances and credits, and the monthly monitoring behind them.
- Tookan implementation and configurationTookan configured on your account so dispatch data carries the cost and performance fields finance needs.
- Vehicle and rider unit economicsContribution per vehicle-day and rider, modelled by type, shift and zone, so capital goes where the fleet earns.
Bring last month. Leave with a score.
Sit down with Qasim Abbas. One table, your numbers, and a clear read on where you stand against par.