📈 CORE KPI: Hitrate
The Hitrate KPI measures how many tasks were completed within the takt as originally planned. It reflects how well operational execution aligns with planning – a key metric in shopfloor management for goal achievement and planning reliability.
🔍 Contents
- What does the Hitrate show?
- How is it calculated?
- Example
- Aggregation and display across team hierarchy
- Data sources and system behavior
- Tips & best practices
- FAQ
✅ What does the Hitrate show?
The Hitrate shows the percentage of planned tasks that were completed within the defined takt.
- 
100%: All planned tasks were completed within the takt 
- 
0%: None of the planned tasks were completed within the takt 
- 
Low values: May indicate unrealistic planning or capacity bottlenecks 
🛠️ How is it calculated?
The calculation happens automatically when the user clicks the “✅ Close takt” button in the Current Takt column (or Current Week).
📐 Formula:
Hitrate (%) = (Completed planned tasks / Total number of planned tasks) × 100
📥 Conditions:
- 
The task must already be in the Current Takt column at the beginning of the takt 
- 
The task must be moved to the Done column during the takt 
- 
The takt must be actively closed using the “Close takt” button 
- 
Tasks that were added after the takt began are not included in the calculation 
🧾 Example:
At the start of the takt, there are 10 task cards in the Current Takt column.
By the end of the takt, 8 of them are moved to “Done”.
When the takt is closed, the Hitrate is calculated as follows:
Hitrate = (8 completed tasks / 10 planned tasks) × 100 = 80%The remaining 2 unfinished tasks stay in the Current Takt column and reduce the overall Hitrate accordingly.
🧩 Aggregation and display across team hierarchy
- 
The Hitrate is calculated per team and displayed on the team board under the corresponding KPI tile. 
- 
In parent teams, an additional KPI “Hitrate aggr.” appears, which shows a weighted aggregation of the Hitrate values from the respective child teams. 
🗃️ Data sources and system behavior
- 
The KPI uses the system columns “Current Takt” and “Done” 
- 
Only tasks that were present on the board at the start of the takt are counted 
- 
The calculation is updated automatically each time the takt is closed 
- 
Tasks in the Buffer or Next Takt columns are excluded 
✨ Tips & Best Practices
- 
Close the takt regularly, for example daily or weekly during your team meetings 
- 
Use the Hitrate to reflect: Was the planning realistic? Are resources missing? 
- 
Combine the Hitrate with the Disturbance Level KPI to visualize unplanned or spontaneous tasks 
❓ FAQ
What counts toward the Hitrate?
→ Only tasks that were in “Current Takt” at the beginning and moved to “Done” before the takt was closed.
What about tasks added during the takt?
→ These are not considered in the Hitrate, but may be reflected in the Disturbance Level KPI.
Are there filters or evaluations by task type?
→ No, the Hitrate KPI does not currently support additional filters or segmentation by task category.