Geometrydidn't importcorrectly —again.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Got superexcitedabout goingon your firstsite visit.Got lostin a plantroomChangedone valueand crashedthe wholemodel.Realized toolate that thewall wasstructuralGot excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathExplainedMEP to anon‑engineerAsked“Wherecan thisriser go?”ConfusedPart L withPart FDone a LightPowerDensityCalculationby handPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Spoke upin adesignreviewGot looped intoa sales callbecause thecustomer askedone technicalquestion.Arguedoverceilingvoid spaceDescribed asmell as“mechanical”Designed asystem andfound out theclient changedthe layout...yesterday.Heard“Can youmake itsmaller?”Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Accidentallyjoined aTeams callwhile on siteBeenasked foranEPR/EPDHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Alreadyattendedyour firstCPD sessionthis yearSpotted aclash incoordinationBeen onsitebefore7 a.m.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highAccidentallymoved anentire systemin Revit andpanickedWrote asustainabilitystatementLostmobilesignal in ariser shaftOpened Revitand waited 10minutes justfor the modelto load.Spent toolong tryingto model acooling coilHad to choosebetween twostandards thatcontradicteach other.Attended acoordinationmeeting thatcould’ve beenan email.Had a modelcrash andtook it as asign to goget coffee.AccidentallytaughtsomeoneaboutlumensDone aduct sizecalc byhandDesigned withASHRAE/CIBSEMade a jokeabout hot airin a designreviewHad toexplain PPEin a TeamsmeetingWalked10k+steps on asite visitDid a factorytour and had topretend youknew whatevery machinedid.Shadowed acommissioningteamForgottento checkvalveclearanceHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Sent yourfirst email…reread it 12times beforehitting send.Got askedfor a ‘quickupdate’ thatturned into afull redesign.GottenconfusedbetweenASHRAE90.1 and 62.1Used “firerating” in asentenceat a partyHad toexplainembodiedcarbonAttended aCIBSE/YENeventSaid “itdepends”to a clientConfused U-value withR-value(once)Looked forvalves in adrawing andsaw noneCopiedtemplates froma previousproject toavoid chaos.Used Excelas a stressmanagementtoolAttendeda designteammeetingDrew adoodle thataccidentallyturned into aschematicSaid “lowcarbon” atleast oncetodayUsedRevit orAutoCADall dayBlamedcoordinationissues onthe ceilingvoid (again)Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Said“That’snot in ourscope!”Wrote“TBC” ona drawinglike a proHad Revitcrash duringyour finalmodel saveSpent moretime formattinga drawing titleblock thandoing actualengineering.Seen BIMclash inNavisworksGeometrydidn't importcorrectly —again.Ate lunch atyour desk nextto ductworkschedules andcoffee rings.Got superexcitedabout goingon your firstsite visit.Got lostin a plantroomChangedone valueand crashedthe wholemodel.Realized toolate that thewall wasstructuralGot excitedto see yourworkinstalled inreal life.Said “Thatneedsinsulation”under yourbreathExplainedMEP to anon‑engineerAsked“Wherecan thisriser go?”ConfusedPart L withPart FDone a LightPowerDensityCalculationby handPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Used the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Spoke upin adesignreviewGot looped intoa sales callbecause thecustomer askedone technicalquestion.Arguedoverceilingvoid spaceDescribed asmell as“mechanical”Designed asystem andfound out theclient changedthe layout...yesterday.Heard“Can youmake itsmaller?”Pretended tounderstand anacronym,Googled itimmediately afterthe meeting.Had to explainthat no,electrical andplumbing don’tshare the sameconduit.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Accidentallyjoined aTeams callwhile on siteBeenasked foranEPR/EPDHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.Alreadyattendedyour firstCPD sessionthis yearSpotted aclash incoordinationBeen onsitebefore7 a.m.Accidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highAccidentallymoved anentire systemin Revit andpanickedWrote asustainabilitystatementLostmobilesignal in ariser shaftOpened Revitand waited 10minutes justfor the modelto load.Spent toolong tryingto model acooling coilHad to choosebetween twostandards thatcontradicteach other.Attended acoordinationmeeting thatcould’ve beenan email.Had a modelcrash andtook it as asign to goget coffee.AccidentallytaughtsomeoneaboutlumensDone aduct sizecalc byhandDesigned withASHRAE/CIBSEMade a jokeabout hot airin a designreviewHad toexplain PPEin a TeamsmeetingWalked10k+steps on asite visitDid a factorytour and had topretend youknew whatevery machinedid.Shadowed acommissioningteamForgottento checkvalveclearanceHad to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Sent yourfirst email…reread it 12times beforehitting send.Got askedfor a ‘quickupdate’ thatturned into afull redesign.GottenconfusedbetweenASHRAE90.1 and 62.1Used “firerating” in asentenceat a partyHad toexplainembodiedcarbonAttended aCIBSE/YENeventSaid “itdepends”to a clientConfused U-value withR-value(once)Looked forvalves in adrawing andsaw noneCopiedtemplates froma previousproject toavoid chaos.Used Excelas a stressmanagementtoolAttendeda designteammeetingDrew adoodle thataccidentallyturned into aschematicSaid “lowcarbon” atleast oncetodayUsedRevit orAutoCADall dayBlamedcoordinationissues onthe ceilingvoid (again)Had to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Said“That’snot in ourscope!”Wrote“TBC” ona drawinglike a proHad Revitcrash duringyour finalmodel saveSpent moretime formattinga drawing titleblock thandoing actualengineering.Seen BIMclash inNavisworks

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