Guaranteed Deliverables - Makegood Procedure Sample Clauses

Guaranteed Deliverables - Makegood Procedure. In the event that actual Deliverables for any campaign fall below guaranteed levels, as set forth in the IO, and/or if there is an omission of any Ad (placement or creative unit), Advertiser or Agency, as applicable, and Media Company will use good faith efforts to agree upon the conditions of a makegood flight either in the IO or at the time of the shortfall. If no makegood can be agreed upon, Advertiser or Agency, as applicable, may execute a credit equal to the value of the under-delivered portion of the applicable IO for which it was charged. In the event that Agency or Advertiser has made a cash prepayment to Media Company, specifically for the campaign IO for which under-delivery applies, then if Agency and/or Advertiser has no overdue and outstanding amounts owing to Media Company under any other agreement for such Advertiser, Advertiser or Agency, as applicable, may elect to receive a refund for the under-delivery equal to the difference between the applicable pre-payment and the value of the delivered portion of the campaign. In no event shall Media Company provide a makegood or extend any Ad beyond the period set forth in the IO without prior written consent of Advertiser or Agency, as applicable.
Sample 1
AutoNDA by SimpleDocs

Related to Guaranteed Deliverables - Makegood Procedure

  • Services and Deliverables The Services and the required Deliverables for the Services are specified below. SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount per annum (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: *Note: Refer to clause 4.3 in the Funding and Service Details about permitted variations in Output Quantities.

  • Tasks and Deliverables A description of and the schedule for each task and deliverable, illustrated by a Xxxxx chart. Start and completion dates for each task, milestone, and deliverable shall be indicated. Must include deliverables specified in SOW-RFP as well as other deliverables that may be proposed by Contractor.

  • Scope of Work and Deliverables 9.1 Background and Scope

  • Reports and deliverables 1. The consortium shall submit a periodic report to the REA for each reporting period within 60 days after the end of each respective period. The report shall comprise:

  • Payment for Project Services As full consideration for the Services to be performed by Contractor, City agrees to pay Contractor as set forth in accordance with the bid and not to exceed fee of $696,243.00 for the project. A monthly progress payment in the amount of ninety-five percent (95%) of the value of the work completed may be made every thirty (30) days upon application by the Contractor and certification by the Project Manager that such work has been completed. Partial payments will be made once each month as the work satisfactorily progresses and after acceptance by the authorized City representative. The progress estimates shall be based upon materials in place, or on the job site and invoiced, and labor expended thereon. From the total of the amount ascertained will be deducted an amount equivalent to five percent (5%) of the whole, which five percent (5%) will be retained by the City until after completion of the entire Contract in an acceptable manner. Any time after fifty percent (50%) of the value of the work has been completed, the City will make any of the remaining partial payments in full. No such estimates or payments shall be required to be made, when, in the judgment of the City Project Manager, the work is not proceeding in accordance with the provision of the Contract, or when in his judgment the total value of the work done since last estimate amounts to less than Five Hundred Dollars ($500.00). The cost of materials conforming to the plans and specifications (materials being those which are required to be contained and incorporated in a finished contract bid item) delivered to the project and not at the time incorporated in the work, may also be included in the estimate for payment. No such estimate or payment shall be construed to be an acceptance of any defective work or improper material. The Contractor shall be responsible for, and shall not remove from the project any material that has been included in the estimate for payment. Final payment shall be made upon the Project Manager certifying that the Contractor has satisfactorily completed the work in conformity with the Contract Documents.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Objection Right for New Sub-processors Client may reasonably object to Data Processor’s use of a new Sub-processor for reasons related to the GDPR by notifying Data Processor promptly in writing within three (3) business days after receipt of Data Processor’s notice in accordance with the mechanism set out in Section 5.2 and such written objection shall include the reasons related to the GDPR for objecting to Data Processor’s use of such new Sub-processor. Failure to object to such new Sub-processor in writing within three (3) business days following Data Processor’s notice shall be deemed as acceptance of the new Sub-Processor. In the event Client reasonably objects to a new Sub-processor, as permitted in the preceding sentences, Data Processor will use reasonable efforts to make available to Client a change in the Services or recommend a commercially reasonable change to Client’s use of the Services to avoid Processing of Personal Data by the objected-to new Sub-processor without unreasonably burdening the Client. If Data Processor is unable to make available such change within a reasonable period of time, which shall not exceed thirty (30) days, Client may, as a sole remedy, terminate the applicable Agreement and this DPA with respect only to those Services which cannot be provided by Data Processor without the use of the objected- to new Sub-processor by providing written notice to Data Processor provided that all amounts due under the Agreement before the termination date with respect to the Processing at issue shall be duly paid to Data Processor. Until a decision is made regarding the new Sub-processor, Data Processor may temporarily suspend the Processing of the affected Personal Data. Client will have no further claims against Data Processor due to the termination of the Agreement (including, without limitation, requesting refunds) and/or the DPA in the situation described in this paragraph.

  • Scheduling Checkout Protocols 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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