Overview
Mileline does not replace the CRM dispatch already lives in. It reads route sheets — the planned (and completed) stops a courier is assigned — then computes distance per person so finance can accrue payouts without a GIS specialist in a spreadsheet.
The work is integration-shaped: map the client’s objects, keep their source of truth, emit kilometres and exceptions they can audit. When a sheet is incomplete or a loop looks implausible, the row stays flagged instead of silently padding a wage.
The challenge
Last-mile payroll based on “how it felt” or on GPS crumbs nobody reconciles. Route sheets already exist. The missing piece is a deterministic pass from sheet → geometry → payable kilometres.
Approach
- Integrate with the company’s CRM — do not fork a second dispatch tool.
- Parse route sheets into ordered stops; resolve geocodes; measure legs.
- Attribute distance to the courier on that sheet, with daily and period rollups.
- Surface exceptions (missing stops, impossible jumps) before payroll lock.
Outcomes
- Payouts that can be explained from the same sheets ops already print.
- Less month-end archaeology; more exception handling.
- A pattern for any fleet that already has routes but not a wage formula.