How the checking works

No black box: this page describes exactly what the pipeline does, and the pipeline is the only thing that writes this site.

1. Requirements come only from official sources

Every verified requirement was read off an official source — a state statute portal, a licensing board, or a workers'-compensation agency — and stores a verbatim quote from that page plus its URL. Insurance blogs and marketing sites are never used as sources.

2. A machine re-checks the quotes on every refresh

The pipeline re-downloads every cited official page and verifies each stored quote still appears there. The date next to a requirement is the last day the quote was actually re-found — not the day someone last felt like updating the site.

3. Lost evidence is flagged, never patched

If a quote disappears, the row flips to not machine-verifiable — check the official source the same day and the event lands in the change log. We do not guess the new rule.

4. What the honest markers mean

Many cells say a requirement is not machine-verifiable. Each marker says why: some official pages went missing in site restructures, some block automated access, some render only in a browser, and for many occupations the state genuinely publishes no statewide insurance mandate (rules sit at city or county level, or in board rules published outside fetchable pages). Sites that fill those gaps anyway are guessing; this one doesn't.

5. What this site is not

Not legal advice, not insurance advice, not a comparison of insurers — no products or carriers are named or ranked anywhere. And verification proves what the official page says, not how a board applies it in practice. City and county requirements are out of scope and can be substantial.

Last full check: 2026-09-05. Sources fetched: 17; fetch failures this run: 0.