Charter School Lottery Compliance: Audit Trails & State Requirements

Running the draw is the easy part. Proving it was fair when an authorizer asks is the hard part. Here is what compliant actually looks like.
Running a random lottery is the easy part. Being able to prove you ran it fairly, months later, when someone official asks, is where schools get tripped up. Your lottery has to hold up to scrutiny, and that comes down to keeping records that show what you did and that it matched your own rules.
Why your authorizer cares
A charter is a contract, and fair enrollment is part of the deal you signed. If you can't explain how seats were assigned, you're exposed, whether that turns up as an audit finding or as an angry parent who's convinced the deck was stacked. The records aren't busywork. They're what protects the school and the families who trusted the process.
What reviewers usually want to see
- An enrollment policy that was published before the lottery, including any priority groups.
- Proof the draw was actually random and that nobody touched the results.
- The full list of applicants, who got seats, and the waitlist order.
- A clear account of how each priority group was defined and applied.
- Records kept for as long as your state requires, ready to produce on request.
The audit trail
An audit trail is a running log of everything that mattered, stamped with when it happened and who did it. That covers the day the window opened and closed, who verified which applications, when the draw ran and with what settings, and every move on the waitlist. What makes it worth anything is that nobody can go back and quietly rewrite it. If your current process lives in a spreadsheet that anyone with the link can edit, you don't really have one.
Proving the draw was random
This is the piece schools underestimate. A spreadsheet's random function is impossible to prove after the fact, because you can re-run it and get different numbers. Software that uses cryptographically secure randomization and hashes the result gives you something solid to point at: this exact result, unchanged. We explain how we handle it on the security page.
Keeping the records
Hold on to the enrollment policy, the lottery settings, the results, and the waitlist together, for as long as your state asks, which is often several years. The schools that breeze through an audit are the ones who can pull all of it up in a couple of minutes instead of digging back through old email.
Where software helps
Good lottery software handles most of this quietly in the background. It snapshots the configuration for each run and logs everything in a way you can't tamper with. The randomization is done properly, and when the state comes knocking you export a clean report instead of building one from scratch. You can see how different tools handle it on the comparison pages, or set your school up for free and look at the records it keeps.