Wrote asustainabilitystatementAlreadyattendedyour firstCPD sessionthis yearGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Attended acoordinationmeeting thatcould’ve beenan email.Got lostin a plantroomAttendeda designteammeetingSpoke upin adesignreviewDesigned asystem andfound out theclient changedthe layout...yesterday.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Had to choosebetween twostandards thatcontradicteach other.Got excitedto see yourworkinstalled inreal life.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Sent yourfirst email…reread it 12times beforehitting send.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Done aduct sizecalc byhandShadowed acommissioningteamChangedone valueand crashedthe wholemodel.Asked“Wherecan thisriser go?”Drew adoodle thataccidentallyturned into aschematicHad Revitcrash duringyour finalmodel saveLooked forvalves in adrawing andsaw noneSaid “Thatneedsinsulation”under yourbreathBeen onsitebefore7 a.m.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Confused U-value withR-value(once)Had a modelcrash andtook it as asign to goget coffee.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Heard“Can youmake itsmaller?”Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highForgottento checkvalveclearanceLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.ExplainedMEP to anon‑engineerPretended tounderstand anacronym,Googled itimmediately afterthe meeting.ConfusedPart L withPart FCopiedtemplates froma previousproject toavoid chaos.Done a LightPowerDensityCalculationby handOpened Revitand waited 10minutes justfor the modelto load.Spotted aclash incoordinationGot askedfor a ‘quickupdate’ thatturned into afull redesign.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Beenasked foranEPR/EPDMade a jokeabout hot airin a designreviewHad toexplainembodiedcarbonSaid “lowcarbon” atleast oncetodayGot looped intoa sales callbecause thecustomer askedone technicalquestion.AccidentallytaughtsomeoneaboutlumensGeometrydidn't importcorrectly —again.GottenconfusedbetweenASHRAE90.1 and 62.1Seen BIMclash inNavisworksGot superexcitedabout goingon your firstsite visit.Arguedoverceilingvoid spaceRealized toolate that thewall wasstructuralSaid“That’snot in ourscope!”Described asmell as“mechanical”Lostmobilesignal in ariser shaftAccidentallymoved anentire systemin Revit andpanickedAccidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSEUsedRevit orAutoCADall daySaid “itdepends”to a clientUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Spent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Walked10k+steps on asite visitSpent toolong tryingto model acooling coilUsed Excelas a stressmanagementtoolWrote“TBC” ona drawinglike a proPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Attended aCIBSE/YENeventHad toexplain PPEin a TeamsmeetingUsed “firerating” in asentenceat a partyBlamedcoordinationissues onthe ceilingvoid (again)Wrote asustainabilitystatementAlreadyattendedyour firstCPD sessionthis yearGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Attended acoordinationmeeting thatcould’ve beenan email.Got lostin a plantroomAttendeda designteammeetingSpoke upin adesignreviewDesigned asystem andfound out theclient changedthe layout...yesterday.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Had to choosebetween twostandards thatcontradicteach other.Got excitedto see yourworkinstalled inreal life.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Sent yourfirst email…reread it 12times beforehitting send.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Done aduct sizecalc byhandShadowed acommissioningteamChangedone valueand crashedthe wholemodel.Asked“Wherecan thisriser go?”Drew adoodle thataccidentallyturned into aschematicHad Revitcrash duringyour finalmodel saveLooked forvalves in adrawing andsaw noneSaid “Thatneedsinsulation”under yourbreathBeen onsitebefore7 a.m.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Confused U-value withR-value(once)Had a modelcrash andtook it as asign to goget coffee.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Heard“Can youmake itsmaller?”Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highForgottento checkvalveclearanceLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.ExplainedMEP to anon‑engineerPretended tounderstand anacronym,Googled itimmediately afterthe meeting.ConfusedPart L withPart FCopiedtemplates froma previousproject toavoid chaos.Done a LightPowerDensityCalculationby handOpened Revitand waited 10minutes justfor the modelto load.Spotted aclash incoordinationGot askedfor a ‘quickupdate’ thatturned into afull redesign.Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Beenasked foranEPR/EPDMade a jokeabout hot airin a designreviewHad toexplainembodiedcarbonSaid “lowcarbon” atleast oncetodayGot looped intoa sales callbecause thecustomer askedone technicalquestion.AccidentallytaughtsomeoneaboutlumensGeometrydidn't importcorrectly —again.GottenconfusedbetweenASHRAE90.1 and 62.1Seen BIMclash inNavisworksGot superexcitedabout goingon your firstsite visit.Arguedoverceilingvoid spaceRealized toolate that thewall wasstructuralSaid“That’snot in ourscope!”Described asmell as“mechanical”Lostmobilesignal in ariser shaftAccidentallymoved anentire systemin Revit andpanickedAccidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSEUsedRevit orAutoCADall daySaid “itdepends”to a clientUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Spent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Walked10k+steps on asite visitSpent toolong tryingto model acooling coilUsed Excelas a stressmanagementtoolWrote“TBC” ona drawinglike a proPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Attended aCIBSE/YENeventHad toexplain PPEin a TeamsmeetingUsed “firerating” in asentenceat a partyBlamedcoordinationissues onthe ceilingvoid (again)

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