What is idle time?
Idle time is a period when a worker is available for duty but is waiting without another necessary task. In field service, it starts when an engineer lacks site access, parts, instructions or a next assignment. It ends when necessary travel, preparation, safety work, documentation, training or another duty activity starts.
That distinction matters. A gap in a diary, a stationary van or a non-billable activity does not prove that somebody was idle. First establish what the person was doing, what prevented the next step and whether the interval was planned.
Is this idle time?
Use this quick check before counting a delay:
Key takeaways
Treat idle time as a confirmed operational state, not a label for every diary gap or non-billable minute. Separate planned standby from assessed preventability, measure actual attended time consistently, and keep worker, equipment and vehicle records apart. Then fix the handoff behind the repeated delay and compare an equivalent period using the same definitions.
- Count waiting only when the worker is available and performing no other necessary task.
- Record planned status and assessed preventability as separate fields.
- Exclude breaks, but keep necessary duty activity in the attended-time denominator.
- Review travel, missed appointments and repeat visits alongside the waiting result.
The Lean Construction Institute's description of waiting waste focuses on unplanned delays affecting people, information or work between process steps. For a field-service team, that makes the handoff a useful unit of diagnosis: what should have arrived, happened or been confirmed before the engineer could continue?
What causes idle time in field service?
Most field-service waiting starts with a failed handoff rather than a lack of effort in the field. Check five points: the schedule, site information, parts and instructions, equipment availability, and office-field communication. The place where information, materials or authority stopped moving usually shows which process needs attention first and who owns it.
1. Scheduling gaps and late reassignment
A job finishes early, cancels or becomes blocked, but the office does not know that the engineer is available. The failed handoff is the status update between field and office. Record completion promptly, set an exception for blocked work and give dispatchers a clear rule for offering the next suitable job.
2. Missing access information
An engineer reaches the address but cannot enter, contact the right person or work within the site's restrictions. The failed handoff occurs before arrival: access details were not collected, checked or passed on. Confirm the appointment window, contact, keys, permits and site instructions before dispatch.
3. Missing parts or instructions
The engineer is present, but the job pack does not identify the right equipment, parts or method. This can create labour waiting, a delayed job or an unnecessary return visit. Check job readiness before allocation: scope, asset history, required skills, parts availability and special instructions should agree.
4. Equipment problems
A failed tool, machine or vehicle can stop work, but equipment downtime and labour idle time are separate records. An engineer may complete documentation, move to another job or support a colleague while equipment is unavailable. Record both resources independently so the repair duration is not automatically counted as worker waiting.
5. Slow office-field communication
Approvals, scope changes and customer decisions can stall work when the update does not reach the person who can act. Agree who owns each type of exception, what evidence they need and how quickly the job should be escalated. Useful job tracking should make a blocked status visible and give the office enough context to respond.
Planned versus unplanned idle time
Planned idle time is attended duty availability set aside without another active task, such as standby for emergency response or a protected gap before a time-critical appointment. Unplanned waiting was not built into the schedule. Record both, then assess preventability separately because planned doesn't mean wasteful and unplanned doesn't prove avoidable.
Unplanned idle time is waiting that was not built into the plan, such as an access failure, a cancelled job with no reassignment or missing parts. Unplanned does not automatically mean preventable. A customer emergency or sudden equipment fault may be outside the team's control, while a recurring access failure may be avoidable with a better confirmation step.
Keep two separate fields: whether the waiting was planned and whether it was assessed as preventable. Allow “not yet assessed” rather than forcing a conclusion before the cause is known. Report planned standby as a separate subtotal within total recorded waiting. Don't include off-duty on-call availability unless it belongs to the attended duty period you defined.
Idle time versus downtime and engine idling
Labour idle time, equipment downtime and engine idling track different resources and need separate records. A waiting engineer is a person-time measure, unavailable equipment is an asset-time measure, and a stationary vehicle with its engine running is a vehicle condition. One status doesn't automatically establish either of the others.
Hounslow Council's definition of engine idling is a vehicle engine left running while the vehicle is not moving. That tells you about the vehicle, not the engineer. The engineer could be speaking with a customer, completing a safety check or waiting. Confirm their activity separately before classifying labour time.
The same rule applies to equipment downtime. If a tool remains unavailable while its operator performs another necessary task, the equipment has downtime but the worker isn't idle during that task.
How to calculate idle time
Calculate the idle-time rate from confirmed waiting and verified attended duty in the same completed period. Divide recorded waiting minutes by actual attended work minutes excluding breaks, then express the result as a percentage. Keep necessary duty activities in the denominator, and don't calculate a rate when attendance is zero or unverified.
Idle-time rate = recorded waiting minutes ÷ attended work minutes excluding breaks, expressed as a percentage
“Attended work minutes” means actual duty time in a completed reporting period. Include necessary travel, preparation, safety work, administration, documentation, training and confirmed waiting. Exclude recorded breaks and absences. Do not substitute rostered hours for verified attendance.
This formula measures recorded waiting under your stated rules. It is not a payroll calculation, an industry target or proof of lost revenue. A lower percentage can reflect less waiting, but it can also reflect a larger denominator or incomplete records.
Record each interval consistently
For every suspected delay, capture:
- worker or resource and the relevant job.
- actual start and end time in one time zone.
- activity category before and after the delay.
- primary waiting reason and any contributing reasons.
- planned or unplanned status.
- preventable, not preventable or not yet assessed.
- evidence used to confirm the interval.
- owner and review date for any corrective action.
Count overlapping causes once per engineer. If missing access and missing parts block the same interval, record it once with one primary reason and the other as a contributing factor. If the limiting cause changes, split the interval at that point.
Do not infer idle time from a blank timesheet or a gap between location points. Mark unexplained attended time as unclassified and investigate it. Track recording coverage so an apparent improvement is not simply a decline in complete records.
For a team rate, add confirmed waiting for the same engineers and completed period, divide by their actual attended work minutes excluding breaks, then express the result as a percentage. Do not average individual percentages unless their attended-time denominators are identical. Keep person-minutes, equipment-minutes and engine-idling minutes in separate measures. When activity records are incomplete, label the result and don't compare it as equivalent to a fully reconciled period.
How to reduce idle time
Reduce idle time by fixing the recurring handoff that caused confirmed waiting, then checking whether the same delay returns. Match each cause to one corrective action, one responsible role and one verification step. Compare equivalent periods and review travel, missed appointments and repeat visits alongside the waiting result before judging the change.
Cyclehoop's account provides a practical example of the reassignment step. Its field team sent updates and evidence from incomplete work while the office viewed work in progress and reassigned jobs during the day when plans changed, as described in Cyclehoop's BigChange customer story.
Review equivalent periods with the same activity definitions and a comparable mix of work. Alongside waiting, check travel time, missed appointments and repeat visits. A change that reduces recorded waiting by sending engineers farther or rushing incomplete work has not necessarily improved the operation.
How field service software can help
Field service software can help when its records support a diagnosed process change. Scheduling and routing can support reassignment, shared job details can improve readiness, and time records can strengthen measurement. The system can't decide whether every gap was avoidable, so managers still need a confirmed activity and waiting reason.
Scheduling, routing and shared job information
Shared scheduling can help dispatchers see availability, respond to cancellations and choose a suitable next job. BigChange job scheduling can calculate routes between jobs using traffic, engineer skills and vehicle equipment. It also carries customer history, site notes and equipment details with each job, with changes reflected across the team. Route support and shared details don't replace a readiness check: somebody still needs to protect customer commitments and confirm that the job information is complete and current.
Citrus offers a related workflow example. Its case describes planning appointments around engineer location and availability, including postcode grouping on particular contracts, and recording materials used so stock could be ordered and collected weekly. See Citrus's BigChange customer story.
Time and reporting visibility
Reliable activity records make the audit possible. BigChange mobile timesheet records let engineers, technicians and operatives log start, break and end times in the mobile app. Combine those records with job status and a confirmed waiting reason. Start and end times alone cannot tell you whether an interval was waiting, necessary travel or another duty activity.
A connected field service management software workflow can bring scheduling, job information, field updates and time records together. The useful outcome is a clearer operational record: managers can trace a recurring delay to its handoff, assign the fix and check the next comparable period.
Frequently asked questions about idle time
What are idle hours?
Idle hours are the total confirmed waiting time within your reporting period. The Lean Construction Institute's description of waiting waste covers unplanned delays between people, information or work. For this audit, record actual start and end points, exclude breaks, and keep person-hours separate from equipment downtime or engine idling.
What is another way to say "idle time"?
Waiting time is the clearest alternative when you mean a confirmed period in which an available worker cannot progress and performs no other necessary task. Avoid using downtime as a direct synonym because it usually identifies an unavailable asset or resource. Define the chosen term once and apply it consistently across records.
What is normal idle time and abnormal idle time?
Normal and abnormal are less precise than planned, unplanned and preventable. The Lean Construction Institute's description of waiting waste covers unplanned delays between process steps. Your audit should then record whether each delay was planned and whether it was preventable. Planned standby can be necessary, while an unexpected delay isn't automatically preventable.
A practical next step
Start with one recurring delay reason and one completed reporting period. Confirm each waiting interval, calculate the rate with the same denominator, and identify the handoff that failed. Assign one corrective action and review an equivalent period, checking that lower waiting hasn't increased travel, missed appointments or repeat visits.
Keep the interpretation disciplined. Separate planned standby from preventable waiting, reconcile unclassified time, and check that lower waiting has not increased travel, missed appointments or repeat visits.
If disconnected schedules, job details and field updates are making that review difficult, talk to a BigChange expert about how to create a clearer field-service workflow.
