Closeout Obligations Sample Clauses

The Closeout Obligations clause defines the responsibilities and procedures that parties must follow when terminating or settling outstanding transactions, typically after a default or early termination event. In practice, this clause outlines how remaining obligations are calculated, netted, and paid, often specifying timelines and methods for determining final settlement amounts. Its core function is to ensure an orderly and predictable process for closing out positions, thereby minimizing uncertainty and financial risk for both parties.
Closeout Obligations. Before submitting its proposed Certificate of Substantial Completion for UGAA approval, Design-Builder shall perform and submit, for UGAA’s review, documents in support of its complete satisfaction of the following Closeout Obligations:
Closeout Obligations. Design-Builder has demonstrated its satisfaction of all Closeout Obligations;
Closeout Obligations. CM has demonstrated its satisfaction of all Closeout Obligations;
Closeout Obligations. Before submitting its proposed Certificate of Substantial Completion for UGAA approval, CM shall perform and submit, for UGAA’s review, documents in support of its complete satisfaction of the following Closeout Obligations:
Closeout Obligations. Contractor has demonstrated its satisfaction of all Closeout Obligations;

Related to Closeout Obligations

  • PROCUREMENT OBLIGATIONS Notwithstanding any other provisions of this Part B, where in this Part B the Customer accepts an obligation to procure that a Former Supplier does or does not do something, such obligation shall be limited so that it extends only to the extent that the Customer's contract with the Former Supplier contains a contractual right in that regard which the Customer may enforce, or otherwise so that it requires only that the Customer must use reasonable endeavours to procure that the Former Supplier does or does not act accordingly.

  • Client Obligations 3.1 The Client warrants and represents that: 3.1.1 it shall co-operate with Centaur as required for the proper performance of the Services; 3.1.2 it shall provide, for Centaur, its agents, subcontractors, consultants and employees, in a timely manner and at no charge, access to the Client's premises during normal office hours (being Monday – Friday 8am – 6pm), office accommodation, data and other facilities as is reasonably required by Centaur or any of them for the proper performance of the Services; 3.1.3 all information it has provided to Centaur in relation to the Services as at the date of the Order Form is accurate, complete and is not misleading and it shall provide, in a timely manner, such further information and Client Material as Centaur may require for the proper performance of the Services, and ensure that such information and Client Material is accurate, complete and not misleading; 3.1.4 it shall be responsible (at its own cost) for preparing and maintaining the relevant premises for the supply of the Services; 3.1.5 it shall inform Centaur of all health and safety rules and regulations and any other reasonable security requirements that apply at any of the Client's premises; 3.1.6 it shall only use the Services for internal business purposes and, without prejudice to the foregoing, shall not use the Services, the Deliverables or any Centaur Materials to develop a product or service that competes with any of the products or services provided by Centaur; 3.1.7 the Client Materials shall not infringe any third party rights, including any third party Intellectual Property Rights; and 3.1.8 it shall obtain and maintain all necessary licences and consents and comply with all relevant legislation in relation to the Services, before the date on which the Services are to start. 3.2 If Centaur's performance of its obligations under this Agreement is prevented or delayed by any act or omission of the Client, its agents, subcontractors, consultants or employees, Centaur shall not be liable for any costs, charges or losses sustained or incurred by the Client that arise directly or indirectly from such prevention or delay.

  • ▇▇▇▇▇ OBLIGATIONS A ▇▇▇▇▇▇▇'s acceptance of funds directly under the Grant or indirectly through a subaward acts as acceptance of the authority of the State, under the direction of the legislative audit committee, to conduct an audit or investigation in connection with those funds. In accordance with the legislative audit committee, DFPS can request any documentation, at any time, to be sent to DFPS to a location DFPS chooses. Examples of documentation that DFPS may request include, but are not limited to: 1. Participant files in their entirety. This includes, but is not limited to: a. Progress notes. b. Action plans. c. Registration forms. d. Surveys. e. Sign-in sheets. f. Monthly tracking forms.

  • Joint Obligations A. The University and the student share the responsibility for ensuring the quality of life within the residence halls, their maintenance, furnishings and facilities, and for a physical environment secure from fire and other hazards. The University will work with students to promote effective security of persons and property in the residence halls.

  • Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.