Venue-providedAV breaksSame pineeds to berebootedmultipletimesKit robot istoo big forstartingsizeMusic stopsplaying andno onenoticesSpeakertakes toolong atawardsSomeone fallsoff achair/bleachersRyangetsdistractedAutomaticWindowsupdatebreaks thingsMicrophonesnaps,cracklesand popsStudentleavesfield mid-matchTeam forgetsto connectbattery, turnon robot, orstart programTMAudiobugsInexplicableTournamentManagerproblemRyansummonsJohn overloudspeakerTeamcontinues todrive afterbuzzersoundsSomeonehas to callDillonRyan or Johndescribesrobottroubleshootingover the micRobot builtthe nightbefore theeventPhilip’strackballfalls outRobotwith <4wheelsAwardwinnersaccidentallyrevealedearlyRefs chasegame objectsthat leavethe field“I need asingle studentrepresentativefrom eachteam”Someonewalks infront of theprojectorRyan andJohnswitchrolesRobotparts lefton fieldRobotthrowsgameelements“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Robotgets stuckon fieldpegsSomeoneother thanRyan or Johnhead refsMatchno-showWaterspilledon fieldMatchstarts 10+minutesearlyAdultupset atevent staffPapertestTM opmissesmatchcountdownSister teams inthe same matchaccidentallyswitchcontrollersTMlagsScoringtablelosespower“Is there apracticefield?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesLast minuterobotbatteryswapAdultcryingMexicanfood fordinnerVenueinternetblockssomethingTwo teamsfrom the sameorg playtogether in thefinalsTeam withno licenseplatesCoachswearingRef closelyexaminesfieldelements orrobot“Whatmatch arewe on?”Adultworkingon robotVolunteersstay inhotel withteam(s)Childrensteppingon a fieldDroppedcontrollerNo staff atscoringtableAdultwon’t letthe kidstalkMatchstarts tooearlyTeam setsup onwrongfield“Is theskills fieldopen?”Someonetrips overa cableScorekeeperdistracted byphone / foodMatchstarts 10+minuteslateTeamstealsfieldelementsTeamforgetsnotebookMultipleteams withidenticalnamesWindowssystemsoundsover PATie forfirst infinalsRefsearchesQ&AHelicoptercoachNetworkingproblemsMemeonrobotRobotBreaksTeamarrives 4+matchesearlyAdult asksrefsquestionsafter beingtold not toPi hasto beresetToddgoesmissingMatchsequencebreakSomeone saysVia isn’tworking but isjust looking atthe wrong event“Whydidn’t wewin [awardx]?”PrintermisbehavesTeam saysthey’re ready,then reachesin to adjustrobotRyan hasa “word ofthe day”Ryan getsirritated andshuts offmic to ventMatchDQ<50% ofteamspost skillsrunsParentasks howrankingsworkVenueroofleaksEntireteam intearsMemeonrobotTeambrakes afieldelementEveryteamposts askills runAudiencecheers athead refrulingEvent winnerdeterminedby matchstop timeHead refand MC arethe samepersonPhilipdevises“creative”technicalsolutionVenue-providedAV breaksSame pineeds to berebootedmultipletimesKit robot istoo big forstartingsizeMusic stopsplaying andno onenoticesSpeakertakes toolong atawardsSomeone fallsoff achair/bleachersRyangetsdistractedAutomaticWindowsupdatebreaks thingsMicrophonesnaps,cracklesand popsStudentleavesfield mid-matchTeam forgetsto connectbattery, turnon robot, orstart programTMAudiobugsInexplicableTournamentManagerproblemRyansummonsJohn overloudspeakerTeamcontinues todrive afterbuzzersoundsSomeonehas to callDillonRyan or Johndescribesrobottroubleshootingover the micRobot builtthe nightbefore theeventPhilip’strackballfalls outRobotwith <4wheelsAwardwinnersaccidentallyrevealedearlyRefs chasegame objectsthat leavethe field“I need asingle studentrepresentativefrom eachteam”Someonewalks infront of theprojectorRyan andJohnswitchrolesRobotparts lefton fieldRobotthrowsgameelements“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Robotgets stuckon fieldpegsSomeoneother thanRyan or Johnhead refsMatchno-showWaterspilledon fieldMatchstarts 10+minutesearlyAdultupset atevent staffPapertestTM opmissesmatchcountdownSister teams inthe same matchaccidentallyswitchcontrollersTMlagsScoringtablelosespower“Is there apracticefield?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesLast minuterobotbatteryswapAdultcryingMexicanfood fordinnerVenueinternetblockssomethingTwo teamsfrom the sameorg playtogether in thefinalsTeam withno licenseplatesCoachswearingRef closelyexaminesfieldelements orrobot“Whatmatch arewe on?”Adultworkingon robotVolunteersstay inhotel withteam(s)Childrensteppingon a fieldDroppedcontrollerNo staff atscoringtableAdultwon’t letthe kidstalkMatchstarts tooearlyTeam setsup onwrongfield“Is theskills fieldopen?”Someonetrips overa cableScorekeeperdistracted byphone / foodMatchstarts 10+minuteslateTeamstealsfieldelementsTeamforgetsnotebookMultipleteams withidenticalnamesWindowssystemsoundsover PATie forfirst infinalsRefsearchesQ&AHelicoptercoachNetworkingproblemsMemeonrobotRobotBreaksTeamarrives 4+matchesearlyAdult asksrefsquestionsafter beingtold not toPi hasto beresetToddgoesmissingMatchsequencebreakSomeone saysVia isn’tworking but isjust looking atthe wrong event“Whydidn’t wewin [awardx]?”PrintermisbehavesTeam saysthey’re ready,then reachesin to adjustrobotRyan hasa “word ofthe day”Ryan getsirritated andshuts offmic to ventMatchDQ<50% ofteamspost skillsrunsParentasks howrankingsworkVenueroofleaksEntireteam intearsMemeonrobotTeambrakes afieldelementEveryteamposts askills runAudiencecheers athead refrulingEvent winnerdeterminedby matchstop timeHead refand MC arethe samepersonPhilipdevises“creative”technicalsolution

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