What triggers an email
- A clause status changes in the public contents or the draft moves stage.
- The planning date or the ballot date changes.
- A transition arrangement is published.
- A source we rely on changes or a correction is needed.
Nothing else. No weekly digest, no marketing.
How it works
A refresh script downloads the public sample and checks it against the record. Any difference is written as a diff. The same diff is what the watch emails. If nothing changed, nothing is sent.
What is watched: the public sample hash and contents, the official ISO stage, edition and page count, the planning assumption, and the source list. The script runs daily. A source that cannot be reached is a failure and is reported, never treated as no change. The paid full text is not watched, because we do not hold it; when it is published, the record needs a rebuild and the watch says so.
Start the watch, USD 29 a month
Stripe handles the subscription and the receipt. Cancel from the receipt or from the Stripe customer page.
What it cannot do
It cannot read the paid full draft. It watches the public record and the dates. When the full text is published, the record will need a rebuild, and the watch will say so.
Record change: 2026-10-19
ISO/DIS 22000:2026 · stage 40.60
Changed: committee note added to the source list.
Before: next committee meeting not recorded.
After: November 2026, Buenos Aires, per committee document N 067.
What it means: the text can still change after the ballot. Keep the plan dated but keep the decisions reversible until publication.
This sample is rendered from the real record and labelled. It is not a promise of a future alert.