Logistics heads in Bangladesh multi-branch operators face a familiar Monday question: “How did we perform last week?” Answers built from depot phone calls and retyped spreadsheets arrive late, disagree branch to branch, and cannot support decisions before problems compound. Dashboards with fifty charts answer nothing; ten numbers compared consistently week over week answer almost everything.
Weekly KPI discipline connects operations to finance and commercial teams on shared facts. Vehicle utilization without fuel variance context misleads; on-time rate without billing lag hides cash flow risk. The metrics below fit one screen — branch comparable, trend visible, exception-owned.
Implement gradually: start with five KPIs until data quality supports ten. False precision from dirty trip close data destroys trust faster than no dashboard at all.
Present the weekly scorecard in the same Monday meeting with branch managers, finance representative, and commercial lead present — KPIs discussed without finance and commercial become operations trivia. When billing lag rises while utilization looks healthy, the conversation should immediately connect trip close discipline to cash flow, not defer to “accounts will chase.” Trend arrows matter more than single-week absolutes; a branch improving from poor to acceptable deserves recognition while still below target.
If data quality blocks a KPI — missing trip close, guessed fuel — fix the input before debating the number. Leadership credibility on dashboards dies when branch managers prove figures wrong twice.
1. Vehicle utilization rate
Active trip hours or revenue km versus available fleet hours — by branch and fleet class. Low utilization with high fixed cost is structural: too many units, wrong lane assignment, or garage backlog keeping vehicles off road. Utilization spikes above sustainable bands predict maintenance pain and driver fatigue next month.
Define “available” identically across branches before comparing — workshop planned vs breakdown should not be lumped ambiguously.
2. Cost per km by route class
Blend fuel, driver cost allocation, toll, maintenance reserve, and vendor hire where applicable — not fuel alone. Route-class cost per km exposes lanes that need rate renegotiation or load redesign. Fleet-wide average cost per km flatters loss-making contract loops.
- Update allocation assumptions quarterly
- Separate owned vs hired cost pools for clarity
- Flag routes above target band two consecutive weeks
3. Fuel variance versus norm
Percentage or litres above/below route-class norm — top five outlier vehicles or pairs weekly. Investigate before averages absorb the signal. Variance trending up fleet-wide may indicate pump price, load factor change, or seasonal traffic — not only driver behaviour.
4. Trip close rate within 24 hours
Percentage of completed trips closed with full document checklist within one day. Billing velocity and dispute prevention depend on this operational habit — finance KPI and ops KPI simultaneously. Branches below threshold get root-cause review: dispatch overload, driver literacy, system friction, or culture.
5. Garage downtime days
Vehicle-days off road for unplanned repair versus planned service. Rising unplanned share indicates preventive maintenance gaps or ageing fleet mismatch to lanes. Downtime by vehicle identifies lemons worth divesting.
6. On-time first-trip departure rate
First-trip punctuality predicts whole-day performance in depot-centric models. Late first wave rarely recovers schedule without overtime or missed windows. Measure at gate out against planned time — not client arrival, which includes variables downstream.
7. Billing cycle lag and open exception count
Days from trip close to invoice generation — cash flow metric, not finance-only. Pair with count of unresolved exceptions: incidents, billing disputes, document gaps carried forward. Rising open exceptions predict client escalation and month-end fire drills.
From dashboard to decision in the same meeting
Each KPI on the weekly scorecard should have named owner and one allowed action when red — not open-ended discussion. Example: fuel variance red triggers garage or coaching review by Wednesday; billing lag red triggers finance-ops huddle same day. Without allowed actions, dashboards become wallpaper.
Archive scorecards monthly — trend review at quarter end reveals whether interventions worked. Branch that stayed red on close rate eight weeks despite meetings needs structural fix: staffing, system friction, or leadership gap — not ninth reminder email.
When two KPIs conflict — high utilization with rising fuel variance — discuss trade-off explicitly in Monday meeting rather than celebrating one while ignoring other. Integrated fleet leadership reads patterns across metrics, not single hero numbers.
Common mistakes to avoid
Publishing KPIs without branch manager accountability produces charts nobody acts on. Changing metric definitions weekly prevents trend comparison — freeze definitions for a quarter. Another mistake is fuel-only focus while utilization collapses — cost per km can look fine while revenue per vehicle falls.
Do not shame branches publicly on first week of measurement; baseline first, target second. Avoid KPIs you cannot data-support — guessed numbers destroy leadership credibility.
Export scorecard to PDF for owner or board monthly — narrative plus ten numbers beats verbal update. Highlight one branch improvement story and one intervention triggered by red KPI to make dashboard tangible for non-operations executives.
Quick action checklist
- Confirm ten weekly KPIs defined with frozen formulas
- Pull branch scorecard every Monday before 10 AM
- Investigate top five fuel outliers and lowest close-rate branch
- Review utilization vs downtime for structural capacity decisions
- Track billing lag trend and assign owner if rising
- Log open exception count with ageing buckets
- Share scorecard with commercial and finance same day
Red KPI three weeks running triggers written improvement plan from branch manager — plan due before fourth Monday review.
Build these KPIs from one operational data source via logistics fleet reporting, explore broader analytics in platform solutions, or request a demo to map metrics to your branch structure.