Said“That’snot in ourscope!”Opened Revitand waited 10minutes justfor the modelto load.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had Revitcrash duringyour finalmodel saveGeometrydidn't importcorrectly —again.Made a jokeabout hot airin a designreviewForgottento checkvalveclearanceShadowed acommissioningteamWrote“TBC” ona drawinglike a proSeen BIMclash inNavisworksGot a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyBeen onsitebefore7 a.m.Said “lowcarbon” atleast oncetodayWrote asustainabilitystatementAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitDesigned withASHRAE/CIBSEArguedoverceilingvoid spaceSpent moretime formattinga drawing titleblock thandoing actualengineering.ConfusedPart L withPart FLooked forvalves in adrawing andsaw noneBeenasked foranEPR/EPDLostmobilesignal in ariser shaftChangedone valueand crashedthe wholemodel.Done aduct sizecalc byhandAlreadyattendedyour firstCPD sessionthis yearGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Realized toolate that thewall wasstructuralGot lostin a plantroomHeard“Can youmake itsmaller?”Said “itdepends”to a clientUsed Excelas a stressmanagementtoolHad to choosebetween twostandards thatcontradicteach other.Said “Thatneedsinsulation”under yourbreathSpoke upin adesignreviewHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Got superexcitedabout goingon your firstsite visit.ExplainedMEP to anon‑engineerAttendeda designteammeetingAttended aCIBSE/YENeventPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Confused U-value withR-value(once)Had a modelcrash andtook it as asign to goget coffee.Got excitedto see yourworkinstalled inreal life.AccidentallytaughtsomeoneaboutlumensAttended acoordinationmeeting thatcould’ve beenan email.Done a LightPowerDensityCalculationby handHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Designed asystem andfound out theclient changedthe layout...yesterday.Spent toolong tryingto model acooling coilHad toexplainembodiedcarbonAte lunch atyour desk nextto ductworkschedules andcoffee rings.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Did a factorytour and had topretend youknew whatevery machinedid.Accidentallymoved anentire systemin Revit andpanickedHad toexplain PPEin a TeamsmeetingDrew adoodle thataccidentallyturned into aschematicHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Got looped intoa sales callbecause thecustomer askedone technicalquestion.GottenconfusedbetweenASHRAE90.1 and 62.1UsedRevit orAutoCADall dayPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Copiedtemplates froma previousproject toavoid chaos.Spotted aclash incoordinationAccidentallyjoined aTeams callwhile on siteDescribed asmell as“mechanical”Sent yourfirst email…reread it 12times beforehitting send.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Blamedcoordinationissues onthe ceilingvoid (again)Asked“Wherecan thisriser go?”Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Said“That’snot in ourscope!”Opened Revitand waited 10minutes justfor the modelto load.Got askedfor a ‘quickupdate’ thatturned into afull redesign.Had Revitcrash duringyour finalmodel saveGeometrydidn't importcorrectly —again.Made a jokeabout hot airin a designreviewForgottento checkvalveclearanceShadowed acommissioningteamWrote“TBC” ona drawinglike a proSeen BIMclash inNavisworksGot a model torun — thenrealized it wasusing lastweek’sgeometry.Used “firerating” in asentenceat a partyBeen onsitebefore7 a.m.Said “lowcarbon” atleast oncetodayWrote asustainabilitystatementAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highWalked10k+steps on asite visitDesigned withASHRAE/CIBSEArguedoverceilingvoid spaceSpent moretime formattinga drawing titleblock thandoing actualengineering.ConfusedPart L withPart FLooked forvalves in adrawing andsaw noneBeenasked foranEPR/EPDLostmobilesignal in ariser shaftChangedone valueand crashedthe wholemodel.Done aduct sizecalc byhandAlreadyattendedyour firstCPD sessionthis yearGot told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Realized toolate that thewall wasstructuralGot lostin a plantroomHeard“Can youmake itsmaller?”Said “itdepends”to a clientUsed Excelas a stressmanagementtoolHad to choosebetween twostandards thatcontradicteach other.Said “Thatneedsinsulation”under yourbreathSpoke upin adesignreviewHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Got superexcitedabout goingon your firstsite visit.ExplainedMEP to anon‑engineerAttendeda designteammeetingAttended aCIBSE/YENeventPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Confused U-value withR-value(once)Had a modelcrash andtook it as asign to goget coffee.Got excitedto see yourworkinstalled inreal life.AccidentallytaughtsomeoneaboutlumensAttended acoordinationmeeting thatcould’ve beenan email.Done a LightPowerDensityCalculationby handHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Designed asystem andfound out theclient changedthe layout...yesterday.Spent toolong tryingto model acooling coilHad toexplainembodiedcarbonAte lunch atyour desk nextto ductworkschedules andcoffee rings.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Did a factorytour and had topretend youknew whatevery machinedid.Accidentallymoved anentire systemin Revit andpanickedHad toexplain PPEin a TeamsmeetingDrew adoodle thataccidentallyturned into aschematicHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Got looped intoa sales callbecause thecustomer askedone technicalquestion.GottenconfusedbetweenASHRAE90.1 and 62.1UsedRevit orAutoCADall dayPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Copiedtemplates froma previousproject toavoid chaos.Spotted aclash incoordinationAccidentallyjoined aTeams callwhile on siteDescribed asmell as“mechanical”Sent yourfirst email…reread it 12times beforehitting send.Had no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Blamedcoordinationissues onthe ceilingvoid (again)Asked“Wherecan thisriser go?”Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.

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