Deliberate Words

This episode reframes supply chain not as a downstream construction issue, but as a design constraint that must be addressed early. Late-stage decisions on equipment and systems often collide with real-world lead times, forcing redesign, substitutions, and schedule impacts. The discussion highlights how integrating market awareness, contractor input, and early equipment selection into the design process can reduce uncertainty and improve alignment. Strategies such as pre-purchasing and locking in long-lead items shift risk forward, allowing the rest of the design to develop with clarity. The takeaway: when supply chain is treated as a design input, not a surprise, projects are better positioned to meet schedule, budget, and performance goals.

Learning Points

Industry insight:
Supply chain challenges can be the result of late design decisions, shifting the burden from design teams to contractors during construction.

Practice takeaway:
Identify long-lead items early and consider strategies such as pre-purchasing or early procurement to maintain project schedules.

Process lesson:
Engaging contractors and leveraging their knowledge of market conditions during design improves decision-making and reduces uncertainty.

Risk or opportunity:
Failing to address supply chain constraints early can lead to redesign, delays, and cost escalation, while proactive planning creates opportunities for schedule and budget control.

People & culture:
Stronger collaboration between designers, contractors, and owners early in the process leads to more informed decisions and better project outcomes.

This episode dives into the familiar specifier experience of going down the research rabbit hole, or as the team calls it, “squirreling.” What starts as a simple product lookup can quickly turn into chasing ASTM references, code citations, performance data, and manufacturer documentation that leads in unexpected directions. Product research used to be limited to curated catalogs, while today’s unlimited online access makes it easy to keep digging long past the original question. Deep research builds expertise, but it can also consume time and distract from decision-making. Dave, Steve & Elias share how these detours often uncover useful knowledge that benefits other projects and reinforces the specifier’s role as a technical resource. The takeaway is not to avoid “squirreling,” but to recognize when it’s productive learning and when it’s simply wandering.

Learning Points

Industry insight:
Product research has expanded dramatically with online resources, increasing both opportunity and information overload for design and specification teams.

Practice takeaway:
Start product research with trusted directories like 4specs.com, the Specifier Portal, or known sources to avoid unnecessary time spent chasing irrelevant information.

Process lesson:
Following references such as ASTM standards and code citations can reveal critical requirements, but teams should define when research has reached sufficient depth for decision-making.

Risk or opportunity:
Excessive research can delay progress, yet strategic “squirreling” builds knowledge that improves future specifications and problem-solving.

People & culture:
Specifiers often serve as knowledge hubs for project teams, using accumulated research experience to guide architects, engineers, and owners toward informed decisions.

This episode explores a recurring request from design teams: generating submittal, QA, and other specification-based reports. The discussion questions the actual purpose of these reports and whether they provide meaningful value. While potential uses include internal review of required submittals or cross-checking contractor submissions, the conversation highlights significant challenges. Inconsistent formatting across consultant specifications, variations in CSI section organization, and reliance on automation all make accurate report generation difficult. The team also considers whether AI could extract submittal data, but notes similar reliability concerns. Ultimately, the episode raises a larger issue: relying on reports as shortcuts may discourage teams from actually reading the specifications. The conversation ends with an open challenge to the industry to reconsider why these reports are requested and whether they truly improve project outcomes.

Learning Points

Industry insight:
Requests for submittal and QA reports are common, but the intended purpose and value of these reports are often unclear.

Practice takeaway:
Before generating specification-based reports, teams should define how the information will be used and whether it improves coordination or decision-making.

Process lesson:
Automated report generation depends on consistent formatting across specifications, which is difficult to achieve when multiple consultants contribute content.

Risk or opportunity:
Using reports as checklists outside the specifications may discourage thorough review of the actual project requirements and lead to missed coordination issues.

People & culture:
Questioning long-standing practices, such as requesting submittal reports, encourages more thoughtful workflows and better engagement with the specifications.

Design intent is the governing framework of a project, yet it is often compromised as it moves from concept through construction.

