Sample War Map
Transport and logistics War Map
Regional road haulier · 3 depots in Auvergne-Rhône-Alpes · 310 employees, 190 trucks
Telematics records every hour of waiting, yet extras are billed only when a driver writes them on paper. Orders are typed by hand, and subcontractor checks depend on memory.
A War Map is an operating map built from real cases and expert interviews. It shows where the business is fragile, what that costs, and what to fix first.
What you receive
- 01Operational Reality
How the work really runs: people, systems, handoffs and exceptions.
- 02Findings
What it costs: quantified problems, process gaps and key-person risks.
- 03Implementation plan
What to fix first: prioritized systems, timeline and value drivers.
30 minutes. We recommend the right starting point.
Regional road haulier · 3 depots in Auvergne-Rhône-Alpes · 310 employees, 190 trucksThis War Map shows how we turn an operational review into an implementation plan. The dates show a possible sequence; the scope and schedule of a real engagement are agreed with you.
Operational Reality
This is what we deliver: a map of where the business is fragile, what it costs, what to automate first, and which systems should exist so leadership can stop carrying the operation by hand.
Illustrative five-week work plan, June 1 to July 3, 2026. Eleven interview roles across eight departments, two depots shadowed, one ride-along and seven systems. The final week combines validation and handover.
Five-week sample timeline · five work blocks
One row per week. Open a week to see each working day.
- Week 1Jun 1 to Jun 5
Orders, planning and the road
Scope set on two depots. Order intake, the planning board, subcontracting and a delivery round shadowed.
People: Patrick Rochette, Valérie Chambon, Mélanie Grangier, Stéphane Ferrand, Cédric Bonnefoy, Aurélien Brun
Daily detail · 5 days
Jun 1Kickoff and scopeAgreed the scope: order intake, planning and subcontracting, extras billing, damage claims, driver compliance and fuel surcharge. Lyon and Clermont-Ferrand depots shadowed; Valence covered through data.
Patrick Rochette · CEOTMSExcelJun 2Order intake shadowShadowed 6:30 to 12:00. Counted 238 orders: 151 by email, 43 by phone, 44 through customer portals. One in eight needed a call back for a missing slot, tail lift or reference.
Mélanie Grangier · Customer Service LeadOutlookTMSJun 3Planning board, LyonThe board is an Excel file rebuilt from a TMS export every afternoon. Driver hours checked truck by truck in telematics. A 17:00 reshuffle for 31 late orders; the board closed at 18:40.
Stéphane Ferrand · Planning ManagerExcelTMSTelematicsJun 4Subcontracting deskAbout 290 trips a week go to subcontractors, found by phone and on the freight exchange. Last prices paid are in a notebook. Carrier documents are checked when there is time.
Cédric Bonnefoy · Subcontracting ManagerExchangeOutlookExcelJun 5Ride-along from 5:00Seven drops. Two waits beyond free time, 1 h 50 and 2 h 15, both recorded in telematics and neither written on the CMR. The ePOD photo upload failed twice in low coverage.
Aurélien Brun · Driver Team LeaderePODTelematics - Week 2Jun 8 to Jun 12
Billing, claims and compliance
Extras billing, fuel surcharge, claims and driver documents traced; second depot compared.
People: Samira Ouali, Brigitte Vial, Franck Duval, Olivier Charrier, Kevin Bayle
Daily detail · 5 days
Jun 8Billing and extrasInvoicing runs monthly from the TMS. Extras are added only when found on paper CMRs or reported by planners. Free time and rates per customer sit in contract PDFs.
Samira Ouali · Billing ManagerTMSSageExcelJun 9Fuel surcharge runThe monthly CNR diesel index is copied into Excel, 14 customer formulas are recalculated and rates are typed into the TMS. About 10 hours a month. In March, 6 customers were billed at the previous rate.
Brigitte Vial · CFOExcelTMSJun 10Damage claims reviewAbout 35 claims a month. Each file needs the CMR with reserves, photos, arrival times and the driver's account. About 3 hours per file; 40% of 2025 files had no photo.
Franck Duval · Claims and Quality ManagerePODTelematicsSageJun 11Driver hours and documentsDriver cards downloaded every 28 days and vehicle units every 90 days, chased by hand. Licences, medical checks and FCO training dates sit in one Excel file. Three FCO certificates expire within 30 days, unflagged.
Olivier Charrier · Fleet and Compliance ManagerTelematicsExcelJun 12Clermont-Ferrand depotSame work, different board: Clermont uses its own Excel layout and its own subcontractor list. Extras are logged in a paper notebook at the desk.
Kevin Bayle · PlannerExcelTMSExchange - Week 3Jun 15 to Jun 19
Internal analysis
Waiting time, order channels, subcontractor files and claims measured against records.
People: No interviews this week
Daily detail · 5 days
Jun 15Waiting-time sampleCompared 4 weeks of telematics stops with invoices. 610 waits beyond the agreed free time; 140 invoiced. Average value of an extra: €48.
TelematicsTMSJun 16Order intake sampleClassified one week of orders by channel and format: 80% manual. Measured keying time and the causes of call-backs.
OutlookTMSJun 17Subcontractor document auditChecked the files of 41 regular subcontractors: 7 expired URSSAF vigilance certificates and 2 insurance certificates past their date.
ExcelExchangeJun 18Claim file reviewReviewed 120 claim files from 2025: 40% without a photo, 22% without a reserve on the CMR, 38 days on average to close.
ePODSageJun 19Time allocation studyCoded shadowing notes and task logs for the 11 interview roles into five time categories.
- Week 4Jun 22 to Jun 26
Opportunities and plan
8 initiatives scored, extras rules tested on real trips, value model and roadmap built.
People: Samira Ouali, Stéphane Ferrand
Daily detail · 5 days
Jun 22Procedure vs practiceCompared documented procedures with observed practice for 18 workflows.
Jun 23Opportunity scoringScored 8 initiatives across 4 departments on value, complexity, compliance impact and dependencies.
Jun 24Extras rules checkTested draft extras rules on 50 real trips. Agreed which telematics statuses count as waiting, and that disputed lines go to the account owner.
Samira Ouali · Billing ManagerTelematicsTMSJun 25Value modelBuilt conservative and higher cases. Separated billed extras and subcontracting prices from released capacity.
Jun 26Roadmap and internal QASequenced the work so that extras capture starts first. Checked every figure against interview notes and source data.
- Week 5 · HandoverJun 29 to Jul 3
Validation and handover
Findings validated with department leads; War Map delivered and first owners named.
People: Stéphane Ferrand, Samira Ouali, Olivier Charrier, Patrick Rochette, Brigitte Vial, Valérie Chambon
Daily detail · 5 days
Jun 29Deliverable assemblyAssembled the War Map in three chapters: operational reality, findings and implementation plan.
Jun 30Validation with department leadsReviewed process maps and the hour register. One correction: the Valence depot already scans CMRs on return, which shortens the paper delay there.
Stéphane Ferrand · Planning ManagerJul 1Final QAFinal check of numbers, dates and dependencies. Handover pack prepared.
Jul 2Pre-handover reviewWalked through findings and value ranges. Agreed that customer pricing for extras, claim settlements and driver scheduling stay with named people.
Patrick Rochette · CEOJul 3War Map deliveryDelivered the War Map and roadmap. Extras capture and the fuel surcharge engine start first, with Samira and Brigitte as owners.
Patrick Rochette · CEO
What We Heard
“If the driver didn't write the waiting time on the CMR, for me it never happened. Even if the truck sat there three hours.”
“Half my morning is copying addresses out of PDFs. The other half is calling people back for the slot they forgot to give.”
“The price I paid last time on Lyon to Marseille? It's in my notebook. Somewhere.”
“The box in the cab knows exactly when I arrived and when I left. Nobody in the office looks at it.”
“We run 190 trucks and still price, plan and bill as if we had 40.”
Team Members Interviewed
Systems Accessed
Strategy Session · 30 min
A real engagement is scoped in the Strategy Session and may begin with a War Map or a bounded Feasibility Sprint.