When implementing value engineering changes, what must accompany the change?

• A. No documentation required.
• B. Only a cost summary showing savings.
• C. Documentation of rationale and impact on safety, performance, and code compliance.
• D. Approve changes verbally and ignore formal records.

Answer: (C)

Value engineering changes must be documented with a clear rationale and an assessment of how the change affects safety, performance, and code compliance. This documentation keeps decisions transparent and traceable, flags any new risks or regulatory implications, and ensures that cost savings don’t undermine essential requirements. Include why the change is preferable, how it achieves the function at a lower cost, and any analyses or tests used to support it. Also spell out safety impacts, performance, durability, interfaces, and how codes or standards are still met or what approvals are needed. Without this record, you lose accountability and risk non‑compliance; simple cost summaries or verbal approvals don’t capture the full picture.