Ryan andJohnswitchrolesMusic stopsplaying andno onenoticesSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultupset atevent staffNetworkingproblemsPrintermisbehavesTM opmissesmatchcountdownInexplicableTournamentManagerproblemSomeonewalks infront of theprojectorPhilipdevises“creative”technicalsolutionTwo teamsfrom the sameorg playtogether in thefinalsRyansummonsJohn overloudspeakerPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesKit robot istoo big forstartingsizeTeam saysthey’re ready,then reachesin to adjustrobotRef closelyexaminesfieldelements orrobotRyan hasa “word ofthe day”CoachswearingTeam withno licenseplatesRobotgets stuckon fieldpegsMemeonrobotTMlagsEvent winnerdeterminedby matchstop timePhilip’strackballfalls outMatchsequencebreakRyangetsdistractedRefs chasegame objectsthat leavethe fieldSomeoneother thanRyan or Johnhead refs“Have youprinted thematchschedule?”Adult asksrefsquestionsafter beingtold not toStudentleavesfield mid-match“Is theskills fieldopen?”TeamstealsfieldelementsTeamforgetsnotebookLast minuterobotbatteryswapRefsearchesQ&ADroppedcontrollerRobotwith <4wheelsAwardwinnersaccidentallyrevealedearlyToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersMatchstarts 10+minuteslateMicrophonesnaps,cracklesand popsVenueroofleaks“Whydidn’t wewin [awardx]?”Multipleteams withidenticalnamesHelicoptercoachRobotthrowsgameelementsAdultcryingVolunteersstay inhotel withteam(s)Ryan getsirritated andshuts offmic to ventTeamarrives 4+matchesearlyScoringtablelosespowerMatchDQMatchstarts tooearlyTMAudiobugsMexicanfood fordinnerAdultwon’t letthe kidstalkSomeone fallsoff achair/bleachersTeambrakes afieldelementScorekeeperdistracted byphone / foodEntireteam intearsAdultworkingon robotRobotparts lefton fieldSpeakertakes toolong atawardsVenueinternetblockssomething“Is there apracticefield?”Matchno-showWindowssystemsoundsover PATeam forgetsto connectbattery, turnon robot, orstart programRobot builtthe nightbefore theevent“When dowe get ournotebooksback?”Matchstarts 10+minutesearlyAutomaticWindowsupdatebreaks things“Whatmatch arewe on?”Audiencecheers athead refrulingPapertestChildrensteppingon a fieldParentasks howrankingsworkWaterspilledon fieldSomeonetrips overa cableTeamcontinues todrive afterbuzzersoundsPi hasto beresetTeam setsup onwrongfieldRyan or Johndescribesrobottroubleshootingover the micEveryteamposts askills run“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonTie forfirst infinals<50% ofteamspost skillsrunsSomeonehas to callDillonSame pineeds to berebootedmultipletimesRobotBreaksVenue-providedAV breaksNo staff atscoringtableMemeonrobotRyan andJohnswitchrolesMusic stopsplaying andno onenoticesSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultupset atevent staffNetworkingproblemsPrintermisbehavesTM opmissesmatchcountdownInexplicableTournamentManagerproblemSomeonewalks infront of theprojectorPhilipdevises“creative”technicalsolutionTwo teamsfrom the sameorg playtogether in thefinalsRyansummonsJohn overloudspeakerPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesKit robot istoo big forstartingsizeTeam saysthey’re ready,then reachesin to adjustrobotRef closelyexaminesfieldelements orrobotRyan hasa “word ofthe day”CoachswearingTeam withno licenseplatesRobotgets stuckon fieldpegsMemeonrobotTMlagsEvent winnerdeterminedby matchstop timePhilip’strackballfalls outMatchsequencebreakRyangetsdistractedRefs chasegame objectsthat leavethe fieldSomeoneother thanRyan or Johnhead refs“Have youprinted thematchschedule?”Adult asksrefsquestionsafter beingtold not toStudentleavesfield mid-match“Is theskills fieldopen?”TeamstealsfieldelementsTeamforgetsnotebookLast minuterobotbatteryswapRefsearchesQ&ADroppedcontrollerRobotwith <4wheelsAwardwinnersaccidentallyrevealedearlyToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersMatchstarts 10+minuteslateMicrophonesnaps,cracklesand popsVenueroofleaks“Whydidn’t wewin [awardx]?”Multipleteams withidenticalnamesHelicoptercoachRobotthrowsgameelementsAdultcryingVolunteersstay inhotel withteam(s)Ryan getsirritated andshuts offmic to ventTeamarrives 4+matchesearlyScoringtablelosespowerMatchDQMatchstarts tooearlyTMAudiobugsMexicanfood fordinnerAdultwon’t letthe kidstalkSomeone fallsoff achair/bleachersTeambrakes afieldelementScorekeeperdistracted byphone / foodEntireteam intearsAdultworkingon robotRobotparts lefton fieldSpeakertakes toolong atawardsVenueinternetblockssomething“Is there apracticefield?”Matchno-showWindowssystemsoundsover PATeam forgetsto connectbattery, turnon robot, orstart programRobot builtthe nightbefore theevent“When dowe get ournotebooksback?”Matchstarts 10+minutesearlyAutomaticWindowsupdatebreaks things“Whatmatch arewe on?”Audiencecheers athead refrulingPapertestChildrensteppingon a fieldParentasks howrankingsworkWaterspilledon fieldSomeonetrips overa cableTeamcontinues todrive afterbuzzersoundsPi hasto beresetTeam setsup onwrongfieldRyan or Johndescribesrobottroubleshootingover the micEveryteamposts askills run“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonTie forfirst infinals<50% ofteamspost skillsrunsSomeonehas to callDillonSame pineeds to berebootedmultipletimesRobotBreaksVenue-providedAV breaksNo staff atscoringtableMemeonrobot

