A reusable spool programme either pays for itself over cycles or it does not, and most operations running one could not say which. The information exists — it is just not being collected or not being looked at.
You do not need a dashboard. Four or five numbers, reviewed periodically, tell you nearly everything.
One: trip rate
Trips per spool per year, which is the denominator in every cost and sustainability calculation. Discussed at length in our trip counting article, which is honest about how few operations can produce it.
If you cannot measure it, estimate it from throughput and check the estimate once. An imperfect number is far better than none.
Two: return rate
Returned against despatched, usually as a percentage. This is the number that most often determines whether a programme works, and it is the easiest to measure — you already know what went out and what came back, if you are counting.
A return rate that is materially below expectation is worth investigating before anything else. Everything downstream of it is affected.
Three: loss rate
Spools that simply disappear, expressed per year as a share of the fleet. Related to return rate but not the same — some spools come back unusable, which is a different problem with a different fix.
Splitting losses into “not returned” and “returned damaged” is worth doing, because the first is a logistics problem and the second is a handling or design problem.
Four: cost per trip
Total programme cost divided by trips. The full treatment is in our cost per trip article. The point here is that it should be calculated with real numbers where available rather than the assumptions used to justify the programme.
Very often the realised figure is worse than the business case, and knowing by how much is useful.
Five: damage-related incidents
Two counts worth keeping: spools retired for damage, and product damage attributed to packaging. The second is harder and more valuable, because it is what the packaging is supposed to prevent.
Where product damage is being tracked, splitting it by whether packaging was implicated is the single most useful thing for prioritising effort.
Six, optionally: dwell time
How long spools spend at each stage. If the loop is slow, this tells you where. It is more diagnostic than a KPI, and worth measuring when something is wrong rather than routinely.
How to use them
Not as a reporting exercise. The value is in:
- Trend rather than level. A return rate of 78% is neither good nor bad without context; a return rate falling from 88% to 78% is a signal.
- Comparison between customers or routes. Aggregate numbers hide that one route returns poorly and everything else is fine.
- Triggering investigation. A threshold below which somebody looks, rather than a number to report upward.
That second one is where most of the practical value is. Loop performance is rarely uniform.
What not to measure
- Purchase price per spool — it is the least informative number and the one everyone tracks
- Anything you will not act on — a metric with no decision attached is overhead
- More than about five things — the collection burden kills the programme
Review frequency
Quarterly is usually right. Monthly is too frequent to see signal in most operations; annually is too slow to catch drift.
The honest observation
Programmes that measure these tend to improve them, largely because measuring requires the counting infrastructure that also makes returns work. Programmes that do not measure usually discover their performance only when someone asks a question they cannot answer.
What we can contribute
Realistic expectations for our hollow board spools in a loop like yours, and an honest view of what return rates are achievable. If your realised numbers are well below what we would expect, that conversation is worth having — the cause is usually identifiable.