What is the difference between scheduled time and productive time?

Scheduled time is the hours committed on the plan. Productive time is the hours that delivered work against a job specification. The gap is created by travel, idle gaps, cancellations, readiness failures on arrival and return visits. Reviewing only scheduled time makes a busy branch look efficient, which is why utilisation programmes that start from the schedule rarely change the outcome.

How do we know whether low utilisation is a demand problem?

Compare idle time with backlog. Low backlog and high idle time indicates a demand constraint, and the response is capacity or coverage. High backlog with high idle time indicates the work existed and was not delivered, which points to route design, sequencing, backfill rules or job readiness. Acting on the wrong one usually turns a cost problem into a service problem.

Should utilisation targets be the same in every branch?

No. Achievable utilisation depends on territory density, job mix and travel distance, so a rural branch and an urban branch cannot be held to one number. The definition of productive time should be identical everywhere; the target should be set against each branch's own trailing performance and against genuinely comparable branches.

Does higher utilisation always improve service?

No. Utilisation pushed too high removes the slack that absorbs emergency work, overruns and absence, and the first visible effect is usually missed appointments and rescheduling. Utilisation should be governed alongside missed appointment rate and service-level exposure, so the trade-off is made deliberately rather than discovered later.

How early can utilisation drift be seen?

Within the current week in most operations, because the leading signals are time based and already recorded: travel share, idle gaps, cancellation lead time, readiness failures and backlog ageing. The delay is almost never data availability. It is that these signals sit in separate systems and are reconciled monthly.

Does Garuda schedule crews or optimise routes?

No. Garuda is a decision layer above scheduling, dispatch, field-service, telematics and finance systems. It shows where productive time is being lost, what it is costing in service and margin terms, and who owns the response. Scheduling, dispatch and route planning remain with the systems and teams that already perform them.

How Can Field-Service Leaders Improve Crew Utilisation?

Direct answer. Crew utilisation improves when leadership measures productive time rather than scheduled time, and can see where the difference between the two is being created: travel, idle time between jobs, cancellations, jobs that were not ready when the crew arrived, skill mismatches that force a return visit, and route design that spreads work too thinly across a branch. A fully booked schedule is not the same as a productive day, which is why utilisation can decline while crews report being busy. The corrective action depends on the cause, so the reading has to separate genuine demand variation from route, scheduling and job-readiness problems, and then attach the pattern to the branch, route or function that can change it, before the backlog turns into missed appointments and service-level risk.

Executive buyer: CEO, COO, Operations Director, Branch Manager, Service Delivery lead
Connected view: Schedule, crew, route, travel, job readiness, backlog, service, finance
Cadence: Weekly governed review by branch and route, with daily reading on missed appointments
Scope boundary: Leadership visibility layer, not a scheduling, dispatch or route optimisation system

Author: GritWiz Executive Research, Decision intelligence editorial team
Published: 2026-07-10
Updated: 2026-07-10

Crew utilisation metric framework for field-service leadership

A governed set, defined identically in every branch and read weekly. Productive time is the anchor metric; the remaining groups explain why productive time and scheduled time differ.

Time use

Productive time share: Productive on-site hours as a share of scheduled crew hours, defined identically across branches.
Travel time share: Drive time as a share of paid crew hours, by branch and route.
Idle time between jobs: Unfilled gaps between consecutive jobs, by crew and day of week.
Overtime against productive hours: Overtime hours set against the productive hours delivered in the same period.

Schedule integrity

Cancellation rate and lead time: Cancellations split by originator and by how much notice was given.
Backfill success rate: Share of cancelled slots refilled with backlog work on the same day.
Schedule adherence: Jobs started within the planned window, by branch and route.

Job readiness

Readiness failure rate: Visits where work could not start on arrival, categorised by cause such as access, parts, permits or customer availability.
Skill-match failure rate: Visits where the assigned crew could not complete the work as specified.
Return visits from readiness or skill causes: Follow-up visits traced to readiness or skill-matching failures rather than to fault recurrence.

Demand and capacity

Backlog ageing: Outstanding work by age, compared with available crew capacity in the same period.
Demand variation by branch: Job volume against the trailing period, by branch and job type.
Route density: Jobs completed per route against distance travelled.

Service exposure

