Robotparts lefton fieldVenueinternetblockssomethingTeam forgetsto connectbattery, turnon robot, orstart program“Is there apracticefield?”VenueroofleaksNo staff atscoringtableMatchsequencebreakMemeonrobotParentasks howrankingsworkSpeakertakes toolong atawardsMultipleteams withidenticalnamesAdultwon’t letthe kidstalkWindowssystemsoundsover PATMlagsTie forfirst infinalsVenue-providedAV breaksRyan or Johndescribesrobottroubleshootingover the micAwardwinnersaccidentallyrevealedearlyTeamstealsfieldelementsEntireteam intearsTeam withno licenseplatesRyan getsirritated andshuts offmic to ventEvent winnerdeterminedby matchstop timeAdultupset atevent staffPhilipdevises“creative”technicalsolutionSomeone fallsoff achair/bleachersRyansummonsJohn overloudspeaker<50% ofteamspost skillsrunsToddgoesmissingMexicanfood fordinnerAutomaticWindowsupdatebreaks thingsMusic stopsplaying andno onenoticesStudentleavesfield mid-matchTeamcontinues todrive afterbuzzersoundsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficulties“Whydidn’t wewin [awardx]?”Ref closelyexaminesfieldelements orrobotCoachswearingNetworkingproblemsRobotBreaksSomeonehas to callDillonEveryteamposts askills runRyan hasa “word ofthe day”Refs chasegame objectsthat leavethe fieldVolunteersstay inhotel withteam(s)Same pineeds to berebootedmultipletimes“Whatmatch arewe on?”TM opmissesmatchcountdownRyan andJohnswitchrolesTwo teamsfrom the sameorg playtogether in thefinalsAdultworkingon robotRobot builtthe nightbefore theeventSomeoneother thanRyan or Johnhead refsHead refand MC arethe samepersonSomeonetrips overa cableMatchstarts 10+minuteslateTeam saysthey’re ready,then reachesin to adjustrobotKit robot istoo big forstartingsizeScorekeeperdistracted byphone / foodTeambrakes afieldelementMatchstarts 10+minutesearlySister teams inthe same matchaccidentallyswitchcontrollersAdult asksrefsquestionsafter beingtold not toRobotgets stuckon fieldpegs“I need asingle studentrepresentativefrom eachteam”“When dowe get ournotebooksback?”AdultcryingMemeonrobotRefsearchesQ&APrintermisbehavesMatchno-showTeamarrives 4+matchesearlyHelicoptercoachRobotwith <4wheelsWaterspilledon fieldMatchstarts tooearlyRobotthrowsgameelementsPi hasto beresetLast minuterobotbatteryswapPhilip’strackballfalls outRyangetsdistractedMicrophonesnaps,cracklesand popsSomeonewalks infront of theprojectorInexplicableTournamentManagerproblemSomeone saysVia isn’tworking but isjust looking atthe wrong event“Is theskills fieldopen?”Team setsup onwrongfield“Have youprinted thematchschedule?”TMAudiobugsMatchDQScoringtablelosespowerDroppedcontrollerPapertestChildrensteppingon a fieldTeamforgetsnotebookAudiencecheers athead refrulingRobotparts lefton fieldVenueinternetblockssomethingTeam forgetsto connectbattery, turnon robot, orstart program“Is there apracticefield?”VenueroofleaksNo staff atscoringtableMatchsequencebreakMemeonrobotParentasks howrankingsworkSpeakertakes toolong atawardsMultipleteams withidenticalnamesAdultwon’t letthe kidstalkWindowssystemsoundsover PATMlagsTie forfirst infinalsVenue-providedAV breaksRyan or Johndescribesrobottroubleshootingover the micAwardwinnersaccidentallyrevealedearlyTeamstealsfieldelementsEntireteam intearsTeam withno licenseplatesRyan getsirritated andshuts offmic to ventEvent winnerdeterminedby matchstop timeAdultupset atevent staffPhilipdevises“creative”technicalsolutionSomeone fallsoff achair/bleachersRyansummonsJohn overloudspeaker<50% ofteamspost skillsrunsToddgoesmissingMexicanfood fordinnerAutomaticWindowsupdatebreaks thingsMusic stopsplaying andno onenoticesStudentleavesfield mid-matchTeamcontinues todrive afterbuzzersoundsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficulties“Whydidn’t wewin [awardx]?”Ref closelyexaminesfieldelements orrobotCoachswearingNetworkingproblemsRobotBreaksSomeonehas to callDillonEveryteamposts askills runRyan hasa “word ofthe day”Refs chasegame objectsthat leavethe fieldVolunteersstay inhotel withteam(s)Same pineeds to berebootedmultipletimes“Whatmatch arewe on?”TM opmissesmatchcountdownRyan andJohnswitchrolesTwo teamsfrom the sameorg playtogether in thefinalsAdultworkingon robotRobot builtthe nightbefore theeventSomeoneother thanRyan or Johnhead refsHead refand MC arethe samepersonSomeonetrips overa cableMatchstarts 10+minuteslateTeam saysthey’re ready,then reachesin to adjustrobotKit robot istoo big forstartingsizeScorekeeperdistracted byphone / foodTeambrakes afieldelementMatchstarts 10+minutesearlySister teams inthe same matchaccidentallyswitchcontrollersAdult asksrefsquestionsafter beingtold not toRobotgets stuckon fieldpegs“I need asingle studentrepresentativefrom eachteam”“When dowe get ournotebooksback?”AdultcryingMemeonrobotRefsearchesQ&APrintermisbehavesMatchno-showTeamarrives 4+matchesearlyHelicoptercoachRobotwith <4wheelsWaterspilledon fieldMatchstarts tooearlyRobotthrowsgameelementsPi hasto beresetLast minuterobotbatteryswapPhilip’strackballfalls outRyangetsdistractedMicrophonesnaps,cracklesand popsSomeonewalks infront of theprojectorInexplicableTournamentManagerproblemSomeone saysVia isn’tworking but isjust looking atthe wrong event“Is theskills fieldopen?”Team setsup onwrongfield“Have youprinted thematchschedule?”TMAudiobugsMatchDQScoringtablelosespowerDroppedcontrollerPapertestChildrensteppingon a fieldTeamforgetsnotebookAudiencecheers athead refruling

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