Buildable {ish}

Everybody needs something on the roof. Mechanical has equipment. Electrical needs conduits. Plumbing needs vents. Architecture wants screens. Structural gets to support all of it. The roof isn't usually the problem. The problem is that everyone assumes someone else coordinated it. In this Scope Gap minisode, Brian and Alex climb onto one of the most crowded and overlooked parts of a building. From equipment supports and conduit penetrations to roof curbs, screens, warranties, and future expansion, they explore why rooftop coordination often falls into the gaps between disciplines—and why those gaps usually show up after the roof is already finished. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠Show Notes The roof assumes: Everyone coordinated their equipment. The penetrations are accounted for. The supports are designed. The future needs were considered. In practice, it becomes: A coordination problem nobody owns. A warranty nobody can maintain. A very expensive core drill. Takeaways: Coordinate rooftop equipment before finalizing layouts. Identify all penetrations, supports, and future expansion needs early. Don't assume another discipline is managing roof coordination. If the roofing contractor is already gone, you're probably out of good options. "The roof problems rarely come from the roof itself. They come from all the decisions that showed up after it was finished." 

Every project starts with a kickoff meeting, a schedule, and a team that swears everything is documented. Then somebody leaves.  Brian and Kyle head into the chaotic world of project handoffs — where meeting minutes vanish, email archives disappear, RFIs are marked resolved without answers, and institutional knowledge walks out the door. From inherited projects and undocumented owner decisions to handoff binders filled with notes that simply say 'See Email,' this episode explores why project transitions can create more risk than the design itself.  If you've ever inherited a project halfway through design, searched years of email chains for answers, or discovered that nobody remembers who approved a critical decision…this one's for you.  Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠Show Notes Chapter 1 – The Exchange Zone • Why project handoffs break down during design • Owner requests that never make it into the drawings • Tribal knowledge versus documented decisions • Managing owner expectations after a PM transition • Why documenting assumptions early matters Chapter 2 – See Email • Deleted inboxes and disappearing project history • Bid logs without context and procurement archaeology • Value engineering decisions nobody remembers making • Personal emails, shared drives, and institutional memory • Why 'See Email' is not a documentation strategy Chapter 3 – Reopening the RFI • Construction-phase handoffs and unresolved issues • RFIs marked closed but never actually answered • How vague contractor questions create expensive misunderstandings • Getting contractor, owner, and design-team buy-in • Resetting expectations when the new PM takes over Chapter 4 – The Binder Trap • Punch lists versus warranty items • Closeout packages that create more confusion than clarity • Live walkthroughs between outgoing and incoming PMs • Collaborative checklists and transition planning • Treating handoffs as a formal project phase Key Takeaways • Assumptions vanish when they are not written down • Project knowledge is often more valuable than project files • Archived emails can save years of confusion and rework • A closed RFI is not resolved unless everyone agrees on the answer • The best handoff is one that happens before someone walks out the door 

Scope Gap is where coordination goes to die.  The concrete isn't usually the problem.  The problem is everything hidden inside it.  In this Scope Gap minisode, Brian and Alex dig into one of the most coordination-heavy elements of any project: the slab on grade. From floor boxes and floor drains to control joints, conduit, reinforcement, and slab depressions, they explore how scope gaps get buried before the concrete truck even arrives—and why those gaps often become demolition plans later. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠Show Notes The slab assumes: Everyone coordinated the utilities. The plumbing elevations are correct. The conduit routing fits. The control joints were coordinated.  In practice, it becomes: A coordination problem nobody owns. A field decision made under schedule pressure. A very expensive concrete saw.  Takeaways: Coordinate utilities before the pour. Verify slab depressions, leave-outs, and floor boxes early. Don't assume someone else owns slab coordination. If the concrete truck is already on site, you're probably out of good options.  "The slab problems rarely come from bad concrete. They come from decisions that never met each other before the pour."  This episode is part of our Scope Gap series – short dives into the spaces between disciplines, responsibilities, and assumptions where construction problems love to hide. 

