How should the RME address disparities between client expectations and code requirements?

• A. Communicate clearly, justify design decisions, and document alternatives and trade-offs
• B. Ignore client expectations if code dictates
• C. Refuse to discuss alternatives
• D. Modify code to satisfy client

Answer: (C)

When client expectations don’t line up with code requirements, the essential approach is transparent communication paired with clear justification and a record of options. You explain what the code requires, why those requirements are in place, and how the design decisions address safety, reliability, or standards. At the same time, you present viable alternatives and lay out the trade-offs—such as impacts on time, cost, performance, and future maintenance—so everyone understands the implications and can make an informed decision together. This approach builds trust, keeps the project aligned with constraints, and provides a documented path for any future changes.

Shutting down the conversation or insisting on only one path undermines collaboration and can lead to misaligned expectations. Refusing to discuss alternatives or changing code purely to satisfy the client without considering constraints can introduce risk, compromise safety, or create maintenance problems.