Pitch is the practical management time increment of a lean production line, calculated as takt time multiplied by the pack quantity in one standard container. Takt time tells you the theoretical beat of customer demand, but it is often too short to manage a floor by directly.
A takt of 42 seconds is impossible to walk the line against every 42 seconds. Pitch scales that beat up to a workable interval, usually somewhere between 10 and 60 minutes, so supervisors can check whether the line is ahead, behind, or on pace at a rhythm humans can actually act on.
Takt time is the drumbeat: available production time divided by customer demand. It is essential for balancing work and sizing a line, but as a real-time control interval it usually fails.
Nobody can meaningfully react to a status signal that fires every 30 or 45 seconds, and doing so would generate constant noise instead of stable rhythm. What a floor needs is a heartbeat slow enough to observe, compare against a plan, and respond to before a small gap becomes a lost shift.
Pitch solves this by rolling several takt cycles into one countable unit tied to a physical quantity you already move: a tray, a tote, a pallet layer, or a finished-goods container. Instead of "one unit every 42 seconds," the line manages to "one full container of 30 units every 21 minutes." That container becomes the visible token of on-pace performance.
The calculation is deliberately simple:
Work through a real scenario. A packaging cell runs one shift of 8 hours. Subtract two 15 minute breaks and a 10 minute changeover, leaving 440 minutes, or 26,400 seconds, of available time. Customer demand is 600 units per shift.
Round to a clean 15 minute pitch and the line now has 29 pitch intervals across the shift, each expected to yield one full shipper of 20 good units.
If the shipper is not filled and staged when the 15 minute mark arrives, the line is behind by a known, quantified amount and the team knows it immediately rather than at shift end. To keep this honest, count only good units.
A high scrap rate quietly steals from every pitch, so pace and quality have to be tracked together.
Because pitch is driven by pack quantity, that number is a genuine design decision, not just a shipping detail. Too large a pack stretches pitch to an hour or more, which delays feedback and lets problems hide. Too small a pack shrinks pitch toward the raw takt and reintroduces the noise you were trying to escape. Practical guidelines:
Pitch does its real work at one specific point in the value stream: the pacemaker process . The pacemaker is the single scheduling point, typically the last continuous-flow step before shipping, that sets the tempo for everything upstream pulling to it. You do not schedule every operation independently.
You schedule the pacemaker to pitch, and the rest of the stream follows through pull. Identifying that point cleanly is a core output of value stream mapping , and it usually sits at or near the system constraint described in the theory of constraints .
The heijunka box (a load-leveling board) is where pitch becomes physical. The box has a column for each pitch interval and a row for each product. A material handler withdraws the kanban for the next interval, delivers it to the pacemaker, and returns to collect finished work exactly one pitch later.
That regular walk, often called the paced withdrawal or runner route, is what converts an abstract schedule into a self-correcting rhythm. Each round trip is a live on-pace or off-pace check, and it feeds directly into a healthy pull system .
Pitch only pays off when someone acts on the signal. The mechanics are straightforward:
This is where pitch connects to broader performance measurement. The same small stops and slow cycles that break a pitch are exactly the losses that erode overall equipment effectiveness. Pitch gives you the short feedback loop; OEE gives you the accumulated scorecard. Together they turn scattered floor problems into a ranked, fixable list.
Pitch depends on knowing, right now, how many good units the pacemaker has actually produced against plan, and most floors still capture that on a clipboard hours late. Fabrico is the real-time data foundation that closes this gap.
Its production monitoring counts good output and captures stop reasons live, so every pitch interval is measured automatically instead of by memory, and its real-time OEE views connect those pitch-level misses to the same loss buckets your improvement work targets.
For lines where older machines have no PLC to tap, Fabrico can read output using computer vision, giving even legacy cells an accurate pace signal.
When a missed pitch traces back to a machine problem, Fabrico's field-ready CMMS turns it into action: work orders, asset history, preventive schedules, and spare-parts tracking in one place, which supports the shift from reactive to proactive maintenance that keeps a pacemaker running to pitch. Fabrico is EU-built with EU data residency. You can see the OEE and production monitoring and CMMS capabilities in detail on the feature pages.
No. Takt time is the raw beat of customer demand, one unit per takt. Pitch is takt time multiplied by the pack quantity, which scales that beat into a longer, more manageable interval. You use takt to balance and size the line, and you use pitch to actually manage and pace the floor in real time.
There is no universal number, but many plants target a pitch somewhere between 10 and 60 minutes. Short enough that a miss is caught quickly, long enough that checking it does not become constant noise. Adjust the pack quantity to land pitch inside a band your team can genuinely respond to, and recalculate whenever demand or available time changes.
No. Any process with reasonably repetitive demand and a definable move or container quantity can use pitch, including packaging, machining cells, and mixed-model lines managed through a heijunka box. Lower-volume or highly variable environments may use a longer pitch or a wider level-loading window, but the core idea of a countable, paced management increment still holds.
Ready to measure every pitch interval automatically and connect pace misses to real-time OEE and maintenance action? Book a Fabrico demo and see the data foundation in action on your own pacemaker process.
Login
Blog
