Deliberate Words

This Deliberate Words episode captures a lively conversation between Dave Stutzman and Steve Gantner of Conspectus and their guest, Tucker Beech, a third-year (of six) Drexel architecture student who first connected with Dave after he guest-spoke to a Drexel class about specifications.

Tucker shares the origin story of her architecture obsession, from a custom-built childhood home and a fifth-grade “intro to architecture” project (complete with a too-small-to-compete fire station model) to being inspired by travel and historic architecture in Europe. She talks candidly about what architecture school is really like, pushing back on the all-nighter myth and emphasizing time management, work-life balance, and personal safety when commuting late in Philadelphia.

A key theme is humility and learning from others. Tucker recounts advice from an architecture camp: never assume you know more than the people doing the work around you. Steve reinforces it with a story from his father (a bricklayer) and explains how that mindset shaped his approach to construction administration.

Professionally, Tucker is exploring “architecture-adjacent” paths that still use her strengths, especially building codes, specifications, and technical observation. She lights up describing how specs let you read a room through details (like recognizing an acoustically sensitive space by door hardware), and the group connects the dots between code knowledge and strong spec writing. Steve encourages her to take business classes if possible, noting how valuable that foundation is in practice.

The episode also has plenty of personality: a running gag about technical glitches, a spirited “cheese drawer” debate (Midwest pride), and Tucker’s other signature interests (dogs, ducks, pumpkins, and dreams of pumpkin chunking with trebuchets).

They close with the show’s “five words or less” question. Tucker’s answer: “providing hope, safety and security to all.” She ties it back to her goal of eventually designing residential projects that give others the same sense of belonging she felt growing up. Dave and Steve wish her luck, invite her to stay in touch with spec questions, and give a light-hearted “hire Tucker” shout-out to listeners in the Philadelphia area.

Steve Gantner, Elias Saltz, and Tina Montone attended the CURT National Conference in Orlando, Florida in early February 2026 and returned with a clear throughline from the conversations taking place across the conference. In this discussion with Dave Stutzman, they reflect on how AI, data centers, power infrastructure, and construction productivity are no longer separate topics, but deeply interconnected forces shaping the future of project delivery.

As data centers continue to be built at unprecedented speed, demand for reliable, redundant power is rising just as quickly. At the same time, AI is emerging as a practical tool to improve construction productivity not by pushing crews to work faster, but by reducing rework, improving information flow, enhancing safety, and accelerating knowledge transfer across generations.

Despite the momentum, significant challenges remain. Regulatory complexity, labor shortages, and long-term declines in U.S. construction productivity continue to strain the industry. A consistent theme throughout CURT was the need for earlier collaboration and better alignment of data across design, construction, and procurement as a pathway to reducing inefficiencies and building long-term industry resilience.

Key Takeaways

• Industry Insight:
  AI, data centers, power availability, and construction productivity are no longer separate issues, they are part of a single, interdependent system shaping project delivery.
• Practice Takeaway:
  Productivity gains will come less from working faster and more from eliminating rework, improving information accuracy, and getting the right data to the right people earlier.
• Process Lesson:
  Early alignment of design, construction, and procurement data is essential to reducing RFIs, delays, and downstream inefficiencies.
• Risk or Opportunity:
  AI presents a significant opportunity to offset labor and productivity challenges, but only if paired with reliable power infrastructure and disciplined implementation.
• People & Culture:
  Technology will not replace experience; the real value lies in using AI to capture, transfer, and amplify human expertise across generations.

In this episode, Dave Stutzman, Steve Gantner, and Elias Saltz tackle a deceptively simple question that carries real contractual risk: Where should reference standards live in the specifications, and should they be dated?  Reference standards belong in Part 2 of the technical sections, not in consolidated lists. Avoid listing dates unless a specific edition is required by code. Rely on Division 01 Quality Requirements to govern which standards apply. Saying things once, in the right place, reduces conflicts, RFIs, and unnecessary risk.

• Industry insight: Reference standards create more risk through duplication and dating than through omission when they are not placed intentionally.
• Practice takeaway: Keep reference standards in Part 2 of technical sections and let Division 01 govern applicability to avoid conflicts.
• Process lesson: Saying things once, in the right place, is the simplest way to improve clarity and reduce downstream rework.
• Risk or opportunity: Eliminating dated, consolidated reference lists reduces RFIs and protects the contract from unnecessary ambiguity.
• People & culture: Good specifications reflect disciplined thinking, shared responsibility, and respect for how teams actually use the documents.

A conversation captured at the Construction Users Round Table.

CURT members don’t gather to admire the industry as it is, we gather to challenge it. Throughout the year, owners come together to wrestle with contracting strategies, team dynamics, technical risk, global pressures, and the realities shaping how projects actually get delivered.

This is the Deliberate Words podcast, In this episode, I’m filling in for David Stutzman and joining Steve Gantner, leaders in Conspectus, the specification company….where words have a power that can create trust, transparency, and transform the process and can significantly impact the success of a construction project and team!

At the September 2025 member meeting, we had the opportunity to bring The immersive collaborative experience to the room. LEGO bricks on the table, assumptions off the table. What followed wasn’t just a workshop, it was dialogue. Candid. Constructive. Occasionally uncomfortable in the best way.

Sitting down afterward with CURT members: Herb Strong of HazTek, Andy Browning and Fred Marsh of Duke Energy, and Nicholas Johnson of Kahua as participants, critics, colleagues, and friends reminded us why these conversations matter. As presenters, the feedback was invaluable. As CURT members, the reflection was even more powerful.

And this is just the beginning.

Next up: the CURT National Conference in Orlando, February 3rd. The conversations continue and only get better.

