The "Where Are They?" Problem: Eliminating the GC–Subcontractor Friction Point
The single most-asked question on a multi-contractor jobsite is also the most expensive. Real-time technician visibility — not status calls — is what ends it.
The Most Expensive Question on a Jobsite
On any given morning, on any given commercial jobsite, the same three words are spoken into a phone, a radio, or a group text: "Where are they?" The general contractor is asking about the HVAC sub. The HVAC sub is asking about the electrical apprentice. The electrical foreman is asking about the parts runner. Everyone is asking about someone, and no one has a good answer.
The friction point is not the technician. The technician is doing their job — driving, diagnosing, picking up parts, finishing the call before this one. The friction point is the communication architecture between organizations. The GC has no native visibility into the subcontractor's dispatch. The subcontractor has no obligation to push status into the GC's system. The gap gets filled by the most expensive form of coordination ever invented: a human making phone calls until they get an answer.
Operators who solve this don't solve it by hiring more dispatchers or sending more texts. They solve it by treating real-time technician visibility as a contractual deliverable — a governed surface the GC can look at without picking up the phone.
What "Where Are They?" Actually Costs
The cost is rarely on a single invoice line. It accumulates across four surfaces — every one of them invisible until you measure it.
Dispatcher hours burned on status calls
A typical mid-market subcontractor dispatcher spends 40–60% of the day answering "where is your tech?" calls from GCs and end customers. That dispatcher is not routing, not load-balancing, not solving real exceptions. They are a human status API.
GC superintendents context-switching
A superintendent running three subs across two floors makes 15–25 outbound coordination calls per day. Each call is a 2–4 minute interruption in the work the super is actually paid to do — sequencing trades and clearing blockers.
Dead time at the gate
When the tech's actual ETA is invisible, GCs over-prepare or under-prepare the access window. Site security, freight elevator slots, and badge-in coordination either sit idle waiting or miss the tech entirely — forcing a re-schedule.
Erosion of GC trust at renewal
A GC that spends 18 months chasing a subcontractor for visibility doesn't renew the master service agreement on price. They renew on the operator who proves, every day, that the GC doesn't have to chase. Visibility is a renewal driver disguised as an operational one.
Visibility as a Contractual Deliverable, Not a Favor
The operators who eliminate the "where are they?" problem treat visibility the way they treat insurance certificates and safety records — as a standing deliverable in the master service agreement, not as a courtesy the GC has to ask for. Three components define what "good" looks like:
- A live tech-status surface the GC can self-serve. The GC's superintendent opens a link, sees every assigned tech for that site, sees real-time location or job-stage, and closes the tab. No phone call. No text. No waiting on a dispatcher to circle back.
- Job-stage events the GC can subscribe to. "En route." "On site." "Diagnosis complete." "Parts required." "Departed." Each event fires automatically as the tech moves through the work order, so the GC's system gets the update at the moment of truth — not when someone remembers to call.
- Exception alerts that surface before the GC notices. When the tech is going to miss the window, the system tells the GC before the GC tells the operator. The conversation stops being "you're late" and starts being "we already re-routed."
The shift is psychological as much as technical. Visibility moves from a thing the GC has to extract to a thing the operator volunteers — and the entire coordination cost collapses with it.
The Implementation Path That Earns GC Trust
Visibility doesn't ship on day one. It is sequenced — each stage proves the next is worth the operational change. The operators who land it follow this path.
Instrument the tech, not the customer
Get every assigned tech reporting job-stage events from a mobile workflow they actually use. No GC visibility yet — just clean, trustworthy data inside your own system. If your own dispatch can't see the tech in real time, no GC ever will.
Pilot a single self-serve link with one GC
Pick one anchor GC. Give their superintendent a live link to the techs assigned to their sites. Measure the drop in inbound status calls over 30 days. The data writes the case for everyone else.
Standardize event payloads and exceptions
Define the exact stage events and exception types every GC sees. Same vocabulary, same triggers, same SLAs. Now the visibility is a product, not a bespoke favor for one customer.
Bake visibility into the MSA
On the next renewal, the visibility deliverable goes into the contract — uptime, event coverage, response on exceptions. This converts an operational advantage into a renewal moat competitors cannot match without rebuilding their stack.
Surface coordination upstream
Once visibility is live across GCs, expose the same surface to the end customers and property managers downstream of the GC. The "where are they?" problem ends not just on the jobsite, but across the full chain of accountability.
The Operators Who Stop Getting Asked
The subcontractors who win the long-cycle GC relationships in the next decade will not be the ones with the cheapest hourly rate. They will be the ones whose GCs stop asking where their techs are — because the answer is already on the screen.
"Where are they?" is not a coordination problem. It is a visibility deficit. Close the deficit, and the question disappears — along with the dispatcher hours, the superintendent context-switching, and the slow erosion of trust that loses the next renewal. The operators who treat visibility as a deliverable, not a favor, get to compete on the work itself. Everyone else keeps answering the phone.
Sources and Further Reading
- The Service Council. Field Visibility Benchmarks — dispatcher time allocation and the operational impact of self-serve status surfaces in subcontractor relationships.
- Aberdeen Group. Subcontractor Coordination research — quantifying superintendent productivity loss from inbound status coordination across multi-trade sites.
- Field Service Insights. Industry analysis of MSA renewal drivers, visibility-as-deliverable contract patterns, and the relationship between governed status surfaces and customer retention.
Related Pages
Continue exploring how ServiceIQ governs the friction points in field operations.
Stop Getting Asked. Start Getting Renewed.
Make real-time technician visibility a deliverable your GCs see every day — and turn coordination friction into a renewal moat.