Lostmobilesignal in ariser shaftGot excitedto see yourworkinstalled inreal life.Made a jokeabout hot airin a designreviewHad toexplain PPEin a TeamsmeetingSpoke upin adesignreviewWrote asustainabilitystatementPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Had toexplainembodiedcarbonBeen onsitebefore7 a.m.Got superexcitedabout goingon your firstsite visit.Accidentallymoved anentire systemin Revit andpanickedPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Said “itdepends”to a clientUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Shadowed acommissioningteamUsed Excelas a stressmanagementtoolWalked10k+steps on asite visitGot looped intoa sales callbecause thecustomer askedone technicalquestion.Sent yourfirst email…reread it 12times beforehitting send.Said “Thatneedsinsulation”under yourbreathAttendeda designteammeetingDid a factorytour and had topretend youknew whatevery machinedid.Designed withASHRAE/CIBSEExplainedMEP to anon‑engineerSpent moretime formattinga drawing titleblock thandoing actualengineering.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Realized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.Seen BIMclash inNavisworksWrote“TBC” ona drawinglike a proSpent toolong tryingto model acooling coilBlamedcoordinationissues onthe ceilingvoid (again)Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highGot askedfor a ‘quickupdate’ thatturned into afull redesign.Had to choosebetween twostandards thatcontradicteach other.Attended aCIBSE/YENeventChangedone valueand crashedthe wholemodel.Attended acoordinationmeeting thatcould’ve beenan email.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Copiedtemplates froma previousproject toavoid chaos.Heard“Can youmake itsmaller?”Confused U-value withR-value(once)Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Designed asystem andfound out theclient changedthe layout...yesterday.ConfusedPart L withPart FSaid “lowcarbon” atleast oncetodayUsedRevit orAutoCADall dayGot lostin a plantroomDrew adoodle thataccidentallyturned into aschematicGottenconfusedbetweenASHRAE90.1 and 62.1Done aduct sizecalc byhandHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Beenasked foranEPR/EPDAccidentallytaughtsomeoneaboutlumensOpened Revitand waited 10minutes justfor the modelto load.Done a LightPowerDensityCalculationby handArguedoverceilingvoid spaceGeometrydidn't importcorrectly —again.Used “firerating” in asentenceat a partyHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had a modelcrash andtook it as asign to goget coffee.Accidentallyjoined aTeams callwhile on siteHad Revitcrash duringyour finalmodel saveAsked“Wherecan thisriser go?”Described asmell as“mechanical”Said“That’snot in ourscope!”Looked forvalves in adrawing andsaw noneSpotted aclash incoordinationForgottento checkvalveclearanceAlreadyattendedyour firstCPD sessionthis yearLostmobilesignal in ariser shaftGot excitedto see yourworkinstalled inreal life.Made a jokeabout hot airin a designreviewHad toexplain PPEin a TeamsmeetingSpoke upin adesignreviewWrote asustainabilitystatementPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Had toexplainembodiedcarbonBeen onsitebefore7 a.m.Got superexcitedabout goingon your firstsite visit.Accidentallymoved anentire systemin Revit andpanickedPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Said “itdepends”to a clientUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Shadowed acommissioningteamUsed Excelas a stressmanagementtoolWalked10k+steps on asite visitGot looped intoa sales callbecause thecustomer askedone technicalquestion.Sent yourfirst email…reread it 12times beforehitting send.Said “Thatneedsinsulation”under yourbreathAttendeda designteammeetingDid a factorytour and had topretend youknew whatevery machinedid.Designed withASHRAE/CIBSEExplainedMEP to anon‑engineerSpent moretime formattinga drawing titleblock thandoing actualengineering.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Realized toolate that thewall wasstructuralGot a model torun — thenrealized it wasusing lastweek’sgeometry.Seen BIMclash inNavisworksWrote“TBC” ona drawinglike a proSpent toolong tryingto model acooling coilBlamedcoordinationissues onthe ceilingvoid (again)Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highGot askedfor a ‘quickupdate’ thatturned into afull redesign.Had to choosebetween twostandards thatcontradicteach other.Attended aCIBSE/YENeventChangedone valueand crashedthe wholemodel.Attended acoordinationmeeting thatcould’ve beenan email.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Copiedtemplates froma previousproject toavoid chaos.Heard“Can youmake itsmaller?”Confused U-value withR-value(once)Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Designed asystem andfound out theclient changedthe layout...yesterday.ConfusedPart L withPart FSaid “lowcarbon” atleast oncetodayUsedRevit orAutoCADall dayGot lostin a plantroomDrew adoodle thataccidentallyturned into aschematicGottenconfusedbetweenASHRAE90.1 and 62.1Done aduct sizecalc byhandHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Beenasked foranEPR/EPDAccidentallytaughtsomeoneaboutlumensOpened Revitand waited 10minutes justfor the modelto load.Done a LightPowerDensityCalculationby handArguedoverceilingvoid spaceGeometrydidn't importcorrectly —again.Used “firerating” in asentenceat a partyHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Had a modelcrash andtook it as asign to goget coffee.Accidentallyjoined aTeams callwhile on siteHad Revitcrash duringyour finalmodel saveAsked“Wherecan thisriser go?”Described asmell as“mechanical”Said“That’snot in ourscope!”Looked forvalves in adrawing andsaw noneSpotted aclash incoordinationForgottento checkvalveclearanceAlreadyattendedyour 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. Lost mobile signal in a riser shaft
  2. Got excited to see your work installed in real life.
  3. Made a joke about hot air in a design review
  4. Had to explain PPE in a Teams meeting
  5. Spoke up in a design review
  6. Wrote a sustainability statement
  7. Pretended to understand an acronym, Googled it immediately after the meeting.
  8. Had to explain embodied carbon
  9. Been on site before 7 a.m.
  10. Got super excited about going on your first site visit.
  11. Accidentally moved an entire system in Revit and panicked
  12. Phone died mid-inspection because there’s no power or Wi-Fi.
  13. Said “it depends” to a client
  14. Used the phrase ‘It depends’ to answer a question, and felt like a real engineer.
  15. Shadowed a commissioning team
  16. Used Excel as a stress management tool
  17. Walked 10k+ steps on a site visit
  18. Got looped into a sales call because the customer asked one technical question.
  19. Sent your first email…reread it 12 times before hitting send.
  20. Said “That needs insulation” under your breath
  21. Attended a design team meeting
  22. Did a factory tour and had to pretend you knew what every machine did.
  23. Designed with ASHRAE/CIBSE
  24. Explained MEP to a non‑engineer
  25. Spent more time formatting a drawing title block than doing actual engineering.
  26. Ate lunch at your desk next to ductwork schedules and coffee rings.
  27. Realized too late that the wall was structural
  28. Got a model to run — then realized it was using last week’s geometry.
  29. Seen BIM clash in Navisworks
  30. Wrote “TBC” on a drawing like a pro
  31. Spent too long trying to model a cooling coil
  32. Blamed coordination issues on the ceiling void (again)
  33. Got told ‘That’s not how we do it on site’—for something straight from code.
  34. Had no idea what anyone was talking about in your first coordination meeting.
  35. Accidentally modeled a floor with no ceiling and wondered why the gains were so high
  36. Got asked for a ‘quick update’ that turned into a full redesign.
  37. Had to choose between two standards that contradict each other.
  38. Attended a CIBSE/YEN event
  39. Changed one value and crashed the whole model.
  40. Attended a coordination meeting that could’ve been an email.
  41. Lost 2 hours to a file crash and said ‘It’s fine’ while dying inside.
  42. Copied templates from a previous project to avoid chaos.
  43. Heard “Can you make it smaller?”
  44. Confused U-value with R-value (once)
  45. Had to explain to someone that your product doesn’t defy the laws of thermodynamics.
  46. Designed a system and found out the client changed the layout... yesterday.
  47. Confused Part L with Part F
  48. Said “low carbon” at least once today
  49. Used Revit or AutoCAD all day
  50. Got lost in a plant room
  51. Drew a doodle that accidentally turned into a schematic
  52. Gotten confused between ASHRAE 90.1 and 62.1
  53. Done a duct size calc by hand
  54. Had to explain that no, electrical and plumbing don’t share the same conduit.
  55. Been asked for an EPR/EPD
  56. Accidentally taught someone about lumens
  57. Opened Revit and waited 10 minutes just for the model to load.
  58. Done a Light Power Density Calculation by hand
  59. Argued over ceiling void space
  60. Geometry didn't import correctly — again.
  61. Used “fire rating” in a sentence at a party
  62. Had to Google something in front of a senior and pretended it was ‘just a double-check.
  63. Had a model crash and took it as a sign to go get coffee.
  64. Accidentally joined a Teams call while on site
  65. Had Revit crash during your final model save
  66. Asked “Where can this riser go?”
  67. Described a smell as “mechanical”
  68. Said “That’s not in our scope!”
  69. Looked for valves in a drawing and saw none
  70. Spotted a clash in coordination
  71. Forgotten to check valve clearance
  72. Already attended your first CPD session this year