In this episode of Deliberate Words, Ben Caldwell, Director of Specifications at the Bjarke Ingels Group (BIG), joins Dave and Steve for a discussion on how design intent can be systematically preserved through documentation, alignment, and early-stage decision-making.

The conversation examines the role of narrative-based specifications, the continued relevance of UniFormat as a systems-based approach, and the value of integrating estimating insight earlier in the process. Rather than treating documentation as a downstream technical exercise, Ben positions it as an active instrument for conveying intent, coordinating systems, and enabling informed decisions. Drawing from BIG’s global practice, the discussion challenges conventional methods and reframes specifications as a critical medium for translating design into constructed reality, with a brief but memorable aside on the unlikely inspiration of a well-crafted banana split.

This episode offers a rare peek behind the curtain at how a specification platform is developed by the very practitioners who use it every day, experienced specifiers who write construction documents and coordinate design intent on active projects. Rather than a traditional software roadmap, the conversation reveals how real project challenges, user feedback, and daily workflow friction drive feature development. The team discusses how even seemingly simple ideas require extensive “what-if” discussions, technical evaluation, and collaboration with developers. A current effort to enable multi-firm collaboration highlights the complexity behind decisions that affect document control and shared content. What makes the discussion unique is hearing specifiers: Dave Stutzman, Steve Gantner, and Elias Saltz explain how their real-world experience shapes the evolution of the tool. The result is a candid look at how practical project needs translate into software features designed to support better collaboration and documentation.

Learning Points

Industry insight:
Developing tools for construction documentation is inherently iterative, shaped by real project use rather than a fixed roadmap.

Practice takeaway:
User suggestions, real-world workflows, and day-to-day friction points are often the strongest drivers for meaningful feature improvements.

Process lesson:
Even small feature requests can create cascading impacts, requiring extensive discussion, prioritization, and testing before implementation.

Risk or opportunity:
Without careful evaluation, new features can disrupt existing workflows; thoughtful development creates opportunities for better collaboration and efficiency.

People & culture:
Open dialogue between users, specifiers, and developers encourages transparency and leads to more practical, usable solutions.

This episode explores the idea behind the Design Intent Gap and why ambiguity in construction documentation continues to create confusion across the industry. The conversation centers on the premise that design intent should be treated as a clear project deliverable, not something implied through drawings and specifications. When the reasoning behind decisions is not documented, contractors, estimators, and suppliers are left to interpret the intent themselves, which can lead to inaccurate pricing, unnecessary value engineering, and misaligned expectations. The team discusses how documenting system requirements, performance criteria, and the rationale behind decisions provides transparency and keeps project teams aligned as design evolves. 

Dave Stutzman calls on the industry to rethink how design intent is captured so projects can move forward with greater clarity, collaboration, and confidence ➡️ Design Intent Gap

Learning Points

Industry insight:
Ambiguity in design documentation forces contractors, estimators, and suppliers to fill in the gaps, often leading to inaccurate pricing and unnecessary project friction.

Practice takeaway:
Treat design intent as a formal deliverable that records decisions, criteria, and the reasoning behind them.

Process lesson:
Documenting system requirements and performance criteria early creates a transparent decision trail that prevents teams from revisiting previously resolved design questions.

Risk or opportunity:
When design intent is not clearly documented, projects risk redesign, delays, and budget impacts. A structured framework for capturing intent improves collaboration and supports better decision-making across the team.

People & culture:
Transparency around design decisions builds trust across architects, engineers, contractors, and owners, helping the entire team move forward with shared understanding.

Quote worth repeating:
“If it’s not documented, it’s not designed.”

Five-word takeaway:
Document intent. Eliminate ambiguity.

This episode explores a frequently overlooked factor in building design: the influence of property insurance requirements on construction documents and specifications. The conversation was sparked by a real project situation where FM Global entered the process late and issued extensive design comments after specifications were already underway. The team discusses how insurers often impose performance standards that exceed building codes, affecting materials, assemblies, and system design. When those requirements are discovered too late, the result can be costly redesign, coordination issues, and project delays.  The key takeaway is simple but critical: identify the owner’s insurer early and communicate those requirements to the entire project team. Doing so helps prevent late-stage redesign, protects document coordination, and allows the building to be designed for risk performance from the start rather than corrected later. 

