Common use of Change Request Log Clause in Contracts

Change Request Log. 7.1 Each entry made in the Change Request Log shall set out the following: (a) serial number of the Change Request; (b) name of the originating party; (c) a brief description of the Change; (d) the current status of the Change; and (e) the date of registration of the Change Request in the Change Request Log. 7.2 The status of the Change Request at any stage in the Change Procedure shall be one of the following: (a) Raised (i.e. that the Change Request has been entered in the Change Request Log, but no Change Proposal has been issued); (b) Pending (i.e. that the Change Request has been raised and the Change Proposal has been issued); (c) Approved by Client (i.e., awaiting implementation); (d) Closed (i.e., all implementation tasks complete); or (e) Rejected by Client (i.e., closed and not implemented). Part 3

Appears in 2 contracts

Samples: Agreement for the Provision of Services (TRX Inc/Ga), Agreement for the Provision of Services (TRX Inc/Ga)

AutoNDA by SimpleDocs

Change Request Log. 7.1 Each entry made in the Change Request Log shall set out consist of the followingfollowing fields: (a) serial number of the Change Request; (b) name of the originating party; (c) a brief description of the Change; (d) the current status of the Change; and (e) the date of registration of the Change Request in the Change Request Log. 7.2 The status of the Change Request at any stage in the Change Procedure Control Management shall be one of the following: (a) Raised raised (i.e. i.e., that the Change Request has been entered in the Change Request Log, but no Change Proposal has been issued); (b) Pending pending (i.e. i.e., that the Change Request has been raised and the Change Proposal has been issued); (c) Approved by Client approved (i.e., awaiting implementation); (d) Closed closed (i.e., all implementation tasks completehave been completed); oror ---------- * Confidential information has been omitted. (e) Rejected by Client rejected (i.e., closed and not implemented). Part 3.

Appears in 2 contracts

Samples: Services Agreement (Exult Inc), Services Agreement (Exult Inc)

Change Request Log. 7.1 Each entry made in the Change Request Log shall set out consist of the followingfollowing fields: (a) serial number of the Change Request; (b) name of the originating party; (c) a brief description of the Change; (d) the current status of the Change; and (e) the date of registration of the Change Request in the Change Request Log. 7.2 The status of the Change Request at any stage in the Change Procedure Control shall be one of the following: (a) Raised raised (i.e. i.e., that the Change Request has been entered in the Change Request Log, but no Change Proposal has been issued); (b) Pending pending (i.e. i.e., that the Change Request has been raised and the Change Proposal has been issued); (c) Approved by Client approved (i.e., awaiting implementation); (d) Closed in process (i.e., being implemented); (e) closed (i.e., all implementation tasks completehave been completed); or (e) Rejected by Client (i.e., closed and not implemented). Part 3

Appears in 1 contract

Samples: Master Services Agreement

Change Request Log. 7.1 Each entry made in the Change Request Log shall set out consist of the followingfollowing fields: (a) serial number of the Change Request; (b) name of the originating party; (c) a brief description of the Change; (d) the current status of the Change; and (e) the date of registration of the Change Request in the Change Request Log. 7.2 The status of the Change Request at any stage in the Change Procedure Control shall be one of the following: (a) Raised raised (i.e. i.e., that the Change Request has been entered in the Change Request Log, but no Change Proposal has been issued); (b) Pending pending (i.e. i.e., that the Change Request has been raised and the Change Proposal has been issued); (c) Approved by Client approved (i.e., awaiting implementation); (d) Closed closed (i.e., all implementation tasks completehave been completed); or (e) Rejected by Client rejected (i.e., closed and not implemented). Part 3Exhibit K – FINAL VERSION 6 Exult April 23, 2003 Exhibit M – FINAL 1 April 23, 2003

Appears in 1 contract

Samples: Master Services Agreement (Exult Inc)

AutoNDA by SimpleDocs

Change Request Log. 7.1 Each entry made in the Change Request Log shall set out consist of the followingfollowing fields: (a) serial number of the Change Request; (b) name of the originating party; (c) a brief description of the Change; (d) the current status of the Change; and (e) the date of registration of the Change Request in the Change Request Log. 7.2 The status of the Change Request at any stage in the Change Procedure Control Management shall be one of the following: (a) Raised raised (i.e. i.e., that the Change Request has been entered in the Change Request Log, but no Change Proposal has been issued); (b) Pending pending (i.e. i.e., that the Change Request has been raised and the Change Proposal has been issued); (c) Approved by Client approved (i.e., awaiting implementation); (d) Closed closed (i.e., all implementation tasks completehave been completed); or (e) Rejected by Client rejected (i.e., closed and not implemented). Part 3Schedule K – Amendment #5 6 Exult Sch. M – Amendment #5 Sch. M – Amendment #5 i

Appears in 1 contract

Samples: Services Agreement (Exult Inc)

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!