What can't field service software reporting tell you?
It cannot tell you about demand that never became a record. Unanswered calls, callers who hung up in the queue, quotes the customer never opened, and jobs that were never created because nobody logged the request are all invisible. It also cannot connect work to what you spent to get it. Field service reporting describes throughput accurately and demand capture not at all.
Survivorship is built into the schema
Every report your field service system produces is computed over records that exist. That sounds obvious until you realize the most expensive events in a service business are the ones that prevent a record from being created: a call that rings out at 7:40 in the morning, a caller who waits ninety seconds and gives up, a web form that errors, a technician who quotes verbally and never enters it.
None of those appear as a zero in your reporting. They appear as nothing at all, which is much worse, because nothing looks like it never happened.
The four questions it structurally cannot answer
- How much demand did we receive? The system knows bookings, not inbound volume. Only the phone system and website know that.
- What did this job cost us to acquire? Ad spend lives in Google, Meta and LSA. There is no field for it on a job.
- Why did this quote lose? The status field says unsold. The reason lives in the conversation.
- Which rep or estimator is actually better? Close rate by person conflates skill with lead quality and job mix unless you control for both.
What to attach so those questions become answerable
Each blind spot has a corresponding source. Inbound demand comes from call tracking and web analytics. Acquisition cost comes from the ad platforms. Loss reasons come from call transcription and analysis, which can surface what the customer objected to rather than what the estimator typed. Fair rep comparison requires normalizing by source and job type before ranking anything.
Joined together, those sources turn the field service record from a throughput log into the operational half of a revenue picture. The field service system remains the system of record for what work was done and what it was worth. It just stops being asked questions it was never built to answer.
A quick diagnostic you can run this week
Take last month's inbound call count from your phone provider and last month's created request count from your field service system. The gap between them is your unmeasured surface. If the gap is large and nobody can explain it, no amount of dashboard work will fix reporting — the demand data simply is not being captured.
Owners are often more disturbed by that one comparison than by anything a dashboard shows them, and it is usually the fastest thing to fix.
Topics: reporting · blind spots · attribution · demand
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.