3 or moretotallyundefinedacronyms usedon a singleslide,An ORBgoes fortwice as longasscheduled,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,Someonegetspaged,3 or morespellingmistakes inone slide,“BadTechnicalInput”,Funnyringtonegoes off,ORB caused bymiscommunication,Someonepronouncesa CC’s namewrong,Someonecomplainsabout nothavingenough coffeeSean suggeststakingsomethingoffline that weall know won’tbe,Someonebrings upstudentpranking,ORBcaused byFC doinga CC task,ORB causedbycompletelydisregardingprocedure,An ORBcaused byusing thewrong file,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,ORB caused byonly one personknowing how toperform a task,“PersonnelError”,An ORBcaused by asimplesyntax error,A CC makesa suggestthat getscompletelyshut down,MAVENishappy,An FDbrutallycriticizessomeone,ORB causedby OASIS-PS blackmagic,Someonefallsasleep,Someonementions a bestpracticesdocument thatno one knowsexists,Sean callspeople whoare glutenfree“special”,Sean saysORBs increaseat thebeginning ofthe semester,Someoneassigns anaction itemto a student,An ORBcaused bybad versioncontrol,Sean asks aquestion with anobvious answerthat leaves theroom speechless,An ORB withno actualeffect on thespacecraft,ORB causedby ignoringcheckproductsoutput,A CCITasks for asignature,Someonetalks about“the thoughtprocess”,Impossibleaction itemsuggested,Someonesends anout of officeemail,An FDblames an“FC” insteadofthemselves,ORB causedby blindlyexecuting amanproc,3 or moretotallyundefinedacronyms usedon a singleslide,An ORBgoes fortwice as longasscheduled,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,Someonegetspaged,3 or morespellingmistakes inone slide,“BadTechnicalInput”,Funnyringtonegoes off,ORB caused bymiscommunication,Someonepronouncesa CC’s namewrong,Someonecomplainsabout nothavingenough coffeeSean suggeststakingsomethingoffline that weall know won’tbe,Someonebrings upstudentpranking,ORBcaused byFC doinga CC task,ORB causedbycompletelydisregardingprocedure,An ORBcaused byusing thewrong file,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,ORB caused byonly one personknowing how toperform a task,“PersonnelError”,An ORBcaused by asimplesyntax error,A CC makesa suggestthat getscompletelyshut down,MAVENishappy,An FDbrutallycriticizessomeone,ORB causedby OASIS-PS blackmagic,Someonefallsasleep,Someonementions a bestpracticesdocument thatno one knowsexists,Sean callspeople whoare glutenfree“special”,Sean saysORBs increaseat thebeginning ofthe semester,Someoneassigns anaction itemto a student,An ORBcaused bybad versioncontrol,Sean asks aquestion with anobvious answerthat leaves theroom speechless,An ORB withno actualeffect on thespacecraft,ORB causedby ignoringcheckproductsoutput,A CCITasks for asignature,Someonetalks about“the thoughtprocess”,Impossibleaction itemsuggested,Someonesends anout of officeemail,An FDblames an“FC” insteadofthemselves,ORB causedby blindlyexecuting amanproc,

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