A customer told me something last week that I keep thinking about.

They handle over 1,000 Declaration of Conformity requests from their clients. Each one manually. Around three hours a week, just on DOCs.

They are not a small team. They are a well-run quality operation at a food ingredients company. And three hours a week just disappeared into one document type that did not exist in their workflow eighteen months ago.

That is what I mean when I talk about invisible work.

PPWR created a legal obligation for brand owners and importers: every unique packaging type on the EU market now needs a signed Declaration of Conformity backed by technical documentation. The brand owner needs it. The compliance obligation sits with them. So they go to their packaging suppliers and ask for it.

Which means the request lands on quality.

And it’s not precisely because quality owns packaging compliance, but because quality is where these requests always end up. The team that knows the documentation, knows the suppliers, knows what can be verified and what cannot. And if you are reading this, you probably already know exactly what I am talking about because it is already in your inbox, so I am not going to explain PPWR to you because you know it better than I do.

What I want to talk about is what happens to your week when one regulation creates a new category of recurring work overnight. Because that is the part nobody plans for.

The DOC itself is not complicated. You map the packaging type, you pull the relevant supplier data, you confirm the substance restrictions, you fill the declaration, you sign off. Done.

The problem is when you have fifty of them. Or a hundred. Or a thousand.

Each one is the same job. Each one takes the same steps. And each one lands on a person who has seventeen other things to do that day.

This is what we built Passionfruit's AI quality colleague to take on. Not because DOCs are hard, but because they are exactly the kind of work that should not require your full attention every time.

You brief it once. It knows your packaging portfolio, your supplier documentation, what has already been verified and what has not. When a DOC request comes in, it finds the right data, fills the declaration, and flags anything it cannot confirm with enough confidence. It brings the work back to you for sign-off. You review, approve, it goes out.

The second request is faster than the first, and the fiftieth is faster than the second. Because it is the same colleague doing the same job, not a different person starting from scratch.

Here is the broader point, though, and this is what I keep coming back to:

PPWR is one example. But every regulation that lands on food companies in the next five years is going to do the same thing. It creates an obligation somewhere upstream. That obligation gets passed down. It lands on quality. And quality absorbs it, adds it to the pile, and figures out how to get through the week.

That has been the story for as long as quality teams have existed. Workload grows. Headcount does not. You find a way.

What I want to change is the assumption that finding a way always means having an overworked team. Because sometimes finding a way means having a colleague who takes the new category of work, runs it consistently, and gives your team's capacity back for the things that actually need your judgment.

That is what we’ve built. And we are just getting started. 😉