Common use of Request for Change Management Clause in Contracts

Request for Change Management. SLA 4.1.1 All requests for change (RFC) are required to be submitted via the Service Desk, where they will be triaged and prioritized accordingly. 4.1.2 Requests for Change are defined as follows: 4.1.2.1 Standard RFC: a pre-defined change that is low impact, low risk and where no additional authorization to effect by the Service Desk is required, other than the instruction in the ticket. This will include, but is not limited to, requests such as reactive / BAU optimization requests (for example title changes, label amendments, tracking link appends), product exclusions, partner setups, BAU reporting, Title/ AB Testing. Standard RFCs require a minimum of 24 hours’ notice to action, however target resolution will vary from a few hours to 48 hours, as relevant, and dependent on the nature and size of the request. 4.1.2.2 Normal RFC: a higher impact, higher risk change that will need to be authorized by stakeholders, where this could have cost associated, and therefore must be approved. This will follow a change management process, whereby a full impact assessment will be done, and resource for delivery planned before auctioning. For example, requests for Strategy Creation/ Forecasting, advanced reporting, or more sophisticated Title/ AB Testing may be classified as Normal RFCs.

Request for Change Management. SLA 4.1.1 All requests for change (RFC) are required to be submitted via the Service Desk, where they will be triaged and prioritized accordingly. 4.1.2 Requests for Change are defined as follows: 4.1.2.1 Standard RFC: a pre-defined change that is low impact, low risk and where no additional authorization to effect by the Service Desk is required, other than the instruction in the ticket. This will include, but is not limited to, requests such as reactive / reactive/BAU optimization requests (for example title changes, label amendments, tracking link appends), product exclusions, partner setups, BAU reporting, Title/ Title/AB Testing. Standard RFCs require a minimum of 24 hours’ notice to action, however target resolution will vary from a few hours to 48 hours, as relevant, and dependent on the nature and size of the request. 4.1.2.2 Normal RFC: a higher impact, higher risk change that will need to be authorized by stakeholders, where this could have cost associated, and therefore must be approved. This will follow a change management process, whereby a full impact assessment will be done, and resource for delivery planned before auctioning. For example, requests for Strategy Creation/ Forecasting, advanced reporting, or more sophisticated Title/ Title/AB Testing may be classified as Normal RFCs.