DUE DATE AND TIMELINES Sample Clauses

DUE DATE AND TIMELINES. 14.3.1. All due dates, deadlines and timelines in this Statement of Work are measured in calendar days unless specifically stated otherwise. Additionally, all due dates, deadlines and timelines in this Contract, based on quarters, refer to state fiscal year calendar quarters, with the first quarter beginning on July 1st of each year. In the event that any due date or deadline falls on a weekend, a Department holiday or other day the Department is closed, the due date or deadline shall be automatically extended to the next business day the Department is open.
AutoNDA by SimpleDocs
DUE DATE AND TIMELINES. EXHIBIT E-1 DELIVERABLES  All due dates, deadlines and timelines in the contract Statement of Work are measured in calendar days unless specifically stated otherwise. Additionally, all due dates, deadlines and timelines in this Contract, based on quarters, refer to state fiscal year calendar quarters, with the first quarter beginning on July 1st of each year. In the event that any due date or deadline falls on a weekend, a Department holiday or other day the Department is closed, the due date or deadline shall be automatically extended to the next business day the Department is open.  The Department may, in its sole discretion, extend the due date, deadline or timeline of any activity, deliverable or requirement under this Statement of Work. Any such extension shall only be valid if it is delivered to the Contractor in writing, in either a hard copy or electronic format.  All Contract deliverables shall be submitted electronically to xxx@xxxxx.xx.xx, the Department’s contract manager, and other Department staff, as determined by the Department.

Related to DUE DATE AND TIMELINES

  • Actions and timeframes The parties agree the following actions and timeframes will be used:

  • Accurate and Timely Submission of Reports a) The reports and administrative fees shall be accurate and timely and submitted in accordance with the due dates specified in this section. Vendor shall correct any inaccurate reports or administrative fee payments within three (3) business days upon written notification by DIR. Vendor shall deliver any late reports or late administrative fee payments within three (3) business days upon written notification by DIR. If Vendor is unable to correct inaccurate reports or administrative fee payments or deliver late reports and fee payments within three

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

  • 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.

  • ATTACHMENT B Applicable California Vehicle Code and Civil Code Provisions Note: Many California laws, which govern a tow Operator’s business and vehicle operations, are included in this attachment. The is list of California statutes included herein is intended as a general guide only and is not meant to be considered all-inclusive. It is the tow Operator’s responsibility to know and comply with all federal and state statutes and all local ordinances relating to his/her business operations, including those that are referred to in this document and those that are not; any new statutes or ordinances that are subsequently adopted; and any amendments, repeals, or modifications of existing statutes and ordinances, including but not limited to those described in this attachment.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Final Project Report Prepare a Final Project Report that addresses, to the extent feasible, comments made by the Grant Manager on the Draft Final Project Report. Submit one (1) reproducible master and an electronic copy of the final. Upload an electronic copy of the final report in pdf format to the FAAST system.

  • Accurate and Timely Contract Information Vendor warrants and represents that the website information specified in the above paragraph will be accurately and completely posted, maintained and displayed in an objective and timely manner. Vendor, at its own expense, shall correct any non- conforming or inaccurate information posted at Vendor’s website within ten (10) business days after written notification by DIR.

  • EODUF Packing Specifications 7.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.

  • Optional Xactimate Response Attachment (Part 2)

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