3D Modeling Club Hackathon: Staff Runbook

Update the existing 10-slide student deck for the Blender hackathon on October 9, 16, and 23, 2026. Preserve the robot, Blooket join QR, Club Meeting Survey https://forms.gle/3tAmLXmgV4GeGscb6, exact 5Star Code: 04106, Shadow EBoard Application, teams of 1–3, beginner/unfinished inclusion, and original credited work. Keep school-account submission of one .blend (max 100 MB) per team before October 23: https://forms.gle/DGVXLR4ut57z4iUh9, with QR on slides 6 and 10 and help email auysal28@students.d125.org. Keep school-only ratings https://forms.gle/AbNvbZHQUVFbspxc7, repeat ratings of other teams, no self-votes, and student average /5 + leader average /15 = /20. Make rewards explicit: everyone gets 1 candy; Blooket top 5 each get 3 EXTRA; a confirmed friend inviter gets 5 EXTRA (one referral per meeting, Oct 9 or 16). Candy rewards stack. Hackathon first place gets $15 TOTAL per team, split equally ($15 solo, $7.50 each for two, $5 each for three). Second place gets 5 candies per member; third gets 3 per member. Personalized award certificates show each recipient’s name and what they won. Use the user-revised Canva certificate, not the superseded template. Include play.blooket.com and explain that leaders display the actual live game code. Preserve the weekly launch links and engagement activities. Keep private staff logistics out of student slides; no invented codes, room/time placeholders, music, or upgrade.

3D Modeling Club Hackathon: Staff Runbook

Open these first

Three-week flow

Friday	Main job	Engagement moment	Blooket leader launch
Oct 9: Imagine	Match teams; choose idea, smallest version, three must-haves; start a blockout	30-second idea pitch	Week 1: 11 questions
Oct 16: Build	Build, help, refine, save and reopen	Two-minute partner swap: one improvement, one question	Week 2: 12 questions
Oct 23: Show	Equal showcase slots; scores; verify winner; celebrate	Share one thing learned; give another team one kind, specific comment	Week 3: 12 questions

Prioritize modeling and every team’s showcase. Use brief games, not all 35 questions. Teams are 1–3; help solo/new students find partners. Optional home work is never required.

Blooket hosting

Student join page: https://play.blooket.com/. Slide 1 has the scan-verified join QR badge on the original robot; slide 9 has the URL and a clickable presenter-note shortcut. Keep the survey/application/submission QR codes intact.
Weekly host links are in the table above and presenter notes on slides 4, 5, and 7. Account: egeuysall; three private sets; free limit 60 players. Do not purchase an upgrade.
Open the week’s link, choose a free mode, test the school network, create a fresh live lobby, and display its real code/QR. No permanent code exists. Keep the game short so modeling and showcases come first.
For the rewarded Blooket round, use identifiable individual nicknames so the top five people can be confirmed. Announce which round counts before starting, record its top five, and award once per person for that round. Do not confuse a shared team nickname with five individual finishers.

Final rewards: candy stacks

Reward	Who receives it	Amount
Club attendance	Every club attendee, including newcomers	1 candy each
Blooket top 5	Each of the top five finishers in the announced rewarded round	+3 candies each
Confirmed friend referral	The inviter, after inviter + newcomer check in with a club leader	+5 candies, one confirmed referral per inviter per meeting (Oct 9 or 16)
Hackathon 1st place	The winning team	$15 total, divided equally
Hackathon 2nd place	Every member of the second-place team	5 candies each
Hackathon 3rd place	Every member of the third-place team	3 candies each
Hackathon award certificate	Each awarded team member	Personalized name + awarded place/achievement

First-place split: 1 member = $15; 2 members = $7.50 each; 3 members = $5 each. It is never $15 per person. This replaces the earlier flat $5-per-person rule.

Candy is additive, not a replacement for attendance candy. Attendance + Blooket = 4; attendance + confirmed referral = 6; both bonuses = 9. Podium candy is a separate award added to any earned club/game/referral candy. The newcomer gets the regular 1 unless they independently qualify for another reward. Track names, confirmed referral pairs, top-five finishers, and distribution to prevent duplicates. Never pressure students to post socially.

Budget: for one rewarded round, plan N attendance candies + 3 × min(5, players) + 5R confirmed-referral candies. On Oct 23 add 5 × second-place team size + 3 × third-place team size (at most 24 podium candies if both teams have 3). Reserve $15 total for first place, and one certificate per awarded member. Follow school food/allergy rules and offer the already planned non-food alternative. Confirm an allowed payout method with the advisor; no purchase or transfer was made here. Candy, Blooket rank, and referrals never affect project judging.

