Future Innovators CampFINO 2026Navigate · Innovate · Elevate

Admin Help

Admin Quick Start

Use these checklists to prepare, run, and close the event cleanly.

Go to Admin Dashboard

Admin workflow order

  1. Create and monitor Homework.
  2. Manage Judge Evaluation.
  3. Manage Team Voting.
  4. Review Final Ranking.

Before the event

  • Confirm all teams and students are in Supabase.
  • Check that every student has a unique access code.
  • Confirm Homework setup is complete.
  • Confirm Judge Evaluation setup is complete.
  • Confirm Team Voting setup is complete.
  • Create judge accounts and Judge Evaluation criteria.
  • Test student login and admin login before sharing the link.

During the event

  • Monitor submitted and not submitted counts.
  • Open session reports to find groups needing follow-up.
  • Use Homework Review to read submitted survey responses when mentors need context.
  • Close sessions when the deadline or event rules require it.
  • Open or close the Judge Evaluation portal when judges are ready.
  • Open or close the Team Voting portal for student voting.

Homework response review

  • Open `/admin/homework/builder` to create or edit Homework surveys.
  • Add paragraph questions and preview the student view before opening a survey.
  • After students submit, question deleting and reordering are locked to protect responses.
  • Open `/admin/homework/review` to view submitted survey responses.
  • Filter responses by Homework session or team.
  • Open a student response to read each question and answer.
  • Return a response for resubmission when a student needs to revise answers.
  • Students may self-edit Homework while the session is still open.
  • After close or deadline, students can resubmit only after admin returns that response.
  • Homework content review does not affect Final Ranking.
  • Homework scoring is still based on submission completion only.
  • Resubmission updates the same record and does not create duplicate points.

Judge account management

  • Edit judge name, email, access code, and active status from `/admin/judges`.
  • Delete only judges that have not submitted scores.
  • If a judge has submitted scores, reset or deactivate that judge instead.

After the event

  • Export Homework CSV for the scoring workbook.
  • Export Judge Evaluation CSV for the scoring workbook.
  • Export Team Voting CSV for the scoring workbook.
  • Review Final Ranking before sharing results.
  • Confirm Homework Score /10 and weighted score columns.
  • Confirm the final file is stored securely.

Deployment link checklist

  • Confirm the production URL opens on desktop and mobile.
  • Confirm `/student-login` and `/admin/login` are accessible.
  • Share the link only after test data is cleared.

Supabase data checklist

  • 6 teams are present.
  • 54 students are present.
  • Each team has 9 students.
  • Each student is assigned to the correct team.
  • Homework sessions and questions are present.
  • Judges and active criteria are present.
  • Team Voting settings are configured.

Deployment settings checklist

  • Supabase connection is configured.
  • Admin password is configured.
  • Production settings are kept private.
  • No secret values are shown in the app.

Access code distribution checklist

  • Send each student only their own access code.
  • Use a private channel for access code delivery.
  • Keep a backup list for mentors or organizers.

CSV export checklist

  • Download Homework CSV from the admin dashboard.
  • Download Judge Evaluation CSV from the judge dashboard.
  • Download Team Voting CSV from the team dashboard.
  • Open it and confirm all 6 teams appear.
  • Check actual submissions and weighted score before sharing.

Data privacy checklist

  • Do not share private access codes publicly.
  • Do not expose student answer text unnecessarily.
  • Share only approved final results.
  • Restrict admin access to trusted organizers.