A little clarity goes a long way.
The first-release path from approved lists to family responses.
For school staff
- Create an event and import one approved CSV for each grade, with seat counts.
- Review the inputs. Freeze them when complete.
- Have a different staff member sign in and approve the frozen inputs as witness.
- Run rehearsals, then have the operator type DRAW to commit one official order.
- Download the signed certificate before publishing results.
- Type PUBLISH when ready. Open the separate public display and reveal names at your own pace.
- Invite verified guardians and issue selected-seat offers. Monitor responses and offer vacancies to the next active waitlist applicant.
For families
Use the invitation your school shares with you. Set a password and sign in with the included school code. Your portal shows your linked children, published results and available offers. Contact the school for missing records, password resets or registration documents.
If something stops during the official draw
Reload the event to check for its saved certificate. A committed event with no completed certificate remains locked. Preserve it and involve your administrator. Never copy the list into another event just to retry.
CSV format
applicant_id,display_name K001,Avery Example K002,"River Example, Jr."
Use UTF-8, unique IDs across the event, and one grade per file. Blank records, extra columns and malformed quoting are rejected. A header-only file intentionally represents zero applicants.
First-release boundaries
School decisions and approved lists remain the school’s responsibility. Online application builders, district matching, document upload, automated email/SMS, subscription checkout and native Mac synchronization are future releases. The browser public display works independently. Payment connectors require separate live-provider testing and authorized activation.