General Event Transcription Sample Clauses

General Event Transcription. The general label requires the delivery of the following services: The provision of accurate transcription and reporting services of live events within a required timescale.
AutoNDA by SimpleDocs

Related to General Event Transcription

  • Regulatory Event New Taxes If, after the Effective Date, a Regulatory Event occurs or New Taxes are imposed, and such event or taxes have a direct, material and adverse effect on the economic benefits to a Party of this ESA, the affected Party shall send written notice to the other Party, setting forth the Regulatory Event or New Taxes and reasonably demonstrating the effect of the same on the affected Party. Upon delivery of such notice, the Parties shall use reasonable efforts to negotiate an amendment to this ESA to mitigate such effect. Alternatively, if as a direct result of such a Regulatory Event or New Taxes, the Competitive Supplier incurs additional, material costs, the Competitive Supplier shall provide a written notice to the Town that documents: a) the effective date of the Regulatory Event or New Taxes; b) a detailed explanation and reasonable demonstration of the material costs incurred as a result of the Regulatory Event or New Taxes; c) the timing of the cost impact to be incurred by the Competitive Supplier; d) the proposed price increase per kWh to be passed on to Participating Consumers; and e) a proposed plan for coordinating with the Local Distributor for an increase in the price per kWh that is billed by the Local Distributor, designed to reimburse the Competitive Supplier for such cost impact. If the Town and the Competitive supplier cannot agree on the amendment to this ESA or reimbursement contemplated by this section, the matter may be subject to dispute resolution in accordance with section 12.2. In no event shall a price change become effective without providing Participating Consumers with a 30-day advance notice of the price change.

  • Legal Action; Utilization of Special Receivership Powers The Assuming Institution shall notify the Receiver in writing (such notice to be given in accordance with Article V below and to include all relevant details) prior to utilizing in any legal action any special legal power or right which the Assuming Institution derives as a result of having acquired an asset from the Receiver, and the Assuming Institution shall not utilize any such power unless the Receiver shall have consented in writing to the proposed usage. The Receiver shall have the right to direct such proposed usage by the Assuming Institution and the Assuming Institution shall comply in all respects with such direction. Upon request of the Receiver, the Assuming Institution will advise the Receiver as to the status of any such legal action. The Assuming Institution shall immediately notify the Receiver of any judgment in litigation involving any of the aforesaid special powers or rights.

  • Termination on Insolvency and Change of Control 43.1. The Authority may terminate the Contractor’s interest in the Framework Agreement with immediate effect by notice where in respect of the Contractor:

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • Additional Event of Suspension Section 4.01. Pursuant to Section 6.02 (l) of the General Conditions, the following additional event is specified, namely, that a situation has arisen which shall make it improbable that the Program, or a significant part thereof, will be carried out.

  • Project Monitoring by the State The State may conduct on-site or off-site monitoring reviews of the Project during the term of this Grant Agreement and for up to ninety (90) days after it expires or is otherwise terminated. The Grantee shall extend its full cooperation and give full access to the Project site and to relevant documentation to the State or its authorized designees for the purpose of determining, among other things:

  • Train Operator Events of Default The following are Train Operator Events of Default:

  • Authority Event of Default Any of the following events shall constitute an event of default by the Authority ("Authority Event of Default”), when not caused by a Developer Event of Default:

  • H1 Termination on Insolvency and Change of Control H1.1 The Authority may terminate the Contract with immediate effect by notice in writing and without compensation to the Contractor where the Contractor is a company and in respect of the Contractor:

  • Submission of Certified Payroll Transcripts for Public Works Contracts Only Contractors and Subcontractors on public works projects must submit monthly payroll transcripts to the Authorized User that has prepared or directs the preparation of the plans and specifications for a public works project, as set forth in the Bid Specifications. For Mini-Bid solicitations, the payroll records must be submitted to the entity preparing the agency Mini-Bid project specification. For “agency specific” Bids, the payroll records should be submitted to the entity issuing the purchase order. For all other OGS Centralized Contracts, such records should be submitted to the individual agency issuing the purchase order(s) for the work. Upon mutual agreement of the Contractor and the Authorized User, the form of submission may be submitted in a specified disk format acceptable to the Department of Labor provided: 1) the Contractor/Subcontractor retains the original records; and, (2) an original signed letter by a duly authorized individual of the Contractor or Subcontractor attesting to the truth and accuracy of the records accompanies the disk. This provision does not apply to Article 9 of the Labor Law building services contracts.

Time is Money Join Law Insider Premium to draft better contracts faster.