What Idle Time Costs a Plant and How It Reaches the P&L

What Idle Hours Mean on a Plant Floor

Idle time is paid time during which a worker or an asset is available to produce but is not producing. The employee is on the clock, or the machine is staffed and ready, and no output comes from that hour. A packer who clocks in at 6 a.m. and waits 40 minutes for the first pallet of film has logged 40 idle minutes. So has a filler that sits ready while the batch tank feeding it waits on a quality release.

Those minutes do not vanish because nothing was made. Payroll pays for them at the full rate. They land in direct labor, push actual hours past the standard hours the output earned, and leave fixed overhead with fewer units to spread across. Labor and overhead per unit rise together, which is why waiting belongs in any honest attempt at calculating true cost per finished unit.

The operational side of the event usually gets captured somewhere. A supervisor knows the film arrived late, and the line log may show a slow start. The financial side surfaces weeks later as an unfavorable labor efficiency variance and an under-absorption entry, with no reason attached and no way to buy the hours back. That timing gap is why the route from a time punch to the P&L is worth tracing one step at a time.

The Formula for Idle Hours

The idle time formula works in two steps. Count the idle hours, then express them as a share of the hours you paid for.

Idle hours = total paid hours minus productive hours

Idle percentage = idle hours ÷ total paid hours × 100

Total paid hours sit in timekeeping or payroll. Productive hours are the hours spent on work that moves product, usually taken from line run time, labor reported against work orders, or standard hours earned for the output. Standard hours earned is the strictest source, because it also counts slow running as unproductive. Whichever source you pick, keep it the same every period so the trend means something. For a machine, use scheduled available hours in place of paid hours and run time at rate in place of productive hours. The hours figure is what you will eventually price. The percentage is what lets you compare a 12-person line with a 40-person line, or this month with last.

A Worked Example With Round Numbers

Here is an illustration. Say a 20-person crew works an eight-hour shift on a packaging line, which is 160 total paid hours. The shift starts 30 minutes late because film was not staged, and a 42-minute quality hold later stops packing while the crew stands by. That is 72 minutes for each of 20 people, or 24 hours.

The labor report shows 136 productive hours. Idle hours are 160 minus 136, which equals 24. The idle percentage is 24 ÷ 160 × 100, or 15%. The same math scales from one person to an entire site, provided paid and productive hours cover the same window.

Nobody would call that a bad shift. The crew worked hard whenever product was there, and output probably landed a little under plan. Still, 24 paid hours produced nothing, and those are the hours to follow through the books.

How Idle Hours Differ From Downtime

Downtime is the asset not running. Idle time is paid capacity not producing. The two overlap often enough that many plants treat them as one number, and that habit is where the costing starts to go wrong.

When a filler breaks down and its crew stands by for the repair, the plant has downtime and idle hours on the same clock. But the downtime log measures the machine, and idle hours measure people on the payroll. A line can run at full rate while part of its crew waits. A line can also sit stopped while everyone who normally runs it does paid, productive work somewhere else.

For Finance, the practical risk is treating the downtime log as a measure of wasted labor. It overstates the cost when crews were redeployed and misses idle hours on lines that never stopped.

A Line Can Run While a Crew Waits

A running line carries idle hours whenever the crew is larger than the work in front of it. Picture a line staffed with 14 people for a SKU that needs 11 at its current rate. Three people spend much of the shift between tasks. Or the case packer at the end of the line keeps waiting on an upstream station that is running, just slowly.

The status board stays green and the downtime log records zero minutes, because nothing went down. Payroll still pays every one of those hours at full rate. In a standard costing plant they show up as actual hours beyond what the output earned, which is the labor efficiency variance covered below. No downtime report will flag them, so a plant that relies on downtime data alone will undercount idle labor on lines that never stop.

A Line Can Stop Without Any Idle Hours

A stopped line produces no idle hours when its crew moves to other paid work. Say a filler goes down for a two-hour repair, and the supervisor sends the crew to help sanitation prepare the next room and to cover a short-handed second line. The downtime log shows two hours. Idle hours are zero, because the people did productive work the whole time. Sending the crew home unpaid would also produce zero idle hours, though few supervisors would do that for a two-hour repair.

The labor cost still has to land somewhere. It belongs to sanitation and the second line now, and unless someone records the move, the time system keeps the hours in the home department. The receiving departments look cheaper than they were. The overhead side still takes a hit, because the stopped filler earned no output to absorb its fixed costs against.

Where Paid Idle Hours Come From

