Common use of Change Initiation Clause in Contracts

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer requests; regulatory changes; changes in technical scope; or other detail program issues or requirements. The Project Lead of the party initiating a change will submit each change request to the other party’s Project Lead, and then both Project Leads will review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-four (24) hours of the receipt of the Change Request Form by the non-initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer Customer requests; regulatory changes; changes in technical scope; or other detail program issues or requirements. The Project Lead of the party initiating a change will shall submit each change request to the other party’s Project Lead, and then both Project Leads will shall review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-four (24) hours of the receipt of the Change Request Form by the non-initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer requests; requests;; regulatory changes; changes;; changes in technical scope; scope;; or other detail program issues or requirements. The Project Lead of the party initiating a change will submit each change request to the other party’s Project Lead, and then both Project Leads will review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-four twenty-­four (24) hours of the receipt of the Change Request Form by the non-initiating non-­initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer Customer requests; regulatory changes; changes in technical scope; or other detail program issues or requirements. The Project Lead of the party initiating a change will shall submit each change request to the other party’s Project Lead, and then both Project Leads will shall review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-twenty- four (24) hours of the receipt of the Change Request Form by the non-initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer requests; regulatory changes; changes in technical scope; or other detail program issues or requirements. The Project Lead of the party initiating a change will submit each change request to the other party’s Project Lead, and then both Project Leads will review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-twenty- four (24) hours of the receipt of the Change Request Form by the non-initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.

Change Initiation. LogRhythm or the Customer may initiate change requests. The reasons for a change may include: customer requests; requestsO regulatory changes; changesO changes in technical scope; scopeO or other detail program issues or requirements. The Project Lead of the party initiating a change will submit each change request to the other party’s Project Lead, and then both Project Leads will review such request for validation. Project changes must be submitted in a clear and concise manner in the form of a Change Request Form (Attachment A). Upon the initiation of a change request, both parties must agree within twenty-/four (24) hours of the receipt of the Change Request Form by the non-/initiating party whether or not to continue performance of the Services or to stop all Services being performed until a mutually agreed upon Change Request Form has been signed by both parties.