
You schedule 10 agents for an eight-hour customer support shift. That's 80 hours of scheduled work. But how many of those hours will actually appear on the client's bill?
One agent waits 20 minutes for a new ticket. Another spends time in a team meeting. A few others attend training, switch between client accounts, or lose access to their CRM during an outage. By the end of the shift, the timesheets may be complete, but the hours tell a more complicated story.
This is where BPO billable hours need closer attention. Some activities may qualify for client billing, while others become part of your operating costs. The difference depends on the work performed and the client agreement.
Let's look at seven areas where these hours go, what managers should measure, and how to get a clearer picture of billable utilization.
BPO billable hours are the hours a business process outsourcing provider can charge to a client under an agreed contract or pricing arrangement.
For example, a client may pay for 10 agents to provide customer support for eight hours daily. The contract determines whether activities such as customer interactions, training, meetings, and system downtime qualify for billing.
Managers should distinguish between these four categories:
These categories help managers understand the difference between attendance, actual working time, and client-billable time. Remember that non-billable activities, such as training and quality reviews, can still support service delivery.
Beyond billable hours, three workforce metrics help explain how agents spend their scheduled time:
Shrinkage: Time agents are unavailable for customer work because of breaks, leave, meetings, or training.
Schedule adherence: How closely do agents follow their assigned schedules?
Occupancy: The share of available time agents spends handling customer interactions and related work.
For more detail, see ICMI's explanation of shrinkage and its contact center cost-per-contact worksheet, which explains occupancy.

