Note
Why the system you bought died in sixty days
Bring up job management software with a contractor who has been going eight years and you will often get a short, flat answer: we tried that once.
Money was spent. Someone came and set it up. There was training. For about three weeks it looked like it was working. Then it was back to the LINE group and the spreadsheet, and nobody has opened the thing since.
It is worth being precise about why that happens, because the usual explanations are wrong.
It was not that your team is resistant to technology
The same technicians who “won’t use the system” are running three chat apps, sending photos all day, and using a banking app without any training whatsoever.
They are not avoiding software. They are avoiding extra work with no visible return, which is an entirely rational thing to avoid.
It was not that the software was bad
Most of these tools are fine. They will hold a job, attach a photo, capture a signature.
The problem is that a general tool arrives empty. Someone still has to decide what the statuses are, what goes on a job order for electrical work in a factory, what a handover form has to contain for a customer’s engineer to sign it. If that never gets decided properly, the tool is a blank container and everyone fills it in differently until they stop filling it in at all.
What actually killed it
Here is the pattern, in one sentence: the system was somewhere to type things in, rather than somewhere the work had to pass through.
That distinction decides everything.
If the system is a place to type things in, then using it is a second task on top of the real job. The real job still happens in the LINE group. Under pressure, and there is always pressure, people do the real job and skip the second task. Not out of defiance. Because there is only so much time and one of those two things is optional.
If the work has to pass through the system, there is no second task, because there is no other route. Nothing to skip.
What “has to pass through” means in practice
Concretely, in installation work, it means the closing gate: no signed handover, no closed job. No closed job, no place in the billing queue.
Now consider what a technician is actually deciding. It is not “should I use the system or not”. It is “do I want this job to count”. Those are very different questions, and only one of them needs a supervisor standing over someone.
The same logic applies to the maintenance side. If the site register is something a person is supposed to update after handover, it will drift and then die, because updating it is a second task. If every closed job writes itself into the register automatically, there is nothing to remember and nothing to skip.
The test to apply before you buy anything
One question, and it is not about features:
If someone ignores this system entirely, does their work still get done and still get paid?
If yes, the system will be dead in sixty days, no matter how good it is or how thorough the training was. If no, if ignoring it means the work does not close and does not get invoiced, then it will survive, and you will not have to nag anybody.
Everything else is a detail. That question is the whole thing.