Time reporting in a field service company is how the hours a crew works on site become figures the office can approve, bill and defend months later. When the hours arrive as a text on Sunday night and are retyped on Monday, the invoice rests on a reconstruction, and nobody can say whether Thursday was three hours or three and a half.
The posts below cover the three parts that decide whether the record holds. One sets out what a time-reporting system must do before a crew uses it without being chased: one clock at a time, travel kept as its own kind of time, and a clear line between what was reported and what was approved. Another explains what GPS in a web app can honestly do, which is read the position at the tap rather than track anyone, and a third shows how to approve a week in twenty minutes instead of a month in a day.
In Closepact's Schema & arbetsorder the position is read when the button is tapped and checked by the server, and a missing reading is stored as unknown; there is no automatic clock-in. Approved hours become an invoice basis, or a draft invoice with the invoicing module. There is no payroll export. The guide to time reporting goes further.
- Time tracking
Time reporting people actually use
The hours arrive as an SMS on Sunday night and somebody retypes them on Monday. Here is what has to be true of a time-reporting system before a crew uses it without being chased.
Jun 30, 2026 · 8 min
- Time tracking
GPS clock-in: what is actually possible
Automatic clock-in when the van arrives is sold constantly and cannot be built in a web app on iOS. Here is what is genuinely possible, and why "no reading" must never be stored as "outside".
Jun 16, 2026 · 8 min
- Time tracking
Approving time without becoming the bottleneck
Approval exists so that the hours on an invoice were agreed by somebody other than the person who reported them. Here is how to run it weekly in twenty minutes instead of monthly in a day.
Jun 9, 2026 · 8 min