Got lostin a plantroomSpotted aclash incoordinationAttended aCIBSE/YENeventBeen onsitebefore7 a.m.Lostmobilesignal in ariser shaftSaid “Thatneedsinsulation”under yourbreathAccidentallymoved anentire systemin Revit andpanickedSent yourfirst email…reread it 12times beforehitting send.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Confused U-value withR-value(once)Alreadyattendedyour firstCPD sessionthis yearOpened Revitand waited 10minutes justfor the modelto load.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Copiedtemplates froma previousproject toavoid chaos.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Accidentallyjoined aTeams callwhile on siteDrew adoodle thataccidentallyturned into aschematicWrote“TBC” ona drawinglike a proWalked10k+steps on asite visitBeenasked foranEPR/EPDDesigned withASHRAE/CIBSEAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highGot superexcitedabout goingon your firstsite visit.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Spent toolong tryingto model acooling coilPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Said“That’snot in ourscope!”Done a LightPowerDensityCalculationby handHad to choosebetween twostandards thatcontradicteach other.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Used “firerating” in asentenceat a partyConfusedPart L withPart FHad toexplainembodiedcarbonGot excitedto see yourworkinstalled inreal life.Attendeda designteammeetingChangedone valueand crashedthe wholemodel.Had a modelcrash andtook it as asign to goget coffee.Made a jokeabout hot airin a designreviewSaid “lowcarbon” atleast oncetodayAccidentallytaughtsomeoneaboutlumensGottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Attended acoordinationmeeting thatcould’ve beenan email.Spent moretime formattinga drawing titleblock thandoing actualengineering.Seen BIMclash inNavisworksHad Revitcrash duringyour finalmodel saveShadowed acommissioningteamAsked“Wherecan thisriser go?”Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Did a factorytour and had topretend youknew whatevery machinedid.UsedRevit orAutoCADall dayForgottento checkvalveclearanceDone aduct sizecalc byhandExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Blamedcoordinationissues onthe ceilingvoid (again)Geometrydidn't importcorrectly —again.Looked forvalves in adrawing andsaw noneSpoke upin adesignreviewPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Described asmell as“mechanical”Arguedoverceilingvoid spaceSaid “itdepends”to a clientUsed Excelas a stressmanagementtoolHeard“Can youmake itsmaller?”Wrote asustainabilitystatementHad toexplain PPEin a TeamsmeetingAte lunch atyour desk nextto ductworkschedules andcoffee rings.Realized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.Got lostin a plantroomSpotted aclash incoordinationAttended aCIBSE/YENeventBeen onsitebefore7 a.m.Lostmobilesignal in ariser shaftSaid “Thatneedsinsulation”under yourbreathAccidentallymoved anentire systemin Revit andpanickedSent yourfirst email…reread it 12times beforehitting send.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Confused U-value withR-value(once)Alreadyattendedyour firstCPD sessionthis yearOpened Revitand waited 10minutes justfor the modelto load.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Copiedtemplates froma previousproject toavoid chaos.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Accidentallyjoined aTeams callwhile on siteDrew adoodle thataccidentallyturned into aschematicWrote“TBC” ona drawinglike a proWalked10k+steps on asite visitBeenasked foranEPR/EPDDesigned withASHRAE/CIBSEAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highGot superexcitedabout goingon your firstsite visit.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Spent toolong tryingto model acooling coilPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Said“That’snot in ourscope!”Done a LightPowerDensityCalculationby handHad to choosebetween twostandards thatcontradicteach other.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Used “firerating” in asentenceat a partyConfusedPart L withPart FHad toexplainembodiedcarbonGot excitedto see yourworkinstalled inreal life.Attendeda designteammeetingChangedone valueand crashedthe wholemodel.Had a modelcrash andtook it as asign to goget coffee.Made a jokeabout hot airin a designreviewSaid “lowcarbon” atleast oncetodayAccidentallytaughtsomeoneaboutlumensGottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Attended acoordinationmeeting thatcould’ve beenan email.Spent moretime formattinga drawing titleblock thandoing actualengineering.Seen BIMclash inNavisworksHad Revitcrash duringyour finalmodel saveShadowed acommissioningteamAsked“Wherecan thisriser go?”Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Did a factorytour and had topretend youknew whatevery machinedid.UsedRevit orAutoCADall dayForgottento checkvalveclearanceDone aduct sizecalc byhandExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Blamedcoordinationissues onthe ceilingvoid (again)Geometrydidn't importcorrectly —again.Looked forvalves in adrawing andsaw noneSpoke upin adesignreviewPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Described asmell as“mechanical”Arguedoverceilingvoid spaceSaid “itdepends”to a clientUsed Excelas a stressmanagementtoolHeard“Can youmake itsmaller?”Wrote asustainabilitystatementHad toexplain PPEin a TeamsmeetingAte lunch atyour desk nextto ductworkschedules andcoffee rings.Realized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.

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