Every project starts with a clean scope, a reasonable budget, and a confident owner. Then somebody says, “While you’re at it…”  Brian and Alex head into the wild world of scope creep — where one extra office triggers structural redesigns, “future-proofing” quietly doubles costs, and punch lists somehow turn into owner wish lists. From vague contract language and moving project targets to value engineering confusion and last-minute upgrades, this episode explores how projects slowly evolve into something nobody originally agreed to build.  If you’ve ever sat through a meeting where someone casually suggested “just one more change,” watched an RFI become a redesign, or discovered the owner expected something that was never actually in the drawings…this one’s for you. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠Show Notes Chapter 1 – Spotting the Tracks How “small” owner requests snowball into major redesigns Scope creep during programming and schematic design Future-proofing and overdesign that never gets used FCA reports, outdated deficiency lists, and shifting priorities Why documenting assumptions early matters Chapter 2 – Herding Cats with Contracts Vague contract language and “as needed” scope traps Defining deliverables, exclusions, and responsibility gaps clearly Design-build repricing games and constant scope negotiation Pre-engineered building surprises and hidden assumptions Why alternates and allowances need tight definitions Chapter 3 – The Migration of Change Orders Owner walkthroughs and late-stage “minor” changes Unforeseen conditions becoming upgrade opportunities Contractors and subs pushing alternate products midstream Schedule impacts, stacked trades, and morale fatigue Using RFIs and change orders to control scope creep Chapter 4 – Punch List or Safari Cleanup? Punch list items becoming owner upgrade requests Warranty confusion and last-minute “clarifications” Municipal requirements appearing after construction is complete Defining substantial completion clearly Why project autopsies help prevent future chaos Key Takeaways Scope creep rarely starts with huge changes — it starts with vague requests Every project change has cost, schedule, and coordination impacts Documentation and meeting minutes are survival tools Tight contracts and clearly defined deliverables prevent chaos later Lessons learned meetings are one of the best training tools a team can have 

It sounds straightforward — until someone cuts a six-inch hole through the wall and fills it with whatever was in the truck. In this Spec Trap minisode, Brian and Alex dig into one of the most abused phrases in construction documents: “Maintain 1-hour rating.” From mystery firestop materials to field-built “solutions” that were never tested, they break down how vague life safety language creates confusion, failed inspections, and expensive late-stage fixes.  Along the way: Someone uses spray foam where it absolutely should not go. Nobody can find the UL assembly. and a crash-test dummy loses its head in a story neither host will ever forget. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes The phrase assumes: Someone detailed the required assembly. The trades coordinated penetrations ahead of time. Everyone understands the tested firestop system. The installer knows what product belongs there. In practice, it becomes: Oversized penetrations patched in the field. Spray foam and red caulk used as universal repair products. Firestop systems chosen after installation instead of before. Trades assuming “someone else” owns the rating continuity. It often leads to: Failed life safety inspections. Delayed occupancy approvals. RFIs after the wall is already closed. Last-minute patchwork that nobody wants to sign off on.  Takeaways Specify the tested assembly, not just the rating. Coordinate penetrations before rough-in. Clearly define responsibility for maintaining rated assemblies. Require approved firestop systems and inspection documentation. “Maintain 1-hour rating sounds simple — until the inspector asks what UL system you used and the entire room suddenly gets quiet.”  This episode is part of The Spec Trap series — short dives into spec language that sounds professional but quietly causes problems in the field. 

Losing a team member mid-project is frustrating. Losing them along with every design decision they ever made? That’s chaos. Brian and Alex break down what really happens when the “brain trust” leaves the building. From undocumented design intent and mystery file folders to confused clients and shifting specs, this episode dives into how quickly a project can unravel when knowledge isn’t shared. If you’ve ever opened a file labeled “FINAL_v7_forREAL_iMEANit,” tried to decode someone else’s half-finished model, or explained a design decision you didn’t make…this one’s for you. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠Show Notes Chapter 1 – The Vanishing Point Long projects = inevitable team turnover (sometimes multiple times)  Why documenting design intent and decisions early is critical  Meeting minutes and decision summaries (and where AI helps…or doesn’t) Shared file systems, version control, and avoiding “desktop hoarding”  Managing owner expectations and capturing their quirks, preferences, and approvals Chapter 2 – Spec Roulette What changes when someone leaves vs. gets let go mid-project  Keeping specs aligned with original design intent through transitions  The importance of version control and updating bid sets immediately  Documenting vendor quotes and assumptions to avoid surprises later  Maintaining relationships and communicating confidence during uncertainty Chapter 3 – Field Day without a Guide Assigning a new point of contact quickly to keep projects moving  Maintaining RFI and submittal turnaround during team transitions  Avoiding the “check their old emails” trap with inbox triage   Protecting scope in the field when history is unclear  Managing team morale and keeping communication clear on site  Chapter 4 – Punch List or Treasure Hunt? Gaps in drawings and specs that show up late in construction  Verifying installations match submittals and chasing missing closeout docs  Creating “as-constructed” record drawings when design history is incomplete  Rebuilding O&M info and leaning on manufacturer reps  Using post-mortems to understand what went wrong and improve processes  Key Takeaways Document early and often. Design memory fades fast  Assign backups for every critical role and responsibility  Keep files, specs, and drawings organized, dated, and accessible  Manage owner expectations and maintain strong vendor relationships  Recognize team effort and learn from every transition 

