TMIThe framing that produces bad software for the trades goes like this: "The work is complex and variable, so we need a powerful system that can handle everything." This framing is wrong, and it's why most trades software is either unusable in the field or quietly abandoned after the first renewal cycle.
What an electrician needs from software at 7am on a job site is not power or comprehensiveness. It is three things: the right information, on their phone, without having to hunt for it.
That's it. Everything else is overhead.
The context problem
A journeyman electrician arriving at a new section of a commercial project needs: the current spec drawing for that section, any open RFIs that affect it, the last inspection photo of the rough work, and any notes from the crew that last touched it. That's four pieces of information. In most companies, those four pieces live in four different places, project management software, email, a shared drive, and a foreman's memory.
The friction this creates is not trivial. It's a ten-minute stop every time a journeyman hits a question. On a complex commercial or industrial job, that happens six to eight times a day per person. The math on lost productivity is brutal, and it's invisible in every project schedule because nobody tracks the time spent retrieving information that should already be in front of you.
"I've got five apps on this phone and none of them know what I'm doing. I have to know which one to look in, and half the time what I need isn't in any of them."
The information exists. The problem is that it was organized for the office, for the PM reviewing submittals at a desk with two monitors, not for the person standing in front of the panel, in a hard hat, with their phone in a belt holster.
The hardware constraint that gets ignored
Software designers forget that electricians work with their hands. They wear gloves. They're on ladders. They're in tight mechanical spaces where pulling out a phone is an event, not a casual action. The device they have is a phone in an Otter box that makes the screen harder to tap, in a building where the signal may be zero because there's six floors of concrete between them and the nearest cell tower.
Software that requires three taps and a search is software that gets used in the trailer. Software that gets used in the trailer is the PM's tool, not the electrician's. The gap between where decisions get made and where information lives is where most of the productivity in the trades disappears.
What good actually looks like
Good software for a journeyman electrician is software they don't notice. It delivers inspection checklists when they're about to start an inspection. It surfaces the relevant spec section when they tap a QR code on the panel. It logs the photo they take and automatically associates it with the work order without requiring them to navigate a folder structure.
It works offline and syncs when signal returns. It's readable in bright sunlight. The tap targets are large enough to use in a glove. None of this is novel engineering, it's discipline: building for a specific human in a specific physical context, and not compromising that context for the sake of features that matter to the person who bought the software but not the person using it.
The best field tools share one quality: they surface exactly what's needed for the next fifteen minutes of work, without requiring the user to know where to look or how to ask for it. The job context does the navigation. The software follows the worker, not the other way around.
The cumulative effect
Individual time savings per electrician per day are modest, twenty to forty minutes, depending on the job complexity. But a thirty-person electrical crew, recovering an average of thirty minutes per person per day, is fifteen person-hours per day. On a year-long commercial project, that's the margin between a profitable job and a break-even one.
There's also a quality effect. When the inspection photo from three weeks ago is available in ten seconds instead of twenty minutes, it gets checked. When the open RFI is visible in context, it gets resolved before the work gets buried in the wall. The downstream rework cost of information that didn't get to the right person at the right time is massive, and entirely invisible until the punch list.
Electricians don't need more software. They need software that works where they are, with what they have, and doesn't ask them to become information architects to use it.