1,001 views
Pending Approvals Count is the number of booking requests, sitter applications, or time-off requests currently sitting in your queue awaiting a yes/no decision from you.
How It’s Calculated
PetBizApp counts every item across your approval queues — new booking requests not yet confirmed, sitter shift-swap or time-off requests, and (if you use it) new sitter applications — that is currently in a pending state, unresolved either way.
What’s a Good Benchmark
Under five, cleared at least once daily, is a healthy working number for most small teams. A queue that regularly sits above ten, or that carries items more than 48 hours old, means decisions are backing up faster than you’re making them, which eventually shows up as frustrated clients and sitters who stop bothering to ask.
Why It Matters
Every item in this queue is someone waiting on you: a client who wants to know if their booking is confirmed, a sitter who needs to know if they can take Saturday off before they commit to something else. A growing pending count is a leading indicator of exactly the kind of slow-response problems that damage Average Response Time and staff morale, before either of those numbers themselves have moved.
This KPI lives on the OPERATE dashboard inside PetBizApp.
A Worked Example
A growing pet sitting business notices its Pending Approvals Count creeping from a typical 2-3 up to 11 over two weeks, coinciding with the owner taking on more new-client sales calls personally. Digging in, most of the backlog is sitter time-off requests for an upcoming holiday weekend that the owner has been putting off deciding because it means figuring out coverage. By blocking 30 minutes to work through the whole queue at once — approving what’s approvable and explicitly declining or countering the rest — the owner clears the backlog and, just as importantly, sitters stop hesitating to submit new requests, which had started to quietly drop off.
How This Looks Different By Business Model
For a solo operator, this queue is almost entirely client booking requests, and a growing count usually just means you’re busy and behind on your own admin — the fix is a fixed daily “approvals” time block rather than handling them ad hoc between visits. For a business with staff, the queue mixes client-facing items (which affect revenue and trust) with staff-facing items (which affect retention and morale) — it’s worth mentally separating the two, since a stalled staff request is arguably more costly long-term than a slightly delayed booking confirmation.
What Causes This Number to Climb
A growing queue usually means one of: the owner has become the bottleneck for decisions that could be delegated to a manager or lead sitter; approval criteria are unclear or inconsistent, so each decision takes longer than it should because there’s no simple rule to apply; the business has grown volume faster than its decision-making process; or genuinely difficult decisions (coverage conflicts, borderline sitter applications) are being avoided rather than resolved.
A Common Misconception
A low Pending Approvals Count doesn’t automatically mean things are running well — it can also mean requests are being approved too quickly, without real scrutiny, which shows up later as scheduling conflicts or a sitter roster that doesn’t match business needs. The target isn’t just “low,” it’s “low and each decision was actually considered.”
How to Keep This Number Under Control
Set a fixed daily time to clear the queue rather than reacting to each item as it lands. Write down simple approval rules in advance (for example, a maximum number of sitters off on any given day) so most decisions become quick rule-checks instead of fresh judgment calls each time. Delegate approval authority for lower-stakes categories once you have a trusted lead sitter or manager.
Common Mistakes
Letting the queue become a to-do list you avoid rather than clear. Approving everything quickly just to make the number go down, without actually checking for conflicts. Not distinguishing urgent, time-sensitive items (a booking request for tomorrow) from ones with more slack (a time-off request for three months out), and treating the whole queue with the same priority.
