Who writes this, and what it will never do

What this site is

MyServerCard answers one question that the people selling the course cannot answer for you: what does your state require for your job. Every state names the credential differently, sets its own deadline, and approves its own list of providers. We read the state, write down what it says, and record the date we read it.

Then we show you every provider the state approved, including the ones that pay us nothing, at the price they charge.

What this site is not

• Not a government agency, and not a licensing body. We do not issue cards. Your state, or a provider it approved, does that.
• Not a course provider and not a storefront for one brand. We do not sell or run training.
• Not affiliated with, endorsed by or sponsored by any state program or provider named here. We name them to identify them, which is the only reason anyone should ever name them.
• No rankings, no top picks, no reviews, no badge of our own. The word "approved" on this site always means approved by that state, and it always links to the state list it came from.
• Not legal advice, and not advice about your situation.

Who writes it

Luciano Canziani, editor. Reads the statutes, the agency FAQs and the state information letters behind every requirement on this site, and records the exact source and the date each one was checked. Responsible for what gets published and for the corrections when a state changes a rule.

One person writes and checks everything here. That is a limit worth knowing: it is why states are published one at a time instead of all fifty at once, and why a state with no page yet is a state we have not finished checking, not a state we forgot.

How to use it

Read the requirement, then open the source link next to it and confirm it yourself before you pay for anything. That is not a disclaimer: it is the point. If we ever make it hard to check our work, we have stopped being useful.

How we check a state · What blocks a page from publishing · How we make money