How is throughput rate calculated in this template?

Throughput rate in parts per hour equals good units divided by runtime minutes, times 60. If a shift makes 1,850 good units in 410 minutes of runtime, the rate is 1,850 / 410 x 60 = 271 parts per hour. Using runtime rather than the full shift length isolates the rate while the machine is actually producing, so you can compare it cleanly against a design or target rate later.

What is the difference between theoretical and actual throughput?

Theoretical throughput is what the line would make at design cycle time with zero downtime and no rejects, computed as 3,600 divided by cycle time in seconds for parts per hour. Actual throughput is what you logged from real production. A 4 second cycle implies 900 parts per hour theoretical. If you actually made 690, the gap is 210 parts per hour, about 23 percent, attributable to stoppages and slow cycles.

Why use good units instead of total units for throughput?

Good units reflect saleable output, so basing rate on them captures quality loss automatically. If a shift ran 2,000 total units but 120 were scrapped or reworked, only 1,880 are good, and using total units would overstate real throughput by 6.4 percent. Log both columns so the difference shows your reject rate, then use good units for the rate that matters to shipping and cost.

How many shifts should I log before trusting the baseline?

Log at least 15 to 20 shifts, roughly two to four weeks of two shift operation, before treating the average rate as a baseline. Fewer than 10 shifts lets a single bad changeover or a strong day skew the mean. Watch the spread too. If shift rates swing more than 15 percent around the average, your process is unstable and the baseline is less meaningful than fixing the variation first.

How do I quantify the throughput gap to target?

Percent of target equals average actual rate divided by target rate, times 100. If your target is 300 parts per hour and you averaged 264, you are at 88 percent, an 12 percent gap. Convert to units by multiplying the shortfall rate by runtime hours: 36 parts per hour short over a 7 hour runtime is 252 units lost per shift, which frames the size of the improvement opportunity in real terms.

How do I link throughput loss to specific causes?

Use the notes column on each shift row to tag the dominant loss, then compare rates across tagged shifts. Throughput loss splits into three buckets: availability loss from downtime, performance loss from slow cycles and minor stops, and quality loss from rejects. If actual rate is 85 percent of target but downtime only explains 8 points, the remaining 7 points are slow cycles or micro stoppages worth investigating.

Production and Throughput

Throughput Analysis Spreadsheet Template

Calculate actual and theoretical throughput for a line, machine, or shift and quantify the gap to target production rate.

Overview

This template lets production managers, line leads, and continuous improvement engineers measure what a line, machine, or shift actually produces against what it theoretically could. It is for anyone who suspects the gap between nameplate rate and real output but cannot yet quantify it. Guessing throughput from a busy day is misleading. Logging good units and runtime per shift gives you a defensible rate in parts per hour and shows exactly how many units downtime and slow cycles cost you.

You log date, shift, machine, good units, total units, and runtime in minutes per entry. Throughput rate is good units divided by runtime minutes times 60, so it is already normalized to parts per hour and comparable across shifts of different lengths. The daily and weekly summary rolls up total good units, total runtime, average rate, your target rate, and percent of target. The notes column ties each shortfall to a cause so the number connects to a reason.

In practice, log every shift for two to four weeks to build a baseline, then read percent of target. A line running 78 percent of target rate is telling you roughly 22 percent of capacity is lost to downtime, slow cycles, or scrap. Use the good versus total units split to separate quality loss from speed loss. Pair it with the live Throughput Calculator to check a single shift instantly, then bring the logged history into a review meeting.

What this template includes

Cycle time and available production time
Planned and unplanned downtime
Theoretical throughput calculation
Actual throughput from production records
Throughput gap in units and percentage
Shift and daily summary rows
Notes column for downtime reasons

Suggested use case

Use this to measure actual vs. theoretical output for a shift, day, or week, and to quantify the impact of downtime and slow cycles on production.

How to use it

Enter cycle time and shift available time.
Log downtime events during the period.
Enter actual units produced.
Review the gap between theoretical and actual throughput.
Use the notes column to link throughput loss to specific causes.

Frequently Asked Questions

How is throughput rate calculated in this template?: Throughput rate in parts per hour equals good units divided by runtime minutes, times 60. If a shift makes 1,850 good units in 410 minutes of runtime, the rate is 1,850 / 410 x 60 = 271 parts per hour. Using runtime rather than the full shift length isolates the rate while the machine is actually producing, so you can compare it cleanly against a design or target rate later.
What is the difference between theoretical and actual throughput?: Theoretical throughput is what the line would make at design cycle time with zero downtime and no rejects, computed as 3,600 divided by cycle time in seconds for parts per hour. Actual throughput is what you logged from real production. A 4 second cycle implies 900 parts per hour theoretical. If you actually made 690, the gap is 210 parts per hour, about 23 percent, attributable to stoppages and slow cycles.
Why use good units instead of total units for throughput?: Good units reflect saleable output, so basing rate on them captures quality loss automatically. If a shift ran 2,000 total units but 120 were scrapped or reworked, only 1,880 are good, and using total units would overstate real throughput by 6.4 percent. Log both columns so the difference shows your reject rate, then use good units for the rate that matters to shipping and cost.
How many shifts should I log before trusting the baseline?: Log at least 15 to 20 shifts, roughly two to four weeks of two shift operation, before treating the average rate as a baseline. Fewer than 10 shifts lets a single bad changeover or a strong day skew the mean. Watch the spread too. If shift rates swing more than 15 percent around the average, your process is unstable and the baseline is less meaningful than fixing the variation first.
How do I quantify the throughput gap to target?: Percent of target equals average actual rate divided by target rate, times 100. If your target is 300 parts per hour and you averaged 264, you are at 88 percent, an 12 percent gap. Convert to units by multiplying the shortfall rate by runtime hours: 36 parts per hour short over a 7 hour runtime is 252 units lost per shift, which frames the size of the improvement opportunity in real terms.
How do I link throughput loss to specific causes?: Use the notes column on each shift row to tag the dominant loss, then compare rates across tagged shifts. Throughput loss splits into three buckets: availability loss from downtime, performance loss from slow cycles and minor stops, and quality loss from rejects. If actual rate is 85 percent of target but downtime only explains 8 points, the remaining 7 points are slow cycles or micro stoppages worth investigating.