Missed appointment rate: Committed appointments not met, by branch and cause.
Service-level exposure: Contracted commitments at risk within the current period.
Reschedule frequency per customer: Customers rescheduled more than once within a defined window.

Ownership

Owner assigned: Whether each surfaced utilisation pattern carries a named accountable role.
Action ageing: Time a surfaced pattern has remained open without a closed action or a documented decision.

Where scheduled time becomes productive time Scheduled hours pass through travel, arrival, readiness and completion before any of them count as productive. Each transition has an owner and a measurable loss, which is why a full schedule can still produce a low productive share.

Scheduled Crew hours committed to planned work. Owner: Scheduling lead. Signal: schedule adherence and planned job duration accuracy.
Travel Movement between jobs across the territory. Owner: Scheduling and Branch Manager. Signal: travel time share and route density.
Arrival Crew on site and able to begin. Owner: Service Delivery lead. Signal: readiness failure rate by cause.
Productive work Work delivered against the job specification. Owner: Branch Manager. Signal: productive time share and skill-match failure rate.
Completion Job closed with no return visit required. Owner: Service Delivery lead. Signal: first-visit completion and return visits from readiness causes.

Why crew utilisation declines

Utilisation falls for structural reasons far more often than for effort reasons. The schedule is built on assumptions about travel, duration and readiness, and every assumption that is wrong converts paid crew hours into non-productive hours somewhere in the day.

The difficulty for leadership is that the loss is distributed. Twenty minutes of extra drive time, a job that was not ready, a cancellation that arrived too late to backfill and a return visit for the wrong skill mix are each small and locally explainable. Aggregated across crews, branches and weeks they become the difference between an acceptable and an unacceptable cost base, and none of them appear on a schedule that shows the day as full.

Scheduled versus productive time: the schedule counts commitment, not delivered work
Travel time: route design and job sequencing determine how much of the day is spent driving
Idle time: gaps between jobs that are too short to fill and too long to ignore
Cancellations: late cancellations create capacity that cannot be backfilled
Job readiness: access, permits, parts, customer availability or prior work not complete on arrival
Skill matching: the assigned crew cannot complete the work, so a second visit is created
Crew availability: leave, training, absence and vehicle downtime absorbed into the same plan
Demand variation: seasonal, contractual and geographic swings that the schedule was not rebuilt for
Overtime: used to recover a day that lost productive hours earlier
Branch context: urban and rural branches face materially different achievable utilisation

Why busy crews can still be unproductive

A crew can be occupied for every hour of the working day without adding billable or contractual value for most of it. Occupancy is a measure of commitment; productivity is a measure of work delivered. When only the schedule is reviewed, the two are treated as the same number.

The day is full, but three of the jobs are return visits for work already paid for
The crew is on the road for a large share of the day because two jobs sit at opposite ends of the territory
A job was reached on time and could not be started because access or parts were missing
A cancellation left a gap that arrived too late to fill with waiting backlog work
The crew assigned had the availability but not the skill, so the visit produced a follow-up rather than a completion

Which signals show utilisation drift early

The early signals sit between the schedule and the completed job, and they are already recorded in scheduling, field-service, telematics and service systems. What is usually missing is a consistent definition of productive time across branches, so the numbers cannot be compared and the drift is not visible until backlog or missed appointments make it obvious.

Productive time as a share of scheduled time, defined identically across branches
Travel time share and average distance between consecutive jobs
Idle time between jobs, by crew and day of week
Cancellation rate and cancellation lead time, split by customer-initiated and centre-initiated
Job-readiness failure rate on arrival, by cause category
Skill-match failure rate and the return visits it generates
Backlog ageing against available capacity
Overtime hours set against productive hours for the same period
Missed appointment rate and service-level exposure by branch

How to separate demand variation from route, scheduling and readiness problems

Demand variation and execution problems produce a similar headline: utilisation is down. The corrective actions are opposite. Rebalancing crews against a genuine demand fall protects cost. Rebalancing crews when the real cause is job readiness removes capacity from a branch that is about to miss its service commitments.

The test is whether the work existed and was not delivered. If backlog is low and idle time is high, demand is the constraint. If backlog is high while idle time is also high, the constraint is inside the operation: route design, sequencing, readiness or skill matching. If travel time share is rising while job counts hold, the constraint is route density.

