Field staff turnover is high in this industry. Training cost is real. The on-site screen of the Field PWA was rebuilt around a simple test: can a brand-new hire complete one full job with no senior tech standing next to them?
The old way. The new technician arrives at the customer site with a printed work order, a phone running a WhatsApp group, and a thirty-minute orientation memory. They take a photo of the ONU; nothing visibly happens, so they take it again. They forget the customer signature step. They try to scan the serial; the barcode reader silently does nothing because camera permission was denied earlier and dismissed without being read. They WhatsApp the supervisor: "hey is this the right photo?". The supervisor is mid-splice up a pole. The customer waits. The first job takes two hours longer than it should and the protocol PDF gets emailed the next morning with the wrong fields.
What ISPCQ does. The on-site screen runs a spec-driven flow that is the same on every job — defined once per service type by ops, not improvised per hire. A visible step-by-step guide is the spine of the screen, not an afterthought: the current step is the largest element. The photo phase shows live progress against what's required, so "did I take a picture, did anything happen?" stops being a question. Camera-blocked is a persistent banner with a fix-it link, not a toast that vanishes before the technician finishes reading. The ONU serial scanner is bundled into the app itself — no CDN dependency, no "scanner doesn't work on a weak connection." Install, fault and swap jobs require a GPS pin at the on-site step, and every step the technician completes is GPS-logged; if location is blocked on the phone, the denial itself is recorded, so a missing coordinate is an auditable fact instead of a silent gap. A confirmation selfie and customer signature gate the close step. The protocol PDF is auto-emailed at close, no manual handoff, and it carries a register number with a check digit, so any protocol can be found again later by number alone.
The operational outcome. New technicians complete their first solo job on their first morning. Senior technicians stop being on-call training resources for the first two weeks. Protocol PDFs go out before the customer leaves the doorway. The escalations that used to come back as "missing photo" or "wrong serial" effectively disappear — not because the technician got better, but because the screen made the wrong action impossible.
One of twenty-three detailed articles on real ISP workflows. Each walks through the problem, what teams used to do, what ISPCQ does, and the operational outcome. The architecture is the same; the workflows differ.