Not every hour outside direct client work is a problem. Training, meetings, and internal coordination are necessary parts of running a BPO operation.
What managers need to understand is how frequently these activities occur, how long they take, and whether the time is accounted for correctly under the client agreement.
When an agent finishes a task or customer interaction, there may be a gap before the next assignment arrives. A few minutes between assignments is often unavoidable. However, repeated gaps across a large team can affect overall utilization.
These gaps can occur when:
Call or ticket volume is lower than expected.
Agents wait for the next queue assignment.
A client account temporarily reduces its workload.
Supervisors take time to redistribute tasks.
Agents move between projects without a clear transition plan.
Metric: Idle percentage
Idle percentage = (Idle minutes ÷ Logged-in minutes) × 100
For example, if 20 agents each have 15 minutes of unassigned time during an eight-hour shift, the team accumulates five idle hours out of 160 logged-in hours.
(20 × 15) ÷ 60 = 5 hours
(5 ÷ 160) × 100 = 3.125%
That is approximately 3.1% idle time. It does not automatically mean five billable hours were lost, but it gives managers a measurable pattern to investigate.
Managers can compare recorded idle periods with queue volume, task assignments, and workload across client accounts. An Idle and Manual Time Report in StaffViz can also help identify employees with recorded idle time, giving managers another source of information when investigating recurring gaps.
If one account consistently shows longer gaps between completed and newly assigned tasks, the cause may be workload forecasting or task routing rather than agent performance.
Agents spend time on activities that support daily operations but may not be included in client billing. These include team meetings, shift handovers, performance updates, timesheet corrections, internal reporting, and administrative coordination.
Some meetings protect service quality and delivery. Others run longer than necessary or include people who do not need to attend.
The goal is to understand how much time internal communication requires and whether the process is well managed, rather than removing necessary activities.
Metric: Internal meeting hours per agent per week, alongside the difference between planned and actual meeting duration.
Consider a daily 15-minute team huddle that regularly runs for 25 minutes. The additional 10 minutes per day adds up to:
50 extra minutes per agent each week.
2,000 extra minutes across a 40-person team.
Approximately 33.3 team hours per week.
Tracking recurring administrative work in the same way helps managers identify opportunities to shorten meetings, remove duplicate reporting, and return more time to production activities.
Training and coaching help BPO teams maintain service quality, particularly when hiring new agents or starting a new client account. However, employees spend part of their working hours learning processes, reviewing procedures, and developing the skills needed for their roles.
Common examples include:
New-hire onboarding and nesting periods.
Product, process, and client-specific training.
Call monitoring and feedback sessions.
Quality assurance reviews.
Refresher and compliance training.
Training time should not automatically be classified as non-billable. Some client agreements cover training or nesting periods, while others treat them as separate operating costs.
Metric: Training hours as a percentage of total worked hours, by team, alongside the time new hires take to reach target production levels.
For example, if a new team spends 20% of its worked hours onboarding during its first two weeks, managers should account for that time when reviewing production hours and planning workloads.
Training records also help managers understand how much time employees spend on learning and development. StaffViz's employee training features allow managers to create and assign courses, articles, quizzes, and assessments. They can also use course time and performance reports to track completion and review individual learning progress.
BPO operations depend on reliable systems. Agents may need CRM platforms, ticketing software, dialers, communication tools, internal applications, and stable internet access to complete their work.
When one of these systems fails, agents may be unable to continue with their assigned tasks.
Common interruptions include:
Internet connectivity problems.
Application crashes or slows down performance.
Login and access issues.
CRM or ticketing system outages.
Hardware problems and delays caused by software updates.
Metric: Employee-hours affected per incident
Employee-hours affected = Number of agents affected × Incident duration in hours
For example, if a CRM issue prevents 15 agents from accessing customer records for 20 minutes, the operational impact is:
15 × (20 ÷ 60) = 5 employee-hours
That figure shows how much working capacity the incident affected. Whether those hours qualify for client billing depends on the contract.
Logging interruptions by application, duration, and affected team also helps managers identify recurring technical problems. As a result, they can raise specific issues with IT or the client instead of relying on general reports about lost productivity.
The previous areas describe what happens during a shift. This one focuses on how the shift was planned.
A BPO can have enough agents on the schedule and still struggle to match staffing demand. Having the right number of agents available when the work arrives matters more than simply filling every scheduled position.
Typical mismatches include:
More agents are scheduled than the workload requires.
Insufficient coverage during peak hours.
Uneven task distribution between shifts is important.
Gaps between shift changes.
Agents assigned to low-volume queues.
Metrics:
Scheduled hours versus required workload hours by hour or interval.
Shrinkage percentage = (Hours unavailable for work ÷ Scheduled hours) × 100.
Historical workload patterns make these comparisons more useful. For example, if a client account consistently receives fewer requests during the first two hours of a shift, managers can review whether staffing levels or task allocation need to change.
Schedule adherence data can also reveal whether the gap comes from the staffing plan or differences between the assigned schedule and actual working patterns.
For more visibility into attendance and scheduled working hours, managers can review StaffViz attendance management.
Some agents handle work for several clients, departments, or projects. Each switch can require logging out of one account and into another, reviewing different procedures, changing applications, learning a new queue, confirming account-specific instructions, and completing handover steps.
These transitions are sometimes necessary. However, frequent switching interrupts work and make time allocation harder to track.
Metric: Account switches per agent per shift × Average transition time, alongside the hours allocated to each account.
For example, six switches in one shift at five minutes each result in:
6 × 5 = 30 minutes of transition time per agent.
Clear account assignments and documented handover procedures can reduce unnecessary transitions.
Make sure time records also identify the correct client or project. Otherwise, managers may have difficulty reconciling working hours with client invoices.
Not every interruption follows a schedule. Agents and supervisors also handle customer escalations, urgent internal support requests, rework caused by incorrect processing, supervisor assistance, unexpected compliance checks, and additional documentation or reporting.
Some of this work directly supports client service, while other activities are internal. Billability depends on the nature of the activity and the contract.
The practical problem is measurement. Unplanned work can be difficult to identify when agents do not record it consistently.
Metric: Hours per week spent on escalations and rework, grouped by cause.
When the same issue keeps appearing, a process of change, clearer instructions, or additional support may reduce the time required to resolve it.
Managers should also compare planned workloads with actual ones to see which teams regularly absorb the most unplanned work.
Billable utilization measures the share of an agent's worked time that qualifies for client billing.
Billable Utilization = (Billable Hours ÷ Total Worked Hours) × 100
For example, an agent works an eight-hour shift, and six hours qualify as billable under the client agreement:
(6 ÷ 8) × 100 = 75%
The agent's billable utilization is 75%.
The remaining two hours may include internal meetings, training, administrative tasks, or other activities. Their classification depends on the contract and the organization's time-recording rules.
For a team of 40 agents, each working eight hours, the calculation looks like this:
This calculation gives managers a starting point. However, utilization alone does not explain why the remaining hours were not billable.
For that, you need activity-level records that separate necessary operational work from unassigned time and avoidable interruptions.
Also, keep billable utilization separate from occupancy. Utilization measures the share of worked time that qualifies for client billing under a defined method. Occupancy focuses on the time agents spend handling customer interactions and related work. The two metrics answer different operational questions.
Accurate tracking starts with clear definitions. Agents and supervisors should understand which activities to record and how those activities relate to client agreements.
Here are five practical steps.
Create consistent categories for client work, internal meetings, training, administration, system interruptions, and other relevant activities.
These categories should reflect actual operations and the terms of client contracts. For example, if one client pays for approved training hours while another does not, the records should distinguish between those arrangements.
Record working hours against the relevant agent, shift, client account, or project.
This shows how time is distributed across accounts, which attendance figures alone cannot explain. It also helps managers review project costs and reconcile recorded hours with client billing.
Time records show when agents work. Activity data adds context to how that time was spent.
For example, if one team records approximately 40 minutes of inactivity during the same hour every shift while queue volume remains stable, the cause might be task routing, a recurring system issue, or a scheduling gap.
However, activity data should not be treated as proof of poor performance on its own. Read it alongside task records, assigned responsibilities, and operating conditions before drawing conclusions.
Review scheduled hours against actual working patterns and workload requirements.
This comparison highlights staffing mismatches, recurring idle periods, and differences between expected and actual activity. Over time, managers can use these patterns to make better scheduling and resource allocation decisions.
Do not wait until the end of the month to investigate unusual patterns.
Review recurring gaps, unexpected interruptions, and inconsistent time records during regular operational reviews. This helps teams address issues before they develop into larger workforce planning or client billing problems.
Timesheets and attendance reports are useful, but they do not always show what happened during the working day. Workforce analytics adds visibility to employee activity patterns, application usage, project time, and working hours.
For BPO operations, this information can help managers:
Identify recurring periods of inactivity.
See how agents spend their working time.
Review application and computer activity.
Compare activity patterns across teams.
Investigate interruptions and unusual work patterns.
Support more informed workforce planning.
StaffViz workforce productivity analytics provides reporting and activity insights that help managers review project progress, team activity, and working patterns. It's employee monitoring capabilities also provide visibility into application usage, activity patterns, and time utilization.
StaffViz also supports time records and project-based reporting through its timesheet management features. BPO managers can use these records alongside client agreements, task assignments, and operational reports when reviewing billable utilization.
However, software cannot decide whether an activity qualifies for billing under a specific client contract. Managers still need to define the right project categories, apply the agreed billing rules, and verify records before invoicing.
Monitoring works best when agents understand what is tracked and why. Explain how the data will be used, focus on identifying process and staffing problems rather than scrutinizing individuals' minute by minute, and check the labor and privacy requirements that apply where your agents work.
Want better visibility into agent working hours and project activity? Explore StaffViz time tracking and book a demo to see how its time records, timesheets, and reporting features can support your workforce management process.


