Commercial electrical
Ten electricians. Drone pads for Walmart.
Schoolfield Electric builds conveyor systems for Amazon and drone pads for Walmart, with ten commercial electricians working national accounts across multiple states. That is a different business from a service van: the work arrives from a broker, the site is three states away, and the paperwork is the deliverable.
Brokered work should not need a human to triage it
A dispatch arrives over the API from a national-accounts broker. It is in South Carolina, so it is the Southwest zone’s work, so it lands in that zone’s unassigned column, where that zone’s team picks it up. No dispatcher reads an email and decides.
- Zone geography resolves down to the USPS carrier route — the area one person can actually cover on foot or in a vehicle — glued up into territories. Carrier route, then ZIP, then county, then state, then a catch-all. Most specific wins.
- Unassigned is a real state with its own column per team. That is what makes it an inbox somebody works rather than a hole work falls into.
- The zone is stamped on the job as a value, not resolved through a join at read time. Redraw your territories next year and last year’s jobs still say which team actually did them — which matters when the zone is the thing you measure profit in.
- Creating work over the API is as good as creating it on the board, because every capability exists on every door by construction. For a broker-fed shop, the API is the front door.
The SOP is what makes a multi-state crew consistent
Ten electricians in five states cannot be supervised by walking past them. The checklist is the supervision — the steps, in order, by the right role, with the photographs attached and the readings captured.
One workflow, scoped
It renders differently for Walmart than for Amazon because the binding scope is different, not because somebody maintains two versions of it and forgets to update one.
Steps that cannot be skipped
Mark the workflow locking and the edits it governs cannot happen outside it. Enforced in the executor, so it holds for the API and for agents too — not just for whoever is looking at a screen.
Custom fields for how you actually work
Circuit, panel, conduit run, torque value, meter number. Declared against the record they belong to, so they show up in the checklist, in the tokens that fill your paperwork, and in your reporting.
Where it left off is a signal
A run reports back ok or fail at each step, so a job half-finished on Thursday is legible on Friday without ringing the crew.
On a Procore job, the proof is the invoice’s argument
Keep Procore. Keep whatever the general contractor makes you use. Buy the workflow seats, run your crews’ checklists on our app, and hand the GC a record of what was done, when, by whom, with the photographs — assembled as you worked rather than reconstructed on Friday.
- The purchase order raised at the counter, with the counter paperwork photographed against the job rather than living in a door pocket until the end of the month.
- The job’s whole story — times, visits, crew, captures — ready to attach to a pay application instead of being chased.
- Your system of record keeps the money. We take the field proof and the office SOPs, and nothing about your contract admin changes.
Photographed at the counter. Filed against the job.