CAPM Practice: Determine how to conduct stakeholder communication

Acknowledgment closes the feedback loop — telling stakeholders their input was heard and how it will be handled (implemented, deferred, or not pursued with explanation). This builds trust and encourages continued participation in requirements development.

**Why not A:** Formally accepting all stakeholder requirements into project scope is a scope management decision, not acknowledgment. Acknowledgment means confirming that input was received and explaining how it will be addressed, which may include deferring or declining a request with a clear explanation.

**Why not C:** Legal acknowledgment of requirements documents by all signatories describes a formal sign-off process. Communication acknowledgment is less formal and more about maintaining stakeholder engagement by showing their contributions are valued and will be considered in the requirements process.

**Why not D:** Sending automatic email receipts when documents are opened is a technical tracking mechanism, not meaningful acknowledgment. True acknowledgment involves a substantive response that tells the stakeholder their input was understood and how it fits into the requirements process.