Did a factorytour and had topretend youknew whatevery machinedid.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Had to choosebetween twostandards thatcontradicteach other.Said “Thatneedsinsulation”under yourbreathLooked forvalves in adrawing andsaw noneChangedone valueand crashedthe wholemodel.Forgottento checkvalveclearanceSpent moretime formattinga drawing titleblock thandoing actualengineering.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Drew adoodle thataccidentallyturned into aschematicPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Alreadyattendedyour firstCPD sessionthis yearGot lostin a plantroomSeen BIMclash inNavisworksSaid “lowcarbon” atleast oncetodayHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Made a jokeabout hot airin a designreviewCopiedtemplates froma previousproject toavoid chaos.Geometrydidn't importcorrectly —again.Sent yourfirst email…reread it 12times beforehitting send.Said “itdepends”to a clientAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitUsed Excelas a stressmanagementtoolDesigned asystem andfound out theclient changedthe layout...yesterday.Had toexplainembodiedcarbonGot superexcitedabout goingon your firstsite visit.Wrote asustainabilitystatementHad toexplain PPEin a TeamsmeetingBeenasked foranEPR/EPDGot a model torun — thenrealized it wasusing lastweek’sgeometry.Got excitedto see yourworkinstalled inreal life.Done aduct sizecalc byhandArguedoverceilingvoid spaceLostmobilesignal in ariser shaftDone a LightPowerDensityCalculationby handRealized toolate that thewall wasstructuralSpoke upin adesignreviewGot askedfor a ‘quickupdate’ thatturned into afull redesign.Accidentallymoved anentire systemin Revit andpanickedBlamedcoordinationissues onthe ceilingvoid (again)Said“That’snot in ourscope!”Attended aCIBSE/YENeventExplainedMEP to anon‑engineerHad a modelcrash andtook it as asign to goget coffee.Been onsitebefore7 a.m.Asked“Wherecan thisriser go?”Had Revitcrash duringyour finalmodel saveGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Wrote“TBC” ona drawinglike a proHeard“Can youmake itsmaller?”Had to explainthat no,electrical andplumbing don’tshare the sameconduit.UsedRevit orAutoCADall dayAccidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSESpotted aclash incoordinationShadowed acommissioningteamDescribed asmell as“mechanical”Attendeda designteammeetingGot looped intoa sales callbecause thecustomer askedone technicalquestion.ConfusedPart L withPart FAttended acoordinationmeeting thatcould’ve beenan email.AccidentallytaughtsomeoneaboutlumensUsed “firerating” in asentenceat a partySpent toolong tryingto model acooling coilGottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Opened Revitand waited 10minutes justfor the modelto load.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Confused U-value withR-value(once)Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Did a factorytour and had topretend youknew whatevery machinedid.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Had to choosebetween twostandards thatcontradicteach other.Said “Thatneedsinsulation”under yourbreathLooked forvalves in adrawing andsaw noneChangedone valueand crashedthe wholemodel.Forgottento checkvalveclearanceSpent moretime formattinga drawing titleblock thandoing actualengineering.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Drew adoodle thataccidentallyturned into aschematicPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Alreadyattendedyour firstCPD sessionthis yearGot lostin a plantroomSeen BIMclash inNavisworksSaid “lowcarbon” atleast oncetodayHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Made a jokeabout hot airin a designreviewCopiedtemplates froma previousproject toavoid chaos.Geometrydidn't importcorrectly —again.Sent yourfirst email…reread it 12times beforehitting send.Said “itdepends”to a clientAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitUsed Excelas a stressmanagementtoolDesigned asystem andfound out theclient changedthe layout...yesterday.Had toexplainembodiedcarbonGot superexcitedabout goingon your firstsite visit.Wrote asustainabilitystatementHad toexplain PPEin a TeamsmeetingBeenasked foranEPR/EPDGot a model torun — thenrealized it wasusing lastweek’sgeometry.Got excitedto see yourworkinstalled inreal life.Done aduct sizecalc byhandArguedoverceilingvoid spaceLostmobilesignal in ariser shaftDone a LightPowerDensityCalculationby handRealized toolate that thewall wasstructuralSpoke upin adesignreviewGot askedfor a ‘quickupdate’ thatturned into afull redesign.Accidentallymoved anentire systemin Revit andpanickedBlamedcoordinationissues onthe ceilingvoid (again)Said“That’snot in ourscope!”Attended aCIBSE/YENeventExplainedMEP to anon‑engineerHad a modelcrash andtook it as asign to goget coffee.Been onsitebefore7 a.m.Asked“Wherecan thisriser go?”Had Revitcrash duringyour finalmodel saveGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Wrote“TBC” ona drawinglike a proHeard“Can youmake itsmaller?”Had to explainthat no,electrical andplumbing don’tshare the sameconduit.UsedRevit orAutoCADall dayAccidentallyjoined aTeams callwhile on siteDesigned withASHRAE/CIBSESpotted aclash incoordinationShadowed acommissioningteamDescribed asmell as“mechanical”Attendeda designteammeetingGot looped intoa sales callbecause thecustomer askedone technicalquestion.ConfusedPart L withPart FAttended acoordinationmeeting thatcould’ve beenan email.AccidentallytaughtsomeoneaboutlumensUsed “firerating” in asentenceat a partySpent toolong tryingto model acooling coilGottenconfusedbetweenASHRAE90.1 and 62.1Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Opened Revitand waited 10minutes justfor the modelto load.Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Confused U-value withR-value(once)Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.

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