Conditional Requests for Delay Sample Clauses

Conditional Requests for Delay. United States x. Xxxxxx, 37 X.X. 553 (A.C.M.R. 1993). Defense counsel submitted a post-trial “Conditional Request for Delay” to cover a portion of time between the preferral of charges and the date of trial. Defense counsel was willing to accept either 37 or 72 days of processing time in return for sentence mitigation by the convening authority. Ambiguity in convening authority’s acceptance was resolved in favor of accused. A.C.M.R. pronounced that “for obvious reasons, we strongly recommend that convening authorities and staff judge advocates not entertain agreements of this nature in the future.”
AutoNDA by SimpleDocs

Related to Conditional Requests for Delay

  • Force Majeure, Notice of Delay, and No Damages for Delay The Contractor will not be responsible for delay resulting from its failure to perform if neither the fault nor the negligence of the Contractor or its employees or agents contributed to the delay and the delay is due directly to acts of God, wars, acts of public enemies, strikes, fires, floods, or other similar cause wholly beyond the Contractor’s control, or for any of the foregoing that affect subcontractors or suppliers if no alternate source of supply is available to the Contractor. In case of any delay the Contractor believes is excusable, the Contractor will notify the Department or Customer in writing of the delay or potential delay and describe the cause of the delay either (1) within 10 days after the cause that creates or will create the delay first arose, if the Contractor could reasonably foresee that a delay could occur as a result, or (2) if delay is not reasonably foreseeable, within five days after the date the Contractor first had reason to believe that a delay could result. The foregoing will constitute the Contractor’s sole remedy or excuse with respect to delay. Providing notice in strict accordance with this paragraph is a condition precedent to such remedy. No claim for damages will be asserted by the Contractor. The Contractor will not be entitled to an increase in the Contract price or payment of any kind from the Department or Customer for direct, indirect, consequential, impact or other costs, expenses or damages, including but not limited to costs of acceleration or inefficiency, arising because of delay, disruption, interference, or hindrance from any cause whatsoever. If performance is suspended or delayed, in whole or in part, due to any of the causes described in this paragraph, after the causes have ceased to exist the Contractor will perform at no increased cost, unless the Department or Customer determines, in its sole discretion, that the delay will significantly impair the value of the Contract to the State of Florida or to Customers, in which case the Department or Customer may (1) accept allocated performance or deliveries from the Contractor, provided that the Contractor grants preferential treatment to Customers with respect to commodities or contractual services subjected to allocation, or (2) purchase from other sources (without recourse to and by the Contractor for the related costs and expenses) to replace all or part of the commodity or contractual services that are the subject of the delay, which purchases may be deducted from the Contract quantity, or (3) terminate the Contract in whole or in part.

  • Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.

  • Notice to Proceed - Site Improvements The Recipient shall not commence, or cause to be commenced, any site improvements or other work on the Land until the Director has issued a Notice to Proceed to the Recipient. Such Notice to Proceed will not be issued until the Director is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and has completed any land acquisition required by the Project. A Notice to Proceed shall be required for all Project prime contractors or direct procurement initiated by the Recipient following execution of this Agreement.

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • Notice of Schedule For any NEO that takes place on a regular, recurring schedule, the sponsoring Department shall be responsible for providing annual notice to the Union. For NEOs that are not offered on a regular, recurring schedule, the sponsoring Department shall provide no less than ten (10) business days’ notice. Said notices shall be provided by email, to the Union NEO Coordinator. This requirement shall apply to all NEOs in which City personnel provide newly-hired employees with information regarding employment status, rights, benefits, duties, responsibilities, or any other employment-related matters.

  • Form and substance of requests for assistance 1. Requests pursuant to this Protocol shall be made in writing. They shall be accompanied by the documents necessary to enable compliance with the request. When required because of the urgency of the situation, oral requests may be accepted, but must be confirmed in writing immediately.

  • Deadlines for Providing Insurance Documents after Renewal or Upon Request As set forth herein, certain insurance documents must be provided to the OGS Procurement Services contact identified in the Contract Award Notice after renewal or upon request. This requirement means that the Contractor shall provide the applicable insurance document to OGS as soon as possible but in no event later than the following time periods:  For certificates of insurance: 5 business days  For information on self-insurance or self-retention programs: 15 calendar days  For other requested documentation evidencing coverage: 15 calendar days  For additional insured and waiver of subrogation endorsements: 30 calendar days Notwithstanding the foregoing, if the Contractor shall have promptly requested the insurance documents from its broker or insurer and shall have thereafter diligently taken all steps necessary to obtain such documents from its insurer and submit them to OGS, OGS shall extend the time period for a reasonable period under the circumstances, but in no event shall the extension exceed 30 calendar days.

  • Notice to Proceed (NTP Following the JOA and purchase order issuance, the County will issue a Notice to Proceed (NTP) that will provide the construction start date, the Work duration period, and the Substantial Completion date. The Contractor agrees to begin and complete construction within the dates specified on the NTP. The County must approve all extensions of time in writing. The County may also issue an Emergency Notice to Proceed (NTP). In the event the County requires the Contractor to respond to an immediate request for work, a Job Order will be created and an Emergency NTP will be issued. The Contractor will be required to perform the Scope of Work included with the Emergency NTP as directed by the County’s Project Manager or designee. The Detailed Scope of Work, Quotation, Subcontractor Listing, Shop Drawings and required Non Pre-priced backup documentation will be submitted upon completion of the emergency work in accordance with the Ordering Procedures detailed in Section III above.

  • NOTICE OF DELAYS Except as otherwise provided under this Contract, when either party has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this Contract, that party shall, within one (1) business day, give notice thereof, including all relevant information with respect thereto, to the other party.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

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