It’s in every set of specifications. It sounds official. And somehow… it still gets ignored. In this Hold for Clarification minisode, we dig into the deceptively simple phrase “install per manufacturer.” It’s the catch-all note that’s supposed to ensure systems perform, warranties hold, and safety isn’t compromised. But too often it turns into a free-for-all in the field. From backwards VAV boxes to missing anchors and voided warranties, we break down how skipping the manual leads to expensive mistakes, finger-pointing, and systems that fail when it matters most. Leave feedbackfor Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes The phrase assumes: The manufacturer’s instructions are being read  Installers understand the requirements  Field conditions match tested conditions  Following the manual is non-negotiable  In practice, it becomes: “We’ve always done it this way”  Ignored clearances and access requirements  Backwards equipment installs (yes, really)  Missing anchors, skipped steps, and “good enough” fixes  Takeaways: Require manufacture cut sheets with shop drawings Inspect before concealment (or at least document with photos) Tie installation checks to commissioning and closeout Trust but verify  “Install per manufacturer isn’t a suggestion. It’s the instructions you ignored before it failed.” This episode is part of our Hold for Clarification series – short dives into the phrases that sound helpful but create chaos in construction documents. 

Travel sounds productive, until it isn’t. Brian and Alex break down what really happens when work leaves the office and moves to your connecting gate B7. From missed flights and last-minute decisions in TSA lines to marking up drawings at 30,000 feet, this episode dives into the chaos of trying to stay productive while constantly in transit. If you’ve ever approved something questionable on airport Wi-Fi or taken a coordination call from a Chili’s, this one’s for you. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠ Show NotesChapter 1 – Designing from seat 17B Working from planes, terminals, and wherever you can find Wi-Fi The reality of trying to review drawings mid-flight or between connections Tools that actually help: downloaded files, tablets, portable monitors, and noise-canceling headphones Why “I’ll just do it on the plane” only works if you’re prepared beforehand Security lines, tight connections, and the six-minute airport record Brian proudly holds Chapter 2 – Procurement from the Parking Lot Making real project decisions while distracted or in transit Submittals, material changes, and approvals happening at the worst possible times Missed calls, delayed responses, and the flood of messages after landing The importance of backups, delegation, and out-of-office communication Time zones, scheduling mistakes, and why 8am isn’t always 8am Chapter 3 – Coordination Calls from the Void Taking meetings from airports, planes, and anywhere with signal The illusion of productivity vs. actual focus while traveling Sleep deprivation, rushed decisions, and “I’ll have to look into that” moments Why quick naps and planning ahead matter more than caffeine Setting boundaries so your schedule doesn’t get taken over mid-travel Chapter 4 – Closeout, I Hardly Boarded Ye Delays, missed connections, and the domino effect on project commitments Trying to finish work before boarding (and hearing your name called at the gate) Rental car roulette, travel mishaps, and unpredictable logistics Burnout from constant travel and the importance of downtime Why being physically present on-site still matters, despite all the chaos Key Takeaways Travel multiplies disorganization. Whatever system you have will be tested Preparation is everything: download files, plan ahead, and communicate early Decisions made under travel stress are often the riskiest ones Time zones, delays, and logistics can derail even the best plans Face-to-face interaction on job sites is still incredibly valuable Maintaining flexibility and a sense of humor is essential 

