Opened Revitand waited 10minutes justfor the modelto load.Realized toolate that thewall wasstructuralForgottento checkvalveclearanceDesigned withASHRAE/CIBSEBlamedcoordinationissues onthe ceilingvoid (again)Accidentallymoved anentire systemin Revit andpanickedConfusedPart L withPart FWalked10k+steps on asite visitDone a LightPowerDensityCalculationby handChangedone valueand crashedthe wholemodel.Spoke upin adesignreviewBeen onsitebefore7 a.m.Lostmobilesignal in ariser shaftHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Beenasked foranEPR/EPDAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highLooked forvalves in adrawing andsaw noneUsed Excelas a stressmanagementtoolHad to choosebetween twostandards thatcontradicteach other.Got lostin a plantroomHad toexplainembodiedcarbonPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Drew adoodle thataccidentallyturned into aschematicSeen BIMclash inNavisworksSent yourfirst email…reread it 12times beforehitting send.Arguedoverceilingvoid spaceGot a model torun — thenrealized it wasusing lastweek’sgeometry.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Shadowed acommissioningteamExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Used “firerating” in asentenceat a partyDescribed asmell as“mechanical”Spent toolong tryingto model acooling coilAccidentallyjoined aTeams callwhile on siteAttendeda designteammeetingGottenconfusedbetweenASHRAE90.1 and 62.1Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Wrote“TBC” ona drawinglike a proHad toexplain PPEin a TeamsmeetingAccidentallytaughtsomeoneaboutlumensSaid “itdepends”to a clientSaid“That’snot in ourscope!”Said “Thatneedsinsulation”under yourbreathAttended aCIBSE/YENeventUsedRevit orAutoCADall daySpent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Done aduct sizecalc byhandGot looped intoa sales callbecause thecustomer askedone technicalquestion.Had a modelcrash andtook it as asign to goget coffee.Wrote asustainabilitystatementGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Copiedtemplates froma previousproject toavoid chaos.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Attended acoordinationmeeting thatcould’ve beenan email.Geometrydidn't importcorrectly —again.Asked“Wherecan thisriser go?”Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Got excitedto see yourworkinstalled inreal life.Said “lowcarbon” atleast oncetodayAlreadyattendedyour firstCPD sessionthis yearHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Made a jokeabout hot airin a designreviewHad Revitcrash duringyour finalmodel saveGot askedfor a ‘quickupdate’ thatturned into afull redesign.Heard“Can youmake itsmaller?”Confused U-value withR-value(once)Got superexcitedabout goingon your firstsite visit.Spotted aclash incoordinationOpened Revitand waited 10minutes justfor the modelto load.Realized toolate that thewall wasstructuralForgottento checkvalveclearanceDesigned withASHRAE/CIBSEBlamedcoordinationissues onthe ceilingvoid (again)Accidentallymoved anentire systemin Revit andpanickedConfusedPart L withPart FWalked10k+steps on asite visitDone a LightPowerDensityCalculationby handChangedone valueand crashedthe wholemodel.Spoke upin adesignreviewBeen onsitebefore7 a.m.Lostmobilesignal in ariser shaftHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Beenasked foranEPR/EPDAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highLooked forvalves in adrawing andsaw noneUsed Excelas a stressmanagementtoolHad to choosebetween twostandards thatcontradicteach other.Got lostin a plantroomHad toexplainembodiedcarbonPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Drew adoodle thataccidentallyturned into aschematicSeen BIMclash inNavisworksSent yourfirst email…reread it 12times beforehitting send.Arguedoverceilingvoid spaceGot a model torun — thenrealized it wasusing lastweek’sgeometry.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Shadowed acommissioningteamExplainedMEP to anon‑engineerDesigned asystem andfound out theclient changedthe layout...yesterday.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Used “firerating” in asentenceat a partyDescribed asmell as“mechanical”Spent toolong tryingto model acooling coilAccidentallyjoined aTeams callwhile on siteAttendeda designteammeetingGottenconfusedbetweenASHRAE90.1 and 62.1Phone diedmid-inspectionbecause there’sno power or Wi-Fi.Wrote“TBC” ona drawinglike a proHad toexplain PPEin a TeamsmeetingAccidentallytaughtsomeoneaboutlumensSaid “itdepends”to a clientSaid“That’snot in ourscope!”Said “Thatneedsinsulation”under yourbreathAttended aCIBSE/YENeventUsedRevit orAutoCADall daySpent moretime formattinga drawing titleblock thandoing actualengineering.Did a factorytour and had topretend youknew whatevery machinedid.Done aduct sizecalc byhandGot looped intoa sales callbecause thecustomer askedone technicalquestion.Had a modelcrash andtook it as asign to goget coffee.Wrote asustainabilitystatementGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Copiedtemplates froma previousproject toavoid chaos.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Attended acoordinationmeeting thatcould’ve beenan email.Geometrydidn't importcorrectly —again.Asked“Wherecan thisriser go?”Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Got excitedto see yourworkinstalled inreal life.Said “lowcarbon” atleast oncetodayAlreadyattendedyour firstCPD sessionthis yearHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Made a jokeabout hot airin a designreviewHad Revitcrash duringyour finalmodel saveGot askedfor a ‘quickupdate’ thatturned into afull redesign.Heard“Can youmake itsmaller?”Confused U-value withR-value(once)Got superexcitedabout goingon your firstsite visit.Spotted aclash incoordination

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