Photo: Quilia / UnsplashEnrollment Application Errors: How to Catch and Correct Mistakes Before They Derail Your Lottery
A single transposed digit in a birth date field. A family that submits twice because they were not sure the first form went through. A rising fifth-grader accidentally slotted into the third-grade pool. None of these mistakes look dramatic in isolation. But when enrollment application errors like these slip into your lottery dataset unchecked, the consequences compound fast: a seat offered to the wrong applicant, a waitlist ordered incorrectly, a compliance question from your authorizer that you cannot answer cleanly.
Most enrollment teams discover these problems after the lottery has already run — when the cost of fixing them is highest and family trust is hardest to rebuild. This guide walks through the most common categories of enrollment application errors, how to catch them before lottery day, and what correction workflows actually look like in practice.
Why Enrollment Application Errors Matter More Than You Think
Lottery integrity depends on data integrity. If your applicant pool contains duplicates, your random selection process is no longer truly random — one family has twice the chance of being drawn. If grade-level fields are wrong, you may fill a seat in a cohort that was already at capacity while leaving another cohort short. If incomplete applications are included without review, you risk offering seats to families who never actually finished the process, which delays onboarding and wastes staff time chasing missing information.
Beyond operational headaches, errors create compliance exposure. Most charter authorizers expect you to demonstrate that your lottery was conducted fairly and that every applicant was treated equally. When your data is messy, you cannot make that case with confidence. And if a family challenges a waitlist placement, you need clean records to show exactly what happened and why.
The good news: the vast majority of enrollment application errors fall into a handful of predictable categories. Once you know what to look for, building a pre-lottery review process is straightforward.
The Five Most Common Enrollment Application Errors
After working with enrollment data across many school contexts, the same mistake types surface again and again. Here are the five you are most likely to encounter.
1. Duplicate Submissions
This is the single most common error. It happens when:
- A parent submits, does not receive a confirmation, and submits again.
- Two guardians in the same household each submit a separate application for the same child.
- A family applies through both an online form and a paper form.
Duplicates are dangerous because they can double a student's chance in the lottery draw. They also inflate your applicant counts, which skews reporting and capacity planning.
How to catch them: Match on a combination of student first name, last name, and date of birth. Do not rely on email address alone — families often use different emails across submissions. Flag any records that match on at least two of three identifiers and review them manually.
2. Mismatched Grade Levels
This happens when a parent selects the wrong grade on the application — usually because the form asks for "grade applying for" and the parent enters the child's current grade instead. It also occurs when a family is unsure whether their child will be retained or promoted.
How to catch them: Cross-reference the grade-level field against the student's date of birth. If a child's age falls well outside the typical range for the selected grade, flag it. You will not catch every case this way, but you will catch the obvious ones — like a four-year-old listed as applying for sixth grade.
3. Incomplete Applications
Some forms arrive missing critical fields: no parent contact information, no student birth date, no grade selection. This often happens with paper applications or with online forms that do not enforce required fields at submission.
How to catch them: Define your minimum required fields before the application window opens. Run a completeness check on every submission as soon as it arrives. If a field is missing, flag the application immediately and reach out to the family while the window is still open so they have time to correct it.
4. Sibling Linkage Errors
Many schools offer sibling preference in their lottery. Errors here include:
- A family listing a sibling who is not actually enrolled at the school.
- Two siblings' applications that are not linked to each other because the parent used different contact information on each form.
- A sibling preference claimed for a step-sibling or household member who does not meet the school's definition of "sibling."
How to catch them: Cross-reference sibling names listed on applications against your current enrollment roster. For new families applying with multiple children, verify that applications share at least one matching guardian name or address. Check your school's sibling definition in your charter or enrollment policy and apply it consistently.
5. Address and Contact Data Errors
Typos in addresses and phone numbers are common and usually harmless — until you need to send a seat offer letter and it bounces, or until you need to verify residency for a geographic preference. Transposed zip codes can also misclassify a family's eligibility for attendance-zone preferences.
How to catch them: Run addresses through a basic validation check (does this zip code exist? does the street name match the city?). For schools with geographic preferences, map addresses against your defined boundaries before the lottery, not after.
Building a Pre-Lottery Error Review Process
Knowing the error types is only useful if you have a systematic process for finding and resolving them before the lottery runs. Here is a practical framework.
Set a Data Freeze Date
Choose a date between the close of the application window and the lottery draw — typically three to five business days. This is your window for cleaning the data. Communicate this timeline to your team so everyone knows that no new applications will be accepted after the window closes and that the review period is protected time.
Run Automated Checks First
Before any human reviews a single record, run automated checks for:
- Duplicate records (matching on name + date of birth)
- Missing required fields
- Grade-level / age mismatches
- Address format validation
- Sibling cross-references against enrollment rosters
These checks can be as simple as spreadsheet formulas or as sophisticated as built-in platform rules. The point is to surface the obvious problems without requiring staff to eyeball every row. If your enrollment platform supports automated validation, configure it before the application window opens so flags appear in real time.
Triage Flagged Records
Not every flag requires the same response. Sort flagged records into three buckets:
- Auto-resolve: Clear duplicates where the same guardian submitted the same information twice. Merge or remove the duplicate and note it in your audit log.
- Family outreach required: Incomplete applications, ambiguous sibling claims, or grade-level mismatches that need clarification from the family. Contact them by phone and email, give a clear deadline for response, and document every attempt.
- Internal review required: Cases where your enrollment policy needs to be interpreted — for example, whether a particular household arrangement qualifies for sibling preference. Bring these to your enrollment director or school leader for a decision, and document the rationale.
Document Everything
For every error you find and every correction you make, keep a record of:
- The original data
- The nature of the error
- The corrective action taken
- Who took it and when
- Any communication with the family
This audit trail is what protects you if a decision is questioned later. It is also what your authorizer will want to see during oversight reviews. Check your state requirements and authorizer expectations around record retention — some specify how long enrollment records must be kept.
Handling Enrollment Application Errors After the Lottery
Despite your best efforts, some errors will surface after the lottery has been drawn. A family calls to say they were placed in the wrong grade pool. A duplicate slipped through. A sibling preference was applied incorrectly.
Here is how to handle these situations without making things worse.
Do not re-run the entire lottery. In most cases, a single error does not require starting over. Instead, assess the impact of the error on the specific applicant and on any other applicants whose placement may have been affected.
Follow your written enrollment policy. Your policy should describe how post-lottery corrections are handled. If it does not, add that language before next year's cycle. Having a documented procedure removes the appearance of ad hoc decision-making.
Communicate transparently with affected families. If a family's placement changes because of an error, tell them what happened, what you are doing to correct it, and what their options are. Families can absorb bad news far more easily when they trust the process.
Log the error for process improvement. Every post-lottery error is a signal that your pre-lottery review missed something. Add it to your list of checks for next year.
Preventing Errors at the Source
The cheapest error to fix is the one that never happens. Here are design choices that reduce errors before they enter your system.
- Use dropdown menus instead of free-text fields for grade level, school year, and other structured data. A parent cannot type "5th" when the only options are "Grade 5" and "Grade 6."
- Require confirmation screens before final submission. Show the family a summary of everything they entered and ask them to confirm. This catches typos and wrong selections before they become your problem.
- Send immediate confirmation messages — email, text, or both — so families know their application was received. This is the single most effective way to prevent duplicate submissions.
- Translate your application into the languages your community speaks. Errors spike when families are guessing at field labels in a language they do not read fluently.
- Limit one application per student at the system level if your platform supports it. Match on name and date of birth at submission time and alert the family if a record already exists.
- Train your front-office staff on common error patterns so they can catch problems when helping families submit paper applications in person.
How Marble Supports This
Marble's enrollment platform is built to catch the errors described in this guide before they reach your lottery. Automated duplicate detection, required-field enforcement, real-time sibling verification, and grade-level validation are part of the core workflow — not afterthoughts bolted on to a spreadsheet. Every correction is logged with a full audit trail, so your records are clean when your authorizer comes asking. If you want to see how it works in practice, visit how it works.