It’s vague. It’s everywhere. And somehow… it always ends up being your problem. In this Hold for Clarification minisode, we unpack the deceptively simple phrase “by others”. It’s the ultimate scope escape hatch that turns responsibility into a guessing game. From missing anchors to design components no one carried, we dig into how two words can create massive gaps in coordination, pricing, and accountability. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠Show Notes The phrase assumes: Everyone knows who “others” are Scope is clearly defined somewhere else Someone else is definitely handling it  In practice, it becomes: A scope dodgeball match A coordination black hole That one detail no one picked up  Takeaways: Name the responsible party Provide design criteria (loads, performance, etc) Cross-reference drawings and specifications If it matters, don’t leave it to “others”  “’By others’ is just the grown-up version of ‘not it’”   This episode is part of our Hold for Clarification series – short dives into the phrases that sound helpful but create chaos in construction documents. 

What happens when beautifully coordinated interiors collide with crooked walls, rogue sprinkler lines, and “it wasn’t in the drawings”? In Part 2 of their conversation with interior designer Emilie Diggs, Brian and Alex head to the job site. From soffit surprises and non-square existing walls to fire protection “no-fly zones,” foam-core mockups, and final punch lists, they unpack how interiors can either rescue a project in the field or get sidelined until it’s too late. If you’ve ever walked a site and thought, “This is not what we designed,” this episode is for you.Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes Chapter 1 – Soffits, Surprises, and Spatial Squeeze Plays Existing walls that aren’t square, plumb, or level and the question of who truly owns layout control When you can’t move structure and must solve problems through finishes and detailing The importance and subtle details of mock-ups “Silent” design drivers and clashes with design features.  Chapter 2 – Welcome to the Waiting Room of Broken Promises Invite interiors to the punch. Closing out complex FF&E Packages Warranty nightmares Key Takeaways Interior designers must be involved throughout construction, not just at the end Existing conditions, especially in renovations, can break a design if no one owns layout control Fire protection, ceilings, and “no-fly zones” demand tight coordination with interiors Mockups can prevent massive change orders and workflow failures Early site visits by interiors catch issues (blocking, outlets, finishes) that are nearly impossible to fix later Clear communication, documentation, and structured choices help guide owners and keep design intent intact 

Interior design isn’t decoration—it’s coordination.  Brian and Alex are joined by interior designer Emilie Diggs to break down what happens when interiors get brought in too late. From undersized rooms and impossible ceiling spaces to VE decisions that gut design intent, this episode explores how poor coordination early creates problems no one can fix later.  If you’ve ever heard “we’re too far along to change it,” this one’s for you. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes Chapter 1 – Interiors as the Afterthought Interiors brought in after layout and structure are already fixed Rooms designed without accounting for real function or furniture Coordination gaps between structure, architecture, and interiors Overlap zones like ceilings and acoustics with unclear ownership  Chapter 2 – FF&E Is Not “Figure It Out Later” Furniture and equipment drive layout, not just finishes Substitutions and “equivalents” that miss design intent Value engineering that removes function, not just cost Long lead items and procurement issues missed in scheduling  Key Takeaways Interiors directly impact function, flow, and user experience Late involvement creates constraints that can’t be solved downstream FF&E should be planned early—not forced in at the end Clear communication prevents most coordination failures Cutting design intent often leads to bigger problems later  Next Episode Part 2 dives into field issues: existing conditions, missed coordination, and everything that “wasn’t in the drawings.” 

You can spot it before you even get out of the truck.  Ducts through beams. Sprinklers fighting light fixtures. Conduit running wherever it feels like. In this Redlines & Regrets minisode, Brian and Alex break down what happens when coordination drawings exist… but nobody actually uses them—and why the field ends up solving problems that should’ve been caught months earlier. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes Classic signs coordination didn’t happen: Ductwork running straight through structure Sprinkler heads perfectly aligned with light fixtures Conduit routed diagonally across everything Soffits that magically appear to hide mistakes  Why it keeps happening: The model exists—but no one references it Trades only review their own sheets Coordination meetings get cut or rushed Schedules prioritize speed over planning Everyone assumes someone else handled it  What it turns into in the field: Emergency huddles around problems that shouldn’t exist Field sketches on drywall scraps and pizza boxes Creative reroutes that wreck performance and clearances Weekend site visits to “approve” what’s already built Change orders for “unforeseen” issues that weren’t actually unforeseen  How to prevent it next time: Make coordination part of the contract—not a suggestion Require composite/overlay drawings before install Get trades involved early in preconstruction Define no-fly zones for each discipline Tie coordination to pay apps and accountability Perform QA/QC before anything gets concealed  Takeaways: Coordination is not optional If no one uses the model, it might as well not exist Field fixes are just expensive versions of missed coordination  “Ignore the model, and you’re building fan fiction—not a building.”  This episode is part of our Redlines & Regrets series—short dives into the mistakes we’ve all seen (and hopefully won’t repeat).

