Someonetrips overa cableTeam setsup onwrongfieldMatchsequencebreakTMlagsRobotthrowsgameelementsMatchno-showPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesRyan andJohnswitchrolesMatchstarts tooearlyRyan hasa “word ofthe day”Everyteamposts askills runTeamarrives 4+matchesearlyLast minuterobotbatteryswapTwo teamsfrom the sameorg playtogether in thefinalsWaterspilledon fieldCoachswearingTeamstealsfieldelementsMicrophonesnaps,cracklesand popsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingTeam withno licenseplatesAdultwon’t letthe kidstalkSomeonewalks infront of theprojectorPhilipdevises“creative”technicalsolution“When dowe get ournotebooksback?”Ryan or Johndescribesrobottroubleshootingover the micMatchstarts 10+minuteslate“Is theskills fieldopen?”No staff atscoringtableMultipleteams withidenticalnamesTM opmissesmatchcountdownTeamcontinues todrive afterbuzzersoundsTeam saysthey’re ready,then reachesin to adjustrobotRobotparts lefton fieldAdult asksrefsquestionsafter beingtold not toAdultworkingon robot“Have youprinted thematchschedule?”PapertestStudentleavesfield mid-matchScorekeeperdistracted byphone / foodAutomaticWindowsupdatebreaks things“I need asingle studentrepresentativefrom eachteam”VenueroofleaksSomeoneother thanRyan or Johnhead refsMusic stopsplaying andno onenoticesSister teams inthe same matchaccidentallyswitchcontrollersTMAudiobugsRyangetsdistracted<50% ofteamspost skillsrunsPhilip’strackballfalls out“Whydidn’t wewin [awardx]?”“Is there apracticefield?”RyansummonsJohn overloudspeakerToddgoesmissingHead refand MC arethe samepersonChildrensteppingon a fieldMexicanfood fordinnerTeamforgetsnotebookSomeonehas to callDillonRef closelyexaminesfieldelements orrobotRobotwith <4wheelsEntireteam intearsVenue-providedAV breaksParentasks howrankingsworkRobot builtthe nightbefore theeventVenueinternetblockssomethingMemeonrobotRyan getsirritated andshuts offmic to ventTeambrakes afieldelementSpeakertakes toolong atawardsAdultcryingInexplicableTournamentManagerproblemRobotgets stuckon fieldpegsSomeone saysVia isn’tworking but isjust looking atthe wrong eventScoringtablelosespowerSomeone fallsoff achair/bleachersWindowssystemsoundsover PA“Whatmatch arewe on?”PrintermisbehavesRefs chasegame objectsthat leavethe fieldTeam forgetsto connectbattery, turnon robot, orstart programMatchstarts 10+minutesearlyMemeonrobotAdultupset atevent staffDroppedcontrollerRefsearchesQ&ASame pineeds to berebootedmultipletimesRobotBreaksVolunteersstay inhotel withteam(s)Kit robot istoo big forstartingsizeEvent winnerdeterminedby matchstop timeMatchDQTie forfirst infinalsHelicoptercoachPi hasto beresetNetworkingproblemsSomeonetrips overa cableTeam setsup onwrongfieldMatchsequencebreakTMlagsRobotthrowsgameelementsMatchno-showPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesRyan andJohnswitchrolesMatchstarts tooearlyRyan hasa “word ofthe day”Everyteamposts askills runTeamarrives 4+matchesearlyLast minuterobotbatteryswapTwo teamsfrom the sameorg playtogether in thefinalsWaterspilledon fieldCoachswearingTeamstealsfieldelementsMicrophonesnaps,cracklesand popsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingTeam withno licenseplatesAdultwon’t letthe kidstalkSomeonewalks infront of theprojectorPhilipdevises“creative”technicalsolution“When dowe get ournotebooksback?”Ryan or Johndescribesrobottroubleshootingover the micMatchstarts 10+minuteslate“Is theskills fieldopen?”No staff atscoringtableMultipleteams withidenticalnamesTM opmissesmatchcountdownTeamcontinues todrive afterbuzzersoundsTeam saysthey’re ready,then reachesin to adjustrobotRobotparts lefton fieldAdult asksrefsquestionsafter beingtold not toAdultworkingon robot“Have youprinted thematchschedule?”PapertestStudentleavesfield mid-matchScorekeeperdistracted byphone / foodAutomaticWindowsupdatebreaks things“I need asingle studentrepresentativefrom eachteam”VenueroofleaksSomeoneother thanRyan or Johnhead refsMusic stopsplaying andno onenoticesSister teams inthe same matchaccidentallyswitchcontrollersTMAudiobugsRyangetsdistracted<50% ofteamspost skillsrunsPhilip’strackballfalls out“Whydidn’t wewin [awardx]?”“Is there apracticefield?”RyansummonsJohn overloudspeakerToddgoesmissingHead refand MC arethe samepersonChildrensteppingon a fieldMexicanfood fordinnerTeamforgetsnotebookSomeonehas to callDillonRef closelyexaminesfieldelements orrobotRobotwith <4wheelsEntireteam intearsVenue-providedAV breaksParentasks howrankingsworkRobot builtthe nightbefore theeventVenueinternetblockssomethingMemeonrobotRyan getsirritated andshuts offmic to ventTeambrakes afieldelementSpeakertakes toolong atawardsAdultcryingInexplicableTournamentManagerproblemRobotgets stuckon fieldpegsSomeone saysVia isn’tworking but isjust looking atthe wrong eventScoringtablelosespowerSomeone fallsoff achair/bleachersWindowssystemsoundsover PA“Whatmatch arewe on?”PrintermisbehavesRefs chasegame objectsthat leavethe fieldTeam forgetsto connectbattery, turnon robot, orstart programMatchstarts 10+minutesearlyMemeonrobotAdultupset atevent staffDroppedcontrollerRefsearchesQ&ASame pineeds to berebootedmultipletimesRobotBreaksVolunteersstay inhotel withteam(s)Kit robot istoo big forstartingsizeEvent winnerdeterminedby matchstop timeMatchDQTie forfirst infinalsHelicoptercoachPi hasto beresetNetworkingproblems

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