Lowresolutionimage(s)Boringslides /no colorSpeakerspends severalminutes talkingto the title slideExcessiveuse of“um” “uh”etc.Incomprehensiblegraphic (chart,graph, diagram,etc.)Work tiesinto Cancer /CVD / War /COVID-19“That’s aninterestingquestion”Speakerwastes 5minutesexplainingoutline“Topiggybackoff _____’squestion /comment…”Speaker flipsforward pasta slide toofast for youto read itYou haveno ideawhat’sgoing onSpeakerapologizestoaudienceBlatanttypoSleepingprofessor/ studentSomeone takesmore snacksthan they couldever eat atseminarSpeakerexplainssomethingobvious“Beyondthe scopeof thiswork”TechnologymalfunctionDoesn’tstart ontime / goesover timeSomeonecreatesexcessivenoise withtheir snacksSpeaker issurprised bywhat appearson the nextslideRambling /longintroductionof speakerSkipsoverslides tosave timeToo muchtimethankingpeopleSpeaker tellsan “amusingstory” that isnot related tothe subject ofthe seminarSpeakerforgets tothank theirresearchteamSpeakermispronouncessomethingSpeakersucks upto hostprofessorUndefinedabbreviationCellphonegoes offSomeonehas a"question"that's actuallya commentResultsconvenientlyshowimprovementLowresolutionimage(s)Boringslides /no colorSpeakerspends severalminutes talkingto the title slideExcessiveuse of“um” “uh”etc.Incomprehensiblegraphic (chart,graph, diagram,etc.)Work tiesinto Cancer /CVD / War /COVID-19“That’s aninterestingquestion”Speakerwastes 5minutesexplainingoutline“Topiggybackoff _____’squestion /comment…”Speaker flipsforward pasta slide toofast for youto read itYou haveno ideawhat’sgoing onSpeakerapologizestoaudienceBlatanttypoSleepingprofessor/ studentSomeone takesmore snacksthan they couldever eat atseminarSpeakerexplainssomethingobvious“Beyondthe scopeof thiswork”TechnologymalfunctionDoesn’tstart ontime / goesover timeSomeonecreatesexcessivenoise withtheir snacksSpeaker issurprised bywhat appearson the nextslideRambling /longintroductionof speakerSkipsoverslides tosave timeToo muchtimethankingpeopleSpeaker tellsan “amusingstory” that isnot related tothe subject ofthe seminarSpeakerforgets tothank theirresearchteamSpeakermispronouncessomethingSpeakersucks upto hostprofessorUndefinedabbreviationCellphonegoes offSomeonehas a"question"that's actuallya commentResultsconvenientlyshowimprovement

UTA Seminar 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
  1. Low resolution image(s)
  2. Boring slides / no color
  3. Speaker spends several minutes talking to the title slide
  4. Excessive use of “um” “uh” etc.
  5. Incomprehensible graphic (chart, graph, diagram, etc.)
  6. Work ties into Cancer / CVD / War / COVID-19
  7. “That’s an interesting question”
  8. Speaker wastes 5 minutes explaining outline
  9. “To piggyback off _____’s question / comment…”
  10. Speaker flips forward past a slide too fast for you to read it
  11. You have no idea what’s going on
  12. Speaker apologizes to audience
  13. Blatant typo
  14. Sleeping professor / student
  15. Someone takes more snacks than they could ever eat at seminar
  16. Speaker explains something obvious
  17. “Beyond the scope of this work”
  18. Technology malfunction
  19. Doesn’t start on time / goes over time
  20. Someone creates excessive noise with their snacks
  21. Speaker is surprised by what appears on the next slide
  22. Rambling / long introduction of speaker
  23. Skips over slides to save time
  24. Too much time thanking people
  25. Speaker tells an “amusing story” that is not related to the subject of the seminar
  26. Speaker forgets to thank their research team
  27. Speaker mispronounces something
  28. Speaker sucks up to host professor
  29. Undefined abbreviation
  30. Cell phone goes off
  31. Someone has a "question" that's actually a comment
  32. Results conveniently show improvement