In this week's episode, Dave Stutzman, Steve Gantner, and Elias Saltz unpack a deceptively simple question with serious implications: Why don’t we recommend requiring manufacturer instructions as a submittal? What follows is a candid discussion on liability, means and methods, and the unintended consequences of asking for information that design teams neither control nor should be reviewing during construction. From informational submittals to samples that add little value, the team reinforces a core principle of good specification practice: clarity during design reduces risk, rework, and unnecessary burden during construction administration.

Learning Points:

• Requesting manufacturer instructions as a submittal can increase architect liability, even if reviewed “for record only.”
• Simply receiving information implies responsibility to review, identify errors, and act on them.
• Manufacturer instructions fall squarely within contractor means and methods, not design review.
• Submittals are not contract documents and should not be used to tweak design decisions late in the process.
• Fewer, more intentional submittals save significant time and cost during construction administration.
• Product compatibility issues must be resolved during design, not after bidding or procurement.
• Over-specifying submittals often exceeds realistic CA budgets and site observation scope.
• Clear specifications reduce change orders, finger-pointing, and downstream risk.

This episode is sparked by a simple question that opened a much bigger reflection: why Conspectus started, and how it became what it is today as the firm enters its 33rd year. David Stutzman shares how the company was born out of economic uncertainty in the early 1990s, when necessity, planning, and a leap of faith converged into a new kind of specification practice. The conversation traces the firm’s evolution from a one-person operation to a multi-disciplinary team, highlighting how organic growth, culture fit, and relationships shaped that journey. It also explored the intentional five-year succession plan now nearing completion, showing how shared leadership has eased pressure while sustaining momentum. The discussion ultimately tied growth, technology, and people together as drivers of more resilient firms and better project outcomes.

Learning Points

• Industry insight: Independent specification consulting has matured from solo practices into scalable, collaborative firms.
• Practice takeaway: Sustainable growth often comes from relationships and timing, not rigid expansion plans.
• Process lesson: Gradual succession planning allows knowledge transfer without overwhelming new leadership.
• Risk or opportunity: Investing in internal tools can evolve into platforms that strengthen both services and business development.
• People & culture: Hiring for fit and capability, rather than preset criteria, builds resilient and diverse teams.

In this year-end episode, the Conspectus team (David Stutzman, Elias Saltz and Steve Gantner) reflect on the signals, surprises, and steady momentum that defined 2025 while looking ahead to what 2026 may hold. Despite mixed economic indicators, Steve & Elias observed increased proposal activity, strong demand in sectors like data centers, logistics, healthcare, and multifamily housing, and a continued rise in design-build delivery.

Conferences—particularly DBIA (Design Build Institute of America) —highlighted growing industry alignment around early collaboration, UNIFORMAT-based thinking, and clearer documentation of design intent. The conversation also underscored the importance of people: emerging professionals, cross-discipline partnerships, and a shared commitment to strengthening the specification community so projects better serve owners’ goals and business cases.

Learning Points

• Market signals don’t tell the whole story: Even with a negative ABI (Architectural Billing Index), proposal requests and active projects increased across several sectors.
• Design-build continues to gain traction: Growth in DBIA membership and RFPs (request for proposals) reflects a broader shift toward earlier contractor involvement and cost-informed design decisions.
• Early communication protects design intent: Regular design updates paired with contractor feedback help maintain alignment between intent, budget, and constructability.
• Next-generation talent is a bright spot: Students and young professionals are entering the industry with curiosity, advocacy, and a desire to improve how buildings are delivered—not just designed.
• Specifications are expanding in scope and influence: Adding engineering expertise and strategic partners enables more comprehensive, coordinated, and current project documentation.
• Collaboration reduces downstream risk: Contractor-driven requests around BABAA (Build America, Buy America Act) compliance revealed the need to address regulatory and sourcing requirements earlier in the process.
• A connected community is the goal for 2026: Stronger relationships among owners, designers, contractors, specifiers, and manufacturers lead to better outcomes—and better repeat projects

This episode dives into a raw and timely conversation sparked by changes to federal student loan caps and the emotional response they triggered within the architectural community. Guest, and Conspectus specifier from VA, Hana Nguyenky, unpacks why the debate struck such a nerve, arguing that the real issue isn’t whether an architecture degree is labeled “professional,” but whether the profession is willing to confront the growing disconnect between education costs, licensure paths, and financial reality.

The discussion exposes deep frustrations around identity, value, and fairness in architecture, questioning long-held assumptions about schooling, professional status, and success. Rather than offering easy answers, the episode challenges listeners to sit with the discomfort and consider whether defending tradition is distracting the industry from addressing access, equity, and long-term sustainability.

Specs Beyond Borders explores what it really takes to deliver construction specifications on large, globally distributed projects. In this episode of Deliberate Words, senior specifier Jim Robbins joins hosts Dave and Steve to share lessons learned from coordinating complex documentation across multiple time zones, design firms, and project packages.

From managing communication hierarchies and maintaining consistency across dozens of deliverables to navigating metric conversions, performance-based specifications, and evolving collaboration workflows, Jim offers practical insight into how international work magnifies the everyday challenges specifiers face. The conversation highlights why early coordination, clear expectations, and adaptability are essential tools for success—no matter where a project is located. 

 This episode tackles confusion around roofing sustainability metrics. Steve breaks down the difference between solar reflectance (SR), emissivity, and solar reflectance index (SRI), explaining how SR and emissivity work together to calculate SRI and why mixing all three in a specification can create conflicts. The team discusses how different programs like LEED, ENERGY STAR, and CalGreen use different metrics, which fuels misunderstanding. The takeaway: understand which system applies, say it once in the right place, and use tools like the Lawrence Berkeley National Lab SRI calculator to clarify data gaps and keep specs aligned with performance goals.