All articles

Takt Time Calculation: Formula, Excel Setup, Worked Example

By Davina · Published

Key takeaways

  • Takt time equals net available production time divided by customer demand for that same period, expressed in time per unit.
  • Net available time excludes breaks, changeovers, and planned maintenance; using gross shift length makes takt look more forgiving than the line can run.
  • If cycle time at the constraint exceeds takt time, the gap is your demand gap and system output is capped by the constraint, not by takt.
  • In Excel, keep labels in column A and inputs in column B so takt formulas never change when client inputs do, and compute per-day takt across a week using MIN to find the tightest target.
  • Takt time is a scoping number that locates the constraint now; it cannot predict where the bottleneck moves after an improvement, which requires a constraint model.

Takt time calculation tells you the pace demand sets for your process: available work time divided by customer demand over that time. This guide runs one line, one shift, and one demand number through the formula, an Excel build, and a side-by-side comparison with cycle time, so you can see demand pace and actual pace on the same numbers.

What Is Takt Time and Why Calculate It?

Takt time is the pace of customer demand: available production time divided by customer demand for that period. The Lean Enterprise Institute defines it as the rate at which a product must be completed to meet customer demand, and its Lean Lexicon is the standard reference for the terminology used throughout this guide.

The calculation supports one decision: whether your process can keep up with demand at its current capacity. If cycle time exceeds takt time at any station, you have a constraint and a demand gap you can quantify before quoting work.

Takt time is a scoping number, not a scheduling engine. It tells you where to look, which is the same first step the Constraint Impact Calculator applies to any process.

What Is the Takt Time Calculation Formula?

Takt time = available production time ÷ customer demand. Both inputs must use matching units: if available time is in seconds, demand is units per that same period, and the output is seconds per unit.

Available time: what to include and exclude

Available time is net run time, not shift length. Start with scheduled shift time, then subtract planned downtime: breaks, changeovers, planned maintenance, meetings. A 480-minute shift with 45 minutes of breaks and 20 minutes of changeover gives 415 minutes of real capacity. Excluding planned downtime matters because takt describes the pace operators must actually sustain, not a theoretical maximum.

Customer demand: which number to use

