Editorial policy
What blocks a page from publishing
Short list, no exceptions. Most of it exists because someone else already got it wrong in public.
A page does not publish if
- A requirement has no source. No agency page, no statute, no official notice, no page. A number without a link is an opinion with a font.
- A requirement has no date. The date we read the source travels with the number, not in the footer.
- An unverified claim is dressed up as a fact. Anything we have not confirmed against the state is labeled as such, in place, every time.
- The page ranks or recommends a provider.No top picks, no "best", no editor's choice, no badge of our own. We reproduce the state's list.
- A commercial link appears without its disclosure. They render together or neither renders. It is one switch in the code, not a habit we rely on remembering.
- The page implies we are official. We are not a state agency, we issue nothing, and we are affiliated with nobody. Program names appear only to identify the program being described.
- The page invents anything about us. No testimonials, no reviews, no user counts, no seals.
Corrections
A wrong or stale requirement is a defect, and it gets treated like one: fixed at the source of the data, re-dated, and re-published. If a state changes a rule, that is not our error, but leaving the old number up is.
Rules move faster than pages. Validity periods change, grace periods get repealed, brand-new mandates start being enforced. That is why every state file gets re-read on a schedule and why the date is the first thing you see next to a number.
Sources we will not use
Other summary sites, course providers describing the requirement their own course satisfies, and AI-generated summaries of any of the above. They are how the same six errors ended up on a dozen pages.