Loading
Because the job sheet is paper or a photo. The engineer writes what they did, it reaches the office days later, and somebody types a summary into the accounting system.
Parts used get missed, time on site is rounded, and out-of-contract work is absorbed because reconstructing it is not worth the argument.
The request becomes a ticket with its entitlement. Scheduling books an engineer against real availability from Nest, and the visit is a task in Loop with its own time and parts.
What was done is recorded on site. Parts consume stock in Books, time becomes billable where the contract says so, and the invoice assembles from both.
It will not optimise routes. Scheduling respects availability and skills; geography is a judgement the scheduler makes.
It also will not work without a signal — offline capture syncs when the device reconnects, which is a delay rather than a loss.
Billing reflects the visit rather than a memory of it. Parts and time are captured where they happened.
Entitlement is visible before the engineer travels, so out-of-contract work is a conversation before the visit rather than an awkward invoice after it.
Capture does, syncing when reconnected.
Yes, from the van or warehouse location in Books.
Yes, recorded against the visit.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.