Use the demand for the period you measured time against, typically average daily demand over a representative window. If the customer wants 1,000 units per week across 5 days, daily demand is 200. Don't average across seasonal peaks blindly; scope against peak-period demand or you'll size the line for a quiet month. Once you have both numbers, the constraint that limits output to that pace is the next thing to find, and the bottleneck analysis in our constraint guide (https://improvefirst.com/learn/bottleneck-payoff-before-simulation) shows how to locate it before any deeper modelling.

Takt Time Calculation Example: One Line, One Shift

Step 1: work out net available time

One shift runs 8 hours with a 30-minute lunch and two 10-minute breaks. Net available time is 480 minus 50, which leaves 430 minutes, or 25,800 seconds. This is the time the line can actually produce, not the time people are on site.

Step 2: divide by demand

The customer orders 215 units per shift. Takt time = 25,800 seconds ÷ 215 units = 120 seconds per unit, or 2 minutes. Takt time describes demand pace, not machine speed; the distinction between takt and cycle time is standard in operations references such as Wikipedia's takt time entry.

Step 3: read the result as a pace target

Here is the same calculation written out as one flow, because this is the paragraph worth lifting for a client memo. A shift of 480 minutes minus a 30-minute lunch and two 10-minute breaks gives 430 minutes of net available time. Demand is 215 units, so 430 ÷ 215 gives a takt time of 2.0 minutes per unit. Every station on the line now has a target: complete one unit every 120 seconds to hit 215 by shift end. If any station's cycle time exceeds 120 seconds, that station is the constraint and total output caps at net available time divided by that station's cycle time, not by takt. Scope that gap before quoting (see the limits of any such estimate at https://improvefirst.com/legal/disclaimer).

How Do You Set Up a Takt Time Calculation in Excel?

Cell layout and formulas

Build the sheet in column A labels, column B values, so you can swap client inputs without touching formulas. Use these cells:

CellLabelExample value
B2Net available time per shift (minutes)420
B3Breaks and planned downtime (minutes)45
B4Net working time (minutes)=B2-B3
B5Daily customer demand (units)90
B6Takt time (minutes/unit)=B4/B5

B6 returns 4.17 minutes per unit. If you work in seconds instead, use =B4*60/B5. The formula never changes; only the inputs do. Keep one row per shift if a client runs two shifts with different demand splits.

Converting between seconds, minutes, and hours

Pick one unit per sheet and label it in the header. To convert: hours to minutes multiply by 60, minutes to seconds multiply by 60. If takt comes out under a minute, show it in seconds, because operators time work in seconds, not decimals. A cell showing 0.69 means nothing on the floor; 41 seconds per unit does.

A weekly demand-variation variant

When demand differs by day, list Monday through Friday demand in B8:B12 and net time per day in C8:C12, then compute takt per day with =C8/B8 in D8 and fill down. The tightest takt of the week, =MIN(D8:D12), is the one your line must sustain. If you reuse this sheet across engagements, check the Improve First terms before adapting it into client deliverables (https://improvefirst.com/legal/terms).

Takt Time vs Cycle Time Calculation: Same Example, Both Numbers

Takt time is the pace demand sets; cycle time is the pace your process actually runs. Same example, two different questions: how fast must we work, and how fast do we work?

Cycle time at the constraint

Take the worked example from the Excel setup: 420 available minutes, 105 units of demand, giving a takt time of 4 minutes per unit. Now time the constraint station across ten cycles and average them. If the constraint averages 4.8 minutes per unit, the line's effective output is 420 ÷ 4.8 = 87.5 units per shift, not 105. Because cycle time is a measurement, not a calculation, you only need simple averaging and time arithmetic in Excel (Microsoft Excel function documentation).

Comparing the two numbers to find the demand gap

The gap is 105 − 87.5 = 17.5 units, your demand gap at current capacity. Takt minus cycle time per unit (0.8 minutes) tells you how much the constraint must improve to close it. When the gap persists across several stations, the constraint has moved or there is more than one; that is the point where a constraint-impact check like the one at https://improvefirst.com/examples/support-ticket-capacity earns its keep before you quote a deeper engagement.

What Do You Do When the Numbers Don't Match?

Cycle time longer than takt: the constraint is limiting throughput

If the line's cycle time exceeds takt time, you have a demand gap you cannot close by working harder. Find the station with the longest cycle time: that is your bottleneck, and system capacity equals its output, nothing more. Short-term fixes are offloading work to another station, adding a second shift on that step only, or reducing its changeover time. Anything else is decoration until the constraint moves.

Cycle time much shorter than takt: overcapacity and wasted spend

If cycle time runs well below takt, you are producing faster than demand requires, and the excess shows up as WIP, backlog of finished goods, or idle capacity you are paying for. Calculate the gap: if takt is 7.5 minutes and cycle time is 5, you are running 150% of the pace demand justifies. Options are rebalancing people to other lines, dropping a shift, or pulling demand forward. Before quoting a bigger engagement, confirm which case you are in, because the two call for opposite interventions.

How Consultants Use Takt Time in Client Scoping

A 30-minute scoping routine

Before quoting a deeper engagement, run one shift's numbers on site: available time, planned downtime, demand for the period. Divide and you have the client's takt time. Then time one cycle at the station they suspect is slow. If cycle time sits under takt with room to spare, the constraint lives elsewhere and you have just redirected the engagement before writing a proposal. That comparison, done twice on two shifts, is usually enough to size the work honestly.

Where a spreadsheet stops and a constraint model starts

The takt-versus-cycle calculation tells you where the constraint is now. It cannot tell you where it moves once you fix it, because throughput is set by the tightest constraint in the system, not by any single station (Theory of Constraints). For that, model the flow: our Constraint Impact Calculator tests whether an improvement changes whole-system output and predicts where the bottleneck relocates next. ProcessModel simulates the same question at a deeper level; a spreadsheet capacity model stops at the arithmetic. Quote the spreadsheet work first, the modelling second.

Common Mistakes in Takt Time Calculation

Using gross shift length instead of net time

Breaks, changeovers, and planned maintenance all shrink the denominator. A 480-minute shift with 60 minutes of downtime gives 420 net minutes, and every downstream number shifts with it. Use gross time and your takt looks more forgiving than the line can actually run.

Mixing units across the division

Demand is often quoted per day while net time is in minutes. Divide 800 units by 420 minutes and you get a meaningless 1.9. Convert so both sides share a unit: 800 units per day against 420 minutes per day gives 0.525 minutes per unit, or a takt of about 31.5 seconds.

Applying one takt to products with different work content

A mixed line with 10-minute jobs and 2-minute jobs cannot hit a single takt honestly. Calculate takt per product family, or weight demand across the mix, and check cycle time against the right target for each.

FAQ

Is takt time the same as lead time?

No. Takt time is the pace demand sets, expressed as seconds or minutes per unit. Lead time is total elapsed time from order to delivery, including queueing, waiting, and transport. A line can hit takt at every station and still carry days of lead time if work sits in queues between steps. One is a target pace, the other a measured duration.

How do you calculate takt time for multiple products with different demand?

Calculate takt per product family, since a single takt cannot honestly govern jobs with different work content. For each family, divide net available time by that family's demand over the period. If products share a line, weight the demand mix and check each product's cycle time against its own takt target rather than one blended number.

What is a good takt time?

There is no universally good number; takt is only meaningful relative to your cycle time. A 2-minute takt is fine if every station completes a unit in under 2 minutes, and impossible if the constraint runs 4.8. What matters is that cycle time at the constraint sits at or below takt with some margin for minor variation.

Can takt time change during the year?

Yes, whenever demand or available time changes. Seasonal peaks raise demand and tighten takt; a quiet month loosens it. If you size a line against average demand, a peak period can push takt below what the constraint can run. Scope against peak-period demand, or compute takt per day across the week and plan for the tightest one.

Does takt time apply to service businesses, not just manufacturing?

Yes. Any process with measurable demand and available working time supports the calculation: tickets per shift, patients per day, or loan applications per week divided by net staffed hours. The same comparison applies too, since the slowest step in the service flow sets output just as a machine constraint does on a production line.