Dusted out aPC withcompressedair upside-downSpilled adrink onhardwareCauseda majorproblemSpent twohourstroubleshootingan issue thathad a simple fixStrippedpc screwsbeyond allrecognitionTried to fixa printerbut madeit worseClosed theuser's appswithout themsaving theirworkDroppedhardwareDidn't todocumentthe fixArrivedlate toworkPut a calleron hold/muteandaccidentallyhung upNotknowingbasic ITknowledgeUnpluggedthe wrongserver orswitch cableForgot todo stuff ona newlysetup PCDamageduser's orworkpropertyCrimped anRJ45 networkcableobviouslywrongClosed aticket withoutactuallyfixing theissueGotcompletelylost trying tofind aUser/RoomAct like theyunderstoodthe taskwhen theyactually didn'tVisiblypanicked infront of auser over anormal issueSet a user'spassword to"NeverExpires" byaccidentDoesn'tknow howto useLinuxLostworkpropertySpelled anew hire’snamewrongLostPCScrewsMisunderstoodthe userForgot themainadminpasswordForgot theirbadge orlockedthemselvesoutLeft theirworkstationunlockedPlugged aUSB in thewrong waytoo manytimesMisunderstooda perfectlysimple requestForced a PCshutdownbecause itwas takingtoo longCaughttaking aquick napat workEscalateda simpleissueHas a messydesk ordidn't cleanup afterthemselvesDid badcablemanagementDoesn'tknow howto fix acomputerAvoidingworkDeleted aneededfile withoutbackupBlamed acompletelyunrelatedsoftware updatefor a hardwarefailureForgot toadd certaininfo whilemaking useraccountGamingon thejobSpent toolong in theworkbathroomCreateda networkloopSnapped theclip off anEthernet cableor just left itloosely pluggedGave theuser thewronginstructionsForgot tohelp a userthey saidthey'd helplaterNotreading orreplying tothe emailGoogled theerror codewhile theuserwatchedUsed technicaljargon on aworker whojust a simplefixDusted out aPC withcompressedair upside-downSpilled adrink onhardwareCauseda majorproblemSpent twohourstroubleshootingan issue thathad a simple fixStrippedpc screwsbeyond allrecognitionTried to fixa printerbut madeit worseClosed theuser's appswithout themsaving theirworkDroppedhardwareDidn't todocumentthe fixArrivedlate toworkPut a calleron hold/muteandaccidentallyhung upNotknowingbasic ITknowledgeUnpluggedthe wrongserver orswitch cableForgot todo stuff ona newlysetup PCDamageduser's orworkpropertyCrimped anRJ45 networkcableobviouslywrongClosed aticket withoutactuallyfixing theissueGotcompletelylost trying tofind aUser/RoomAct like theyunderstoodthe taskwhen theyactually didn'tVisiblypanicked infront of auser over anormal issueSet a user'spassword to"NeverExpires" byaccidentDoesn'tknow howto useLinuxLostworkpropertySpelled anew hire’snamewrongLostPCScrewsMisunderstoodthe userForgot themainadminpasswordForgot theirbadge orlockedthemselvesoutLeft theirworkstationunlockedPlugged aUSB in thewrong waytoo manytimesMisunderstooda perfectlysimple requestForced a PCshutdownbecause itwas takingtoo longCaughttaking aquick napat workEscalateda simpleissueHas a messydesk ordidn't cleanup afterthemselvesDid badcablemanagementDoesn'tknow howto fix acomputerAvoidingworkDeleted aneededfile withoutbackupBlamed acompletelyunrelatedsoftware updatefor a hardwarefailureForgot toadd certaininfo whilemaking useraccountGamingon thejobSpent toolong in theworkbathroomCreateda networkloopSnapped theclip off anEthernet cableor just left itloosely pluggedGave theuser thewronginstructionsForgot tohelp a userthey saidthey'd helplaterNotreading orreplying tothe emailGoogled theerror codewhile theuserwatchedUsed technicaljargon on aworker whojust a simplefix

IT Intern 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
39
40
41
42
43
44
45
46
47
48
49
50
  1. Dusted out a PC with compressed air upside-down
  2. Spilled a drink on hardware
  3. Caused a major problem
  4. Spent two hours troubleshooting an issue that had a simple fix
  5. Stripped pc screws beyond all recognition
  6. Tried to fix a printer but made it worse
  7. Closed the user's apps without them saving their work
  8. Dropped hardware
  9. Didn't to document the fix
  10. Arrived late to work
  11. Put a caller on hold/mute and accidentally hung up
  12. Not knowing basic IT knowledge
  13. Unplugged the wrong server or switch cable
  14. Forgot to do stuff on a newly setup PC
  15. Damaged user's or work property
  16. Crimped an RJ45 network cable obviously wrong
  17. Closed a ticket without actually fixing the issue
  18. Got completely lost trying to find a User/Room
  19. Act like they understood the task when they actually didn't
  20. Visibly panicked in front of a user over a normal issue
  21. Set a user's password to "Never Expires" by accident
  22. Doesn't know how to use Linux
  23. Lost work property
  24. Spelled a new hire’s name wrong
  25. Lost PC Screws
  26. Misunderstood the user
  27. Forgot the main admin password
  28. Forgot their badge or locked themselves out
  29. Left their workstation unlocked
  30. Plugged a USB in the wrong way too many times
  31. Misunderstood a perfectly simple request
  32. Forced a PC shutdown because it was taking too long
  33. Caught taking a quick nap at work
  34. Escalated a simple issue
  35. Has a messy desk or didn't clean up after themselves
  36. Did bad cable management
  37. Doesn't know how to fix a computer
  38. Avoiding work
  39. Deleted a needed file without backup
  40. Blamed a completely unrelated software update for a hardware failure
  41. Forgot to add certain info while making user account
  42. Gaming on the job
  43. Spent too long in the work bathroom
  44. Created a network loop
  45. Snapped the clip off an Ethernet cable or just left it loosely plugged
  46. Gave the user the wrong instructions
  47. Forgot to help a user they said they'd help later
  48. Not reading or replying to the email
  49. Googled the error code while the user watched
  50. Used technical jargon on a worker who just a simple fix