Most paid idle hours trace back to a short list of causes, and Operations can usually name the cause within minutes. Waiting on materials is the familiar one, whether that means late replenishment from the warehouse, a short supplier shipment, or a staging miss at shift start. Unbalanced staffing is another, with a crew sized for a fast SKU running a slow one. Changeovers create waits while mechanics swap tooling or sanitation finishes an allergen clean. Quality holds pause a line until the lab releases product. Early clock-ins add paid minutes before the line is ready for anyone.

None of these are mysteries on the floor. The supervisor who watched the trailer arrive late knows exactly why the first hour was slow. What goes missing is the link between that reason and the paid hours, so by the time Finance sees the cost, the story has to be rebuilt from memory. Distribution centers and 3PLs run into the same thing when pickers clocked in for a 6 a.m. start wait on a wave release or a late inbound trailer.

Some of these hours protect safety and quality, and a hold that stopped a bad lot was money well spent. Others are avoidable. Telling the two apart is the useful work.

How Idle Hours Travel to the P&L

Idle hours reach the P&L through labor and overhead at once, and both routes raise the cost of every good unit made that period. The trip takes five steps. Each step is ordinary accounting, which is part of why the total goes unnoticed, since no single entry looks wrong on its own.

The walk below follows a plant on standard costing and reuses the illustrative shift from the formula section, with 160 paid hours, 136 productive hours, and 24 idle hours. In an actual costing plant the route is shorter, because idle pay flows straight into the cost of whatever was produced, but it ends in the same place.

The Hours Land in Direct Labor

Paid idle hours post to direct labor by default, because the time system knows the employee was clocked into a production department and nothing tells it otherwise. Payroll pays all 160 hours, and labor distribution charges them to the packaging department or to whichever work orders ran that shift.

Some plants keep an indirect code for waiting, and a supervisor can move hours there. In practice the recoding is uneven, since it depends on someone noticing the wait, picking the right code, and entering it before payroll closes. Reclassified hours move into the overhead pool as indirect labor, which changes where the cost sits without making it smaller. Either way, the 24 idle hours are paid at the full rate, plus the payroll taxes and benefits that ride on every paid hour.

Actual Hours Outrun Standard Hours

Idle hours left in direct labor raise actual hours with no matching output, which produces an unfavorable labor efficiency variance. The calculation is actual hours minus the standard hours allowed for the output, times the standard labor rate.

In the illustration, the output earned 136 standard hours and the crew logged 160. At an illustrative standard rate of $30 an hour, the 24-hour gap is a $720 unfavorable variance for one shift. Repeat that shift 20 times in a month and the line carries $14,400 of it.

The figure is accurate, and it says little about cause. Waiting on film, a stale standard, slow running, and hours posted to the wrong line all produce the same unfavorable number. Good variance reporting for Operations Finance separates efficiency from rate, which is the right start. It still cannot say how much of the efficiency gap was people waiting for work.

Fixed Overhead Goes Under-Absorbed

Idle hours that cost output also leave fixed overhead under-absorbed, because standard costing applies overhead only to the output produced. Depreciation, rent, salaried supervision, and base utilities accrue by the day whether the line packs or waits. Hours that earned no output absorbed none of it.

Say fixed overhead is applied at an illustrative $50 per standard hour, and the budgeted volume counted on all 160 hours producing. The 24 hours that earned nothing leave $1,200 of that shift's fixed overhead unabsorbed. At month end the shortfall closes as an unfavorable volume variance, a mechanism laid out in this comparison of standard costing and real time costing for overhead.

This step bites hardest when the waiting stopped output, as with the late start and the quality hold. When a line kept running and only surplus crew waited, output held and the cost stays mostly in labor.

Cost Per Unit Climbs From Both Directions

Cost per unit rises on the labor side and the overhead side together, because both costs held steady while the unit count fell. In the illustration, the line runs at 50 units per standard hour, so the shift was planned for 8,000 units and made 6,800.

Crew pay of $4,800, which is 160 hours at $30, now spreads over 6,800 units instead of 8,000. That moves labor from $0.60 to about $0.71 per unit. The shift's $8,000 of budgeted fixed overhead rises from $1.00 to about $1.18 per unit. Combined, conversion cost per good unit climbs from $1.60 to about $1.88, roughly 18% higher, from 72 minutes of waiting.

Selling price did not move, so margin on every one of those units got thinner. Plants that quote or price from standard cost carry a second exposure, because the standard still says $1.60 while the product costs closer to $1.88 whenever a shift looks like this one.

