How to Document Your Charter School Enrollment Lottery for an Audit
Charter school authorizers conduct compliance reviews. Parents file complaints. Occasionally, attorneys get involved. In every one of these scenarios, the school that has complete, well-organized lottery documentation resolves the situation faster — with less damage — than the school that doesn't.
The problem is that most schools think about documentation after they need it — not before. By then, it's too late to generate a complete record. You're stuck reconstructing what happened from memory, emails, and spreadsheet versions, hoping it holds together.
This guide tells you exactly what lottery documentation you need, how to organize it, and how to make sure it exists before anyone asks for it.
Why Documentation Matters More Than You Think
Federal law (ESSA) requires charter schools to use random lottery selection when oversubscribed. Your charter agreement almost certainly includes compliance requirements tied to that mandate. Your authorizer has the right to request documentation of any lottery you've run — typically with short notice.
When documentation is requested, what happens next depends on what you have:
Schools with complete documentation answer the inquiry with a single export, confirm compliance, and move on. The process takes hours.
Schools with incomplete documentation spend days or weeks assembling records, fill gaps with approximations, and often end up with a record that has enough inconsistencies to raise more questions. The process takes weeks and leaves a mark on the authorizer relationship.
The difference isn't luck. It's whether documentation was treated as a planned output of the lottery process or an afterthought.
The Six Records Every Lottery Must Produce
1. The Complete Applicant List
Every application submitted before the lottery's closing deadline, including the applicant's name, application date, and timestamp.
This is the foundation of your compliance record. It proves who was eligible to be included in the draw, that the deadline was applied consistently, and that no applications were added or removed after the draw.
What to include:
- Student name
- Application date and timestamp
- Grade level applied for
- Any preference categories claimed (sibling, returning student, etc.)
- Status (included in draw / excluded and why)
Red flag to avoid: Any gap between applications received and applications included in the draw that isn't clearly documented and justified.
2. The Randomization Record
Documentation of exactly how the lottery draw was conducted — the method, the tool, the inputs, and the outputs.
"We ran it randomly" is not documentation. You need to be able to show how results were generated in a way that a neutral third party could independently verify.
What to include:
- The tool or software used
- The randomization method (algorithm name and version if applicable)
- The random seed or input used to generate results (if applicable)
- The date and time the draw was run
- Who ran the draw
- A statement that results are reproducible using the documented seed and method
The Excel problem: Excel's RAND() function does not produce a fixed seed and recalculates every time the file opens. Results cannot be reproduced. This is why Excel is not appropriate for lottery documentation.
3. The Full Ranked Results
The complete ordered list of all applicants following the draw — not just who was selected, but the full ranking, including waitlisted and non-selected applicants.
If a parent asks why their child was ranked 47th instead of 12th, you need to show the complete list, not just the top results. Partial records create credibility problems.
What to include:
- Every applicant, in ranked order from the draw
- Clear designation: Selected / Waitlisted / Not Selected
- Waitlist position numbers
- Seat counts by grade level
4. Preference Category Documentation
A record of how any preference categories (sibling, returning student, staff child, geographic zone, etc.) were applied in the lottery.
Preference categories are the most common source of lottery disputes. If a family claims their sibling preference wasn't applied — or was applied incorrectly — you need documentation showing exactly how preferences were configured and which applicants they affected.
What to include:
- Which preference categories were active in this lottery
- The source authorization for each preference (charter agreement section, board resolution, etc.)
- How many applicants claimed each preference
- How preferences were applied relative to the random draw
- The names of applicants who received each preference designation
5. Offer and Response History
A record of every offer made from the lottery results — who was offered a seat, when the offer was sent, the response deadline, and the outcome.
Waitlist management is the most legally exposed part of the post-lottery process. If a seat was offered to the wrong family, offered out of order, or an offer expired without proper follow-up, the documentation needs to show what actually happened.
What to include:
- Date and time each offer was sent
- Offer deadline
- Outcome: Accepted / Declined / Expired
- Date of acceptance, declination, or expiration
- Waitlist promotions: who was promoted, when, and from what position
6. Draw Timestamp and Authorization Record
A verifiable record of when the lottery was run and who authorized or conducted it.
The timing of the draw matters. Results should be generated after the application deadline and before offers are sent. Any question about whether the draw preceded or followed a specific event needs a clear timestamp answer.
What to include:
- Date and time the draw was run (to the minute)
- Name and title of the staff member who ran the draw
- Confirmation that the applicant list was locked before the draw
- If the draw was observed: names of observers
How to Organize Your Documentation
All six records should be stored together, in a format that can be exported and shared on short notice. The goal is to be able to respond to a documentation request the same day it arrives.
Best practice: Keep a single lottery documentation package for each lottery you run. Label it clearly with the school name, lottery year, and grade levels. Store it somewhere accessible to more than one person — not on a single administrator's laptop.
Retention: Keep lottery documentation for a minimum of 5 years. Some states require longer. Check with your authorizer.
The Fastest Way to Have All of This Ready
Assembling this documentation manually — from spreadsheets, emails, and notes — is time-consuming and error-prone. The most reliable way to have complete lottery documentation is to use software that generates it automatically as part of the lottery process.
Marble produces all six records automatically for every lottery:
- Complete timestamped applicant list, locked before the draw
- Cryptographic draw seed and algorithm version, recorded at draw time
- Full ranked results with waitlist positions
- Preference category configuration and application
- Complete offer and response history with timestamps
- One-click compliance export containing everything above
When documentation is requested, the answer is a single export — not a week of assembly.
Summary Checklist
Before you consider your lottery documentation complete, confirm you have:
- Complete applicant list with timestamps
- Documentation of randomization method and seed
- Full ranked results (all applicants, in order)
- Preference category configuration and application record
- Offer and response history with dates
- Draw timestamp and authorization record
- Everything stored in one place, accessible, exportable
If any of these are missing or incomplete, now is the time to establish a process that produces them automatically — before the next lottery season, not after a compliance review.