Rework Rate Calculator
Turn code churn into a signal. See what share of your changed code gets rewritten or reverted - and whether that number is healthy.
Your measurement windows
Enter total lines changed and how many were reworked or reverted within the churn window.
Some churn is normal. Watch for a rising trend or a few hot files driving most of it.
Numbers above are illustrative, editable estimates. Replace them with your own repository data.
What rework rate actually measures
Rework rate - also called code churn - is the share of code that gets rewritten or reverted shortly after it lands. If a team changes 5,000 lines in a period and 1,000 of them are torn out again within the churn window, the rework rate is 20%. It is one of the clearest ways to see whether shipped code is actually solving the problem, or just moving it.
High churn rarely means people are bad at their jobs. It usually points upstream: fuzzy requirements, missing acceptance criteria, thin review, or AI-generated code merged before anyone understood it. That is why rework rate pairs so well with flow metrics like cycle time and DORA metrics - throughput means little if a chunk of the work has to be redone.
If you are shipping with AI assistants, this number matters even more. Read how to measure AI coding tools and AI vs human code quality to put the rate in context, then close the loop with a clear spec using our product plan generator.