Nothing Shows Up Until Close

None of this is visible in the ledger until month-end close, and by then the hours are paid and the period is over. Payroll processes punches on its own weekly or biweekly cycle. Production confirmations post on another. The ERP usually calculates and settles work order variances as part of period-end processing.

What arrives is one efficiency line per department, holding a month of waiting pooled with slow running, standards drift, and misposted hours, plus a single entry for under-absorbed overhead. Your close is a beautifully accurate autopsy. It reports precisely how much the month lost and says almost nothing about which shifts, which causes, or which hours could have been avoided.

By the time the variance review happens, the late film delivery is four weeks old. If the staging problem behind it was never fixed, the same pattern has likely repeated every week since.

Why the Floor Record and the Ledger Never Meet

Idle hours stay hidden because the operational event and its financial consequence live in different systems that share no common key during the period. The time system knows who was clocked in, against which home department, and for how long, but not whether that person was producing. The production system knows when the line ran and sometimes why it stopped, but not who stood at it or what their hours cost. The ERP holds standards, rates, and overhead, and it waits for both to post.

Joining them by hand means exporting punches and production, matching them by line and shift in spreadsheets, and pricing the gap. The exercise is slow enough that it usually happens once a month, if at all, which is the core argument for moving from a monthly variance report to a live view of production cost.

Both teams are doing their jobs here. Operations holds the reason, Finance holds the cost, and during the month neither side has both.

Pricing Idle Hours While the Month Is Still Open

Pricing idle hours inside the period takes labor punches, production records, and standards tied together by line, shift, and SKU as the work happens. As AI-Native Controllership software, Jetson lets Finance teams at manufacturers, distributors, and 3PLs connect operating data to the ledger and explain where cost went. The ERP stays where it is, and Jetson extends it, sending reconciled operational data back once the hours tie out.

Attribute and Investigate do most of the work on idle hours. Attribute assigns each paid hour to the department, line, and SKU where it was spent, including mid-shift moves, using punches from ADP, UKG, or Paylocity, production data from sources such as Redzone, and standards from SAP, Microsoft Dynamics 365, or Infor. Investigate quantifies what idle hours cost in efficiency variance and lost absorption, distinguishing necessary costs from avoidable spend, so standby during a quality hold and a wait on late film get treated differently. Because the attribution runs continuously, the efficiency variance and the absorption shortfall build day by day in the department that incurred them, where Finance can watch them form.

That gives Operations a specific, answerable question while the week is still live, such as what held up film on Tuesday's first shift. Early clock-ins are paid idle hours too, and they show what finding the cost inside the week is worth. In one published customer result, roughly $100,000 in unapproved early clock-ins was identified mid-week, before the cost reached payroll.

Bringing Idle Hours Into the Month They Happen

Idle hours will never reach zero, and some of them protect safety, quality, or a customer commitment. The aim is knowing which ones, and what they cost, while the week can still change. With Jetson, Finance and Operations work from the same record of paid hours, output, and cost, so idle labor gets explained in the week it happens. Request a demo and see idle hours attributed on your own lines.

Frequently Asked Questions

Are Idle Hours the Same as Downtime?

No. Downtime measures an asset that is not running, while idle hours measure paid people or ready equipment that are not producing. The two overlap when a crew stands by during a breakdown. A running line can still carry idle labor, though, and a stopped line can carry none if its crew moves to other paid work. Using the downtime log to measure wasted labor miscounts in both directions.

Is Idle Labor a Direct or Indirect Cost?

It depends on how the plant codes it. By default, paid idle hours stay in direct labor, because the employee was clocked into a production department. Plants that use an indirect waiting code move those hours into manufacturing overhead instead. Both treatments raise cost per unit. The direct route shows up as an unfavorable labor efficiency variance, and the indirect route inflates the overhead pool.

Can Payroll Data Alone Show Idle Hours?

No. Payroll shows paid hours, and the idle calculation also needs productive hours from production records such as line run time, work order labor, or standard hours earned. Finding idle hours means joining the two sources by person, line, and shift. Without that join, idle labor stays folded into total labor cost and appears only as an efficiency variance at close.

What Is a Normal Level of Idle Hours?

No reliable published benchmark exists for idle time across industries, because plants define productive hours differently and record waiting with different levels of discipline. Your own trend by line, shift, and cause is a better reference. A rising share on one line usually points to a specific cause, such as material staging or a crew sized for a different SKU, that Operations can fix once it is visible.

‍