Your assembly cell worked fewer hours than the shift plan, but the labor efficiency variance is unfavorable. Check the hours the actual output earned under its standard. If the cell completed fewer units or switched to a product with a shorter routing, it can earn fewer standard hours even as clock hours fall.
Subtract standard labor hours allowed for actual output from actual direct labor hours, then multiply by the standard hourly rate. A positive result is unfavorable in this convention because the operation used more time than its standard allowed. Use the standard wage rate for the efficiency calculation so a change in pay does not change the cost assigned to the hour difference.
Match charged hours and output to the operation
Start from the completed quantities and the approved routing (the sequence of operations and their standard times). Calculate earned hours for each product and operation. Where the standard includes a fixed setup allowance per qualifying batch, count the approved setup separately from the per-unit run time. Multiplying setup time by every unit would grant hours for setups that never took place.
Use actual hours posted to the corresponding production operation. Check the meaning of a recorded hour before adding time from more than one system. A machine can run for an hour while two people staff it, resulting in two direct labor hours. A shift timecard can also include work charged to other operations. Where the system posts standard time on completion, keep it distinct from observed clock time.
OpenStax uses the actual production level in its direct labor time variance calculation. Keep the rate aligned to the labor group being measured. If operations use different standard rates, value each operation’s hour difference at its own rate before summing the dollar amounts. A single blended rate can change the reported result when the work shifts across groups.
Separate extra hours from an above-standard wage rate
Assume an assembly cell finished 300 units of A at 0.20 standard labor hours each and 100 units of B at 0.50 hours each. There is a shared $25 standard hourly rate, no separate setup allowance in this example, and all 120 recorded direct hours are attributable to those completions. The actual labor cost is $3,240, or $27 per hour.
| Measure | Calculation | Result |
|---|---|---|
| Standard hours earned | (300 × 0.20) + (100 × 0.50) | 110 hours |
| Labor efficiency variance | (120 − 110) × $25 | $250 unfavorable |
| Labor rate variance | 120 × ($27 − $25) | $240 unfavorable |
| Total direct labor variance | $3,240 actual − (110 × $25) standard | $490 unfavorable |
The cell used ten hours more than the actual output earned, which accounts for $250 of the cost difference. The remaining $240 comes from paying $2 more per hour across the 120 hours worked. If the shift plan called for 130 hours, comparing actual with that plan would imply ten hours saved. That planned number describes staffing expectations and would give the opposite sign for the efficiency question.
Resolve timing and routing differences before assigning causes
Pull the standard and time records for the operations with the largest hour gaps. Confirm the routing revision in use and whether the recorded time covers setup, run, or rework. An added inspection step may be legitimate work under a process change that has yet to reach the standard. Rework can consume hours with no new completion. Keep the rework time visible instead of crediting the same finished unit twice.
Check the cutoff where operations span shifts or periods. A time entry may post on Friday and the related completion on Monday. Reconcile the example at the closed-order level, then check how your plant assigns hours and earned output to work in process for period reporting. Keep a reference to any time that was posted to the wrong operation so correcting it does not erase why the first report differed.
Review sustained unfavorable gaps alongside downtime or quality events before changing staffing assumptions. A delay attributed to tooling needs evidence from the operation rather than a deduction from the dollar amount. Use production downtime tracking to find the interruption record that can support that explanation.
The fixed overhead volume variance uses standard activity to explain how much fixed overhead the plant absorbed. Keep the labor variance at the operation level until the time postings reconcile. The hours earned in a direct labor calculation can use a different activity base from the machine hours used to apply overhead.
If the shop changes crew size during the run, inspect each worker’s charged time or use a record that already represents crew labor hours. Multiplying the duration of a whole run by the final crew size can overstate the time when staffing changed partway through. If actual direct hours and actual wages come from separate reports, reconcile them to the same group and period before calculating an actual hourly rate. A payroll accrual for another shift can otherwise appear to be a wage premium on this operation.
Keep reported and corrected hours visible in the variance review when a time entry is amended. Someone investigating the original result should be able to identify the entry that changed and the completion it belonged to without comparing separate versions of the spreadsheet.
Inspect the operation key on a time record
Open a supported source and check whether permitted time records and completion records identify the same production operation.
Where Permute fits in direct labor review
Permute is the context layer we sell between business records and the AI tools people use. We can connect supported sources and use your identifiers to relate labor transactions, operation completions, and approved routing versions.
We can use your declared rules to separate the hour and wage effects in a recurring report. Reviewers can see the hours and wage basis as permitted by their access, while an operations report can show hour exceptions without exposing payroll detail.
A cost accountant can ask why one cell’s cost variance rose and trace the hour effect to permitted operation records and standard revisions.
Leave payroll and routing approvals with their owners
We read from connected systems and do not write back to the system of record. Payroll owners confirm what counts in actual labor cost, and engineering and costing owners approve changes to time standards and rates.
Use the cost bridge to route the investigation
Labor efficiency variance measures excess or saved hours for the output the cell made, priced at the standard wage. In the assembly example, the cell used ten excess hours worth $250 at that rate. The higher wage accounts for another $240, which can be reviewed against payroll. Use the operation records and routing version to explain the time difference before changing the standard.
Review a labor variance with Permute
Bring the standard routing, one completed order, and the operation time and rate records you are permitted to share.
Questions about the labor efficiency calculation
Can efficiency variance be zero when labor cost is over standard?
Yes. Actual hours can match the hours earned while the actual wage exceeds the standard rate. In that case the difference sits on the rate side of the bridge.
What if the routing uses minutes and labor records use hours?
Convert the routing time to hours before comparing it with actual hours and multiplying by a rate per hour. Retain the original unit and conversion so a reviewer can reproduce the calculation.