Billable hours are the working hours a BPO provider can charge to a client under the agreed contract.
Billable hours qualify for client invoicing, while non-billable hours are absorbed as operating costs because the contract does not cover them.
Divide total billable hours by total worked hours and multiply by 100. For example, 60 billable hours out of 80 worked hours equal to 75% utilization.
Not always. Some client contracts cover onboarding and training, while others treat these activities as internal operating costs.
It depends on the billing agreement. Clients may pay for reserved agent capacity or scheduled coverage even when agents have no active assignments.
Monitor idle time, review workload distribution, improve scheduling, and investigate recurring operational interruptions without cutting necessary training or quality checks.
StaffViz helps managers review employee activity, working hours, and timesheets. Managers can compare these records with client contracts to identify billable and non-billable times.
Yes. StaffViz's Idle and Manual Time Report helps managers review recorded idle time and identify recurring periods of inactivity.
Yes. StaffViz provides time tracking, timesheet management, attendance records, and employee activity insights to help managers review working patterns.
Yes. StaffViz supports course assignments, articles, quizzes, and assessments. Its Course Time and Course Performance Reports help managers review employee progress and training completion.
Enhance team efficiency and collaboration with StaffViz, the ultimate tool for managing remote and hybrid teams.
Talk To Us
Powered by Staffviz