Learning Points

Industry insight:
Building codes establish minimum life-safety requirements, but property insurers often require higher standards to reduce loss risk from fire, wind, flood, or structural failure.

Practice takeaway:
Design teams should ask early in the project who the building’s insurer will be and obtain any applicable guidelines or requirements before design decisions are finalized.

Process lesson:
Insurance requirements affect multiple disciplines, including roofing systems, exterior wall assemblies, fire protection, and structural design. Communicating these requirements across the entire design team is critical.

Risk or opportunity:
Late discovery of insurance requirements can trigger redesign and coordination problems. Addressing them early can reduce project risk and potentially lower insurance premiums for the owner over the life of the building.

This episode centers on renewed interest in System and Performance Descriptions (SPDs) as a structured way to document design intent earlier in the project lifecycle. Dave shares how initial skepticism often turns into clarity once teams see how SPDs organize information and capture what is known, when it is known, without defaulting to copied narratives or premature material decisions. The discussion highlights the limitations of traditional design narratives and the risks of compressed schedules that push coordination downstream into construction administration. The team explores how SPDs can support collaboration with contractors, estimators, and owners, reduce RFIs and substitutions, and even serve as construction specifications in certain delivery models. At its core, the conversation frames SPD not as a new burden, but as a practical shift toward clearer thinking, earlier alignment, and fewer surprises in the field.

Learning Points

• Industry insight: There is growing appetite across the AECO industry for clearer, earlier documentation of design intent that bridges design and construction.
• Practice takeaway: Document systems first. Define what assemblies must do and why before locking into specific products or materials.
• Process lesson: Structured system descriptions improve coordination, reduce presuppositions, and allow meaningful contractor and estimator input during design.
• Risk or opportunity: The risk is continuing compressed, reactive workflows that generate RFIs and rework. The opportunity is minimizing construction administration effort through deliberate early alignment.

This episode reinforces a simple but powerful idea: clarity early costs less than correction later.

This episode was sparked by a familiar and uncomfortable question: should you copy a specification section from a prior project, or start from scratch? Steve Gantner, Elias Saltz, Dave Stutzman explored why “copy-paste” has become such a common criticism from contractors and why that perception exists in the first place. They unpacked the risks of inheriting outdated codes, discontinued products, and mismatched scope, especially when prior edits and deletions are invisible. At the same time, they acknowledged the realities of practice, where templates, masters, and institutional knowledge can be powerful tools when managed correctly. The conversation ultimately reinforced that credibility, coordination, and project-specific thinking are what protect both the documents and the firm’s reputation.

Learning Points

• Industry insight: Contractors notice when specifications feel recycled. “Copy-paste” documents erode trust and signal a lack of coordination.
• Practice takeaway: If you reuse content, treat it as a template, not a finished product. Read it line by line against current drawings, codes, ownership, and site conditions.
• Process lesson: Masters and maintained templates are safer than copying entire project manuals. Controlled updates reduce the risk of generational errors compounding over time.
• Risk or opportunity: The risk is hidden liability, outdated requirements, and reputational damage. The opportunity lies in disciplined document management that strengthens accuracy, efficiency, and confidence across the project team.

In the end, the consensus leaned toward a simple principle: best practice is to start fresh, or at least review as if you did.

Colin Gilboy, founder of 4specs.com, sat down with Conspectus executives David Stutzman, Steve Gantner, and Elias Saltz in Orlando, FL to button up the final details of its acquisition and share something bigger with the industry, his retirement. We were able to capture a glimpse of that moment and the conversation behind it.

For decades, 4specs.com has been a steady compass for product and manufacturer research in the AECO world. Colin talks about how it started, why he built it, and the simple principle that guided it from day one: give people honest, useful information and let the quality speak for itself.

There is a long history between Colin and Dave, built on respect and a shared belief that better education, transparent knowledge, and strong community connections lead to better projects. This episode feels less like a transaction and more like a passing of the torch.