Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Been onsitebefore7 a.m.Said “Thatneedsinsulation”under yourbreathHad a modelcrash andtook it as asign to goget coffee.Spotted aclash incoordinationCopiedtemplates froma previousproject toavoid chaos.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Got a model torun — thenrealized it wasusing lastweek’sgeometry.GottenconfusedbetweenASHRAE90.1 and 62.1Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Changedone valueand crashedthe wholemodel.ConfusedPart L withPart FAsked“Wherecan thisriser go?”Attended acoordinationmeeting thatcould’ve beenan email.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Wrote asustainabilitystatementGot lostin a plantroomGot excitedto see yourworkinstalled inreal life.Did a factorytour and had topretend youknew whatevery machinedid.Looked forvalves in adrawing andsaw nonePhone diedmid-inspectionbecause there’sno power or Wi-Fi.Geometrydidn't importcorrectly —again.Accidentallymoved anentire systemin Revit andpanickedSaid “itdepends”to a clientBeenasked foranEPR/EPDForgottento checkvalveclearanceGot looped intoa sales callbecause thecustomer askedone technicalquestion.Designed asystem andfound out theclient changedthe layout...yesterday.ExplainedMEP to anon‑engineerSpoke upin adesignreviewRealized toolate that thewall wasstructuralDescribed asmell as“mechanical”Confused U-value withR-value(once)Got superexcitedabout goingon your firstsite visit.Arguedoverceilingvoid spaceGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Lostmobilesignal in ariser shaftOpened Revitand waited 10minutes justfor the modelto load.Designed withASHRAE/CIBSEAccidentallytaughtsomeoneaboutlumensAttendeda designteammeetingSeen BIMclash inNavisworksUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Had toexplain PPEin a TeamsmeetingSent yourfirst email…reread it 12times beforehitting send.Heard“Can youmake itsmaller?”UsedRevit orAutoCADall dayDrew adoodle thataccidentallyturned into aschematicAte lunch atyour desk nextto ductworkschedules andcoffee rings.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highHad to choosebetween twostandards thatcontradicteach other.Had toexplainembodiedcarbonWrote“TBC” ona drawinglike a proWalked10k+steps on asite visitHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Alreadyattendedyour firstCPD sessionthis yearDone a LightPowerDensityCalculationby handMade a jokeabout hot airin a designreviewLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Used Excelas a stressmanagementtoolAccidentallyjoined aTeams callwhile on siteDone aduct sizecalc byhandSpent toolong tryingto model acooling coilAttended aCIBSE/YENeventSpent moretime formattinga drawing titleblock thandoing actualengineering.Had Revitcrash duringyour finalmodel saveShadowed acommissioningteamSaid“That’snot in ourscope!”Blamedcoordinationissues onthe ceilingvoid (again)Used “firerating” in asentenceat a partySaid “lowcarbon” atleast oncetodayHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Been onsitebefore7 a.m.Said “Thatneedsinsulation”under yourbreathHad a modelcrash andtook it as asign to goget coffee.Spotted aclash incoordinationCopiedtemplates froma previousproject toavoid chaos.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Got a model torun — thenrealized it wasusing lastweek’sgeometry.GottenconfusedbetweenASHRAE90.1 and 62.1Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Changedone valueand crashedthe wholemodel.ConfusedPart L withPart FAsked“Wherecan thisriser go?”Attended acoordinationmeeting thatcould’ve beenan email.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Wrote asustainabilitystatementGot lostin a plantroomGot excitedto see yourworkinstalled inreal life.Did a factorytour and had topretend youknew whatevery machinedid.Looked forvalves in adrawing andsaw nonePhone diedmid-inspectionbecause there’sno power or Wi-Fi.Geometrydidn't importcorrectly —again.Accidentallymoved anentire systemin Revit andpanickedSaid “itdepends”to a clientBeenasked foranEPR/EPDForgottento checkvalveclearanceGot looped intoa sales callbecause thecustomer askedone technicalquestion.Designed asystem andfound out theclient changedthe layout...yesterday.ExplainedMEP to anon‑engineerSpoke upin adesignreviewRealized toolate that thewall wasstructuralDescribed asmell as“mechanical”Confused U-value withR-value(once)Got superexcitedabout goingon your firstsite visit.Arguedoverceilingvoid spaceGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Lostmobilesignal in ariser shaftOpened Revitand waited 10minutes justfor the modelto load.Designed withASHRAE/CIBSEAccidentallytaughtsomeoneaboutlumensAttendeda designteammeetingSeen BIMclash inNavisworksUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Had toexplain PPEin a TeamsmeetingSent yourfirst email…reread it 12times beforehitting send.Heard“Can youmake itsmaller?”UsedRevit orAutoCADall dayDrew adoodle thataccidentallyturned into aschematicAte lunch atyour desk nextto ductworkschedules andcoffee rings.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highHad to choosebetween twostandards thatcontradicteach other.Had toexplainembodiedcarbonWrote“TBC” ona drawinglike a proWalked10k+steps on asite visitHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Alreadyattendedyour firstCPD sessionthis yearDone a LightPowerDensityCalculationby handMade a jokeabout hot airin a designreviewLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Used Excelas a stressmanagementtoolAccidentallyjoined aTeams callwhile on siteDone aduct sizecalc byhandSpent toolong tryingto model acooling coilAttended aCIBSE/YENeventSpent moretime formattinga drawing titleblock thandoing actualengineering.Had Revitcrash duringyour finalmodel saveShadowed acommissioningteamSaid“That’snot in ourscope!”Blamedcoordinationissues onthe ceilingvoid (again)Used “firerating” in asentenceat a partySaid “lowcarbon” atleast oncetoday

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