Got a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Lostmobilesignal in ariser shaftDesigned withASHRAE/CIBSEBlamedcoordinationissues onthe ceilingvoid (again)Seen BIMclash inNavisworksLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Wrote asustainabilitystatementSpotted aclash incoordinationArguedoverceilingvoid spaceWalked10k+steps on asite visitExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Attended aCIBSE/YENeventSaid “lowcarbon” atleast oncetodayAttended acoordinationmeeting thatcould’ve beenan email.Accidentallymoved anentire systemin Revit andpanickedGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Been onsitebefore7 a.m.Asked“Wherecan thisriser go?”Realized toolate that thewall wasstructuralAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSaid “itdepends”to a clientAte lunch atyour desk nextto ductworkschedules andcoffee rings.Shadowed acommissioningteamConfusedPart L withPart FDescribed asmell as“mechanical”Copiedtemplates froma previousproject toavoid chaos.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Wrote“TBC” ona drawinglike a proSaid“That’snot in ourscope!”Made a jokeabout hot airin a designreviewSaid “Thatneedsinsulation”under yourbreathForgottento checkvalveclearanceAttendeda designteammeetingSent yourfirst email…reread it 12times beforehitting send.Confused U-value withR-value(once)Accidentallyjoined aTeams callwhile on siteHad Revitcrash duringyour finalmodel saveSpoke upin adesignreviewBeenasked foranEPR/EPDHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Spent toolong tryingto model acooling coilHad toexplain PPEin a TeamsmeetingPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Done aduct sizecalc byhandHad to choosebetween twostandards thatcontradicteach other.Looked forvalves in adrawing andsaw noneUsed Excelas a stressmanagementtoolAlreadyattendedyour firstCPD sessionthis yearHeard“Can youmake itsmaller?”Got superexcitedabout goingon your firstsite visit.Got excitedto see yourworkinstalled inreal life.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Done a LightPowerDensityCalculationby handHad toexplainembodiedcarbonAccidentallytaughtsomeoneaboutlumensGeometrydidn't importcorrectly —again.Got askedfor a ‘quickupdate’ thatturned into afull redesign.UsedRevit orAutoCADall dayGottenconfusedbetweenASHRAE90.1 and 62.1Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Opened Revitand waited 10minutes justfor the modelto load.Had a modelcrash andtook it as asign to goget coffee.Spent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Drew adoodle thataccidentallyturned into aschematicChangedone valueand crashedthe wholemodel.Got lostin a plantroomGot a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Lostmobilesignal in ariser shaftDesigned withASHRAE/CIBSEBlamedcoordinationissues onthe ceilingvoid (again)Seen BIMclash inNavisworksLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Wrote asustainabilitystatementSpotted aclash incoordinationArguedoverceilingvoid spaceWalked10k+steps on asite visitExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Attended aCIBSE/YENeventSaid “lowcarbon” atleast oncetodayAttended acoordinationmeeting thatcould’ve beenan email.Accidentallymoved anentire systemin Revit andpanickedGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Been onsitebefore7 a.m.Asked“Wherecan thisriser go?”Realized toolate that thewall wasstructuralAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSaid “itdepends”to a clientAte lunch atyour desk nextto ductworkschedules andcoffee rings.Shadowed acommissioningteamConfusedPart L withPart FDescribed asmell as“mechanical”Copiedtemplates froma previousproject toavoid chaos.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Wrote“TBC” ona drawinglike a proSaid“That’snot in ourscope!”Made a jokeabout hot airin a designreviewSaid “Thatneedsinsulation”under yourbreathForgottento checkvalveclearanceAttendeda designteammeetingSent yourfirst email…reread it 12times beforehitting send.Confused U-value withR-value(once)Accidentallyjoined aTeams callwhile on siteHad Revitcrash duringyour finalmodel saveSpoke upin adesignreviewBeenasked foranEPR/EPDHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Spent toolong tryingto model acooling coilHad toexplain PPEin a TeamsmeetingPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Done aduct sizecalc byhandHad to choosebetween twostandards thatcontradicteach other.Looked forvalves in adrawing andsaw noneUsed Excelas a stressmanagementtoolAlreadyattendedyour firstCPD sessionthis yearHeard“Can youmake itsmaller?”Got superexcitedabout goingon your firstsite visit.Got excitedto see yourworkinstalled inreal life.Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Done a LightPowerDensityCalculationby handHad toexplainembodiedcarbonAccidentallytaughtsomeoneaboutlumensGeometrydidn't importcorrectly —again.Got askedfor a ‘quickupdate’ thatturned into afull redesign.UsedRevit orAutoCADall dayGottenconfusedbetweenASHRAE90.1 and 62.1Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Opened Revitand waited 10minutes justfor the modelto load.Had a modelcrash andtook it as asign to goget coffee.Spent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Drew adoodle thataccidentallyturned into aschematicChangedone valueand crashedthe wholemodel.Got lostin a plantroom

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