How updates work
The document changes when the rule changes.
That is the whole proposition, so here is exactly how it happens, including the part that is a person rather than a machine and the part that is not switched on yet.
Every document names its sources
Not a category, not a topic — the specific official pages the document is built on, printed inside the file and listed on its product page. That list is the watch list. If a document cannot name a source, we do not sell it.
Those pages are fetched and hashed
The page is fetched and its body is hashed. A change is a different hash, not a guess from a summary or a news feed. Byte-identical bodies across repeat fetches are what make this trustworthy rather than noisy.
Every change is reviewed before anything moves
A different hash means something moved, not that it matters. The diff is read and reviewed before a document is re-issued — which is why you do not get a rewritten file every time an agency fixes a typo.
The document is rewritten and replaced
The new version appears in your account, numbered and dated. You do not pay again and you do not have to be watching for it. Your old copy is kept too, with its date, so you can always show which version was correct at the time.
You are told, in plain words, only when something changed
No weekly digest of nothing. Quiet is the normal state and quiet means nothing moved. A note goes out when a document you own has actually been replaced, and it says what changed and why.
Whose pages we read
109 official sources across 27 authorities. These are the actual pages, not a topic list. The registry also holds 5 reference sources for the aisles where no agency publishes anything: those are read the same way, and they are never counted or described as official.
What this cannot do
- It cannot tell you that you are compliant. It tells you the document you hold matches the sources it names, as of the day those sources were last read.
- It cannot watch a rule nobody has published. If an agency changes practice without changing a page, a hash will not see it.
- It cannot know your site. A document that is current can still be wrong for the job you are actually doing, which is what the fitted edit is for.