Attended acoordinationmeeting thatcould’ve beenan email.Shadowed acommissioningteamDescribed asmell as“mechanical”Designed withASHRAE/CIBSEDone aduct sizecalc byhandHeard“Can youmake itsmaller?”Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Got excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Forgottento checkvalveclearanceGeometrydidn't importcorrectly —again.Attendeda designteammeetingLooked forvalves in adrawing andsaw noneHad to choosebetween twostandards thatcontradicteach other.Had Revitcrash duringyour finalmodel saveHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Got lostin a plantroomLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Sent yourfirst email…reread it 12times beforehitting send.Confused U-value withR-value(once)Realized toolate that thewall wasstructuralHad a modelcrash andtook it as asign to goget coffee.Been onsitebefore7 a.m.Spent moretime formattinga drawing titleblock thandoing actualengineering.Done a LightPowerDensityCalculationby handDesigned asystem andfound out theclient changedthe layout...yesterday.Said “lowcarbon” atleast oncetodaySpent toolong tryingto model acooling coilPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had toexplain PPEin a TeamsmeetingUsed Excelas a stressmanagementtoolArguedoverceilingvoid spaceSaid “itdepends”to a clientPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Got superexcitedabout goingon your firstsite visit.Alreadyattendedyour firstCPD sessionthis yearWrote“TBC” ona drawinglike a proGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.GottenconfusedbetweenASHRAE90.1 and 62.1Attended aCIBSE/YENeventGot a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.AccidentallytaughtsomeoneaboutlumensConfusedPart L withPart FOpened Revitand waited 10minutes justfor the modelto load.Did a factorytour and had topretend youknew whatevery machinedid.Accidentallyjoined aTeams callwhile on siteBlamedcoordinationissues onthe ceilingvoid (again)Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSaid“That’snot in ourscope!”Had toexplainembodiedcarbonSpoke upin adesignreviewSeen BIMclash inNavisworksMade a jokeabout hot airin a designreviewBeenasked foranEPR/EPDExplainedMEP to anon‑engineerHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Drew adoodle thataccidentallyturned into aschematicChangedone valueand crashedthe wholemodel.Lostmobilesignal in ariser shaftCopiedtemplates froma previousproject toavoid chaos.Accidentallymoved anentire systemin Revit andpanickedAsked“Wherecan thisriser go?”Walked10k+steps on asite visitGot looped intoa sales callbecause thecustomer askedone technicalquestion.Wrote asustainabilitystatementUsedRevit orAutoCADall daySpotted aclash incoordinationAte lunch atyour desk nextto ductworkschedules andcoffee rings.Attended acoordinationmeeting thatcould’ve beenan email.Shadowed acommissioningteamDescribed asmell as“mechanical”Designed withASHRAE/CIBSEDone aduct sizecalc byhandHeard“Can youmake itsmaller?”Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Got excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Forgottento checkvalveclearanceGeometrydidn't importcorrectly —again.Attendeda designteammeetingLooked forvalves in adrawing andsaw noneHad to choosebetween twostandards thatcontradicteach other.Had Revitcrash duringyour finalmodel saveHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Got lostin a plantroomLost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Sent yourfirst email…reread it 12times beforehitting send.Confused U-value withR-value(once)Realized toolate that thewall wasstructuralHad a modelcrash andtook it as asign to goget coffee.Been onsitebefore7 a.m.Spent moretime formattinga drawing titleblock thandoing actualengineering.Done a LightPowerDensityCalculationby handDesigned asystem andfound out theclient changedthe layout...yesterday.Said “lowcarbon” atleast oncetodaySpent toolong tryingto model acooling coilPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had toexplain PPEin a TeamsmeetingUsed Excelas a stressmanagementtoolArguedoverceilingvoid spaceSaid “itdepends”to a clientPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Got superexcitedabout goingon your firstsite visit.Alreadyattendedyour firstCPD sessionthis yearWrote“TBC” ona drawinglike a proGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.GottenconfusedbetweenASHRAE90.1 and 62.1Attended aCIBSE/YENeventGot a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.AccidentallytaughtsomeoneaboutlumensConfusedPart L withPart FOpened Revitand waited 10minutes justfor the modelto load.Did a factorytour and had topretend youknew whatevery machinedid.Accidentallyjoined aTeams callwhile on siteBlamedcoordinationissues onthe ceilingvoid (again)Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSaid“That’snot in ourscope!”Had toexplainembodiedcarbonSpoke upin adesignreviewSeen BIMclash inNavisworksMade a jokeabout hot airin a designreviewBeenasked foranEPR/EPDExplainedMEP to anon‑engineerHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Drew adoodle thataccidentallyturned into aschematicChangedone valueand crashedthe wholemodel.Lostmobilesignal in ariser shaftCopiedtemplates froma previousproject toavoid chaos.Accidentallymoved anentire systemin Revit andpanickedAsked“Wherecan thisriser go?”Walked10k+steps on asite visitGot looped intoa sales callbecause thecustomer askedone technicalquestion.Wrote asustainabilitystatementUsedRevit orAutoCADall daySpotted aclash incoordinationAte lunch atyour desk nextto ductworkschedules andcoffee rings.

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