Episode Summary
Yes, I would slightly rewrite it, not because the current summary is inaccurate, but because it emphasizes “copying specs” enough that it could feel very similar to the earlier “Copy a Project or Section?” episode.
I’d shift the center of gravity toward creating efficiencies across a series of related projects, with copying as the problem that sparks the conversation. That better captures the discussion about tagging, common requirements, owner standards, and maintaining a living source document.
Revised Summary
This week on What a Week, Dave Stutzman, Steve Gantner, and Elias Saltz explore how specification teams can create efficiencies when working on multiple projects for the same architect or owner. When projects share standards, assemblies, and delivery methods, there is an opportunity to build from common information rather than starting from scratch each time.
But efficiency comes with a warning: reused information can easily be mistaken for finished information. When a specification already looks complete, project-specific differences may receive less scrutiny, allowing outdated or incorrect requirements to slip through and potentially lead to conflicts or RFIs.
The conversation looks beyond simply copying projects and considers a more intentional approach: developing common requirements once, then using tools such as tagging to manage the differences between individual projects. Done well, that shared source can support multiple projects and potentially evolve into an owner guide specification.
But it still requires ongoing review and maintenance as codes, materials, products, and project needs change.
The takeaway: efficiency comes from building on what you know, not assuming what worked before will work again.
Learning Points
Industry Insight
Reusing specifications across similar projects can create efficiencies, but similar projects rarely remain identical as design progresses.
Practice Takeaway
Reuse sections and proven requirements, but review every specification line by line to confirm it reflects the current project.
Process Lesson
Instead of copying an entire project, build common requirements once and use tools such as tagging to manage project-specific differences within a shared source.
People & Culture
Efficiency still depends on attention and communication. When documents already look complete, teams need the discipline to question what has changed rather than assume previous decisions still apply.
Risk or Opportunity
A well-maintained common specification can become a valuable owner resource across multiple projects, but it must evolve with changes in codes, materials, products, and manufacturers.
It’s okay to copy sections. It’s okay to borrow from projects. I wouldn’t recommend copying an entire project unless you’re committed to going through it line by line.
Elias Saltz, Steve Gantner, David Stutzman
