IT services · New Zealand
Vehicle GPS trips turned into engineer timesheets
An IT services company's engineers stopped rebuilding their week from memory. Cartrack trips become time entries on ConnectWise tickets.
Trips → time
built from Cartrack trips
Per ticket
entries land on the ConnectWise ticket
The problem
Field engineers drive between client sites all day. At the end of the week they had to rebuild where they had been and for how long, then key it into ConnectWise ticket by ticket. Time went missing, and travel was hard to bill correctly.
What I built
A small service that pulls each engineer’s trips from Cartrack and turns them into a day: where the vehicle stopped, how long it stayed, and which trips were travel. It knows the office location, so office time and site time split apart. Each day becomes timesheet entries on the engineer’s ConnectWise tickets.
Engineers sign in with Microsoft and see each day’s trips, and the timesheet built from them, in a simple dashboard. A sync keeps trips current, and the whole thing deploys from GitHub with Docker.
The result
Timesheets start from what the vehicle actually did, not from memory. Engineers start from a filled-in day instead of a blank week, and travel time stops falling through the cracks.