Ref closelyexaminesfieldelements orrobotRefsearchesQ&ATwo teamsfrom the sameorg playtogether in thefinalsRobotwith <4wheelsSomeoneother thanRyan or Johnhead refsRyan andJohnswitchrolesRobot builtthe nightbefore theeventTeamstealsfieldelementsAdultcryingVenueroofleaksMatchstarts 10+minuteslateMultipleteams withidenticalnamesChildrensteppingon a fieldPhilip’strackballfalls out“Whatmatch arewe on?”Audiencecheers athead refrulingSpeakertakes toolong atawardsRobotparts lefton fieldTeamforgetsnotebookAdultwon’t letthe kidstalkRyan getsirritated andshuts offmic to ventVenueinternetblockssomethingWaterspilledon fieldLast minuterobotbatteryswapWindowssystemsoundsover PAEvent winnerdeterminedby matchstop timeHead refand MC arethe sameperson“When dowe get ournotebooksback?”Pi hasto beresetRobotgets stuckon fieldpegsSister teams inthe same matchaccidentallyswitchcontrollersAdult asksrefsquestionsafter beingtold not toEntireteam intearsRyangetsdistractedTeambrakes afieldelementAdultupset atevent staffMatchsequencebreakTeamarrives 4+matchesearlySomeone saysVia isn’tworking but isjust looking atthe wrong eventInexplicableTournamentManagerproblemTie forfirst infinalsVenue-providedAV breaksMatchDQSomeonewalks infront of theprojectorMicrophonesnaps,cracklesand popsRyan hasa “word ofthe day”“Is theskills fieldopen?”Someone fallsoff achair/bleachersMusic stopsplaying andno onenoticesParentasks howrankingsworkMexicanfood fordinnerAdultworkingon robotTMlagsTeam saysthey’re ready,then reachesin to adjustrobotMemeonrobot“Whydidn’t wewin [awardx]?”RyansummonsJohn overloudspeakerMatchstarts 10+minutesearlyTeam setsup onwrongfieldPrintermisbehavesNo staff atscoringtable“Is there apracticefield?”Matchstarts tooearlyTeam forgetsto connectbattery, turnon robot, orstart programPapertestAutomaticWindowsupdatebreaks thingsTM opmissesmatchcountdown“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe field<50% ofteamspost skillsrunsHelicoptercoachTMAudiobugsDroppedcontrollerNetworkingproblemsKit robot istoo big forstartingsizeStudentleavesfield mid-matchPhilipdevises“creative”technicalsolutionSame pineeds to berebootedmultipletimesTeamcontinues todrive afterbuzzersoundsEveryteamposts askills runSomeonehas to callDillonVolunteersstay inhotel withteam(s)Team withno licenseplatesScoringtablelosespowerScorekeeperdistracted byphone / foodPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSomeonetrips overa cableAwardwinnersaccidentallyrevealedearlyToddgoesmissingRyan or Johndescribesrobottroubleshootingover the micRobotBreaksCoachswearingRobotthrowsgameelementsMatchno-show“I need asingle studentrepresentativefrom eachteam”MemeonrobotRef closelyexaminesfieldelements orrobotRefsearchesQ&ATwo teamsfrom the sameorg playtogether in thefinalsRobotwith <4wheelsSomeoneother thanRyan or Johnhead refsRyan andJohnswitchrolesRobot builtthe nightbefore theeventTeamstealsfieldelementsAdultcryingVenueroofleaksMatchstarts 10+minuteslateMultipleteams withidenticalnamesChildrensteppingon a fieldPhilip’strackballfalls out“Whatmatch arewe on?”Audiencecheers athead refrulingSpeakertakes toolong atawardsRobotparts lefton fieldTeamforgetsnotebookAdultwon’t letthe kidstalkRyan getsirritated andshuts offmic to ventVenueinternetblockssomethingWaterspilledon fieldLast minuterobotbatteryswapWindowssystemsoundsover PAEvent winnerdeterminedby matchstop timeHead refand MC arethe sameperson“When dowe get ournotebooksback?”Pi hasto beresetRobotgets stuckon fieldpegsSister teams inthe same matchaccidentallyswitchcontrollersAdult asksrefsquestionsafter beingtold not toEntireteam intearsRyangetsdistractedTeambrakes afieldelementAdultupset atevent staffMatchsequencebreakTeamarrives 4+matchesearlySomeone saysVia isn’tworking but isjust looking atthe wrong eventInexplicableTournamentManagerproblemTie forfirst infinalsVenue-providedAV breaksMatchDQSomeonewalks infront of theprojectorMicrophonesnaps,cracklesand popsRyan hasa “word ofthe day”“Is theskills fieldopen?”Someone fallsoff achair/bleachersMusic stopsplaying andno onenoticesParentasks howrankingsworkMexicanfood fordinnerAdultworkingon robotTMlagsTeam saysthey’re ready,then reachesin to adjustrobotMemeonrobot“Whydidn’t wewin [awardx]?”RyansummonsJohn overloudspeakerMatchstarts 10+minutesearlyTeam setsup onwrongfieldPrintermisbehavesNo staff atscoringtable“Is there apracticefield?”Matchstarts tooearlyTeam forgetsto connectbattery, turnon robot, orstart programPapertestAutomaticWindowsupdatebreaks thingsTM opmissesmatchcountdown“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe field<50% ofteamspost skillsrunsHelicoptercoachTMAudiobugsDroppedcontrollerNetworkingproblemsKit robot istoo big forstartingsizeStudentleavesfield mid-matchPhilipdevises“creative”technicalsolutionSame pineeds to berebootedmultipletimesTeamcontinues todrive afterbuzzersoundsEveryteamposts askills runSomeonehas to callDillonVolunteersstay inhotel withteam(s)Team withno licenseplatesScoringtablelosespowerScorekeeperdistracted byphone / foodPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSomeonetrips overa cableAwardwinnersaccidentallyrevealedearlyToddgoesmissingRyan or Johndescribesrobottroubleshootingover the micRobotBreaksCoachswearingRobotthrowsgameelementsMatchno-show“I need asingle studentrepresentativefrom eachteam”Memeonrobot

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