VIQC Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
  1. Ryan and John switch roles
  2. Music stops playing and no one notices
  3. Someone says Via isn’t working but is just looking at the wrong event
  4. Adult upset at event staff
  5. Networking problems
  6. Printer misbehaves
  7. TM op misses match countdown
  8. Inexplicable Tournament Manager problem
  9. Someone walks in front of the projector
  10. Philip devises “creative” technical solution
  11. Two teams from the same org play together in the finals
  12. Ryan summons John over loudspeaker
  13. Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
  14. Kit robot is too big for starting size
  15. Team says they’re ready, then reaches in to adjust robot
  16. Ref closely examines field elements or robot
  17. Ryan has a “word of the day”
  18. Coach swearing
  19. Team with no license plates
  20. Robot gets stuck on field pegs
  21. Meme on robot
  22. TM lags
  23. Event winner determined by match stop time
  24. Philip’s trackball falls out
  25. Match sequence break
  26. Ryan gets distracted
  27. Refs chase game objects that leave the field
  28. Someone other than Ryan or John head refs
  29. “Have you printed the match schedule?”
  30. Adult asks refs questions after being told not to
  31. Student leaves field mid-match
  32. “Is the skills field open?”
  33. Team steals field elements
  34. Team forgets notebook
  35. Last minute robot battery swap
  36. Ref searches Q&A
  37. Dropped controller
  38. Robot with <4 wheels
  39. Award winners accidentally revealed early
  40. Todd goes missing
  41. Sister teams in the same match accidentally switch controllers
  42. Match starts 10+ minutes late
  43. Microphone snaps, crackles and pops
  44. Venue roof leaks
  45. “Why didn’t we win [award x]?”
  46. Multiple teams with identical names
  47. Helicopter coach
  48. Robot throws game elements
  49. Adult crying
  50. Volunteers stay in hotel with team(s)
  51. Ryan gets irritated and shuts off mic to vent
  52. Team arrives 4+ matches early
  53. Scoring table loses power
  54. Match DQ
  55. Match starts too early
  56. TM Audio bugs
  57. Mexican food for dinner
  58. Adult won’t let the kids talk
  59. Someone falls off a chair/bleachers
  60. Team brakes a field element
  61. Scorekeeper distracted by phone / food
  62. Entire team in tears
  63. Adult working on robot
  64. Robot parts left on field
  65. Speaker takes too long at awards
  66. Venue internet blocks something
  67. “Is there a practice field?”
  68. Match no-show
  69. Windows system sounds over PA
  70. Team forgets to connect battery, turn on robot, or start program
  71. Robot built the night before the event
  72. “When do we get our notebooks back?”
  73. Match starts 10+ minutes early
  74. Automatic Windows update breaks things
  75. “What match are we on?”
  76. Audience cheers at head ref ruling
  77. Paper test
  78. Children stepping on a field
  79. Parent asks how rankings work
  80. Water spilled on field
  81. Someone trips over a cable
  82. Team continues to drive after buzzer sounds
  83. Pi has to be reset
  84. Team sets up on wrong field
  85. Ryan or John describes robot troubleshooting over the mic
  86. Every team posts a skills run
  87. “I need a single student representative from each team”
  88. Head ref and MC are the same person
  89. Tie for first in finals
  90. <50% of teams post skills runs
  91. Someone has to call Dillon
  92. Same pi needs to be rebooted multiple times
  93. Robot Breaks
  94. Venue-provided AV breaks
  95. No staff at scoring table
  96. Meme on robot