How we check every update

Software finds the change. A person decides whether it is worth your time, and checks every word against the state's own text before it is sent.

Two colleagues reviewing a document together in an office

1. Only official sources

We read the states' own pages: rule chapters, state registers, agency notices, forms and program pages. Each one is stored every time we read it, so we can always show what it said before and after. Each state's page lists the sources we watch.

2. A change has to be proven

A change only counts when two stored copies of a page differ. Layout shuffles, page dates and footers are set aside, so a website redesign does not become an alert.

3. Matched to the right agencies

Each change is matched to its state and to the agency types it affects. A home health change never reaches an assisted living agency, and a Texas change never reaches an Ohio one.

4. A brief, checked against the text

A plain-English brief is drafted from the changed text: what changed, who it affects, what to do and by when. Every quote in it is checked against the state's published words; an action that cannot be traced to the text is removed rather than guessed.

5. A person approves it

A reviewer reads the brief against the source and approves it, or decides it should not be sent and records why. Nothing goes out unapproved. The printable memo names who released each update and when.

6. After it is sent

  • When the rule changes again, the new update says "Update to the notice of" the earlier date, and links back to it.
  • If we ever withdraw an update, it is marked as withdrawn in your portal, and its memo is no longer offered.
  • The official text is always the authority. We are not a law firm and this is not legal advice.

See a real, approved update.

Every part explained, as the Monday email and the survey memo.