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

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