How fast is fast? Cycle time, takt time and the one number that actually matters

October 1, 2026 · 4 min read

Robot brochures quote speed in degrees per second and picks per minute. Your line runs in cases per hour on a Thursday afternoon. Here is how the three time words relate, with a worked example, and why the number the cell has to beat is never on the datasheet.

The short answer

Takt time is how often the line needs a part to come off to meet demand: a line that must produce 90 cases an hour has a takt of 40 seconds. Cycle time is how long the cell actually takes to do one: pick, move, place, return, open, close, settle. If the cycle is longer than the takt at your peak, the cell falls behind and a person steps in. Everything on the datasheet is an input to the cycle time. None of it is the cycle time.

The datasheet number and what it leaves out

A palletizing robot that advertises 13 picks a minute measured that on a short move with a light case and no waiting. Your cycle includes the full travel from a real pick point to a real place point on the far side of a pallet, the gripper's open and close time, the settle time before release so the case does not bounce, any wait for the conveyor to index, and the speed reduction the risk assessment may impose when a person is near. A third longer than the headline is normal. The datasheet is a laboratory. Your plant is a plant.

The worked example

Picture a line averaging 60 cases an hour and peaking at 90, which is a takt of 60 seconds on average and 40 seconds at peak. A quoted cell does 8 picks a minute on the brochure, a 7.5 second cycle, which sounds absurdly comfortable. Add the real move distance, a two second settle, a conveyor index and a collaborative speed limit, and the real cycle might be 15 seconds. Still comfortable against 40. Now make the cases heavy enough that the robot must pick one at a time instead of two, and add a pallet change every 60 cases that stops the cell for 90 seconds unless there are two pallet positions. The effective cycle creeps toward 20 seconds. Still inside 40, with margin. That is a yes.

Now change one thing. Make the peak 180 an hour, a 20 second takt, because the line runs two products at once on a Thursday. The cell that looked absurdly comfortable now has zero margin, and zero margin means one bad pallet and it never catches up. That is the conversation to have before the quote, with a stopwatch, on a Thursday.

Why average kills cells

The monthly report says 60 an hour. The quote is sized to 60 with margin. The peak is 90, the cell holds 75, and for two hours every afternoon the overflow is hand stacked by the person the robot was meant to free. Nobody did anything wrong. The specification used the wrong number. The number that matters is the peak, with honest derates, with margin on top, which is why the first question the concierge on this site asks about any line is what it does at its fastest.

The physics you cannot negotiate

Collaborative speed limits near people come from how hard a moving mass may hit a body, and no amount of wanting changes them. If your takt needs an arm moving faster than the assessment allows with people present, you get a fenced cell, a second arm, or a slower line. Warp speed is not available at this payload.

What to bring to the conversation

Your peak rate, measured. Your part weight, the heaviest. Your pallet or batch change frequency. Whether people are near the cell while it runs. With those four facts, a competent integrator can estimate a real cycle in an hour, and the concierge on this site can give you a preliminary read in ten minutes, in ranges, with the derates stated.

Give Joe, the concierge here, your peak rate and your heaviest part. He will do this arithmetic out loud and tell you which side of the margin line you live on.

Related on this site

Takt is what the line demands, cycle is what the cell delivers, and the number that matters is the cell's real cycle, with derates, against your peak takt, with margin. The datasheet is the beginning of that calculation, not the end.

Put it to the test on your own job

Tell Joe what you are running and he will apply this to your numbers, including telling you when a robot is the wrong answer.

More notes