Status Chasing: Your Team's Most Expensive Habit

Your operations team finished last week’s projects. But how much of that week was spent doing the work, and how much was spent figuring out where things stood?

Status chasing is the time your team spends asking “where is this?”, emailing for updates, pinging colleagues for progress, and sitting in meetings that exist only because nobody can see what’s happening without asking. According to Peakflo’s research on approval workflows, organizations processing around 200 requests per month lose 30 to 60 hours monthly just on follow-up activities. That’s nearly a full-time person doing nothing but asking other people what’s going on.

The frustrating part: status chasing feels productive. You’re getting answers, moving things along, making sure nothing falls through the cracks. But the work itself isn’t advancing. You’re just measuring where it stopped.

Where Does the Chasing Happen?

Status chasing hides inside workflows that look normal until you break down how time is actually spent.

Between approvals. A purchase request goes to a manager. The requester waits a day, hears nothing, sends a follow-up email. Still nothing. They walk over and ask. The manager says “I’ll look at it this afternoon.” Peakflo’s data shows the actual review takes 15 to 30 minutes, but the full cycle stretches to 3 to 7 business days. The review isn’t the bottleneck. All that waiting and following up is.

Across departments. When work moves from sales to operations, or operations to finance, there’s a gap where nobody knows the current state. Did the signed contract make it to the project setup team? Did finance process that vendor payment? Did the client send back the documents operations requested? Each gap creates a chain of “just checking in” messages.

In status meetings. Monday standups, Wednesday check-ins, Friday wrap-ups. Many of these meetings exist because there’s no other way to know what’s happening. If the information lived in a shared system, half those meetings would become unnecessary. We explored a related dynamic in how process handoffs break down.

Through management layers. The COO asks the department head. The department head asks the team lead. The team lead asks the person doing the work. The answer travels back up the chain. Three people interrupted, four context switches created, and the answer was “it’s on track.” That kind of management-as-relay is one of the least measured drains on operational capacity.

How Much Does Status Chasing Actually Cost?

The numbers add up faster than most teams expect.

Consider a 15-person operations team. If each person spends just 45 minutes per day on status-related activities (checking in, waiting for responses, attending update meetings, searching for where something is in the process), that’s 56 hours per week. At a blended cost of $40 per hour, you’re looking at roughly $116,000 per year spent on finding out where things are rather than moving them forward.

That’s a conservative estimate. McKinsey’s operations research has found that 20 to 30 percent of operating expenses in mid-size organizations are consumed by process inefficiency, with coordination overhead and approval queues being significant contributors.

The hidden multiplier is interruption cost. Every “quick question” about status pulls someone out of focused work. Getting back to full concentration takes an average of 23 minutes, according to research from the University of California, Irvine. A person who gets asked for three status updates in a morning has effectively lost that morning to fragmented attention.

How to Stop Chasing and Start Knowing

The fix isn’t about discipline or better communication habits. It’s about making status visible without requiring someone to ask for it.

Make work states explicit. Every task, request, or project should have a visible status that updates as it moves. Not in someone’s head. Not in their email. In a shared system where anyone with a stake can check without interrupting the person doing the work. When your decision latency drops, so does the chasing.

Replace meetings with dashboards. If a meeting exists solely to collect status updates from individuals, it’s a symptom, not a solution. A real-time view of project states, open requests, and pending approvals removes the need to gather that information verbally. Keep meetings for decisions, not data collection.

Set time-based escalation rules. Instead of people chasing approvals manually, define what happens when something hasn’t moved in 24 hours. Automatic reminders, backup approvers, or escalation paths mean nobody has to wonder whether their request is stuck.

Track cycle time, not just completion. Completion metrics tell you what got done. Cycle time tells you how long things sat waiting. The gap between “active work time” and “total elapsed time” on any process is a direct measure of how much chasing your team is doing. If a task takes 2 hours of work but 8 days to complete, those 6 extra days are mostly waiting and chasing.

Frequently Asked Questions

What is status chasing in business operations?

Status chasing is the time employees spend asking for updates, sending follow-up emails, attending meetings, and checking on the progress of tasks, approvals, or requests. It happens when operational visibility is low and the only way to know where something stands is to ask the person responsible for it.

How much time do teams lose to status chasing?

Research shows organizations lose 30 to 60 hours per month just on approval follow-ups alone. When you include status meetings, cross-department check-ins, and management coordination, mid-size teams often spend the equivalent of one full-time employee’s hours on status-related activities.

How do you reduce status chasing in operations?

The most effective approach is making work status visible in a shared system so nobody needs to ask. This includes explicit task states, automated notifications when items are overdue, dashboards that replace status meetings, and time-based escalation rules for approvals.

How Tier2 Keel Makes Status Visible

The chasing patterns described above come from the same root cause: work state lives in people’s heads, their inboxes, or disconnected spreadsheets. Keel puts it in one place.

Tier2 Keel tracks work from lead capture through project delivery, invoicing, and settlement in a single system. When a deal converts to a project, everyone involved can see its status without asking. Approvals, task assignments, and handoffs all happen inside the same workflow, with built-in notifications and escalation rules that replace the “just checking in” emails.

Instead of asking three people where a client project stands, you look at the dashboard. Instead of running a meeting to collect status updates, you spend that meeting making decisions.

See how Keel works or book a walkthrough with our team.

The next time you catch yourself typing “just checking in on this,” that message is worth about $116,000 a year to eliminate.