Monitoring: EFSA News, Alerts, and the Specialist's Moment

Everything in this guide so far has one weak point we need to name: it's correct as of the day you applied it. A newly approved claim can open a communication gate for you tomorrow; a refused one can touch exactly the wording your category uses; and your own funnel — new ads, rewritten pages, fresh reviews — drifts out of the perimeter precisely in the weeks nobody is looking.

The answer is not permanent vigilance, which doesn't exist in practice. It's the same principle as in the other guides: the machine watches, you judge — with one extra layer specific to this territory: the short, precise list of the moments when judgment is handed to the specialist.

What you'll be able to do after this chapter

set up your regulatory tracking system: what goes on the Watchlist and what the radar brings on its own;
run the verification rhythm — monthly for register and funnel, immediately for the events that demand it;
know in advance which events go straight to the specialist, so the decision isn't made under pressure.

The principle

The system has three floors, each with its own rhythm:

The continuous flow — the machine works alone: your formula's ingredients sit on the Watchlist, Home shows you at every visit what changed since the last one, and the EFSA Radar brings the new decisions complete with their exposure. Nothing to do here except the setup — once.
The monthly rhythm — one hour, two questions. First: has anything appeared in the register that concerns me? — new decisions on your ingredients, approved claims that open themes for you, refusals touching the category's wordings. Second: is my funnel still the audited one? — the inventory from chapter 6, revisited on what changed in the meantime: ads launched, pages edited, new reviews displayed.
The specialist's threshold — the part that gets written BEFORE it's needed. The events that go straight to validation, with no internal debate: a new wording touching the health promise (ad, label, landing); a register decision on an ingredient in your formula — approval, refusal, changed conditions or levels; a formula change — any carrier added or removed re-judges the claims; and entering a new market, where local interpretation and language change the problem.

The threshold's logic deserves a line: the moment you need the specialist is exactly the moment you're tempted to save their time — the launch is close, the pressure is high. That's why the list is written now, calmly, and followed mechanically. A whole guide of discipline is worth nothing if the last link is negotiated under pressure.

The workflow in RavenBI

The setup (once): put your formula's ingredients on the Watchlist — the hero and the carriers — plus the category you compete in. Turn on alerts for what you don't want to miss between visits.
Check Home at every visit: the changes on your entities since the last visit — the regulatory signals appear here alongside the rest of the market's moves.
Monthly, question 1: open the EFSA Radar filtered on your ingredients and the latest interval's decisions. For each new decision: does it touch me? If yes — it's on the threshold list, so it goes to the specialist, with the summary and official source from the radar.
Monthly, question 2: revisit the funnel inventory from chapter 6 only on what changed: the ads launched since the last audit, the pages edited, the new displayed content. Whatever touches the health promise goes through chapter 5's filter.
Keep a minimal journal — the date, what you checked, what you sent to the specialist, what changed. Not for bureaucracy: for the day someone asks "since when have you been communicating this?" and your answer is a date, not a shrug.

How to read the signals

A claim approved on one of your ingredients = a new communication gate — there may be an early-positioning window, to be weighed with the radar's exposure; to the specialist with it, with priority;
A claim refused that touches the category's wordings = the wave of rewordings may follow — check your own copy first, then watch how the market reacts;
Changed conditions or levels on a carrier = formula and claim get re-judged together — exactly the case the carriers sit on the Watchlist for;
Whole months with nothing relevant = the normal of this territory — the register moves slowly; let the monthly rhythm be boring and resist the temptation to abandon it for exactly that reason.

The typical mistakes

setting up the system and never opening it again — unread alerts are the functional equivalent of their absence;
leaving the funnel audit "for when we launch something big" — drift comes from the small, frequent changes, not from launches;
negotiating the specialist's threshold under launch pressure — the list was written calmly precisely for this moment;
monitoring only the register and not the market — a newly approved claim counts double when you see, in its exposure, how many brands, products, and active ads the decision touches.

Exercise

Do the setup now, while the guide is fresh: the formula's ingredients on the Watchlist, the alerts on, the monthly hour in the calendar with the two questions written in the invitation, and — separately, in a short document — the threshold list: the four types of events that go straight to the specialist. The first monthly check runs on what you already have: the funnel inventory from chapter 6 and the formula's claims from chapter 3.

With this, the guide is closed — and, like any good system, it only starts working now. You have the whole road: the claim as an asset, the radar that keeps it current, the formula that unlocks it, the map of the space where it differentiates, the copy that carries it into the market without exceeding it, the funnel that keeps it intact, and the rhythm that watches over it all. The list of permitted promises we didn't give you — it's in the register, alive, tied to your market in RavenBI. The method for building on it is, from now on, yours.