Low backlog with high idle time: demand variation, so rebalance capacity and review coverage
High backlog with high idle time: scheduling, sequencing or dispatch rules, not demand
Stable job count with rising travel share: route design and territory boundaries
Normal travel with falling completions: job readiness and skill matching
Utilisation gap isolated to specific branches: local operating discipline or branch context, judged against a comparable branch

What poor utilisation costs across time, effort, money and quality

Utilisation loss is paid for twice: once in the crew hours that produced nothing, and again in the service commitments that were pushed into the following week.

Time: capacity lost to travel and idle gaps, backlog ageing, and corrective action delayed to the next review cycle
Effort: manual rescheduling, repeated customer follow-up, branch-by-branch investigation to explain a utilisation number
Money: paid non-productive hours, overtime used to recover lost days, poor route density, and revenue deferred with the backlog
Quality: missed appointments, second visits for work that should have completed first time, inconsistent service between branches
Trust: customers rescheduled more than once, and account or contract confidence eroded before renewal
Leadership confidence: utilisation debated rather than governed, because each branch computes it differently

Which owner should act, and what action should follow

Utilisation drift is only actionable once the pattern is attached to the role that controls the cause. Most utilisation programmes stall because the number is reported to leadership while the levers sit with scheduling, branch operations and the functions that prepare the job.

Branch or Operations Manager: crew mix, local sequencing, absence cover and branch operating discipline
Scheduling or Dispatch lead: route design, territory boundaries, job sequencing and backfill rules for cancellations
Service Delivery lead: job readiness standards, parts and access preparation, skill-matching rules
Customer or Contract lead: cancellation behaviour, appointment windows and contractual commitments
COO: capacity decisions across branches, and the trade-off between utilisation targets and service reliability

Utilisation causes and what leadership feels later The operating cause on the left is measurable in the current week. The consequence on the right is usually the first version leadership sees, once backlog or service commitments have already moved.

Cause	Consequence
Jobs sequenced across a wide territory	Travel absorbs the day; the branch appears fully booked and delivers fewer completions
Late cancellations with no backfill rule	Paid capacity idles while backlog ages in the same branch
Access, parts or permits not confirmed before dispatch	Crews travel, cannot start, and a second visit is created for work already scheduled once
Crew assigned on availability rather than skill	Visit produces a follow-up instead of a completion, and the customer is rescheduled
Schedule built on outdated job durations	Days overrun, overtime recovers the promise, and the cost lands outside the job record
Demand variation not reflected in crew deployment	One branch idles while a neighbouring branch runs a growing backlog
Utilisation defined differently in each branch	Group comparison is unusable, so drift is argued rather than acted on

Which reading separates demand from route, scheduling and readiness Read the columns together before deciding. Removing capacity from a branch whose real constraint is job readiness converts a utilisation problem into a service-level problem.

Points to demand variation

Backlog low against available capacity
Job volume below the trailing period
Idle time rising with normal travel share
Cancellation rate broadly unchanged

Points to route or scheduling

Backlog high while idle time is also high
Travel time share rising with a stable job count
Route density falling in one territory
Cancelled slots rarely backfilled

Points to job readiness or skill

Readiness failures concentrated by cause category
Return visits traced to readiness or skill mismatch
First-visit completion falling in one branch
Reschedules concentrated on specific customers or job types

From surfaced utilisation pattern to owned action The sequence a weekly leadership review should follow once utilisation drift appears, so the review closes with an owner, an action and a review date.

Surface Name the branch, route or crew group where productive time has fallen against its own trailing reading.
Classify Decide whether the cause is demand variation, route design, scheduling rules, job readiness or skill matching.
Assign Attach one accountable role: Branch Manager, Scheduling lead, Service Delivery lead, Contract lead or COO.
Act Approve the structural change: route or territory adjustment, backfill rule, readiness standard or crew deployment change.
Review Set the review date and the existing signal, usually productive time share with backlog ageing, that will show whether it worked.

Worked example: full schedules, falling productive time in two branches

A field-service company reviews utilisation monthly and sees crews scheduled close to capacity across every branch. Completions per crew decline over several weeks, backlog ages in two branches, and the branches report that the teams are working flat out.

