Job & fleet tracking
In many offices a whiteboard runs the company, and one person can read it. This page is about replacing both with a board that knows where every job, ute and hour is, from the office or the cab.
Fig A · The board in the office and the job in the pocket are the same record
What it covers
Office ↔ field, one recordHow it's built
For the cab, not the boardroomThe field side is a mobile web app: nothing to install from an app store, nothing to update, works on whatever phones the crew already carries. It is designed for the worst conditions it will meet: big touch targets, readable in full sun, and tolerant of dead spots. Actions queue when coverage drops and sync when it returns.
The office side is the day board and the record system behind it, running on your own infrastructure and wired into invoicing and payroll (see accounting pipelines). Subcontractors can be given limited logins that show their jobs and nothing else.
What it replaces
The whiteboardThe whiteboard, the 6am group-chat scramble, paper timesheets in the glovebox, and the Friday afternoon reconstruction of where everyone was on Tuesday. One record, written once, at the moment the work happens.
Asked every time
Common questionsWhat happens with no reception?
The field view keeps working on what it already has, and anything the crew does is queued on the phone. When coverage returns it syncs in the background. A black spot costs minutes of freshness, not the day's records.
We already use a job app. Replace it or work with it?
Either. If the app is mostly working, we build around it and fill the gaps it leaves, usually reporting, payroll flow, or the fleet side. If you are paying per seat for a thing you fight daily, we scope a replacement and migrate the history. The cost page has the arithmetic for that decision.
Do subbies get access?
Yes, scoped. A subcontractor sees their assigned jobs, uploads their PODs and dockets, and sees nothing about margins, other crews or other clients. Access expires when the engagement does.