Team withno licenseplatesMatchDQTeamcontinues todrive afterbuzzersoundsSomeonewalks infront of theprojectorScorekeeperdistracted byphone / foodRyan getsirritated andshuts offmic to ventPhilip’strackballfalls outEveryteamposts askills runHelicoptercoachTM opmissesmatchcountdownTeam setsup onwrongfieldScoringtablelosespowerMatchno-showSomeonehas to callDillonMicrophonesnaps,cracklesand popsTeamforgetsnotebookPhilipdevises“creative”technicalsolution“When dowe get ournotebooksback?”Kit robot istoo big forstartingsize“Have youprinted thematchschedule?”Head refand MC arethe samepersonRefsearchesQ&AMatchstarts tooearlyPapertestMatchsequencebreakRobotparts lefton fieldRobotthrowsgameelements“Is there apracticefield?”Tie forfirst infinalsAdultwon’t letthe kidstalkMemeonrobotWindowssystemsoundsover PAChildrensteppingon a fieldRyangetsdistractedMatchstarts 10+minuteslateTeam forgetsto connectbattery, turnon robot, orstart programSpeakertakes toolong atawardsNetworkingproblemsTeamarrives 4+matchesearly“Is theskills fieldopen?”AutomaticWindowsupdatebreaks thingsRobot builtthe nightbefore theeventPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSister teams inthe same matchaccidentallyswitchcontrollersSame pineeds to berebootedmultipletimesVenueinternetblockssomethingEntireteam intearsWaterspilledon fieldPrintermisbehavesTeambrakes afieldelementParentasks howrankingsworkRobotgets stuckon fieldpegsSomeonetrips overa cableTeamstealsfieldelementsStudentleavesfield mid-matchRefs chasegame objectsthat leavethe fieldAwardwinnersaccidentallyrevealedearlyRyansummonsJohn overloudspeakerVolunteersstay inhotel withteam(s)VenueroofleaksAudiencecheers athead refrulingRyan andJohnswitchrolesDroppedcontrollerRef closelyexaminesfieldelements orrobotNo staff atscoringtableSomeone saysVia isn’tworking but isjust looking atthe wrong eventVenue-providedAV breaksRobotwith <4wheels“Whatmatch arewe on?”Someoneother thanRyan or Johnhead refsTMAudiobugsMemeonrobot<50% ofteamspost skillsrunsMatchstarts 10+minutesearlyAdult asksrefsquestionsafter beingtold not toMusic stopsplaying andno onenoticesRyan hasa “word ofthe day”“Whydidn’t wewin [awardx]?”Adultworkingon robotEvent winnerdeterminedby matchstop timeTeam saysthey’re ready,then reachesin to adjustrobotTMlagsLast minuterobotbatteryswapInexplicableTournamentManagerproblemToddgoesmissingAdultupset atevent staffAdultcryingRyan or Johndescribesrobottroubleshootingover the micTwo teamsfrom the sameorg playtogether in thefinalsMexicanfood fordinnerCoachswearing“I need asingle studentrepresentativefrom eachteam”Someone fallsoff achair/bleachersRobotBreaksPi hasto beresetMultipleteams withidenticalnamesTeam withno licenseplatesMatchDQTeamcontinues todrive afterbuzzersoundsSomeonewalks infront of theprojectorScorekeeperdistracted byphone / foodRyan getsirritated andshuts offmic to ventPhilip’strackballfalls outEveryteamposts askills runHelicoptercoachTM opmissesmatchcountdownTeam setsup onwrongfieldScoringtablelosespowerMatchno-showSomeonehas to callDillonMicrophonesnaps,cracklesand popsTeamforgetsnotebookPhilipdevises“creative”technicalsolution“When dowe get ournotebooksback?”Kit robot istoo big forstartingsize“Have youprinted thematchschedule?”Head refand MC arethe samepersonRefsearchesQ&AMatchstarts tooearlyPapertestMatchsequencebreakRobotparts lefton fieldRobotthrowsgameelements“Is there apracticefield?”Tie forfirst infinalsAdultwon’t letthe kidstalkMemeonrobotWindowssystemsoundsover PAChildrensteppingon a fieldRyangetsdistractedMatchstarts 10+minuteslateTeam forgetsto connectbattery, turnon robot, orstart programSpeakertakes toolong atawardsNetworkingproblemsTeamarrives 4+matchesearly“Is theskills fieldopen?”AutomaticWindowsupdatebreaks thingsRobot builtthe nightbefore theeventPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSister teams inthe same matchaccidentallyswitchcontrollersSame pineeds to berebootedmultipletimesVenueinternetblockssomethingEntireteam intearsWaterspilledon fieldPrintermisbehavesTeambrakes afieldelementParentasks howrankingsworkRobotgets stuckon fieldpegsSomeonetrips overa cableTeamstealsfieldelementsStudentleavesfield mid-matchRefs chasegame objectsthat leavethe fieldAwardwinnersaccidentallyrevealedearlyRyansummonsJohn overloudspeakerVolunteersstay inhotel withteam(s)VenueroofleaksAudiencecheers athead refrulingRyan andJohnswitchrolesDroppedcontrollerRef closelyexaminesfieldelements orrobotNo staff atscoringtableSomeone saysVia isn’tworking but isjust looking atthe wrong eventVenue-providedAV breaksRobotwith <4wheels“Whatmatch arewe on?”Someoneother thanRyan or Johnhead refsTMAudiobugsMemeonrobot<50% ofteamspost skillsrunsMatchstarts 10+minutesearlyAdult asksrefsquestionsafter beingtold not toMusic stopsplaying andno onenoticesRyan hasa “word ofthe day”“Whydidn’t wewin [awardx]?”Adultworkingon robotEvent winnerdeterminedby matchstop timeTeam saysthey’re ready,then reachesin to adjustrobotTMlagsLast minuterobotbatteryswapInexplicableTournamentManagerproblemToddgoesmissingAdultupset atevent staffAdultcryingRyan or Johndescribesrobottroubleshootingover the micTwo teamsfrom the sameorg playtogether in thefinalsMexicanfood fordinnerCoachswearing“I need asingle studentrepresentativefrom eachteam”Someone fallsoff achair/bleachersRobotBreaksPi hasto beresetMultipleteams withidenticalnames

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