“Per my last email…” — famous last words.  Brian and Alex break down how projects go sideways when emails replace actual documentation. From silent approvals and missing threads to field decisions made over text, this episode dives into why inboxes are not contracts, and how those messages can still come back to bite you. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes Chapter 1 – When Email Becomes Design Design decisions made without drawings or documentation. Missing stakeholders and uncoordinated changes. Decisions made via email instead of formal RFIs or meetings.  Chapter 2 – Procurement by Inbox Misinterpreting “go ahead” vs actual authorization to proceed. Unclear vendor scope and inconsistent pricing assumptions. Risks of proceeding without contracts or purchase orders.  Chapter 3 – Field Direction vs Reality Crews working from emails, texts, and verbal approvals. Conflicts between drawings and unofficial field direction. Need for clear yes/no responses and formal documentation.  Chapter 4 – Closeout and the Email Black Hole Lost warranty info and O&M manuals buried in inboxes. Confusion over final versions and responsibility at turnover. Payment delays tied to missing or undocumented approvals.  Key Takeaways Emails are not contracts. Formal documentation (RFIs, drawings, contracts) is required for decisions. Lack of clarity leads to rework and risk. Assume every email could be read in court. Link to Brian’s article for Steel Erector’s Association of America https://issuu.com/seaa_admin/docs/connector-2010-edition  on pg 58-59 

It sounds like quality control — until someone asks certified by who?  In this Spec Trap minisode, Brian and Alex break down one of the most common and least defined phrases in construction specifications. From expired welding certifications to installers who are “basically certified,” they explore how vague certification language turns quality assurance into RFIs, schedule delays, and paperwork hunts. Leave feedback for Brian and Alex ⁠⁠⁠⁠[email protected]⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠X: ⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes The phrase assumes: Someone defined who the certifying authority is. Certification actually exists for that product. Everyone agrees on what “certified” means.  In practice, it becomes: Expired certification cards from years ago. One “certified” person who isn’t actually on site. Installers claiming certification that no one verified.  It often leads to: Submittals getting kicked back while paperwork is tracked down. Schedule delays when certification cannot be proven. Warranty fights when manufacturers demand proof after installation.  Takeaways Name the certifying authority in the spec. Require proof before installation starts. Define what happens if certification cannot be verified.  “Installer shall be certified sounds solid — until you realize it’s the construction version of ‘must be good with people’ on a job posting.”  This episode is part of The Spec Trap series — short dives into spec language that sounds professional but quietly causes problems in the field. 

It looked perfect in Revit… then the demo started. Brian and Alex dig into what happens when BIM models are built on old drawings, wishful thinking, and unchecked assumptions. From LOD confusion to fabrication finger-pointing and field fixes with a sledgehammer, this episode is your reminder that 3D coordination is not the same as reality. Leave feedback for Brian and Alex ⁠⁠⁠[email protected]⁠⁠⁠ LINKS: Website: ⁠⁠⁠https://buildableish.com/⁠⁠⁠Instagram: ⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠X: ⁠⁠⁠https://x.com/Buildableish⁠⁠⁠LinkedIn: ⁠⁠⁠https://www.linkedin.com/company/buildable-ish/Show Notes Chapter 1 – Trust issue in design Models based on old drawings without field verification. Levels of Development (LOD 300 and beyond) and what they actually include. Why small tolerances and hidden conditions still cause clashes.  Chapter 2 – Fabrication meets Fiction How connected fabrication models reveal design oversights. The risk of unclear responsibility for verifying existing dimensions. A steel fabrication example where incorrect assumptions caused installation failure.  Chapter 3 – Field Clashes and Finger Pointing Conflicting drawing versions with different dimensions and quantities. Coordination breakdowns when documents are reissued without clear revision tracking. The importance of ownership and accountability during installation.  Chapter 4 – The Model vs. the Record Reconciling installed conditions with inspection requirements. The value of maintaining model updates throughout construction. COBie data extraction and how small errors can impact facility operations.  Key Takeaways Verify existing conditions before relying on any model. Define who I s responsible for model accuracy and field verification. Maintain revision clarity and update models during construction. Treat BIM as a coordination tool, not a guarantee of reality. 

