Looked forvalves in adrawing andsaw noneUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Spent toolong tryingto model acooling coilCopiedtemplates froma previousproject toavoid chaos.Said“That’snot in ourscope!”Asked“Wherecan thisriser go?”Sent yourfirst email…reread it 12times beforehitting send.Got superexcitedabout goingon your firstsite visit.Confused U-value withR-value(once)Seen BIMclash inNavisworksWrote asustainabilitystatementAlreadyattendedyour firstCPD sessionthis yearChangedone valueand crashedthe wholemodel.Had toexplainembodiedcarbonAttended aCIBSE/YENeventShadowed acommissioningteamBeen onsitebefore7 a.m.Had Revitcrash duringyour finalmodel saveSpent moretime formattinga drawing titleblock thandoing actualengineering.Wrote“TBC” ona drawinglike a proSaid “itdepends”to a clientExplainedMEP to anon‑engineerRealized toolate that thewall wasstructuralGeometrydidn't importcorrectly —again.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Heard“Can youmake itsmaller?”Forgottento checkvalveclearanceBlamedcoordinationissues onthe ceilingvoid (again)Had a modelcrash andtook it as asign to goget coffee.AccidentallytaughtsomeoneaboutlumensGot a model torun — thenrealized it wasusing lastweek’sgeometry.Spotted aclash incoordinationAccidentallymoved anentire systemin Revit andpanickedGot excitedto see yourworkinstalled inreal life.Arguedoverceilingvoid spaceDrew adoodle thataccidentallyturned into aschematicSaid “Thatneedsinsulation”under yourbreathAttended acoordinationmeeting thatcould’ve beenan email.GottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Accidentallyjoined aTeams callwhile on siteSaid “lowcarbon” atleast oncetodayOpened Revitand waited 10minutes justfor the modelto load.Spoke upin adesignreviewMade a jokeabout hot airin a designreviewGot lostin a plantroomAttendeda designteammeetingAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Done a LightPowerDensityCalculationby handHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.UsedRevit orAutoCADall dayConfusedPart L withPart FHad toexplain PPEin a TeamsmeetingDone aduct sizecalc byhandDid a factorytour and had topretend youknew whatevery machinedid.Described asmell as“mechanical”Designed withASHRAE/CIBSEGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Designed asystem andfound out theclient changedthe layout...yesterday.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Used “firerating” in asentenceat a partyHad to choosebetween twostandards thatcontradicteach other.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Lostmobilesignal in ariser shaftBeenasked foranEPR/EPDUsed Excelas a stressmanagementtoolLooked forvalves in adrawing andsaw noneUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Spent toolong tryingto model acooling coilCopiedtemplates froma previousproject toavoid chaos.Said“That’snot in ourscope!”Asked“Wherecan thisriser go?”Sent yourfirst email…reread it 12times beforehitting send.Got superexcitedabout goingon your firstsite visit.Confused U-value withR-value(once)Seen BIMclash inNavisworksWrote asustainabilitystatementAlreadyattendedyour firstCPD sessionthis yearChangedone valueand crashedthe wholemodel.Had toexplainembodiedcarbonAttended aCIBSE/YENeventShadowed acommissioningteamBeen onsitebefore7 a.m.Had Revitcrash duringyour finalmodel saveSpent moretime formattinga drawing titleblock thandoing actualengineering.Wrote“TBC” ona drawinglike a proSaid “itdepends”to a clientExplainedMEP to anon‑engineerRealized toolate that thewall wasstructuralGeometrydidn't importcorrectly —again.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Heard“Can youmake itsmaller?”Forgottento checkvalveclearanceBlamedcoordinationissues onthe ceilingvoid (again)Had a modelcrash andtook it as asign to goget coffee.AccidentallytaughtsomeoneaboutlumensGot a model torun — thenrealized it wasusing lastweek’sgeometry.Spotted aclash incoordinationAccidentallymoved anentire systemin Revit andpanickedGot excitedto see yourworkinstalled inreal life.Arguedoverceilingvoid spaceDrew adoodle thataccidentallyturned into aschematicSaid “Thatneedsinsulation”under yourbreathAttended acoordinationmeeting thatcould’ve beenan email.GottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Accidentallyjoined aTeams callwhile on siteSaid “lowcarbon” atleast oncetodayOpened Revitand waited 10minutes justfor the modelto load.Spoke upin adesignreviewMade a jokeabout hot airin a designreviewGot lostin a plantroomAttendeda designteammeetingAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Done a LightPowerDensityCalculationby handHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.UsedRevit orAutoCADall dayConfusedPart L withPart FHad toexplain PPEin a TeamsmeetingDone aduct sizecalc byhandDid a factorytour and had topretend youknew whatevery machinedid.Described asmell as“mechanical”Designed withASHRAE/CIBSEGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Designed asystem andfound out theclient changedthe layout...yesterday.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Used “firerating” in asentenceat a partyHad to choosebetween twostandards thatcontradicteach other.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Lostmobilesignal in ariser shaftBeenasked foranEPR/EPDUsed Excelas a stressmanagementtool

