Someoneassigns anaction itemto a studentORB caused bymiscommunicationAn FDblames an“FC” insteadofthemselvesORB causedbycompletelydisregardingprocedureSean asks aquestion with anobvious answerthat leaves theroom speechlessAn FDbrutallycriticizessomeoneSomeonesends anout of officeemail“BadTechnicalInput”An ORBgoes fortwice as longas scheduledAn ORB withno actualeffect on thespacecraftAn ORBcaused by asimplesyntax errorFunnyringtonegoes offSean callspeople whoare glutenfree “special”Sean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskORB causedby blindlyexecuting amanprocThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonegetspagedImpossibleaction itemsuggestedAn ORBcaused bybad versioncontrolSomeonefallsasleepSomeonementions a bestpracticesdocument thatno one knowsexistsSean suggeststakingsomethingoffline that weall know won’tbeA CCITasks for asignatureSomeonepronouncesa CC’sname wrongSomeonebrings upstudentprankingMAVENishappyA CC makesa suggestthat getscompletelyshut downORBcaused byOASIS-PSblack magicSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong fileSomeonetalks about“the thoughtprocess”ORB causedby ignoringcheckproductsoutputPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB caused byonly one personknowing how toperform a task3 or moretotallyundefinedacronyms usedon a singleslide“PersonnelError”3 or morespellingmistakes inone slideSomeoneassigns anaction itemto a studentORB caused bymiscommunicationAn FDblames an“FC” insteadofthemselvesORB causedbycompletelydisregardingprocedureSean asks aquestion with anobvious answerthat leaves theroom speechlessAn FDbrutallycriticizessomeoneSomeonesends anout of officeemail“BadTechnicalInput”An ORBgoes fortwice as longas scheduledAn ORB withno actualeffect on thespacecraftAn ORBcaused by asimplesyntax errorFunnyringtonegoes offSean callspeople whoare glutenfree “special”Sean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskORB causedby blindlyexecuting amanprocThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonegetspagedImpossibleaction itemsuggestedAn ORBcaused bybad versioncontrolSomeonefallsasleepSomeonementions a bestpracticesdocument thatno one knowsexistsSean suggeststakingsomethingoffline that weall know won’tbeA CCITasks for asignatureSomeonepronouncesa CC’sname wrongSomeonebrings upstudentprankingMAVENishappyA CC makesa suggestthat getscompletelyshut downORBcaused byOASIS-PSblack magicSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong fileSomeonetalks about“the thoughtprocess”ORB causedby ignoringcheckproductsoutputPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB caused byonly one personknowing how toperform a task3 or moretotallyundefinedacronyms usedon a singleslide“PersonnelError”3 or morespellingmistakes inone slide

ORB DAY BINGO 2018 - 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
  1. Someone assigns an action item to a student
  2. ORB caused by miscommunication
  3. An FD blames an “FC” instead of themselves
  4. ORB caused by completely disregarding procedure
  5. Sean asks a question with an obvious answer that leaves the room speechless
  6. An FD brutally criticizes someone
  7. Someone sends an out of office email
  8. “Bad Technical Input”
  9. An ORB goes for twice as long as scheduled
  10. An ORB with no actual effect on the spacecraft
  11. An ORB caused by a simple syntax error
  12. Funny ringtone goes off
  13. Sean calls people who are gluten free “special”
  14. Sean says ORBs increase at the beginning of the semester
  15. ORB caused by FC doing a CC task
  16. ORB caused by blindly executing a manproc
  17. There’s a TDRS with one ‘S’ and one with two ‘S’s in the same ORB
  18. Someone gets paged
  19. Impossible action item suggested
  20. An ORB caused by bad version control
  21. Someone falls asleep
  22. Someone mentions a best practices document that no one knows exists
  23. Sean suggests taking something offline that we all know won’t be
  24. A CCIT asks for a signature
  25. Someone pronounces a CC’s name wrong
  26. Someone brings up student pranking
  27. MAVEN is happy
  28. A CC makes a suggest that gets completely shut down
  29. ORB caused by OASIS-PS black magic
  30. Someone complains about not having enough coffee
  31. An ORB caused by using the wrong file
  32. Someone talks about “the thought process”
  33. ORB caused by ignoring check products output
  34. Pat starts talking about BDM and no one understands what he’s saying except for Gina and Robby and now Ross and Reidar
  35. ORB caused by only one person knowing how to perform a task
  36. 3 or more totally undefined acronyms used on a single slide
  37. “Personnel Error”
  38. 3 or more spelling mistakes in one slide