If a recommended resolution to an issue is known, how should it be addressed in the RFI?

If a recommended resolution to an issue is known, how should it be addressed in the RFI?

• A. Propose the recommended resolution, including cost and schedule impacts.
• B. Do nothing until the next design review.
• C. Provide only a brief summary of the issue.
• D. Submit the resolution without cost or schedule information.

Answer: (A)

When you already know a recommended resolution for an issue raised in an RFI, present that solution in the RFI along with its cost and schedule impacts. This gives stakeholders a concrete path to evaluate and helps them decide quickly, rather than forcing them to infer a course of action. Including cost and schedule impacts is essential because it shows how the proposed fix will affect the project budget and timeline, allowing comparison with alternatives and enabling informed approval. It demonstrates that the solution has been considered in terms of feasibility and risk, not just technical merit. Leaving out the proposed resolution or the cost/schedule information leads to delays and ambiguity. Proposing the resolution without its cost or schedule implications leaves decision-makers without the full picture, while offering only a brief summary or the solution without the impacts fails to provide actionable guidance. If useful, briefly note assumptions, potential risks, and any required contingencies so the team can assess trade-offs and align on a path forward.

When you already know a recommended resolution for an issue raised in an RFI, present that solution in the RFI along with its cost and schedule impacts. This gives stakeholders a concrete path to evaluate and helps them decide quickly, rather than forcing them to infer a course of action.

Including cost and schedule impacts is essential because it shows how the proposed fix will affect the project budget and timeline, allowing comparison with alternatives and enabling informed approval. It demonstrates that the solution has been considered in terms of feasibility and risk, not just technical merit.

Leaving out the proposed resolution or the cost/schedule information leads to delays and ambiguity. Proposing the resolution without its cost or schedule implications leaves decision-makers without the full picture, while offering only a brief summary or the solution without the impacts fails to provide actionable guidance.

If useful, briefly note assumptions, potential risks, and any required contingencies so the team can assess trade-offs and align on a path forward.