Contractors Request for a Change Order Sample Clauses

Contractors Request for a Change Order 
AutoNDA by SimpleDocs

Related to Contractors Request for a Change Order

  • Change Order The Change Order is then submitted to the Project Manager who immediately processes the CO with OPC as required by Bulletin 3.5 and BGS’ Contracting Plan.

  • Change Orders Any alteration or deviation from the Services mentioned or any other contractual specifications that result in a revision of this Agreement shall be executed and attached to this Agreement as a change order (“Change Order”).

  • Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Notice of Work Schedules ‌ (a) Work schedules for regular employees shall be posted at least 14 days in advance of the starting day of a new schedule. (b) In the event that the work schedule or shift for a regular employee or an auxiliary employee working a scheduled shift roster is changed without 48 hours' advance notice and such change is the result of the actions of another employee covered by this agreement utilizing the benefits provided for by the provisions of this agreement, the employee will receive a premium of 85¢ per hour in addition to their regular pay, for work performed on the first shift to which they changed. (c) In the event that an employee's work schedule or shift is changed without five days advance notice and the change results from causes other than defined in (b) above, the employee shall receive a premium at the applicable overtime rate for work performed on the first shift to which they changed, except that if the change results from no fault of the Employer they shall not receive a premium at overtime rates but shall receive the premium defined under (b) above.

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.

  • Drawings and Specifications 9.1 A complete list of all Drawings that form a part of the Contract Documents are to be found as an index on the Drawings themselves, and/or may be provided to Developer and/or in the Table of Contents. 9.2 Materials or Work described in words that so applied have a well-known technical or trade meaning shall be deemed to refer to recognized standards, unless noted otherwise. 9.3 Trade Name or Trade Term It is not the intention of the Contract Documents to go into detailed descriptions of any materials and/or methods commonly known to the trade under “trade name” or “trade term.” The mere mention or notation of “trade name” or “trade term” shall be considered a sufficient notice to Developer that it will be required to complete the work so named, complete, finished, and operable, with all its appurtenances, according to the best practices of the trade. 9.4 The naming of any material and/or equipment shall mean furnishing and installing of same, including all incidental and accessory items thereto and/or labor therefor, as per best practices of the trade(s) involved, unless specifically noted otherwise. 9.5 Contract Documents are complementary, and what is called for by one shall be binding as if called for by all. As such, Drawings and Specifications are intended to be fully cooperative and to agree. However, if Developer observes that Drawings and Specifications are in conflict with the Contract Documents, Developer shall promptly notify District and Architect in writing, and any necessary changes shall be made as provided in the Contract Documents. 9.6 Figured dimensions shall be followed in preference to scaled dimensions, and Developer shall make all additional measurements necessary for the work and shall be responsible for their accuracy. Before ordering any material or doing any work, each Developer shall verify all measurements at the building and shall be responsible for the correctness of same. 9.7 Should any question arise concerning the intent or meaning of the Contract Documents, including the Plans and Specifications, the question shall be submitted to the District for interpretation. If a conflict exists in the Contract Documents, these Construction Provisions shall control over the Facilities Lease, which shall control over the Site Lease, which shall control over Division 1 Documents, which shall control over Division 2 through Division 49 documents, which shall control over figured dimensions, which shall control over large-scale drawings, which shall control over small-scale drawings. In no case shall a document calling for lower quality and/or quantity of material or workmanship control. However, in the case of discrepancy or ambiguity solely between and among the Drawings and Specifications, the discrepancy or ambiguity shall be resolved in favor of the interpretation that will provide District with the functionally complete and operable Project described in the Drawings and Specifications. 9.8 Drawings and Specifications are intended to comply with all laws, ordinances, rules, and regulations of constituted authorities having jurisdiction, and where referred to in the Contract Documents, the laws, ordinances, rules, and regulations shall be considered as a part of the Contract Documents within the limits specified. 9.9 As required by Section 4-317(c), Part 1, Title 24, CCR: “Should any existing conditions such as deterioration or non-complying construction be discovered which is not covered by the DSA-approved documents wherein the finished work will not comply with Title 24, California Code of Regulations, a construction change document, or a separate set of plans and specifications, detailing and specifying the required repair work shall be submitted to and approved by DSA before proceeding with the repair work.”

  • Escrow Format Specification 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!