ERP & MRP Planning worked example
Backlog Burn Down at 17% recovery schedule allowance: a worked example
This scenario runs the backlog burn down calculation on the strong side: 17% recovery schedule allowance, with every other input held at its documented default. a production planner needs to estimate when open backlog can be cleared
The inputs for this scenario
- Open backlog quantity: 2,500 units (unchanged)
- Net good output rate: 420 units / day (unchanged)
- Recovery schedule allowance: 17 % (raised for this scenario; the documented default is 15)
Working through the calculation
- Applying the documented formula (Base backlog burn-down time = open backlog quantity รท net good output rate) to the inputs above produces each figure below.
- At this operating point the engine returns 6.96 days for estimated backlog burn-down time, the number this scenario is built around.
- At this operating point the engine returns 5.95 days for base backlog days at net output.
- At this operating point the engine returns 17 % for recovery schedule allowance.
- At this operating point the engine returns 420 units / day for net good output rate.
How this compares with the baseline
- Against the tool's baseline example, where recovery schedule allowance sits at 15% and the headline result is 6.85 days, this scenario comes in 1.74% above the baseline at 6.96 days.
- Use it when a backlog opens up and you need a credible recovery date, or to test whether added capacity will clear it in time. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Estimated backlog burn-down time: 6.96 days (headline result)
- Base backlog days at net output: 5.95 days
- Recovery schedule allowance: 17 %
- Net good output rate: 420 units / day
Run it with your numbers
- Every input above is editable in the live Backlog Burn Down calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.