Symptom Schedules close to full across the network; completions per crew and productive time share falling in two branches.
Hidden operating signal Travel time share is rising on the routes those branches run, late cancellations are not being backfilled, and readiness failures on arrival are concentrated in one cause category.
Service consequence Appointments are pushed into the following week, some customers are rescheduled more than once, and contracted commitments move into the risk window.
Margin consequence Paid hours produce fewer completions, overtime is used to recover the lost days, and deferred work carries revenue into the next period.
Metric that reveals it Productive time share by branch, read together with travel time share, backfill success rate, readiness failure rate by cause and backlog ageing.
Responsible owner Scheduling lead for route design and backfill rules, Service Delivery lead for the readiness cause, Branch Manager for crew deployment in the two branches.
Immediate action Tighten job sequencing in the affected territories, introduce a same-day backfill rule for late cancellations, and confirm readiness before dispatch for the failing cause category.
Leadership decision required Decide whether capacity is rebalanced between branches or the territory boundaries change, with a named owner, a review date and a success signal before the backlog reaches the service-level threshold.

Leadership acts on route, backfill and readiness while the backlog is still recoverable, rather than adding crews against a utilisation number that would not have improved.

Illustrative example based on recurring patterns in multi-branch field-service operations. Not a specific client attribution. No figures are presented as benchmarks.

Leadership checklist for improving crew utilisation

If more than two of these cannot be answered clearly at the weekly leadership review, the visibility layer is the constraint, not the branch.

Which branch has utilisation drift against its own trailing reading?
Are crews scheduled or actually productive?
Is travel time rising while job counts stay flat?
Are cancellations creating idle capacity that backlog could have filled?
Are jobs ready before crews arrive, and which cause fails most often?
Is skill matching creating return visits?
Is the pattern demand variation or an execution constraint?
Which route, crew or branch owns the issue?
Is the issue visible before the weekly or monthly review?

Executive FAQ

What is the difference between scheduled time and productive time?: Scheduled time is the hours committed on the plan. Productive time is the hours that delivered work against a job specification. The gap is created by travel, idle gaps, cancellations, readiness failures on arrival and return visits. Reviewing only scheduled time makes a busy branch look efficient, which is why utilisation programmes that start from the schedule rarely change the outcome.
How do we know whether low utilisation is a demand problem?: Compare idle time with backlog. Low backlog and high idle time indicates a demand constraint, and the response is capacity or coverage. High backlog with high idle time indicates the work existed and was not delivered, which points to route design, sequencing, backfill rules or job readiness. Acting on the wrong one usually turns a cost problem into a service problem.
Should utilisation targets be the same in every branch?: No. Achievable utilisation depends on territory density, job mix and travel distance, so a rural branch and an urban branch cannot be held to one number. The definition of productive time should be identical everywhere; the target should be set against each branch's own trailing performance and against genuinely comparable branches.
Does higher utilisation always improve service?: No. Utilisation pushed too high removes the slack that absorbs emergency work, overruns and absence, and the first visible effect is usually missed appointments and rescheduling. Utilisation should be governed alongside missed appointment rate and service-level exposure, so the trade-off is made deliberately rather than discovered later.
How early can utilisation drift be seen?: Within the current week in most operations, because the leading signals are time based and already recorded: travel share, idle gaps, cancellation lead time, readiness failures and backlog ageing. The delay is almost never data availability. It is that these signals sit in separate systems and are reconciled monthly.
Does Garuda schedule crews or optimise routes?: No. Garuda is a decision layer above scheduling, dispatch, field-service, telematics and finance systems. It shows where productive time is being lost, what it is costing in service and margin terms, and who owns the response. Scheduling, dispatch and route planning remain with the systems and teams that already perform them.

Sources and further reading

How Garuda supports crew utilisation visibility

Garuda connects schedule, crew, route, branch, job-readiness, service and financial signals from the systems a field-service business already runs, surfaces utilisation exceptions that need leadership attention with consequence and context, supports ownership and follow-up on each surfaced pattern, and lets executives ask operational questions across those connected systems. Garuda does not replace scheduling, dispatch, FSM, CRM, ERP, payroll or technician applications, and it is not a route optimisation engine.

See How Garuda supports crew utilisation visibility

Related analysis

Assess where crew utilisation visibility is delayed

Walk through where schedule, travel, idle time, cancellation, job-readiness and branch signals are reaching leadership after the capacity has already been lost. See Garuda in action during the same session.

Assess where crew utilisation visibility is delayed