{"id":1422,"date":"2026-08-26T00:31:19","date_gmt":"2026-08-26T00:31:19","guid":{"rendered":"https:\/\/mestric.com\/takt-time-izracun\/"},"modified":"2026-08-26T00:31:19","modified_gmt":"2026-08-26T00:31:19","slug":"takt-time-izracun","status":"publish","type":"post","link":"https:\/\/mestric.com\/de\/takt-time-izracun\/","title":{"rendered":"Takt time izra\u010dun: the formula and worked examples"},"content":{"rendered":"<\/p>\n<p>Takt time equals net available production time divided by customer demand, measured over the same period. If your shift offers 420 minutes of available production time and customers need 210 units, your takt time is 2.0 minutes per unit \u2014 that is your pacing target, not a stopwatch reading.<\/p>\n<p>Two conditions make this calculation reliable. First, keep the units consistent: seconds against seconds, minutes against minutes, ensuring the demand and time windows exactly match. Second, match the time window to the demand window exactly, so a weekly order quantity gets divided by a weekly available time, not a single shift.<\/p>\n<ul>\n<li><strong>Formula:<\/strong> Net available production time \u00f7 Customer demand = Takt time<\/li>\n<li><strong>Worked example:<\/strong> 420 minutes \u00f7 210 units = 2.0 minutes per unit<\/li>\n<\/ul>\n<p><strong>Statistic to remember:<\/strong> <a href=\"https:\/\/www.6sigma.us\/manufacturing\/takt-time-vs-cycle-time\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">aim for cycle time at roughly 90\u201395% of takt time<\/a> \u2014 this buffer absorbs normal variation without missing customer demand. Takt time itself is a planning target set by demand, never a measured process speed.<\/p>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<p>Takt time is a demand-driven planning target calculated as net available production time divided by customer demand, and it only stays useful when recalculated promptly after real shifts in either input.<\/p>\n<table>\n<thead>\n<tr>\n<th>Point<\/th>\n<th>Details<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Use the core formula<\/td>\n<td>Net available production time \u00f7 customer demand, with matching units and time windows.<\/td>\n<\/tr>\n<tr>\n<td>Exclude planned downtime only<\/td>\n<td>Remove breaks, maintenance and changeovers from available time; track unplanned stops separately.<\/td>\n<\/tr>\n<tr>\n<td>Apply the 90\u201395% rule<\/td>\n<td>Design cycle time to sit at 90\u201395% of takt time to absorb normal variation without missing demand.<\/td>\n<\/tr>\n<tr>\n<td>Fix bottlenecks before investing<\/td>\n<td>Rebalance work content and cut changeovers before approving new machines or automation.<\/td>\n<\/tr>\n<tr>\n<td>Recalculate on real change<\/td>\n<td>Update takt regularly when demand or capacity changes significantly.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"table-of-contents\">Table of Contents<\/h2>\n<ul>\n<li><a href=\"#how-to-calculate-takt-time-step-by-step\">How to calculate takt time step by step<\/a><\/li>\n<li><a href=\"#what-counts-as-available-production-time-and-customer-demand\">What counts as available production time and customer demand?<\/a><\/li>\n<li><a href=\"#worked-examples-across-shift-day-and-week-horizons\">Worked examples across shift, day and week horizons<\/a><\/li>\n<li><a href=\"#takt-time-vs-cycle-time-whats-the-difference\">Takt time vs cycle time: what\u2019s the difference?<\/a><\/li>\n<li><a href=\"#what-to-do-when-cycle-time-exceeds-takt-time\">What to do when cycle time exceeds takt time<\/a><\/li>\n<li><a href=\"#how-often-should-you-recalculate-takt-time\">How often should you recalculate takt time?<\/a><\/li>\n<li><a href=\"#operationalising-takt-time-with-an-mes\">Operationalising takt time with an MES<\/a><\/li>\n<li><a href=\"#why-the-textbook-version-of-takt-time-undersells-the-real-skill\">Why the textbook version of takt time undersells the real skill<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ul>\n<h2 id=\"how-to-calculate-takt-time-step-by-step\">How to calculate takt time step by step<\/h2>\n<p>Getting a defensible takt time calculation means working through five deliberate steps rather than plugging numbers into a formula blind. Skip any one of them and the result looks precise while being quietly wrong.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-16618\/1787481729929_Diagram-of-five-takt-time-calculation-steps.jpeg\" alt=\"Diagram of five takt time calculation steps\"><\/p>\n<p><strong>Step 1: Choose your calculation horizon.<\/strong> Decide whether you are planning per shift, per day, per week, or per month, and use that identical window for both your time and demand figures. A common error is calculating available time for one shift while demand reflects a full week\u2019s orders.<\/p>\n<p><strong>Step 2: Compute net available production time.<\/strong> Start with scheduled time, then subtract planned breaks, scheduled changeovers, and planned maintenance. These are known, budgeted absences from production and belong outside the calculation entirely, according to the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Takt_time\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">standard definition of takt time<\/a>. Do not subtract unplanned stoppages here; that capacity loss belongs in a separate downtime analysis, not baked into your planning number.<\/p>\n<p><strong>Step 3: Select your demand signal.<\/strong> Committed customer orders give the most accurate figure. When firm orders aren\u2019t available for the full horizon, use a conservative forecast or a rolling average rather than an optimistic sales projection, which tends to understate takt time and sets an unrealistic pace.<\/p>\n<p><strong>Step 4: Divide and choose a workable unit.<\/strong> <a href=\"https:\/\/www.oee.com\/takt-time\/what-is-takt-time\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Available production time divided by customer demand<\/a> gives you the raw number, but the unit you express it in matters for usability. Seconds suit high-volume lines running thousands of units a day; minutes suit typical mixed-model assembly; hours suit complex, low-volume builds like heavy equipment or custom fabrication.<\/p>\n<p><strong>Step 5: Round conservatively and operationalise.<\/strong> Round down when staffing to that takt time to avoid understaffing a fast-moving line, and round up when the number will drive line balancing across multiple stations. Convert the final figure into staffing ratios or station cycle-time targets so the shop floor has something concrete to work against.<\/p>\n<p><strong>Pro Tip:<\/strong> <em>Write your takt time calculation down with its inputs, not just the result. When someone questions the number six weeks later, you want to show your working, not recreate it from memory.<\/em><\/p>\n<h2 id=\"what-counts-as-available-production-time-and-customer-demand\">What counts as available production time and customer demand?<\/h2>\n<p>Ambiguity here is the single biggest reason two planners looking at the same line produce two different takt times. Fixing the definitions once, in writing, removes that variance permanently.<\/p>\n<p><strong>Exclude from available time:<\/strong><\/p>\n<ul>\n<li>Scheduled breaks and shift handovers<\/li>\n<li>Planned preventive maintenance windows<\/li>\n<li>Planned changeovers between product variants<\/li>\n<li>Any other budgeted, calendar-known absence from production<\/li>\n<\/ul>\n<p>These are removed because they are known in advance and already factored into the schedule. Leaving them in inflates available time and produces a takt time that looks achievable on paper but isn\u2019t.<\/p>\n<p><strong>Keep out of the takt calculation, but track separately:<\/strong> unplanned stoppages, minor stops, and rework. These represent capacity loss, not scheduled unavailability, and belong in a downtime and loss analysis rather than a subtraction from your takt formula. Net available time strictly means scheduled time minus planned absences, full stop.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-16618\/1787481718864_Technician-hands-adjusting-machine-controls.jpeg\" alt=\"Technician hands adjusting machine controls\"><\/p>\n<p>On demand: committed customer orders are the gold standard input. When you lack firm orders for the whole planning horizon, use a conservative forecast or a trailing average of recent order volumes, and flag any promotional spike or seasonal dip that could distort a short window. For multiple lines or mixed shift patterns, normalise available time per line individually rather than aggregating across dissimilar equipment, and note clearly which lines share pooled labour so staffing calculations don\u2019t double count operators.<\/p>\n<h2 id=\"worked-examples-across-shift-day-and-week-horizons\">Worked examples across shift, day and week horizons<\/h2>\n<p>The maths stays identical across scales, but <a href=\"https:\/\/lean6sigmahub.com\/measure-phase-understanding-takt-time-and-cycle-time-for-process-excellence\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">the unit you choose changes with volume<\/a>. Below are three cases planners commonly hit.<\/p>\n<p>A few things worth noticing about these examples:<\/p>\n<ul>\n<li>Converting minutes to seconds for the packaging line makes the takt target more usable at the workstation.<\/li>\n<li>The low-volume example uses hours because each assembly is complex enough that smaller units would cause unwieldy decimals.<\/li>\n<li>If weekly demand decreases while available time stays constant, takt time lengthens, meaning the pace eases.<\/li>\n<li>Rounding decisions affect staffing calculations by building in margin or requiring more capacity.<\/li>\n<\/ul>\n<h2 id=\"takt-time-vs-cycle-time-whats-the-difference\">Takt time vs cycle time: what\u2019s the difference?<\/h2>\n<p>Takt time is your demand-driven target, calculated from customer orders and available time. Cycle time is what your process actually measures, station by station, stopwatch in hand. Planned cycle time sits between them, calculated as takt time multiplied by expected uptime, and it\u2019s what workstation design should target rather than raw takt itself.<\/p>\n<p><a href=\"https:\/\/blog.roboflow.com\/takt-time-vs-cycle-time\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Confusing these two figures is one of the most common traps in production planning<\/a>: takt tells you what pace is needed, cycle time tells you what pace you\u2019re achieving, and the gap between them is where the real work happens.<\/p>\n<p>The widely used rule of thumb: cycle time should sit at roughly 90 to 95% of takt time. That five to ten percent buffer absorbs normal variation, minor stops, and operator fatigue without the line falling behind demand. Push cycle time right up against takt with zero margin and any hiccup turns into a missed shipment.<\/p>\n<p>To read the result visually, plot cycle time per station on a bar chart against a horizontal takt line. Stations with bars above the line are bottlenecks constraining your whole output; stations well below the line are carrying idle capacity you could redeploy elsewhere. This single chart usually tells a production manager where to focus faster than a page of KPI tables.<\/p>\n<p><strong>Pro Tip:<\/strong> <em>Build the takt line into your line-balancing chart from day one, not after problems appear. Designing workstations against planned cycle time from the start avoids costly rebalancing later.<\/em><\/p>\n<h2 id=\"what-to-do-when-cycle-time-exceeds-takt-time\">What to do when cycle time exceeds takt time<\/h2>\n<p>When a station\u2019s measured cycle time creeps above takt, you have a real gap between what the line produces and what customers need. The fix depends on how much time you have and how much the gap costs you.<\/p>\n<ol>\n<li><strong>Immediate, same-day steps:<\/strong> authorise short-term overtime, redeploy a trained operator from a lower-demand station, or stand up a temporary parallel workstation to absorb overflow volume.<\/li>\n<li><strong>Tactical changes within weeks:<\/strong> apply SMED (Single-Minute Exchange of Die) techniques to cut changeover time, rebalance work content across stations, and standardise the operator method at the bottleneck so cycle time stops varying station to station.<\/li>\n<li><strong>Investment-level fixes:<\/strong> add a machine, introduce targeted automation at the constrained step, or redesign the process flow entirely if the bottleneck is structural rather than a one-off spike.<\/li>\n<li><strong>Demand-side levers:<\/strong> level production across the week instead of batching orders, negotiate flexible delivery windows with key customers, or stagger order intake to smooth peaks that are driving an artificially tight takt time.<\/li>\n<\/ol>\n<p>Deciding which lever to pull comes down to duration and cost. A demand spike lasting two weeks rarely justifies capital investment; overtime or redeployment covers it more cheaply. A persistent gap that reappears every recalculation cycle, though, signals a structural capacity shortfall that no amount of overtime will fix, and that\u2019s when line redesign or added equipment earns its cost. <a href=\"https:\/\/mestric.com\/de\/why-analyse-production-flow-a-guide-for-manufacturers\/\" target=\"_blank\" rel=\"noopener\">Rebalancing the line for smoother flow<\/a> often resolves more of the gap than adding headcount ever does.<\/p>\n<p><strong>Pro Tip:<\/strong> <em>Before authorising capital spend, check whether the bottleneck is a genuine capacity ceiling or simply an unbalanced line. Reallocating 30 seconds of work content from an overloaded station to an underused one costs nothing and often closes half the gap.<\/em><\/p>\n<h2 id=\"how-often-should-you-recalculate-takt-time\">How often should you recalculate takt time?<\/h2>\n<p><a href=\"https:\/\/resources.rework.com\/libraries\/process-management\/takt-time\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Takt time should move only when the underlying demand or capacity genuinely changes<\/a> \u2014 treat it as a fixed planning constant between reviews, not something you nudge daily to match yesterday\u2019s output.<\/p>\n<p>The calculation errors that recur most often:<\/p>\n<ul>\n<li><strong>Mixed time horizons<\/strong> \u2014 dividing a weekly demand figure by a daily available time window, or vice versa.<\/li>\n<li><strong>Double-counting planned downtime<\/strong> \u2014 subtracting a changeover once in available time and again in a separate efficiency factor.<\/li>\n<li><strong>Using gross instead of net capacity<\/strong> \u2014 forgetting to remove scheduled breaks before dividing.<\/li>\n<li><strong>Cherry-picking a demand period<\/strong> \u2014 basing takt on an unusually quiet or busy week rather than a representative one.<\/li>\n<\/ul>\n<p>Validate any new takt figure against historical cycle time data before rolling it out, and pilot significant changes on one line before applying them factory-wide.<\/p>\n<h2 id=\"operationalising-takt-time-with-an-mes\">Operationalising takt time with an MES<\/h2>\n<p>Manual takt time calculation works fine on a spreadsheet until your product mix, shift patterns, and order volumes all shift in the same month. That\u2019s usually when the manual version quietly falls out of date and nobody notices until output slips.<\/p>\n<p>An MES platform such as Mestric removes that lag by pulling the inputs directly from the shop floor rather than from someone\u2019s memory of last Tuesday\u2019s shift report.<\/p>\n<ul>\n<li><a href=\"https:\/\/mestric.com\/de\/real-time-production-data\/\" target=\"_blank\" rel=\"noopener\">Mestric connects directly to machines and operator terminals<\/a> to capture actual cycle times and downtime as they happen, rather than relying on end-of-shift paperwork.<\/li>\n<li>Dashboards can plot live cycle time against your calculated takt line per station, flagging the exact point where a line starts falling behind.<\/li>\n<li>Automated alerts notify supervisors the moment a station exceeds takt, so corrective action happens within the shift rather than in next week\u2019s review meeting.<\/li>\n<\/ul>\n<blockquote>\n<p>Manual takt calculations are only as good as their inputs, and inputs collected by hand drift out of date the moment a shift pattern or order book changes. Automating the collection of net available time and cycle time closes that gap and keeps the number honest.<\/p>\n<\/blockquote>\n<p>Book a demonstration to see how connected machine data turns a static takt calculation into a live monitoring feed for your own lines.<\/p>\n<h2 id=\"why-the-textbook-version-of-takt-time-undersells-the-real-skill\">Why the textbook version of takt time undersells the real skill<\/h2>\n<p>Most guides treat takt time calculation as an arithmetic exercise: divide time by demand, done. The genuine skill sits entirely in what you decide to exclude from \u201cavailable time\u201d and which demand figure you trust, and that\u2019s the part conventional advice glosses over fastest.<\/p>\n<p>Planners who get burned by takt time usually aren\u2019t bad at division. They inherited a spreadsheet where someone quietly folded unplanned downtime into the available time calculation two years ago, and nobody has questioned it since. The number still looks authoritative. It just isn\u2019t measuring what anyone thinks it\u2019s measuring.<\/p>\n<p>My honest view: recalculation discipline matters more than calculation precision. A takt time correct to two decimal places but six weeks stale will mislead you faster than a rougher number recalculated last Tuesday. Treat takt as a design constraint you build workstations around, not a KPI you chase after the fact, and resist the urge to fiddle with it daily to match whatever happened on the floor yesterday. Fix the constant, manage the variance with capacity levers, and only move the takt line when demand or capacity genuinely shifts underneath you.<\/p>\n<blockquote>\n<p><em>\u2014 Andra\u017e<\/em><\/p>\n<\/blockquote>\n<h2 id=\"sources\">Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.oee.com\/takt-time\/what-is-takt-time\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Takt Time<\/a><\/li>\n<li><a href=\"https:\/\/www.6sigma.us\/manufacturing\/takt-time-vs-cycle-time\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Takt time vs cycle time<\/a><\/li>\n<li><a href=\"https:\/\/en.wikipedia.org\/wiki\/Takt_time\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Takt time<\/a><\/li>\n<li><a href=\"https:\/\/resources.rework.com\/libraries\/process-management\/takt-time\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Takt time: Formula and How to Calculate It<\/a><\/li>\n<li><a href=\"https:\/\/lean6sigmahub.com\/measure-phase-understanding-takt-time-and-cycle-time-for-process-excellence\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Understanding takt time and cycle time<\/a><\/li>\n<\/ul>\n<h2 id=\"recommended\">Recommended<\/h2>\n<ul>\n<li><a href=\"https:\/\/mestric.com\/de\/kako-upravljati-s-proizvodnjo-v-realnem-casu-vodic-2026\/\" target=\"_blank\" rel=\"noopener\">Kako upravljati s proizvodnjo v realnem \u010dasu: vodi\u010d 2026<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/de\/vodic-za-nacrtovanje-proizvodnih-kapacitet-2026\/\" target=\"_blank\" rel=\"noopener\">Vodi\u010d za na\u010drtovanje proizvodnih kapacitet 2026<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/de\/kako-upravljati-s-prioritetami-v-proizvodnji-vodic-2026\/\" target=\"_blank\" rel=\"noopener\">Kako upravljati s prioritetami v proizvodnji: vodi\u010d 2026<\/a><\/li>\n<li><a href=\"https:\/\/mestric.com\/de\/kako-zmanjsati-operativne-stroske-s-pametno-tovarno\/\" target=\"_blank\" rel=\"noopener\">Kako zmanj\u0161ati operativne stro\u0161ke s pametno tovarno<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Learn how to calculate takt time efficiently with our formula and practical examples. Improve your production pacing and meet demand!<\/p>","protected":false},"author":1,"featured_media":1424,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1422","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-learn"],"acf":[],"_links":{"self":[{"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/posts\/1422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/comments?post=1422"}],"version-history":[{"count":1,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/posts\/1422\/revisions"}],"predecessor-version":[{"id":1423,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/posts\/1422\/revisions\/1423"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/media\/1424"}],"wp:attachment":[{"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/media?parent=1422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/categories?post=1422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mestric.com\/de\/wp-json\/wp\/v2\/tags?post=1422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}