Because Even Approved Substitutions Can Create Unapproved Problems
On paper, it’s a seamless switch: same rating, same size, same performance. But in the field, that “approved equal” triggers visual clashes, install delays, or architect pushback. The issue isn’t the material—it’s the trust gap.
When vendors treat substitutions as an afterthought, PMs start treating them as a risk.
What Creates the Trust Gap?
Lack of clear documentation on what’s different.
No visual sample or mock-up, especially for exposed applications.
Material arrives before formal approval—or before the PM is looped in.
Even when it’s technically compliant, it can feel like a shortcut. And once a PM sees you cutting corners on transparency, they begin to wonder what else is being hidden.
What PMs Say (When You’re Not Around)
“We had to explain their change to the client.”
“It matched spec, but it wasn’t what the architect expected.”
“They handled it like a procurement problem—not a design one.”
Why It Damages Relationships
Triggers re-approval loops and install delays.
Shifts burden to the PM to fix or justify your decision.
Suggests you prioritize your own lead time over project integrity.
How to Prevent the Fallout
Send a clear substitution memo: differences, rationale, and visual changes.
Include the GC, architect, and PM—don’t just work through procurement.
Confirm install compatibility with your field team before approval.
Conclusion
Substitutions aren’t just a material choice—they’re a moment of truth. Handle it with transparency, and you reinforce trust. Handle it in silence, and you signal risk. PMs never forget the difference.
