CHANGE REQUEST LOG Clause Samples

The Change Request Log clause establishes a formal record-keeping process for tracking all requests for changes to a project or agreement. It typically requires that each change request be documented with relevant details such as the date, description, status, and any actions taken, ensuring that all parties have a clear and up-to-date understanding of proposed and approved modifications. This clause helps maintain transparency, prevents misunderstandings, and ensures that changes are managed systematically throughout the course of the project or contract.
POPULAR SAMPLE Copied 1 times
CHANGE REQUEST LOG. 7.1 Each entry made in the Change Request Log shall consist of the following 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 Control Process shall be one of the following: -------- * Confidential information has been omitted. Human Resources Services Agreement - Schedule K - Final 4 October 18, 2001 Proprietary and Confidential International Paper / Exult (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 (i.e., awaiting implementation); (d) closed (i.e., all implementation tasks have been completed); or (e) rejected (i.e., closed and not implemented). Human Resources Services Agreement - Schedule K - Final 5 October 18, 2001 Proprietary and Confidential International Paper / Exult SCHEDULE L ACCOUNT GOVERNANCE SCHEDULE 1.0 INTRODUCTION 1.1 This Account Governance Schedule provides a high level outline of the account governance process that the Parties will implement to manage the administration of the Agreement and the Services. The purpose of this schedule is to define agreed upon principles and processes that will guide the Parties' relationship under the Agreement.
View SourceView Similar (4)
CHANGE REQUEST LOG. 7.1 Each entry made in the Change Request Log shall consist of the following 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 Change Control Management 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 (i.e., awaiting implementation); (d) closed (i.e., all implementation tasks have been completed); or ---------- * Confidential information has been omitted. (e) rejected (i.e., closed and not implemented).
View SourceView Similar (7)
CHANGE REQUEST LOG. (1) HPES will be responsible for tracking and reporting all Changes implemented by HPES in a Change Request log (each, a “Change Request Log”). Each entry made in the Change Request Log will consist of the following fields: (a) Change Request number, (b) name of the originator of the Change Request, (c) a brief description of the Change, (d) the current status of the Change, and (e) the date that the Change Request was entered in the Change Request Log. (2) The status of the Change Request or Change Proposal (as applicable) at any stage in the Change Control Procedure will be one of the following, or substantially similar: (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 (i.e., awaiting implementation), (d) closed (i.e., all implementation tasks have been completed), or (e) rejected (i.e., closed and not implemented).
View SourceView Similar (3)
CHANGE REQUEST LOG. 7.1 Each entry made in the Change Request Log shall consist of the following 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. -------- * Confidential information has been omitted. Schedule K - Technical Services Agreement - Final 4 October 18, 2001 Proprietary and Confidential International Paper / Exult 7.2 The status of the Change Request at any stage in the Change Control Process shall be one of the following:
View SourceView Similar (2)
CHANGE REQUEST LOG. Subject to Section 8.8, Contractor shall maintain a log of purported Owner instructions or comments that Contractor reasonably considers represent a change to the scope of Work made by Owner, which, in Contractor’s view, should result in the issuance of a Change Order by Owner pursuant to Section 8.2. Such log shall contain sufficient detail, including the date on which such instruction was given, for the Parties to identify the instruction or comment at issue. The Parties shall review such log during the Monthly progress review meetings as described in Appendix S. Neither the addition of items by Contractor to this log, including Change Orders requested by Contractor that may be listed in the log, nor the review of such log with Owner during the Monthly progress review meetings, shall constitute a Change Order or a formal request to Owner for a Change Order, and Owner’s failure to comment or dispute items on such log shall not be deemed an admission by Owner that such log is accurate or otherwise agreed upon by the Parties. Requests for Change Orders to be issued by Owner must be made in accordance with Section 8.2. If after review of the log by the Parties, Contractor believes that Owner’s instructions or comments nonetheless constitute a change in the Work, Contractor shall notify Owner in writing, and if Owner disagrees and does not issue a Change Order request under Section 8.2 or a unilateral Change Order under Section 8.6 with respect to such Work, either Party may submit such disagreement to dispute resolution proceedings in accordance with Section 20.1.
View Source
CHANGE REQUEST LOG. 3.1 Provider will provide Customer, as part of its monthly reporting obligations, a summary specifying the status of all pending Change Requests and Change Proposals. 3.2 Each entry made in the Change Request Log will consist of the following fields: (A) 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. 3.3 The status of the Change Request at any stage in Change Control Procedures will 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 (i.e., awaiting implementation); (D) closed (i.e., all implementation tasks have been completed); or (E) rejected (i.e., closed and not implemented). MA-IB-00136-2018 The data to be filled in on the Change Request Form is the following: Document Number Chronological number of the Change Requests Version Document version to keep track of the version history Creation Date Date of creation of the Change Request Beneficiary Name of the beneficiary for which this Change Request is required Request Date Date at which the Change Request was requested Requested By Name of the individual who originated the request at Customer or Provider Position Position of the originator of the Change Requested Priority Priority is proposed by Provider’s Authorized Representative and approved by the Customer’s Authorized Representative. Priority may be:* Urgent: the request has to be implemented on an expedited basis; or* High/Medium/Low: the Change Request is not urgent but has a level of priority and is to be implemented in the timeframe agreed in the final Change Order Impacted Service Location Service Location(s) that will be impacted by the proposed Change Overall Description High level explanation of the Change Request Overall Impact Evaluation High level evaluation of the main impacts of the Change Request Estimated costs for detailed analysis Initial estimate of the costs necessary for the preparation and drafting of a detailed, written proposal relative to the Change Estimated costs for implementation Initial estimate of the costs needed to implement the Change, including the increase or decrease or any additional Fees that may be due pursuant to the propose...
View Source
CHANGE REQUEST LOG. Each entry made in the Change Request Log shall consist of the following fields:
View Source
CHANGE REQUEST LOG. ‌ All changes to project scope, budget or schedule will be tracked on this log. Pending decisions that may affect project delivery should be tracked as project issues. 1. INTRODUCTION: 1 2. PURPOSE 1 1. Introduction‌ Organizational Readiness is the ability of the organization to fulfill obligations with regard to IT projects by providing information technology, personnel, resources, information or knowledge in a timely manner to make the project a success. In addition to items provided, organizational readiness includes the organizations ability to receive, accept and use new information, tools, capability, software, and process created by the project.
View Source

Related to CHANGE REQUEST LOG

  • Change Request Either Landlord or Tenant may request Changes after Landlord approves the Approved Plans by notifying the other party thereof in writing in substantially the same form as the AIA standard change order form (a “Change Request”), which Change Request shall detail the nature and extent of any requested Changes, including (a) the Change, (b) the party required to perform the Change and (c) any modification of the Approved Plans and the Schedule, as applicable, necessitated by the Change. If the nature of a Change requires revisions to the Approved Plans, then the requesting party shall be solely responsible for the cost and expense of such revisions and any increases in the cost of the Tenant Improvements as a result of such Change. Change Requests shall be signed by the requesting party’s Authorized Representative.

  • Change Requests 4.1.1. Either party can request changes to the Service.

  • PRODUCT AND PRICING CHANGE REQUESTS Supplier may request Equipment, Product, or Service changes, additions, or deletions at any time. All requests must be made in writing by submitting a signed Sourcewell Price and Product Change Request Form to the assigned Sourcewell Supplier Development Administrator. This approved form is available from the assigned Sourcewell Supplier Development Administrator. At a minimum, the request must: • Identify the applicable Sourcewell contract number; • Clearly specify the requested change; • Provide sufficient detail to justify the requested change; • Individually list all Equipment, Products, or Services affected by the requested change, along with the requested change (e.g., addition, deletion, price change); and • Include a complete restatement of pricing documentation in Microsoft Excel with the effective date of the modified pricing, or product addition or deletion. The new pricing restatement must include all Equipment, Products, and Services offered, even for those items where pricing remains unchanged. A fully executed Sourcewell Price and Product Change Request Form will become an amendment to this Contract and will be incorporated by reference.

  • Advance Request To obtain a Term Loan Advance, Borrower shall complete, sign and deliver an Advance Request (at least one (1) Business Day before the Closing Date and at least five (5) Business Days before each Advance Date other than the Closing Date) to Agent. The Lenders shall fund the Term Loan Advance in the manner requested by the Advance Request provided that each of the conditions precedent to such Term Loan Advance is satisfied as of the requested Advance Date.

  • Funding Request The Borrower hereby requests the Funding pursuant to Section 2.1 and Section 2.3 of the Loan Agreement.