Arguedoverceilingvoid spaceGeometrydidn't importcorrectly —again.Walked10k+steps on asite visitChangedone valueand crashedthe wholemodel.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.GottenconfusedbetweenASHRAE90.1 and 62.1UsedRevit orAutoCADall dayAte lunch atyour desk nextto ductworkschedules andcoffee rings.Said“That’snot in ourscope!”Lostmobilesignal in ariser shaftDesigned asystem andfound out theclient changedthe layout...yesterday.Done a LightPowerDensityCalculationby handSpoke upin adesignreviewGot looped intoa sales callbecause thecustomer askedone technicalquestion.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had a modelcrash andtook it as asign to goget coffee.Sent yourfirst email…reread it 12times beforehitting send.ConfusedPart L withPart FRealized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.Got excitedto see yourworkinstalled inreal life.Done aduct sizecalc byhandSaid “Thatneedsinsulation”under yourbreathAlreadyattendedyour firstCPD sessionthis yearPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Attendeda designteammeetingDrew adoodle thataccidentallyturned into aschematicGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Said “lowcarbon” atleast oncetodayExplainedMEP to anon‑engineerBeenasked foranEPR/EPDSpotted aclash incoordinationForgottento checkvalveclearanceAsked“Wherecan thisriser go?”Been onsitebefore7 a.m.Got lostin a plantroomHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Spent toolong tryingto model acooling coilAttended acoordinationmeeting thatcould’ve beenan email.Attended aCIBSE/YENeventDid a factorytour and had topretend youknew whatevery machinedid.Looked forvalves in adrawing andsaw noneHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Used Excelas a stressmanagementtoolAccidentallytaughtsomeoneaboutlumensBlamedcoordinationissues onthe ceilingvoid (again)Opened Revitand waited 10minutes justfor the modelto load.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Heard“Can youmake itsmaller?”Made a jokeabout hot airin a designreviewPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Had toexplainembodiedcarbonSpent moretime formattinga drawing titleblock thandoing actualengineering.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had Revitcrash duringyour finalmodel saveDescribed asmell as“mechanical”Seen BIMclash inNavisworksGot superexcitedabout goingon your firstsite visit.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWrote asustainabilitystatementConfused U-value withR-value(once)Shadowed acommissioningteamLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Said “itdepends”to a clientWrote“TBC” ona drawinglike a proHad toexplain PPEin a TeamsmeetingHad to choosebetween twostandards thatcontradicteach other.Copiedtemplates froma previousproject toavoid chaos.Accidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSEAccidentallymoved anentire systemin Revit andpanickedUsed “firerating” in asentenceat a partyArguedoverceilingvoid spaceGeometrydidn't importcorrectly —again.Walked10k+steps on asite visitChangedone valueand crashedthe wholemodel.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.GottenconfusedbetweenASHRAE90.1 and 62.1UsedRevit orAutoCADall dayAte lunch atyour desk nextto ductworkschedules andcoffee rings.Said“That’snot in ourscope!”Lostmobilesignal in ariser shaftDesigned asystem andfound out theclient changedthe layout...yesterday.Done a LightPowerDensityCalculationby handSpoke upin adesignreviewGot looped intoa sales callbecause thecustomer askedone technicalquestion.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had a modelcrash andtook it as asign to goget coffee.Sent yourfirst email…reread it 12times beforehitting send.ConfusedPart L withPart FRealized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.Got excitedto see yourworkinstalled inreal life.Done aduct sizecalc byhandSaid “Thatneedsinsulation”under yourbreathAlreadyattendedyour firstCPD sessionthis yearPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Attendeda designteammeetingDrew adoodle thataccidentallyturned into aschematicGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Said “lowcarbon” atleast oncetodayExplainedMEP to anon‑engineerBeenasked foranEPR/EPDSpotted aclash incoordinationForgottento checkvalveclearanceAsked“Wherecan thisriser go?”Been onsitebefore7 a.m.Got lostin a plantroomHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Spent toolong tryingto model acooling coilAttended acoordinationmeeting thatcould’ve beenan email.Attended aCIBSE/YENeventDid a factorytour and had topretend youknew whatevery machinedid.Looked forvalves in adrawing andsaw noneHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Used Excelas a stressmanagementtoolAccidentallytaughtsomeoneaboutlumensBlamedcoordinationissues onthe ceilingvoid (again)Opened Revitand waited 10minutes justfor the modelto load.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Heard“Can youmake itsmaller?”Made a jokeabout hot airin a designreviewPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Had toexplainembodiedcarbonSpent moretime formattinga drawing titleblock thandoing actualengineering.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had Revitcrash duringyour finalmodel saveDescribed asmell as“mechanical”Seen BIMclash inNavisworksGot superexcitedabout goingon your firstsite visit.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWrote asustainabilitystatementConfused U-value withR-value(once)Shadowed acommissioningteamLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Said “itdepends”to a clientWrote“TBC” ona drawinglike a proHad toexplain PPEin a TeamsmeetingHad to choosebetween twostandards thatcontradicteach other.Copiedtemplates froma previousproject toavoid chaos.Accidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSEAccidentallymoved anentire systemin Revit andpanickedUsed “firerating” in asentenceat a party

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