Personalized certificates

User-revised Canva certificate. This is the design the user currently has open and modified; do not overwrite it with the earlier generated design/PDF.
After results are verified, duplicate the master for each awarded member. Replace the sample recipient name with the student’s exact name and include what they won, such as 1st Place, 2nd Place, or 3rd Place: 3D Modeling Club Hackathon, with their team/project if useful. Use October 23, 2026. Keep the user’s revised styling and representative labels.
Proofread each name, place, and team against the verified results before exporting/printing. Do not issue an award before judging or invent recipient names/signatures. Keep the master editable; personalize copies.

Submission checks

School owner: auysal28@students.d125.org. Published, school-only, one response per account. One teammate submits for the team before the October 23 meeting: team/member names, project title, idea/learning, credits, and TeamName_ProjectTitle.blend.

One required file, max 100 MB; total capacity 10 GB. Verify the extension and open the file, since Forms cannot filter only .blend. Pack supported resources, check external dependencies, and reopen. Screenshots are optional, not replacements. For upload/submission trouble, corrected files, or files over 100 MB, students should email auysal28@students.d125.org before the October 23 meeting. Uploaded files cannot be replaced via the edit link; arrange the same private correction/oversize handoff for all teams before the deadline. Written details can be edited.

Real .blend upload/submission tested; test entry and Drive copies cleaned up. Verified receipts and new-response email notifications enabled. Before the showcase, open every file and save a local backup/preview.

Judging: /20

The school-only student rating form collects verified email, own team, rated team/project, a required 1–5 score, a no-self-vote confirmation, and optional kind feedback. Allow repeat submissions so each student can rate every other team. Results are not shared with respondents. The live URL is on slide 8 and clickable in its presenter notes; a separate scan-verified QR image is available.

Review the private ratings sheet: normalize presented team names, check self-votes against the team roster, and keep only the first valid score per email/per rated team. Transfer valid sums/counts to the existing Judging /20 tracker. Leaders still score separately for /15. Do not mix the ratings sheet’s Form Responses 1 with the submission tracker’s Form Responses 1. A real test rating was accepted; the test response and sheet row were removed.

Students rate every OTHER team 1–5. Leaders independently score Creativity, Modeling, and Effort & Learning 1–5 each. Student average /5 + average leader total /15 = final /20. Example: 4 + 13 = 17. Beginners and unfinished work remain eligible; judge demonstrated learning, not guessed hours.

In the tracker’s Judging /20 tab, enter team details, valid student score sum/count, and leader total sum/count. H:J calculate the averages and total. K:L hold learning/creativity averages for ties. Do not overwrite Form Responses 1, which receives submissions automatically. Formula example and zero-vote rejection tested; 50 blank team rows ready.

Paper backup: student ballot = voter ID, own team, rated team, 1–5, helpful comment. Leader card = judge, team, three criterion scores, total /15. Exclude self-votes, duplicates, and invalid scores; competing leaders cannot judge. If a team has no valid student ratings, collect missing ratings before ranking. Keep full precision. Ties: learning average, then creativity, then advisor. Have a second person verify the first-, second-, and third-place teams before announcing prizes; avoid public low-score rankings.

Internet-free mini-rounds

Week	Question	Answer
1	Default Blender G shortcut? / Maximum team size?	Move / 3
2	Strong build order? / Save shortcut?	Main shapes before details / Ctrl+S
3	Maximum final score? / Can students self-vote?	20 / No

Event-day checklist

Assign host/timekeeper, Blender-help lead, and submission/judging lead.
Test devices, projector, Blender version, school network; prepare team cards and paper ballots.
Bring $15 total for first place, budget candy for attendance + Blooket + confirmed referrals + 2nd/3rd place, and prepare personalized certificate copies. Follow school food/allergy rules.
Verify 5Star Code: 04106 for each Friday. Survey is a meeting-day preference poll, not attendance.
Ask the Shadow EBoard form owner to clarify its undated “this Wednesday” wording. Both source forms opened on Oct 4; no responses submitted.
Before Oct 23: acknowledge submissions, test files, back them up, and prepare equal showcase slots.

No meeting room or clock time is needed in these materials. Submission QR codes and original survey/application QR destinations were decoded successfully. Personalized award certificates are part of the prizes. Full earlier runbook/answer bank remains in note version history; this is the concise operating version.