Did a factorytour and had topretend youknew whatevery machinedid.Made a jokeabout hot airin a designreviewConfused U-value withR-value(once)Designed asystem andfound out theclient changedthe layout...yesterday.Wrote“TBC” ona drawinglike a proBeen onsitebefore7 a.m.Wrote asustainabilitystatementGot superexcitedabout goingon your firstsite visit.Attended aCIBSE/YENeventCopiedtemplates froma previousproject toavoid chaos.Spotted aclash incoordinationAte lunch atyour desk nextto ductworkschedules andcoffee rings.Said “itdepends”to a clientLooked forvalves in adrawing andsaw noneDesigned withASHRAE/CIBSEUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Changedone valueand crashedthe wholemodel.Had Revitcrash duringyour finalmodel saveConfusedPart L withPart FHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Had toexplainembodiedcarbonBeenasked foranEPR/EPDPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Shadowed acommissioningteamSaid “Thatneedsinsulation”under yourbreathWalked10k+steps on asite visitPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Alreadyattendedyour firstCPD sessionthis yearAttended acoordinationmeeting thatcould’ve beenan email.Forgottento checkvalveclearanceArguedoverceilingvoid spaceSpoke upin adesignreviewGot excitedto see yourworkinstalled inreal life.Sent yourfirst email…reread it 12times beforehitting send.Geometrydidn't importcorrectly —again.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Asked“Wherecan thisriser go?”Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Seen BIMclash inNavisworksBlamedcoordinationissues onthe ceilingvoid (again)Said“That’snot in ourscope!”Lostmobilesignal in ariser shaftAccidentallymoved anentire systemin Revit andpanickedHad toexplain PPEin a TeamsmeetingUsedRevit orAutoCADall dayHad a modelcrash andtook it as asign to goget coffee.Used “firerating” in asentenceat a partyHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Opened Revitand waited 10minutes justfor the modelto load.Described asmell as“mechanical”Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Realized toolate that thewall wasstructuralHad to choosebetween twostandards thatcontradicteach other.Done a LightPowerDensityCalculationby handAttendeda designteammeetingAccidentallytaughtsomeoneaboutlumensAccidentallyjoined aTeams callwhile on siteHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.ExplainedMEP to anon‑engineerSpent moretime formattinga drawing titleblock thandoing actualengineering.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Heard“Can youmake itsmaller?”Got lostin a plantroomAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSpent toolong tryingto model acooling coilUsed Excelas a stressmanagementtoolGot askedfor a ‘quickupdate’ thatturned into afull redesign.Said “lowcarbon” atleast oncetodayGottenconfusedbetweenASHRAE90.1 and 62.1Drew adoodle thataccidentallyturned into aschematicDone aduct sizecalc byhandDid a factorytour and had topretend youknew whatevery machinedid.Made a jokeabout hot airin a designreviewConfused U-value withR-value(once)Designed asystem andfound out theclient changedthe layout...yesterday.Wrote“TBC” ona drawinglike a proBeen onsitebefore7 a.m.Wrote asustainabilitystatementGot superexcitedabout goingon your firstsite visit.Attended aCIBSE/YENeventCopiedtemplates froma previousproject toavoid chaos.Spotted aclash incoordinationAte lunch atyour desk nextto ductworkschedules andcoffee rings.Said “itdepends”to a clientLooked forvalves in adrawing andsaw noneDesigned withASHRAE/CIBSEUsed the phrase‘It depends’ toanswer aquestion, andfelt like a realengineer.Changedone valueand crashedthe wholemodel.Had Revitcrash duringyour finalmodel saveConfusedPart L withPart FHad to explainthat no,electrical andplumbing don’tshare the sameconduit.Had toexplainembodiedcarbonBeenasked foranEPR/EPDPhone diedmid-inspectionbecause there’sno power or Wi-Fi.Shadowed acommissioningteamSaid “Thatneedsinsulation”under yourbreathWalked10k+steps on asite visitPretended tounderstand anacronym,Googled itimmediately afterthe meeting.Alreadyattendedyour firstCPD sessionthis yearAttended acoordinationmeeting thatcould’ve beenan email.Forgottento checkvalveclearanceArguedoverceilingvoid spaceSpoke upin adesignreviewGot excitedto see yourworkinstalled inreal life.Sent yourfirst email…reread it 12times beforehitting send.Geometrydidn't importcorrectly —again.Got a model torun — thenrealized it wasusing lastweek’sgeometry.Got looped intoa sales callbecause thecustomer askedone technicalquestion.Asked“Wherecan thisriser go?”Got told ‘That’snot how we doit on site’—forsomethingstraight fromcode.Seen BIMclash inNavisworksBlamedcoordinationissues onthe ceilingvoid (again)Said“That’snot in ourscope!”Lostmobilesignal in ariser shaftAccidentallymoved anentire systemin Revit andpanickedHad toexplain PPEin a TeamsmeetingUsedRevit orAutoCADall dayHad a modelcrash andtook it as asign to goget coffee.Used “firerating” in asentenceat a partyHad to Googlesomething infront of a seniorand pretendedit was ‘just adouble-check.Opened Revitand waited 10minutes justfor the modelto load.Described asmell as“mechanical”Had to explain tosomeone thatyour productdoesn’t defy thelaws ofthermodynamics.Realized toolate that thewall wasstructuralHad to choosebetween twostandards thatcontradicteach other.Done a LightPowerDensityCalculationby handAttendeda designteammeetingAccidentallytaughtsomeoneaboutlumensAccidentallyjoined aTeams callwhile on siteHad no ideawhat anyonewas talkingabout in yourfirst coordinationmeeting.ExplainedMEP to anon‑engineerSpent moretime formattinga drawing titleblock thandoing actualengineering.Lost 2 hoursto a file crashand said ‘It’sfine’ whiledying inside.Heard“Can youmake itsmaller?”Got lostin a plantroomAccidentallymodeled a floorwith no ceilingand wonderedwhy the gainswere so highSpent toolong tryingto model acooling coilUsed Excelas a stressmanagementtoolGot askedfor a ‘quickupdate’ thatturned into afull redesign.Said “lowcarbon” atleast oncetodayGottenconfusedbetweenASHRAE90.1 and 62.1Drew adoodle thataccidentallyturned into aschematicDone aduct sizecalc byhand

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