August is when field IT stops being theoretical

The Heritage Day long weekend is over. Sylvan Lake is starting to empty. Back-to-school flyers are at the front of the Co-op. Downtown is busy again for the first time in three weeks. And out on the lease, the field tablet that worked fine in May has spent two months getting cooked in 32-degree sunlight - which is when most mid-market operators discover that their field IT works in a Calgary office at 22 degrees and stops working in a Daysland field at 32.

The gap between the IT you bought and the IT your field actually uses shows up in August. The workarounds are the data.

Every company that has people working outside an office has a gap between the IT they bought and the IT those people use. This is not a controversial observation. It is barely an observation. It is more like a description of weather.

(Last August, in the hailstorm that wrote off a parking lot's worth of cars at Chinook Centre, three operators I know lost field gear to roof leaks they didn't know they had.)

The gap shows up in August because August is when the politeness of February runs out. The crew that politely worked around a slow VPN in February isn't polite about it in August when they are 200 kilometers from the office on a Friday afternoon. The route driver who used to call dispatch when the mobile app timed out now just stops using the app. The healthcare aide who could not get into the records system at a patient's home in March now has six months of workarounds that nobody knows about. The workarounds are the data.

(Companies sometimes ask whether their field operations are using their IT investment. The honest answer is: yes, but not in the way you bought it for. The honest follow-up is: that's fine, you just have to know what's actually happening.)

Three patterns to investigate. Each of them is happening at your company right now. Probability that they are happening at your company right now: 100 percent, give or take.

Personal devices doing real work. Not in the corporate-speak "shadow IT" sense, where the word "shadow" implies that someone has done something nefarious. In the actual real sense. Field people use their phones for things your provisioned hardware cannot do reliably. Photos of damaged equipment. Screenshots of warning codes. Voice notes that become text later. If your security model says "no personal devices touch company data" and your operations model only works because personal devices touch company data, you have a documentation problem, not a security problem. Catch up the documentation before an audit catches up the gap. (The audit will catch up the gap.)

Spreadsheets that should be system data. Anywhere your field operations are running on shared spreadsheets - schedules, asset locations, incident logs, anything - is a place where the system you bought either does not fit the work or was not trained into the team. The spreadsheets are accidentally institutional knowledge. When the person who maintains them leaves, the spreadsheets accidentally institutional-knowledge themselves out the door.

Phone calls instead of system updates. When the field calls the office to coordinate instead of updating a shared system, your asynchronous workflow does not actually work. Each call is also a moment where data did not get captured. Six months of calls is six months of operational data that does not exist. (You can sometimes reconstruct it later from billing or from someone's memory, but reconstructed data is a polite fiction the rest of the organization agrees to treat as real.)

Why this matters specifically right now, in approximately a four-week window before the September questionnaires arrive: cyber insurance carriers and Q4 auditors are getting much more specific about how field-level data moves. The standard questions used to be "do you have MFA on email?" They are now "describe how a field tech's photo of a customer site reaches your records system and who can see it along the way." If your honest answer is "I'm not sure, but probably WhatsApp," you will feel that at renewal.

The fix is not more tools. The fix is catching the actual workflow up to the documented one, or the documented one up to the actual one. Either is fine. The gap between them is what hurts. (The gap, like the weather in August, is also what creates the workarounds in the first place.)

- The Operator's Brief, August 2026 · Vencer Group