Loading
Loading
Product concept
Route planning that takes carbon as seriously as delivery windows.
Context
The concept is shaped around a fictional Dutch regional carrier: eighty vehicles, contract customers who raise emissions in every tender, and planners who like the routing tool they already have. TerraFleet does not replace their routing. It makes the carbon visible in the place where the decisions are made.
Challenge
A planner choosing between two feasible routes has no idea that one produces a third less CO₂. Emissions live in an annual report; decisions happen every morning at seven. The gap between those two moments is where a fleet's footprint actually gets made.
Approach
work.projects.terra-fleet.solution
Research
We traced how an emissions number is produced today: fuel receipts, a conversion table, and an intern's spreadsheet, once a year. Then we asked when the number would actually be useful: at planning time, per route, per customer. That shift from yearly to daily defines the whole product.
User flow
The essential path through the product, step by step.
Tomorrow's routes load with distance, stops, and a computed CO₂ figure per route.
Two feasible plans sit side by side; the greener one is visible before anyone commits.
Vehicle profiles matter here: the same route scores differently in an electric van than in a diesel truck.
The delivery map strip shows progress and flags exceptions without leaving the dashboard.
Weekly and quarterly emissions roll up per customer, ready for a tender or an audit.
Design direction
The interface stays warm on purpose: forest green on cream, soft corners, generous air. Sustainability software often scolds; TerraFleet encourages. The leaf-toned area chart and calm metric cards make emissions feel like progress being tracked rather than guilt being assigned.
Interface preview of TerraFleet with illustrative demo data, no client information.
Architecture
The layers that make it dependable, from client to data.
Server-rendered web client with the route list, map strip, and emissions charts.
Computes CO₂ per route from vehicle profiles, load factors, and distance.
Routes, vehicles, and deliveries in one model, importable from existing planning tools.
Aggregated history that produces customer and audit reports on schedule.
Responsive
Planning happens on a big screen, so the dashboard keeps its density there. On a phone the platform narrows to the day in progress: route status, exception flags, and the headline emissions figure a manager quotes in a meeting.
Interface preview of TerraFleet with illustrative demo data, no client information.
Outcome
The concept demonstrates that emissions tracking belongs inside the planning workflow, not after it. It gives us a working reference for the data model and the calculation engine, both of which carry over directly into logistics engagements where carbon reporting is on the table.
Stack
06
Next case study
Product conceptDocuments that read themselves, and a human who only sees the doubtful ones.