When a company enforces formal authorization for a proposed modification what formal and detailed document must be created to specify the exact tasks and deliverables required to carry out the change?

A technical design document (TDD) specifies the architectural and technical details of how a solution will be built, but not necessarily the tasks, deliverables, and timelines for carrying out a change from a project management perspective.

A change request record in an ITSM system initiates and tracks a change, but it typically doesn't contain the extensive, detailed breakdown of tasks and deliverables found in an SOW for complex modifications.

A Statement of Work (SOW) is a formal document commonly used in project management to define the scope of work, deliverables, objectives, tasks, schedule, and expected outcomes for a specific project or modification. When formal authorization is given for a change, an SOW ensures all parties understand the exact requirements and execution plan in detail.

A quality assurance and test plan outlines how the changes will be tested and validated, not the specific tasks and deliverables required to implement the change itself.