The project management platform was selected after a thorough evaluation. Three vendors, a scoring matrix, a demonstration for the leadership team. It does everything the office needs.
Six months later the superintendents are back to photographs and text messages, and the daily reports are being typed up in the evening from memory.
The software is not the problem. The trailer has one bar of signal, the tablet was chosen for its price, and nobody asked what happens to the workflow when the connection drops halfway through a form.
Field technology fails for field reasons
Connectivity is intermittent, not absent. This is worse than absent, because software written for a good connection behaves unpredictably on a bad one. Forms half-submit. Photos queue and silently fail. Two people edit the same record and one edit disappears. Crews learn not to trust it, and once trust is gone it does not come back with a training session.
The hardware is wrong. Consumer tablets in gloved hands, in daylight, in dust, in cold. They crack, they cannot be read outside, and they cannot be operated by somebody wearing gloves. The device budget is a tenth of the software budget and it decides whether the software gets used.
The workflow was designed by people who do not do it. A daily report that takes twenty minutes on a laptop takes forty on a phone at the end of a twelve-hour day. The crew will not do it, and they are right not to.
Nobody owns the site. Office IT stops at the office. The site has a router somebody bought, a camera system the security vendor installed, a connection nobody monitors, and no named owner. When it fails there is no process, only phone calls.
What actually works
Pick tools that work offline properly, and test that claim rather than accepting it. The test is simple: put the device in aeroplane mode, complete a full daily report with photographs, restore the connection, and confirm nothing was lost. Do this during the evaluation, not after the contract.
Buy hardware for the environment. Rugged, readable in sunlight, operable with gloves, and enough of them that a broken one is replaced the same day rather than becoming the reason a site stops reporting.
Treat connectivity as site infrastructure with a named owner, a standard kit, and a setup checklist that runs with mobilisation rather than three weeks after it.
Design the field workflow with the people who will use it, and make it short. If the daily report takes more than five minutes, it will be done badly or not at all, and a badly completed report is worse than none because it looks like data.
Why this is worth attention
Field data is the input to everything else. Job cost accuracy, change order substantiation, schedule confidence, safety records, and the documentation that decides a dispute two years later all depend on what got captured at the site on the day.
When the field tooling does not work, the office compensates with re-entry, phone calls and estimates, and the cost of that shows up as administrative overhead rather than as a technology failure. It is rarely attributed correctly.
The security piece nobody plans for
Site networks get connected to the office network because it was convenient, often by a vendor, often without anybody deciding. That connection is a path from the least controlled part of your estate to the most sensitive part of it. It is worth knowing whether it exists before somebody else finds it.