Every Job Status Call Costs More Than the Call Itself
Most project-based service businesses answer the same question dozens of times a day: where does that job stand? Each answer takes two minutes. The true cost, once interruption recovery time is counted, runs much higher.
Every project-based service business runs on a particular rhythm of questions. A quote goes out, work gets confirmed, a job starts. In the gaps between those moments, one question circulates more than any other: "Where does that stand?" Customers ask it when they haven't heard anything. Staff ask it when they need to coordinate. Owners ask it when they're checking progress across a book of active work. The question sounds routine. But in a business running 10 or 15 jobs at once, it is being asked more often than almost anything else - and answering it costs significantly more than the two-minute call it appears to be.
The True Cost of an Interruption That Feels Like Work
The direct cost of a status question seems negligible. A customer calls to check where their order stands. You spend a couple of minutes on the phone, confirm everything is on track, and move on. That's the visible cost: two minutes and a little focus.
The research tells a different story. Gloria Mark at the University of California, Irvine, found that after an interruption, workers take an average of 23 minutes and 15 seconds to fully return to the task they were doing beforehand. Microsoft's 2025 Work Trend Index, surveying 31,000 knowledge workers across 31 markets, found that employees face around 275 interruptions per working day from meetings, emails, and chats. Three interruptions together consume roughly an hour of productive work. UK IT company Nasstar's 2025 analysis, drawing on Microsoft's research, put the aggregate cost of workplace interruptions to the British economy at £488 billion per year - the equivalent of a 25% productivity loss across white-collar sectors.
Most of that research examines corporate environments, where the interruptions are Teams notifications, unplanned meetings, and internal messages. A project-based SMB has a different version of the same problem. Here, a meaningful share of the daily interruption load is status questions - and unlike a distracting message notification, these feel like legitimate business activity. Someone genuinely needs to know where a job stands. Helping them is part of the job. That's precisely what makes the cost invisible.
The interruption math
Gloria Mark's UC Irvine research found each interruption requires an average of 23 minutes to recover from. In a business where staff field 10 status calls or queries a day, that recovery time alone could account for three to four hours of lost productive work across the team - before anyone counts the time spent on the call itself.
Why the Same Question Keeps Coming Back
The status question costs what it costs partly because the answer isn't accessible without asking. In most service businesses with fewer than 50 staff, job status lives in people's heads, in email threads, in WhatsApp messages, and in notebooks kept on desks. There is no single place where anyone - customer, team member, or owner - can look and get a current, reliable answer without involving another person.
That structure means the same question gets asked repeatedly, not just once per job per day. A customer calls because they cannot find the answer elsewhere. A staff member asks their colleague because there is no record they can check. The owner chases the operations lead because they are tracking progress from memory. Each conversation is short. Across a week with 15 live jobs, they add up to significant management time - and that figure does not account for the time lost by the person being asked.
The second cost is less visible. The person answering the status question often doesn't have an immediate answer themselves. They have to check - a call to a colleague, a search through an email chain, a look at a document somewhere on a shared drive. So a single status question from a customer can create a chain of two or three internal interruptions before a confident answer gets back to them. Each link in that chain carries its own recovery time cost.
What Changes When Status Is Visible Without Asking
The answer to the status question problem is not a faster reply or a better call-handling process. It is removing the need for the question in the first place. When job status is recorded in a job record that anyone authorized can view - updated as work progresses, visible to whoever needs it - the status question becomes self-serve.
A customer who can get an accurate update without calling does not call. A staff member who can see where a job stands without interrupting a colleague does not interrupt them. An owner who can review the current position of every live job in under two minutes does not spend the first hour of the morning piecing that picture together from conversations.
That shift changes the working day in a specific and practical way. Rather than the morning starting in reactive mode - catching up with what happened overnight, fielding the first round of status calls, chasing the team for progress reports - work can begin from a known, shared starting position. Decisions that need to be made get made earlier, because the information needed to make them is already visible. Tools like project tracking exist specifically to create this visibility: a single view of live job status that staff update in real time and that removes the need for the check-in call.
Track it for one week
count how many times your team is asked for a job status update - by customers or internally. Note how many of those questions required your staff to go and find the answer before they could give it. The total time across a week is usually larger than most business owners expect.
The Part of the Day You Don't Account For
The status question is not going away. Customers need reassurance. Staff need to coordinate. Owners need visibility across the book. But answering it manually - through calls, messages, and direct check-ins - is a structural choice, not an operational inevitability. In a business running 10 or more jobs at any time, the volume of status-chasing is not a sign that the team is attentive and responsive. It is a sign that job information is not where it needs to be.
Research on interruptions makes the cost concrete: three status calls in a morning, each answered in two minutes, consume not six minutes of productive time but something closer to an hour once the recovery cost of each interruption is factored in. Across a team of eight people, that pattern every day adds up to a working week of lost productive output over the course of a month.
The businesses that move the status question from a conversation to a lookup don't just save a few calls. They recover a meaningful share of their team's productive capacity - and they get a working day that starts from a known position rather than a guessed one.
Sources
- Employee Productivity Statistics 2026: Engagement, Costs & TrendsSQ Magazine · accessed 2026-08-18
- Workplace interruptions cost UK economy GBP £488 billion each yearIT Brief UK · accessed 2026-08-18
Related pages
Ready to run your business
on one platform?
Book a free demo and see how Zigaflow fits your team.