The roast does not end when you drop the beans
Cacao is roughly 45 to 55% cocoa butter. That is a lot of fat, and fat holds heat. A batch of beans coming out of a drum at end-of-roast temperature is a substantial thermal mass with nowhere to put its energy — so it keeps cooking itself.
Which means the finish temperature you carefully hit is not necessarily where the beans actually finished. If it takes four or five minutes for the batch to come down, the roast carried on for four or five minutes past the point you decided to stop.
This is the most common way careful roasting gets quietly undone. People profile precisely, watch the bean temperature, pull at exactly the right moment — and then tip the beans into a bowl and let them sit.
Why it gets worse as you scale
A half-pound sample roast cools fairly quickly on its own: small mass, lots of surface area relative to it. A ten-pound batch is a different problem entirely. The mass goes up faster than the exposed surface does, so the bigger the batch, the longer the carry-over and the further past your target it drifts.
So a cooling arrangement that was perfectly adequate while you were learning becomes a real source of inconsistency at production volume — and it does so gradually, which makes it hard to notice.
There is a second cost. Cooling time is cycle time. If a batch takes fifteen minutes to roast and eight to cool, cooling is a third of your session. At the point where you are roasting to fill orders, that is throughput you are simply giving away.