Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highHad Revitcrash duringyour finalmodel saveAttended aCIBSE/YENeventBlamedcoordinationissues onthe ceilingvoid (again)Drew adoodle thataccidentallyturned into aschematicDesigned asystem andfound out theclient changedthe layout...yesterday.Described asmell as“mechanical”Designed withASHRAE/CIBSECopiedtemplates froma previousproject toavoid chaos.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Been onsitebefore7 a.m.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Looked forvalves in adrawing andsaw noneSeen BIMclash inNavisworksGot excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathHad to choosebetween twostandards thatcontradicteach other.Spoke upin adesignreviewHad toexplainembodiedcarbonHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Lostmobilesignal in ariser shaftHeard“Can youmake itsmaller?”Asked“Wherecan thisriser go?”Spent toolong tryingto model acooling coilRealized toolate that thewall wasstructuralDone aduct sizecalc byhandGot a model torun — thenrealized it wasusing lastweek’sgeometry.Said“That’snot in ourscope!”Forgottento checkvalveclearanceUsed Excelas a stressmanagementtoolConfused U-value withR-value(once)Said “itdepends”to a clientGottenconfusedbetweenASHRAE90.1 and 62.1Made a jokeabout hot airin a designreviewHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Accidentallyjoined aTeams callwhile on siteUsedRevit orAutoCADall dayUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Wrote“TBC” ona drawinglike a proSpotted aclash incoordinationSent yourfirst email…reread it 12times beforehitting send.Attendeda designteammeetingUsed “firerating” in asentenceat a partyDid a factorytour and had topretend youknew whatevery machinedid.Said “lowcarbon” atleast oncetodayConfusedPart L withPart FPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Wrote asustainabilitystatementGot lostin a plantroomGot looped intoa sales callbecause thecustomer askedone technicalquestion.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Arguedoverceilingvoid spaceWalked10k+steps on asite visitAttended acoordinationmeeting thatcould’ve beenan email.Shadowed acommissioningteamHad toexplain PPEin a TeamsmeetingAccidentallytaughtsomeoneaboutlumensExplainedMEP to anon‑engineerLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Accidentallymoved anentire systemin Revit andpanickedHad a modelcrash andtook it as asign to goget coffee.Opened Revitand waited 10minutes justfor the modelto load.Changedone valueand crashedthe wholemodel.Done a LightPowerDensityCalculationby handSpent moretime formattinga drawing titleblock thandoing actualengineering.Beenasked foranEPR/EPDGeometrydidn't importcorrectly —again.Got superexcitedabout goingon your firstsite visit.Alreadyattendedyour firstCPD sessionthis yearAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highHad Revitcrash duringyour finalmodel saveAttended aCIBSE/YENeventBlamedcoordinationissues onthe ceilingvoid (again)Drew adoodle thataccidentallyturned into aschematicDesigned asystem andfound out theclient changedthe layout...yesterday.Described asmell as“mechanical”Designed withASHRAE/CIBSECopiedtemplates froma previousproject toavoid chaos.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Been onsitebefore7 a.m.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Looked forvalves in adrawing andsaw noneSeen BIMclash inNavisworksGot excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathHad to choosebetween twostandards thatcontradicteach other.Spoke upin adesignreviewHad toexplainembodiedcarbonHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Lostmobilesignal in ariser shaftHeard“Can youmake itsmaller?”Asked“Wherecan thisriser go?”Spent toolong tryingto model acooling coilRealized toolate that thewall wasstructuralDone aduct sizecalc byhandGot a model torun — thenrealized it wasusing lastweek’sgeometry.Said“That’snot in ourscope!”Forgottento checkvalveclearanceUsed Excelas a stressmanagementtoolConfused U-value withR-value(once)Said “itdepends”to a clientGottenconfusedbetweenASHRAE90.1 and 62.1Made a jokeabout hot airin a designreviewHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Accidentallyjoined aTeams callwhile on siteUsedRevit orAutoCADall dayUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Wrote“TBC” ona drawinglike a proSpotted aclash incoordinationSent yourfirst email…reread it 12times beforehitting send.Attendeda designteammeetingUsed “firerating” in asentenceat a partyDid a factorytour and had topretend youknew whatevery machinedid.Said “lowcarbon” atleast oncetodayConfusedPart L withPart FPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Wrote asustainabilitystatementGot lostin a plantroomGot looped intoa sales callbecause thecustomer askedone technicalquestion.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Arguedoverceilingvoid spaceWalked10k+steps on asite visitAttended acoordinationmeeting thatcould’ve beenan email.Shadowed acommissioningteamHad toexplain PPEin a TeamsmeetingAccidentallytaughtsomeoneaboutlumensExplainedMEP to anon‑engineerLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Accidentallymoved anentire systemin Revit andpanickedHad a modelcrash andtook it as asign to goget coffee.Opened Revitand waited 10minutes justfor the modelto load.Changedone valueand crashedthe wholemodel.Done a LightPowerDensityCalculationby handSpent moretime formattinga drawing titleblock thandoing actualengineering.Beenasked foranEPR/EPDGeometrydidn't importcorrectly —again.Got superexcitedabout goingon your firstsite visit.Alreadyattendedyour firstCPD sessionthis year

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