Does your operator know what assumptions your formulator made this morning?

Feed and pet food manufacturing depends on close alignment between at least three teams: the formulator, the operator, and quality control. In a well-functioning operation, these three functions form a loop, each informing and refining the others. Formulation shapes production. Production generates data that improves formulation. Quality validates the outcome and feeds that signal back upstream.

In practice, that loop is rarely closed. Not because of any failure of skill or intent, but because the data each team generates largely stays within their own domain. What the formulator knows does not reach the operator in a useful form. What the operator learns on the line does not flow back to the formulator. What quality finds out reaches the others too late to change what already happened.

The result is that three teams with complementary expertise end up working in parallel rather than together. Each is doing their job well. But they are doing it with only part of the picture.

Where the data gap sits

When a product comes off spec, it is rarely because someone made a mistake. It is more often because each team made a perfectly reasonable decision based on the information available to them. And the information available to them was incomplete.

The formulator works from ingredient specifications that represent a statistical average across many deliveries. That is a reasonable approach when real-time lot data is not available. But ingredients vary. Moisture levels shift between deliveries. Protein concentrations fluctuate. When the actual batch on the line differs from the assumed value in the formulation database, that gap does not announce itself. It shows up quietly; in moisture readings at the end of the run, in protein figures that come back slightly low, in a right-first-time failure that triggers a review.

The operator, meanwhile, is working with considerable skill and experience. They know their line intimately. They are reading it continuously, adjusting process parameters in real time based on what they see and what they have learned over years. What they do not have is visibility into the upstream assumptions: what moisture the formulator was expecting, what protein level the recipe was built around, where the tolerances sit. That context would make their adjustments more targeted. Without it, even the most experienced operator is compensating without the full picture.

Quality control brings analytical rigour and a clear standard to measure against. Their role is to confirm the product before it ships.  And they do that well. The structural limitation is timing: quality data becomes available after the batch has run. That means findings can prevent the next problem, but not the current one.

The financial impact of disconnected teams shows up most visibly in over-formulation. Because ingredient variability is not fully visible in real time, formulators rationally build safety margins into their targets. If the guaranteed analysis requires 22% protein on the label, the internal formulation target might sit at 24% — a buffer designed to absorb the variability that cannot be seen or predicted. It is a sensible response to an information gap.

That buffer has a cost. More expensive ingredients than the product strictly requires, on every batch, every day. Closing the information gap — giving formulators accurate, current ingredient data — does not eliminate the need for buffers entirely, but it makes them smaller, more precise, and based on actual variability rather than worst-case assumptions.

There is a second cost that is harder to put a number on: the knowledge that experienced operators carry in their heads. The understanding of how a particular line behaves when a high-moisture batch comes through. The instinct for when to adjust and by how much. The awareness that certain raw materials run differently in summer than in winter. That knowledge is enormously valuable. And in most plants, it exists nowhere but in the operator's memory. When they move on, it goes with them. The person who follows inherits the equipment and the run sheet, but not the context that makes the run sheet work.

When manufacturers talk about improving collaboration, the focus often falls on meetings, communication, and clearer handoffs. Those things matter. But they treat a structural problem as a behavioural one.

The deeper issue is that formulation data, production data and quality data do not live in the same place. Teams cannot act on information they cannot see. The operator cannot contextualise their adjustments against formulation assumptions they have never been shown. The formulator cannot refine their model based on production outcomes they were never told about. Quality cannot get ahead of a problem that becomes visible only after the fact.

What connected workflows provide is not more communication. It is shared data. The ingredient assumptions behind a recipe become visible to the people running it. The adjustments made on the line flow back to the people who built it. Quality findings arrive in time to inform decisions, not just document outcomes. Each team's expertise is amplified by the others', because for the first time they are all looking at the same picture.

That shift does not change what each team does. It changes what each team can do. And the results are measurable: tighter formulations, smaller buffers, fewer deviations, faster responses when variability appears, and process knowledge that stays in the organisation because it is captured in data rather than held in memory.

When formulation, production and quality share the same data in real time, every team gets what they have always been missing ; not new responsibilities, but the full picture they need to do their existing job better.

→  Formulators get actual lot-level ingredient data feeding into their models, and receive production feedback that makes each successive formula more precise.

→  Operators see the ingredient assumptions behind the recipe they are running. Their process knowledge gets documented and shared, so it stays in the organisation when experienced people move on.

→  Quality teams gain visibility earlier in the process, shifting from confirming what went wrong to helping prevent it.

→  The whole organisation works from the same version of reality. Decisions get faster, buffers get smaller, and the gap between what was formulated and what was produced gets narrower every cycle.

If ingredient variability shifts between a delivery and the production run that uses it, does your formulator find out? Does the operator running the line have sight of the assumptions the recipe was built on? When quality identifies a deviation, does that finding reach the formulator before the next batch runs?

These are not questions about competence. Every team in this picture is competent. They are questions about whether the information infrastructure your teams work within is giving them what they need to apply that competence fully.

The gap between what was formulated and what was produced is not a people problem. It is a data flow problem. And that, at least, is something that can be solved.

Closing this loop is the challenge that BESTMIX Recipe Management was built around. If this resonates with what you see in your own operation, we would be glad to talk.