Say a raw material changes, and your spec now carries a may-contain for sesame that wasn’t there before.

Your team updates the spec. A statement goes out to every customer who buys that product. That part usually happens quickly.

Then the slower part starts. Over the next months the questionnaires come back. One customer asks for an updated allergen questionnaire. Another is due for its regular update. A third sends a new template altogether. Each one in their own Excel, Word or PDF, with their own columns and their own way of asking about may-contain.

Every one of them has to reflect the change. Which means whoever fills it in has to remember the sesame line, and not copy last year’s answer from the version on file.

What I want to talk about is why that is harder than it sounds, even in teams that do everything right.

From what I see, quality teams are good at keeping a spec up to date. What is much harder is keeping track of everything that was said based on it. Every statement, every questionnaire, every declaration is a copy of your spec in someone else’s format. The more customers you serve, the more copies there are.

Your spec is one document. The answers built on it are everywhere.

This is the part of the job we built Passionfruit’s AI quality colleague to carry.

It starts on the day of the change. Passionfruit works from your own systems, like SharePoint, so once the updated spec is in there, that is what it works from. You ask it to draft the statement for your customers, and it writes it from the updated source documents. You read it, adjust what you want, and sign it off.

Then the questionnaires come in. Passionfruit fills them inside the customer’s own Word, Excel or PDF file, from your current documents. So the answers include the sesame change, because it’s in your spec.

When it’s done, it tells you which documents it used. And if you want to know where a specific answer came from, you ask, and it tells you.

Nothing goes out until you have checked it. You approve, edit or reject.

So the change only has to happen once, in your spec. The statement and the questionnaires after it are written from there.

Allergens are just one example. It works the same way for any change to a spec, and in Word, Excel or PDF, whatever format the request arrived in.

I think keeping everything you send in line with your spec is exactly the kind of work an AI quality colleague should carry. Your team then gets to spend its time on the questions that actually need their judgment.

If you want to see what this looks like with your own documents, give us 30 minutes of your time. Bring a statement you had to send after a change, or an allergen questionnaire from your inbox, in whatever format it came in. We will show you exactly how it gets handled.