SCI-OLY
Science Olympiad Event Assignment Planner
Spread a limited roster across a long event list, line up backups, and catch overloads and same-block conflicts early.
What you'll need
Have these numbers handy.
Before you share
- Leave out private student, family, payment, tax, credential, medical, and emergency-contact details. Initials or labels work fine.
- Double-check rules, forms, fees, schedules, safety, and eligibility on the official program, school, and event pages.
- Your work saves in this browser when supported — download a backup for anything you'd hate to lose.
Science Olympiad assignment grid
Division note not set / Prepared by not set
| Event | Type | Primary | Backup | Block | Status |
|---|---|---|---|---|---|
| Event row 1 | Type not set | Missing | Missing | Block not set | Draft |
| Code | Primary | Backup | Total | Over target |
|---|---|---|---|---|
| No student-code load yet. | ||||
- Add student codes before sharing this assignment grid. Use codes, not student names or emails.
- Some event rows are missing primary coverage.
What you get
What you can print or export.
- Event assignment draft
- Student load check
- Backup coverage notes
- Conflict reminders
Print the packet, export a CSV, or download a backup file straight from the tool.
Example packet
Spring invitational assignment draft
A coach assigns anonymous student codes across study, build, lab, and partner events, then checks overloads, backup coverage, and same-block conflicts before the team meeting.
- Covered events: 8 of 8
- Backup coverage: 8 of 8
- Overloaded codes: 1
- Same-block conflicts: 1
- Student-code load table for coach review
Assumptions
What this tool assumes.
- Use anonymous student codes only; keep names, emails, medical details, emergency contacts, addresses, IDs, and private family information outside SciPacket.
- Official event lists, rules, schedules, eligibility, forms, and safety requirements must be checked at the official source.
- Schedule blocks are coach-entered planning labels and do not verify tournament timing.
- The planner flags load and conflicts from entered rows; you still need to review skills, absences, partners, and event-specific requirements locally.
The math
How the numbers are figured.
- Covered events = event rows with a primary student code.
- Backup coverage = event rows with a backup student code.
- Student-code load counts primary and backup assignments for each entered code.
- Overloaded codes are primary assignment counts above the coach-entered target.
- Same-block conflicts flag one primary student code assigned to more than one event in the same schedule block.
- Unknown primary or backup codes create review warnings when they are not in the student-code list.
FAQ
Questions
FAQ
What does this assignment planner do?
It checks event coverage, backups, student-code load, overloads, and same-block conflicts in your browser. You can print, export CSV, or download a backup file.
FAQ
Can I enter student names or contact information?
No. Use anonymous student codes only. Keep names, emails, medical details, emergency contacts, addresses, IDs, and private family information in your approved roster system.
FAQ
Does this include official Science Olympiad rules or event schedules?
No. This planner only organizes local assignment notes. Check official national, state, tournament, and school sources for current rules, schedules, eligibility, forms, and safety requirements.
Related tools
Coaches who use this one usually need these too.
One list for everything that has to make it onto the bus: coach binder, student materials, devices, snacks, forms, and the pit or table boxes.
- Packing checklist
- Coach binder list
- Student materials list
Plan stations, materials, facilitators, family guides, table signs, and volunteer roles for STEM night.
- Station plan
- Materials list
- Volunteer roles
Work backward from fair night: forms, SRC/IRB checkpoints, judging, awards, and the deadlines in between.
- Timeline draft
- Rules-check reminders
- Judging prep notes