Buildable {ish}

Brian and Alex

A smart, funny podcast cohosted by a structural engineer and a project manager – two professionals who live day-to-day in construction coordination. We take a candid, smart, and often humorous look at what really happens between design intent and finished construction. Each episode breaks down a common project challenge; misaligned specs, missing details, inspection surprises, field fixes, and the infamous “that wasn’t on the drawings” moment. Keywords: Buildable, Buildableish, Buildable ish, Build, Buildable(ish), Buildable (ish)

  1. 6d ago

    History Under Construction

    Show Description Just because a building is old enough to collect Social Security doesn’t mean it’s historic. But who decides what’s worth preserving? And why can replacing a window turn into a neighborhood civil war? Brian and Alex welcome historic preservation planner Martha Lauer to explore the complicated world of historic buildings, property rights, preservation commissions, and the challenges of bringing yesterday’s architecture into today’s world. From controversial modern homes in historic neighborhoods to moving entire houses, repairing century-old masonry, and navigating preservation rules, this episode explores what happens when history, engineering, and public opinion collide. Because sometimes the hardest part of restoring an old building isn’t the building. It’s getting everyone to agree on what should be saved. Show Notes Chapter 1 – History Isn’t Frozen. It’s Negotiated. What makes a building historic—and why age alone isn’t enoughNational Register recognition versus local historic designationHow communities decide which buildings and neighborhoods deserve protectionPreserving architectural character without freezing buildings in timeMoving historic houses and balancing authenticity with modern needs Chapter 2 – Private Property Meets Public Interest When property rights collide with historic preservation regulationsMartha’s firsthand account of a controversial new home in a historic neighborhoodPreservation commissions, design guidelines, public hearings, and appealsWhy windows, rooflines, setbacks, and even trees can become battlegroundsThe complications of neighboring properties, historic districts, and redevelopment Chapter 3 – Building Yesterday with Today’s Tools Repairing historic buildings using modern materials and construction techniquesThe difference between preserving original construction and recreating historic appearancesWhy pressure washing old brick or using the wrong mortar can cause serious damageBalancing accessibility, energy efficiency, building codes, and preservationAdaptive reuse, tax credits, and repurposing historic structural elements Chapter 4 – Lessons Learned: Preserving the Past Without Losing the Future Understanding a building’s significance before developing renovation plansCoordinating early with preservation commissions and experienced craftspeopleManaging owner expectations, budgets, schedules, and unexpected conditionsWhy preservation often requires creativity, compromise, and patienceRemembering that historic preservation is about stewardship, not simply nostalgia Key Takeaways Old doesn’t automatically mean historic. Significance, context, and integrity matter.National recognition and local historic designation are not the same thing.Preservation doesn’t necessarily mean using obsolete materials or construction methods.Early coordination with preservation officials can prevent expensive redesigns and delays.Successful preservation balances history, safety, functionality, and the needs of future generations. Links & Contact Website – www.buildableish.com Email – brian@buildableish.com LinkedIn – Buildable(ish) Instagram – Buildable(ish) X – @Buildableish Martha Lauer | LinkedIn

    History Under Construction
  2. Nov 4 ·  Bonus

    Hold for Clarification: Standard of Care

    Show Description  “That’s not how I would have designed it.”  Five words that can turn a perfectly reasonable design into an argument about professional negligence.  But different doesn’t automatically mean wrong, and the professional standard of care isn’t a promise of perfection.  In this Hold for Clarification minisode, Brian and Alex explore what the standard of care actually means, why mistakes aren’t automatically negligence, and how seemingly harmless contract language can create obligations no reasonable architect or engineer should promise to meet.  Because there’s a big difference between exercising professional judgment and guaranteeing you’ll never make a mistake.  Show Notes  The Standard of Care means:  Exercising the reasonable skill and care expected of similarly situated professionals.  Evaluating decisions based on the circumstances, not hindsight.  Recognizing that more than one design solution may be acceptable.  Where things go wrong:  Design preferences get mistaken for deficiencies.  Every error gets labeled professional negligence.  Contracts promise perfection or error-free documents.  Expectations exceed the ordinary professional standard of care.  Takeaways:  Different doesn’t automatically mean defective.  A mistake isn’t necessarily negligence.  Code compliance alone doesn’t establish that the standard of care was met.  Professional judgment matters more than personal preference.  Never casually contractually guarantee perfection.  “The standard of care doesn’t require you to be perfect. It requires you to be reasonably competent. Apparently, that’s still open to interpretation.”  This episode is part of our Hold for Clarification series—short dives into the words and phrases we hear every day in design and construction that sound straightforward but often create confusion, coordination issues, and costly mistakes.  Leave Feedback for Brian and Alex  brian@buildableish.com  Follow Us On  LinkedIn – Buildable(ish)  Instagram – Buildable(ish)  X – @Buildableish

    Hold for Clarification: Standard of Care
  3. Oct 28

    Chiller Plant Surgery

    Show Description  “We’re just replacing a couple of chillers.” Famous last words.  A chiller plant is the mechanical heart of a building. Replacing it while the building is still occupied is a little like performing open-heart surgery without putting the patient to sleep. The equipment is enormous, the systems are interconnected, and somebody inevitably discovers a valve that doesn’t do what everyone thought it did.  Brian and Alex are joined by mechanical engineer Scott, who brings decades of chiller plant construction and design experience, to unpack what really happens when major cooling equipment needs to be replaced. From temporary systems and carefully staged shutdowns to equipment access, long lead times, pressure-testing mishaps, and an unforgettable NASA chiller story, they explore why “just swap it out” is rarely a plan.  If you’ve ever tried to renovate a critical facility without interrupting operations—or trusted an existing drawing a little too much—this one’s for you.  Show Notes  Chapter 1 – The Building’s Beating Heart  What a chiller plant actually does—and why it matters to the whole building  Why critical facilities depend on reliable cooling and redundancy  The difference between replacing equipment and replacing an interconnected system  How the “open-heart surgery” analogy becomes painfully accurate  Chapter 2 – You Can’t Just Turn It Off  Planning shutdowns around occupied buildings and ongoing operations  Temporary cooling, bypasses, and maintaining service during construction  Coordinating equipment selection, access, rigging, and piping connections  Long lead times and the consequences of decisions made too late  Chapter 3 – What Could Possibly Go Wrong?  Existing conditions and piping that do not match expectations  Valves, isolation plans, and the hazards of opening a system too soon  Pressure-testing surprises and why water finds the weakest point  A NASA chiller, a mysterious rattle, and an expensive mechanical lesson  Chapter 4 – Lessons from the Operating Room  Why sequencing and controls belong in the conversation early  How design and construction experience inform better decisions  The importance of field verification, communication, and contingency planning  Why successful chiller replacements depend on the entire project team  Key Takeaways  A chiller replacement is a building-operations project, not merely an equipment swap.  Temporary systems, shutdown sequencing, and control strategies must be planned together.  Existing piping and valve conditions need verification before anyone commits to a shutdown.  Equipment access, lead times, and construction logistics can drive the entire project.  Good coordination keeps the building running—and prevents expensive surprises.  Links & Contact  Website – www.buildableish.com  Email – brian@buildableish.com  LinkedIn – Buildable(ish)  Instagram – Buildable(ish)  X – @Buildableish

    Chiller Plant Surgery
  4. Oct 21 ·  Bonus

    Scope Gap: Housekeeping Pads

    Show Description Six inches of concrete. Six disciplines of denial. Housekeeping pads sound simple—until nobody knows who owns them. Brian and Alex dig into missing details, late equipment submittals, anchorage headaches, frost-depth surprises, and how a $500 pad becomes a five-figure coordination problem. Show Notes Who owns the pad? Mechanical identifies the equipment; architecture and structural coordinate its location and details—or assume someone else did.Equipment substitutions can turn a generic pad detail into an RFI.When a pad becomes a foundation Equipment loads, vibration, anchor embedment, and elevated slabs can require structural evaluation.Exterior pads may need frost protection and foundations—not just more concrete.The construction-phase surprise Changes to pad size or height affect drains, piping, clearances, and schedules.The concrete is cheap. Redesign, delays, and change orders are not.Key Takeaways Identify pad ownership early and coordinate across disciplines.Verify actual equipment loads, dimensions, anchorage, and support conditions.Solve design gaps before the concrete truck arrives. “The only thing harder than getting six inches of concrete poured is getting six design professionals to agree whose job it was.” Links & Contact Send your scope-gap stories and feedback:brian@buildableish.com Apple Podcasts:https://podcasts.apple.com/us/podcast/buildable-ish/id1869438323 Spotify:https://open.spotify.com/show/2mrLDMHmM9RuuSFfWpwwVH Follow Buildable(ish) on LinkedIn, Instagram, and X(@Buildableish). #Buildableish #ScopeGap #HousekeepingPads#StructuralEngineering #ArchitectureEngineering #ConstructionCoordination

    Scope Gap: Housekeeping Pads
  5. Oct 14

    Standard Details; The Most Dangerous Sheet in the Set

    Show Description The detail says “typical.” The building says otherwise. And somehow, the contractor is supposed to make it work. Brian and Alex take on standard details—the familiar sheets that make a drawing set look complete, even when the details have nothing to do with the building being designed. A wood-framed project somehow generates a welded steel moment-connection submittal. The question from the field? Where exactly are we supposed to weld it? From a Louisiana healthcare facility devastated by water infiltration tied in part to a misapplied roof-edge detail to obsolete manufacturers, decades-old welding references, and a wall section reportedly used as a floor detail, they explore how “we’ve always used it” becomes a very expensive design criterion. They also dig into what happens when typical details ignore installation sequence, trade interfaces, tolerances, and the actual conditions in the field—and why “contractor to coordinate” is not a substitute for design. Because standard details are useful. Unquestioned standard details are dangerous. If you’ve ever found a detail in your set and wondered which project it escaped from…this episode is for you. Show Notes Chapter 1 – Copy, Paste, and Pray · Why old CAD and Revit detail libraries keep getting carried forward without meaningful review. · The Louisiana roof-edge detail that contributed to severe water infiltration in an evacuated healthcare facility. · The manufacturer named in a detail that had been out of business for more than 15 years. · How changing codes, materials, and building assemblies make once-valid details obsolete. · Why a full sheet of details can create an illusion of coordination. Chapter 2 – Field Meets Fiction · A steel connection detail on a building without structural steel—and the resulting fabrication submittal. · Welding requirements referencing a 1981 code long after construction practices had changed. · The story of a wall section reportedly applied as a floor detail. · Why “typical” gets treated as universal when conditions and interfaces vary. · Constructability problems involving trade conflicts, tolerances, tools, and installation sequence. Chapter 3 – The Gap Nobody Owns · What happens when the drawings, specifications, and actual construction conditions disagree. · How vague notes such as “contractor to coordinate” shift questions without resolving them. · Why “unless noted otherwise” does not identify where a typical detail truly applies. · How unresolved assumptions become RFIs, field fixes, change orders, and disputes. Chapter 4 – Standardize Smarter · Audit standard detail libraries instead of treating them as permanent, approved content. · Assign ownership and update details for current codes, products, and construction methods. · State the conditions and limitations for using each detail. · Coordinate across disciplines and review details for actual constructability. · Capture field corrections so the same mistake does not become next year’s standard. Key Takeaways · A standard detail is a starting point—not proof that it belongs on the project. · “Typical” does not eliminate the need to verify geometry, materials, codes, and interfaces. · A detail can be perfectly drafted and completely wrong for the building. · If a field fix exposes a library problem, correct the library—not just the project. · Standardize the process of checking details, not the habit of copying them. Links & Contact Listen: Apple Podcasts – https://podcasts.apple.com/us/podcast/buildable-ish/id1869438323 Spotify – https://open.spotify.com/show/2mrLDMHmM9RuuSFfWpwwVH?si=4c57b988b1174f1d Website: https://buildableish.com Follow and share Buildable (ish) on X, LinkedIn, and Instagram.

    Standard Details; The Most Dangerous Sheet in the Set
  6. Oct 7 ·  Bonus

    Hold for Clarification: See Architectural

    “See Architectural.”Two words. Three disciplines. Zero answers.In this Hold for Clarification minisode, Brian and Alex follow one of the AEC industry’s favorite coordination loops: Structural says see Architectural, Architectural says see Mechanical, and Mechanical sends you right back toStructural.From a housekeeping pad that nobody quite owned to an RFI for a duct penetration that spent a week circulating between disciplines, they look at when a cross-reference actually helps—and when it becomes a polite way to avoid making a decision.Because a good reference should lead to an answer, not a scavenger hunt. And coordination by RFI referral is not coordination. Leave feedback for Brian and Alex brian@buildableish.com Follow us on LinkedIn – Buildable(ish)Instagram – Buildable(ish)X – @Buildableish Show Notes When “See Architectural” Works Across-reference should point to information clearly owned by another discipline.Reference an exact sheet, detail, section, note, or schedule—not an entire drawing set.The reference should make the next step obvious and preserve the design intent. When the Reference Becomes a Roundabout Structural → Architectural → Mechanical → Structural: everyone provides direction, but nobody provides the answer.A housekeeping pad exposes the gray area between equipment requirements, room layout, and structural support.An unanswered coordination item becomes an RFI, then a schedule problem, then potentially a change-order discussion. Who Actually Owns It? Most coordination failures live at discipline boundaries where ownership was never made explicit.Assign responsibility for overlap items early and resolve the gray areas during coordination meetings.Project managers should treat unresolved references as project risks and close the loop before construction. Takeaways Use specific references that lead to actual information.Do not use a cross-reference to transfer responsibility or postpone a decision.Coordinate internally before issuing an RFI response involving multiple disciplines.Ask whether a contractor—or a fresh set of eyes—could actually build from the information provided.If you would not want the note quoted back to you in an RFI six months later, resolve it now. “Am I helping someone find information, or am I helping myself avoid a decision?” This episode is part of our Hold for Clarification series – short dives into the phrases that sound helpful but create chaos in construction documents.

    Hold for Clarification: See Architectural
  7. Sep 30

    Submittals are Approval Theatre

    Show Description “You approved it.” Few phrases make a design professional regret picking up the phone faster. Brian and Alex take on submittals—the supposedly straightforward process of confirming that what the contractor intends to provide is consistent with thedesign. Except somewhere between “reviewed,” “approved as noted,” and “no exceptions taken,” a review stamp can start to look a lot more powerful than it actually is. From delegated design packages missing critical criteria to substitutions that are only spiritually similar to the specified product, they explore how incomplete information, strategic highlighting, schedule pressure, and scope gaps turn submittal review into approval theatre. They also dig into what happens when the material is already on site—or worse, already installed—before anyone finishes asking whether it actually works. Because submittals are supposed to verify the design, not finish it. And a stamp doesn’t make it right. It just makes it traceable.  Links & Contact Website– buildableish.comEmail – brian@buildableish.comLinkedIn – Buildable(ish)Instagram – Buildable(ish)X – @Buildableish Show Notes Chapter 1 – What Did We Actually Approve? What submittals are supposed to do—and why they are verification tools, not another design phase.The difference between “approved,” “reviewed,” and “no exceptions taken.”Why a review stamp does not transfer responsibility for every dimension, connection, and detail.Delegated design and the importance of clearly defining loads, criteria, interfaces, and design intent.What happens when the submittal exposes information that should have been resolved in the construction documents.  Chapter 2 – Where It Starts to Drift Vendor substitutions that look close enough until someone checks the thickness, installation method, maintenance requirements, or downstream impacts.“Strategic submittals” that highlight favorable information while leaving critical loads, dimensions, connections, or clearances unresolved.Why missing information cannot simply be filled in with assumptions.Scope gaps hiding at the interfaces between equipment, supports, structure, and other trades.How “we need this today” turns schedule pressure into review pressure.  Chapter 3 – Where It Breaks The inevitable field response: “But we built what you approved.”What happens when a missing dimension gets filled in during construction instead of clarified during review.Materials arriving—or being installed—while the submittal is still under review.Why retroactive approval changes the question from “Is this correct?” to “Can we live with what is already here?”How discipline-by-discipline reviews can miss the coordination problem between them.  Chapter 4 – Beyond the Stamp Define exactly what the review covers and use consistent response language.Do not rely on submittals to complete an unfinished design.Review for coordination—not just technical compliance within one discipline.Reject incomplete submittals instead of allowing the schedule to manufacture an approval.Document changes outside the submittal process when they modify the actual design.  Key Takeaways Submittals are verification tools, not design tools.A review stamp does not make incomplete information complete.Schedule pressure should not determine technical acceptance.Delegated design still requires clear design criteria and coordination with the Engineer or Architect of Record.\If something matters, show it, coordinate it, and document it.A stamp doesn’t make it right. It just makes it traceable.

    Submittals are Approval Theatre
  8. Sep 23 ·  Bonus

    Redlines & Regrets: Dig Here

    Show Description “The survey covered it.” Four words that can get very expensive once somebody starts digging. In this Redlines & Regrets minisode, Brian and Alex dig into surveys, assumptions, and the dangerous gap between what a survey actually investigated and what everyone assumes it investigated. From utility survey quality levels and buried limitations to a geotechnical boring that found an eight-inch water main the hard way, they look at what happens when confidence replaces verification. Because a completed survey does not mean a complete understanding of the site—and the ground doesn’t care what everyone assumed. Listen here: Apple Podcasts: https://podcasts.apple.com/us/podcast/buildable-ish/id1869438323 Spotify:https://open.spotify.com/show/2mrLDMHmM9RuuSFfWpwwVH?si=4c57b988b1174f1d Show Notes Signs you may be digging on an assumption: Everyone says “the survey covered it,” but nobody has read the scope.Missing information is treated as proof that nothing is there.Designers, contractors, and owners assume someone else verified the critical information.Survey limitations and exclusions never make it past the report. Why it happens: Different surveys answer different questions.Budget, schedule, technology, and investigation methods limit what can actually be found.Survey scope gets lost as information moves between owner, consultant, designer, and contractor.Confidence grows each time the information changes hands—even when verification does not. What happens in the field: A geotechnical boring finds an eight-inch water main that wasn’t shown.An excavator finds a buried gas line with a metallic “tunk” and a very loud whistle.Repairs, traffic control, delays, meetings, and finger-pointing replace the original project plan.Everyone finally reads the scope after the damage is done. Takeaways: Define the survey scope around what the project actually needs.Read the report, not just the exhibit.Understand what was investigated—and what was not.Verify critical information before excavation, not during it.Design with the information you have, not the information you wish you had. Lesson Learned: Don’t confuse a completed survey with a complete understanding of the site. This episode is part of our Redlines & Regrets series—short stories from the field where small oversights become expensive lessons. Each episode explores real coordination failures, design decisions, and construction missteps so you don’t have to learn them the hard way. Leave feedback for Brian and Alex brian@buildableish.com   Follow us on LinkedIn – Buildable{ish} Instagram – Buildable{ish} X – @Buildable{ish}

    Redlines & Regrets: Dig Here

Ratings & Reviews

5
out of 5
11 Ratings

About

A smart, funny podcast cohosted by a structural engineer and a project manager – two professionals who live day-to-day in construction coordination. We take a candid, smart, and often humorous look at what really happens between design intent and finished construction. Each episode breaks down a common project challenge; misaligned specs, missing details, inspection surprises, field fixes, and the infamous “that wasn’t on the drawings” moment. Keywords: Buildable, Buildableish, Buildable ish, Build, Buildable(ish), Buildable (ish)

You Might Also Like