Bingo: The Young Engineer Edition - 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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
  1. Looked for valves in a drawing and saw none
  2. Used the phrase ‘It depends’ to answer a question, and felt like a real engineer.
  3. Phone died mid-inspection because there’s no power or Wi-Fi.
  4. Spent too long trying to model a cooling coil
  5. Copied templates from a previous project to avoid chaos.
  6. Said “That’s not in our scope!”
  7. Asked “Where can this riser go?”
  8. Sent your first email…reread it 12 times before hitting send.
  9. Got super excited about going on your first site visit.
  10. Confused U-value with R-value (once)
  11. Seen BIM clash in Navisworks
  12. Wrote a sustainability statement
  13. Already attended your first CPD session this year
  14. Changed one value and crashed the whole model.
  15. Had to explain embodied carbon
  16. Attended a CIBSE/YEN event
  17. Shadowed a commissioning team
  18. Been on site before 7 a.m.
  19. Had Revit crash during your final model save
  20. Spent more time formatting a drawing title block than doing actual engineering.
  21. Wrote “TBC” on a drawing like a pro
  22. Said “it depends” to a client
  23. Explained MEP to a non‑engineer
  24. Realized too late that the wall was structural
  25. Geometry didn't import correctly — again.
  26. Had to explain that no, electrical and plumbing don’t share the same conduit.
  27. Heard “Can you make it smaller?”
  28. Forgotten to check valve clearance
  29. Blamed coordination issues on the ceiling void (again)
  30. Had a model crash and took it as a sign to go get coffee.
  31. Accidentally taught someone about lumens
  32. Got a model to run — then realized it was using last week’s geometry.
  33. Spotted a clash in coordination
  34. Accidentally moved an entire system in Revit and panicked
  35. Got excited to see your work installed in real life.
  36. Argued over ceiling void space
  37. Drew a doodle that accidentally turned into a schematic
  38. Said “That needs insulation” under your breath
  39. Attended a coordination meeting that could’ve been an email.
  40. Gotten confused between ASHRAE 90.1 and 62.1
  41. Lost 2 hours to a file crash and said ‘It’s fine’ while dying inside.
  42. Accidentally joined a Teams call while on site
  43. Said “low carbon” at least once today
  44. Opened Revit and waited 10 minutes just for the model to load.
  45. Spoke up in a design review
  46. Made a joke about hot air in a design review
  47. Got lost in a plant room
  48. Attended a design team meeting
  49. Accidentally modeled a floor with no ceiling and wondered why the gains were so high
  50. Walked 10k+ steps on a site visit
  51. Had to explain to someone that your product doesn’t defy the laws of thermodynamics.
  52. Done a Light Power Density Calculation by hand
  53. Had to Google something in front of a senior and pretended it was ‘just a double-check.
  54. Used Revit or AutoCAD all day
  55. Confused Part L with Part F
  56. Had to explain PPE in a Teams meeting
  57. Done a duct size calc by hand
  58. Did a factory tour and had to pretend you knew what every machine did.
  59. Described a smell as “mechanical”
  60. Designed with ASHRAE/CIBSE
  61. Got told ‘That’s not how we do it on site’—for something straight from code.
  62. Got looped into a sales call because the customer asked one technical question.
  63. Designed a system and found out the client changed the layout... yesterday.
  64. Had no idea what anyone was talking about in your first coordination meeting.
  65. Used “fire rating” in a sentence at a party
  66. Had to choose between two standards that contradict each other.
  67. Ate lunch at your desk next to ductwork schedules and coffee rings.
  68. Got asked for a ‘quick update’ that turned into a full redesign.
  69. Pretended to understand an acronym, Googled it immediately after the meeting.
  70. Lost mobile signal in a riser shaft
  71. Been asked for an EPR/EPD
  72. Used Excel as a stress management tool