Change Request Procedures. (a) A Party may request a Change by issuing a written request for that Change to the other Party in the form set out in Exhibit C (such request being a “Change Request”). No Change will be valid unless consented to in writing by both Parties. (b) Neither Party shall object to a Change to the extent that it is reasonably necessary to comply with applicable Law or the requirements of a relevant governmental authority (a “Regulatory Requirement”) (such change being a “Regulatory Change”). Each Regulatory Change shall be implemented by the Parties (i) in a manner so as to minimize the impact on the provision or receipt of the applicable Services, and (ii) as soon as reasonably practicable once the requesting Party becomes aware of the Regulatory Requirement. (c) The Parties shall, acting reasonably, discuss and agree upon any Change Request proposed pursuant to Section 3.1 within fifteen (15) Business Days of the receipt of the relevant Change Request by a Party. Upon agreement, the Parties shall implement the Change in accordance with its terms and the Change shall be automatically deemed an amendment to this Agreement or the applicable SOW, as applicable. (d) Each Party shall bear its own costs of considering and responding to Change Requests proposed by either Party. In respect of: (i) Changes (other than Regulatory Changes), the Party requesting the Change shall bear the other Party’s reasonable, direct and evidenced costs associated with implementing the Change; and (ii) Regulatory Changes, each Party shall bear equally any reasonable, direct and evidenced costs associated with implementing the Change.
Appears in 1 contract
Sources: Commercial Cooperation Agreement (TechTarget, Inc.)
Change Request Procedures. (a) A Party may request a Change by issuing a written request for that Change to the other Party in the form set out in Exhibit C D (such request being being, a “Change Request”). No Change will be valid unless consented to in writing by both Parties.
(b) . Neither Party shall object to a Change to the extent that it is reasonably necessary to comply with applicable Law or the requirements of a relevant governmental authority (a “Regulatory Requirement”) (such change being a “Regulatory Change”). Each Regulatory Change shall be implemented by the Parties (i) in a manner so as to minimize the impact on the provision or receipt of the applicable Services, and (ii) Services as soon as reasonably practicable once and, in any event, prior to the requesting Party becomes aware of date on which the relevant Regulatory RequirementChange comes into effect.
(cb) The Parties shall, acting reasonably, discuss and agree upon any Change Request proposed pursuant to Section 3.1 11.1 within fifteen (15) Business Days of the receipt of the relevant Change Request by a Party. Upon agreement, the Parties shall implement the Change in accordance with its terms and the Change shall be automatically deemed an amendment to this Agreement or the applicable SOW, as applicableterms.
(dc) Each Party shall bear its own costs of considering and responding to Change Requests proposed by either Party. In respect of:
(i) Changes (other than Regulatory Changes), the Party requesting the Change shall bear the other Party’s incremental reasonable, direct and evidenced costs associated with implementing the Change; and
(ii) Regulatory Changes, each Party shall bear equally any incremental reasonable, direct and evidenced costs associated with implementing the ChangeChange shall be borne by Provider, except that any incremental reasonable, direct and evidenced costs associated with implementing a Regulatory Change that primarily affects the Business rather than the business of Provider shall be borne by Recipient.
Appears in 1 contract
Change Request Procedures. (a) A Party may request a Change by issuing a written request for that Change to the other Party in the form set out in Exhibit C B (such request being being, a “Change Request”). No Change will be valid unless consented to in writing by both Parties.
(b) . Neither Party shall object to a Change to the extent that it is reasonably necessary to comply with applicable Law or the requirements of a relevant governmental authority (a “Regulatory Requirement”) (such change being a “Regulatory Change”). Each Regulatory Change shall be implemented by the Parties (i) in a manner so as to minimize the impact on the provision or receipt of the applicable Services, and (ii) Services as soon as reasonably practicable once and, in any event, prior to the requesting Party becomes aware of date on which the relevant Regulatory RequirementChange comes into effect.
(cb) The Parties shall, acting reasonably, discuss and agree upon any Change Request proposed pursuant to Section 3.1 11.1 within fifteen (15) Business Days of the receipt of the relevant Change Request by a Party. Upon agreement, the Parties shall implement the Change in accordance with its terms and the Change shall be automatically deemed an amendment to this Agreement or the applicable SOW, as applicableterms.
(dc) Each Party shall bear its own costs of considering and responding to Change Requests proposed by either Party. In respect of:
(i) Changes (other than Regulatory Changes), the Party requesting the Change shall bear the other Party’s incremental reasonable, direct and evidenced costs associated with implementing the Change; and
(ii) Regulatory Changes, each Party shall bear equally any incremental reasonable, direct and evidenced costs associated with implementing the ChangeChange shall be borne by Provider, except that any incremental reasonable, direct and evidenced costs associated with implementing a Regulatory Change that primarily affects the Business rather than the business of Provider shall be borne by Recipient.
Appears in 1 contract
Sources: Reverse Transitional Services Agreement (TechTarget, Inc.)