Notice and Supporting Documentation Sample Clauses

Notice and Supporting Documentation. Design-Builder shall not be entitled to an adjustment in the Guaranteed Completion Date(s) for any events that occurred more than fourteen (14) days before Design-Builder’s written notice to Owner. The written notice shall set forth, at a minimum, a description of: (a) the event giving rise to the request for an equitable adjustment in the Guaranteed Completion Date(s); (b) the nature of the impacts to Design-Builder and its Subcontractors of any tier, if any; (c) the impact to the critical path; and (d) to the extent possible the amount of the adjustment in the Guaranteed Completion Date(s) requested. Failure to properly give such written notice shall, to the extent Owner’s interests are prejudiced, constitute a waiver of Design-Builder’s right to an equitable adjustment.
AutoNDA by SimpleDocs
Notice and Supporting Documentation. Design-Builder shall not be entitled to an adjustment in the Guaranteed Completion Date(s) for any events that occurred more than fourteen (14) days before Design-Builder’s written notice to Owner. The written notice shall set forth, at a minimum, a description of:

Related to Notice and Supporting Documentation

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Supporting Documents The Company shall have received the following:

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Service Documentation The “Service Documentation” includes;

  • Other Documentation Administrative Agent shall have received all documents and instruments that Administrative Agent has then reasonably requested, in addition to those described in this Section 4.1. All such additional documents and instruments shall be reasonably satisfactory to Administrative Agent in form, substance and date.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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