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

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