It sounds harmless. It’s everywhere. And it’s quietly responsible for RFIs, field rework, and at least one contractor staring out the window questioning their life choices. In this Hold for Clarification minisode, we break down why this catch-all phrase turns clear drawings into scavenger hunts – and how to stop using it as a loophole. Leave feedback for Brian and Alex ⁠⁠[email protected]⁠⁠ LINKS: Website: ⁠⁠https://buildableish.com/⁠⁠Instagram: ⁠⁠https://www.instagram.com/buildableish⁠⁠X: ⁠⁠https://x.com/Buildableish⁠⁠LinkedIn: ⁠⁠https://www.linkedin.com/company/buildable-ish/Show Notes The phrase assumes: Everyone reads every sheet. Everyone understands the note hierarchy. Everyone interprets “otherwise” the same way.  In practice, it becomes: A scavenger hunt. A coordination gamble. A very expensive Saturday.  Takeaways: Be explicit. Call out exceptions clearly. Stop hiding hierarchy in the general notes.  “If your drawings rely on “Unless Noted Otherwise” to hold them together…it won’t.”  This episode is part of our Hold for Clarification series – short dives into the phrases that sound helpful but secretly cause chaos. 

When ducts, lights, sprinklers, and structural all fight for the same ceiling space, someone is losing – and it’s usually the schedule. Brian and Alex break down above-ceiling coordination, BIM promises, and why “it fit in the model” does not mean it will fit in the field. Leave feedback for Brian and Alex ⁠[email protected]⁠ LINKS: Website: ⁠https://buildableish.com/⁠Instagram: ⁠https://www.instagram.com/buildableish⁠X: ⁠https://x.com/Buildableish⁠LinkedIn: ⁠https://www.linkedin.com/company/buildable-ish/Show Notes Chapter 1 – Welcome to the Cage Match How multiple systems compete for limited plenum space. Why above-ceiling coordination becomes a conflict between trades. The role of structure in defining what is physically possible.  Chapter 2 – The Return of the BIM that Lied The difference between modeled coordination and field installation. Assumptions made during design that do not translate on site. Why clashes still occur even after coordination meetings.  Chapter 3 – Who Gets to Win? How the order of installation impacts final layout. What happens when one trade installs before others are ready. The practical consequences of limited space above the gird.  Chapter 4 – Inspections and the Great Hideaway Issues discovered during inspection above the ceiling. Conflicts between installed systems and required clearances. Why above-ceiling problems are difficult to correct late in the game.  Key Takeaways Above ceiling space is critical infrastructure, not leftover volume. BIM coordination is only as good as the assumptions behind it. Field sequencing decisions can undo months of design effort. The earlier the coordination, the fewer ceiling-tile casualties. Keywords: Buildableish, Buildable, Buildable ish, Buildable(ish), Buildable (ish)

Welcome to Buildable {ish}! A podcast about the messy, maddening, and occasionally miraculous process of turning drawings into buildings. In this episode, your hosts Brian and Alex are setting expectations about what we’re here to talk about. We’re not doing leadership lessons from your C-suite or perfect hindsight from the guy who’s never worn a hard hat. We’re breaking down real life project problems from design to construction, with the field fixes, scope gaps, and “how did this get approved?” moments that actually happen on site. And yes, we’re going to laugh about it, because if you don’t laugh in this industry, you’ll cry. Leave feedback for Brian and Alex [email protected] LINKS: Website: https://buildableish.com/Instagram: https://www.instagram.com/buildableishX: https://x.com/BuildableishLinkedIn: https://www.linkedin.com/company/buildable-ish/Keywords: Buildableish, Buildable, Buildable ish, Buildable(ish), Buildable (ish)