A 42-person consulting firm we talked to runs every timesheet through one operations director. Every Friday, roughly 40 people submit their hours, and payroll plus the week's billing sync both wait on her clearing that queue. She's good at her job. She's also on client calls two or three afternoons a week, and twice last quarter the whole firm's invoicing slipped by a day because of it. That's not a people problem. It's a workflow that was designed for a 10-person team and never got rebuilt.
In this guide
Why one approver stops working around 15 people Route approvals to whoever actually knows the work Build the escalation path before you need it Cover PTO without freezing a week of billing Frequently asked questions
Why One Approver Stops Working Around 15 People
Do the math on a single-approver setup and the ceiling shows up fast. Reviewing a timesheet properly, checking hours against the project plan, flagging anything that looks off, takes three to five minutes if you're doing it right rather than just clicking approve. At 15 direct reports submitting weekly, that's an hour of uninterrupted review time every Friday. At 40, it's closer to three hours, and it has to happen in a window small enough that payroll and invoicing still go out on schedule. Almost nobody blocks off three clean hours on a Friday afternoon.
So what actually happens is the queue backs up. Approvals get batched into Monday morning, which pushes the billing run a day, which pushes the invoice a day, which stretches days sales outstanding by a day, every single week, forever. None of that shows up as a dramatic failure. It shows up as a firm that's quietly always a little behind, and nobody can point to why.
The fix usually isn't a better reminder email to the one approver. It's admitting the org chart and the approval chain shouldn't be the same thing. If your team is still inconsistent about logging hours in the first place, that's worth fixing before you touch routing at all, our guide to time tracking best practices for agencies and consulting firms covers the basics that make approvals fast instead of a guessing game.
Route Approvals to Whoever Actually Knows the Work
A department head approving hours on six different client projects is being asked to judge work they never saw happen. They're checking whether the number looks reasonable, not whether the hours match what was actually delivered. That's how a scope-creep problem sails through approval three weeks in a row before anyone with project context notices.
The better model splits approval by who has visibility, not by who sits where on the org chart:
- Project or engagement lead approves hours logged against their own active projects, since they're the only one who can tell if the hours match the work that shipped
- Practice or department lead approves internal hours, bench time, and PTO, the categories that never touch a client project code
- Finance or ops does one final pass right before the billing run, checking only the hours flagged for client invoicing, not re-reviewing every line already approved upstream
- Contractor and subcontractor hours route straight to whoever owns that vendor relationship, so a 1099 timesheet doesn't sit in a full-time manager's queue behind their own team's hours
A single weekly timesheet can carry rows for three different clients, and each row should route to the lead who owns that engagement, not all to one manager who has to piece together context on projects they're not staffed on. This is the kind of routing logic worth checking for directly when you're comparing tools; see how approval rules and project ownership connect on the features page before you assume your current system can do it.
Build the Escalation Path Before You Need It
Every firm has an approver who goes quiet for a few days. It's rarely malicious, they're heads-down on a client deliverable or traveling, and the timesheet queue just isn't top of mind. Without an escalation rule, that quiet stretch becomes everyone else's problem the moment the billing run comes due.
A workable default: a reminder at 24 hours, a second reminder at 48, and an automatic reassignment to a named backup approver at 72 hours if nothing's happened. That backup doesn't need deep project context, just enough authority to unblock the queue and flag anything that looks genuinely wrong. The goal isn't a perfect review at hour 72, it's making sure nothing sits untouched for a week.
Unapproved timesheets past 72 hours are the most common reason we hear for a delayed billing run. Not bad time entries, not client disputes, just hours sitting in a queue nobody was forced to look at. An escalation rule turns a silent bottleneck into a two-day delay instead of a two-week one.
This is also where plan tier matters more than people expect. Configurable escalation and multi-step approval chains tend to live in the mid and upper tiers of most PSA pricing, so it's worth checking what your current plan actually supports on the pricing page rather than assuming the feature is included everywhere.
Cover PTO Without Freezing a Week of Billing
Approvers take vacation, and that's when a single-approver setup breaks hardest. A director out for two weeks in December, right when year-end invoicing needs to close clean, can stall a firm's entire billing cycle if nobody thought to reassign the queue before she left.
Set this up as a standing rule, not a scramble every time someone books time off:
- Every approver names a backup when they set their own PTO, not after someone notices the queue is stuck
- Delegated approval authority is temporary and reverts automatically on the approver's return date, so nobody inherits a queue permanently by accident
- Backups get a lightweight view, project hours, budget flags, and prior approvals, not the full history a project lead would need
Two weeks of paid leave shouldn't cost a firm two weeks of delayed invoices. If PTO coverage and approval delegation aren't things your current setup handles cleanly, that's usually a sign the tool was built for tracking hours, not for running the approval and billing chain that depends on them.
See approval routing built for how your team actually delivers
Get a live walkthrough of role-based approvals, escalation rules, and PTO coverage inside Autovella's connected time and billing workflow.
Frequently asked
In most services firms, the project or engagement lead should approve hours logged against their own projects, since they're the one who knows whether the work actually happened as described. The direct manager should only approve internal hours, PTO, and bench time. Splitting it this way means no single person is reviewing work they can't actually judge.
A reasonable default is a reminder at 24 hours and an automatic escalation to a backup approver at 48 to 72 hours, especially in the days right before a billing run. Firms that let timesheets sit for a week without any escalation almost always end up pushing invoices to the following cycle.
Yes, and for anyone billing across multiple active projects it's usually necessary. A single weekly timesheet can be split by project line, with each line routed to the lead who owns that engagement, so one late approver on one project doesn't hold up hours that are already cleared on two others.