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.