CheckFirst ESA by Simpli Software

· updated

Reading Your Program's Handbook Without Losing Your Mind

Reading Your Program's Handbook Without Losing Your Mind

Program handbooks are long, written by committee, and organized for the people who administer the program rather than for the parent trying to decide about a purchase on a Tuesday night. You do not have to read one cover to cover. You do have to read the right parts of the right document.

Here is a method.

Step 0: Make sure you have the right document

This step catches more mistakes than all the others combined.

Check the school year. It is usually on the cover. Make sure it is the year you are in, not the year the file was sitting in your downloads folder from.

Check the revision date. Often on the cover page, in the footer of every page, or on a "summary of changes" page. A document revised mid-year is the version that counts.

Check you have all the documents. Many programs publish more than one: a family handbook, a purchasing or marketplace guide, a category list, a provider directory. They are not always revised at the same time, so a handbook and a purchasing guide can genuinely disagree. If they do, that is a question for the program, not a puzzle for you to solve by picking the one you like.

Save it locally with the year in the filename. program-handbook-2026-27.pdf. Websites reorganize, links break, and the version you read is worth being able to point to later.

Step 1: Read six sections first

Most of a handbook is context. These are the parts that change what you do:

  1. Who administers the program and how to contact them. This is who answers questions and who reviews your expenses. Note the support email or the in-portal message path.
  2. What the money may be used for. The categories, and any list of things it may not be used for. Read both — the second list is usually shorter and more specific, and it is where surprises live.
  3. How you pay. Marketplace, direct payment to a provider, reimbursement, or a mix. This determines whether your own money is ever at risk.
  4. What documentation you must keep and submit. Itemized receipts? A purpose statement? Proof of delivery? Anything you will be asked for later is much easier to produce at purchase time.
  5. Dates. Application windows, submission windows, reporting dates, anything that expires. Put them in your calendar the same day you read them.
  6. What happens if something is turned down. Every handbook says something about this, and almost nobody reads it until they need it. Read it before you need it — see What Happens If an ESA Purchase Gets Rejected.

Everything else you can read when it becomes relevant.

Step 2: Build a one-page cheat sheet

As you read, keep one page — paper, a note, a document, whatever you will find again. On it:

  • The program's full name and who administers it.
  • The support contact you are supposed to use.
  • The handbook version and revision date you read.
  • The categories, in your own words, one line each.
  • How you are supposed to pay.
  • What you must keep for every purchase.
  • Every date, in a list.
  • Your open questions.

This page, not the handbook, is what you will consult ninety percent of the time. Re-make it when a new handbook comes out. The re-making is what forces you to notice what changed.

Step 3: Read the language carefully in three specific places

Handbook prose is precise in ways that are easy to skim past.

"May" versus "must." "Receipts must be itemized" and "receipts may be requested" are very different obligations.

Lists that say "including" versus lists that say "only." "Including but not limited to" means the list is examples. "Only the following" means the list is the whole universe. This one distinction accounts for a lot of misunderstandings.

The clause that says the program can change things. Nearly every handbook has one. It is why "it was fine last year" is not an argument, and why checking the current version each year is not paranoia.

Step 4: Know what to do when the handbook doesn't answer you

It often will not. Your situation is more specific than the document.

Do not infer. The gap between "the handbook doesn't say no" and "that's fine" is exactly where families lose money.

Do not take a parent group's word for it. Those groups are excellent for finding out what questions to ask and genuinely unreliable for what the rule is. Different state, different program, different year, one person's experience with one reviewer. More on that in Who Actually Decides What ESA Money Can Be Used For.

Ask the program, in writing, quoting the document. A question that cites the section gets a better answer than one that does not:

"Section 4 lists instructional materials as a category, and Section 7 says receipts must be itemized. For a bundled curriculum kit sold as a single line item, does the vendor's packing list satisfy the itemization requirement?"

Save the answer with the handbook. Same folder, dated filename. An answer in writing from the program is the most useful document you will collect all year, and it is the thing you will want if a decision is ever revisited.

Step 5: Re-read twice a year

Once before the school year starts, and once mid-year. The mid-year pass is short: check whether a new revision has been published, and if so, look for a summary-of-changes page. If there is not one, compare your cheat sheet against the new document rather than re-reading the whole thing.

A note on tone

If the handbook feels hostile, it is usually not. It is written to cover a program's obligations, and it is written for many families at once. Nobody on the other end is trying to catch you out. Asking a question early is normal, expected, and much cheaper than guessing.

What to do next

  • Confirm the school year and revision date on the document you are using. If it is last year's, stop and go get this year's.
  • Read the six sections above, and nothing else, in one sitting.
  • Make your one-page cheat sheet.
  • Send your open questions to the program in writing, and save the answers next to the handbook.

CheckFirst ESA is an organizing tool that keeps receipts, records and program deadlines in one place. It is not your program administrator and it does not make decisions about your purchases.

This article is for general information and isn't a substitute for guidance from your program. Rules can change; always confirm with your program before you buy.

Related reading