Event Preparation Sample Clauses

Event Preparation. On Shabbat or Yom Tov morning, no preparations or set‐up may interfere with any Minyan or with Youth Groups. Any equipment associated with the Event must not be visible during davening. When preparing for an Event, during the Event and subsequent to the Event, Renter and the caterer and other service providers shall use their best efforts to minimize noise, disturbances and interference with the Minyanim and other activities that may be taking place in the Shul.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Event Preparation. If early entry to the Hall is required to prepare for an event, permission must be obtained from the Bookings Secretary in advance; an additional charge may be made.
Sample 1Sample 2Sample 3See All (5)
Event Preparation. Preparations or set-up for events may not interfere with Youth Groups or services. When preparing for an event, during the event and subsequent to the event, Renter and the caterer and other service providers shall use their best efforts to minimize noise, disturbances and interference with the minyanim and other activities that may be taking place in the Shul.
Sample 1Sample 2
Event Preparation. The Lessee agrees that all event preparation, including deliveries, set up and decoration of the Premises must take place only during the Event times as described in Section 4 unless otherwise agreed by the Lessor in writing prior to the Event. Additional fees may apply if the premature arrival of event deliveries interferes with the use of the premises by the Lessor or another Lessee.
Sample 1
Event Preparation. When preparing for an Event, during the Event and subsequent to the Event, Renter and the caterer and other service providers shall use their best efforts to minimize noise, disturbances and interference with the Minyanim and other activities that may be taking place in the Shul.
Sample 1
Event Preparation. Please consider the material composition and usefulness of items that you will be handing out to [Event] attendees, such as brochures and giveaways. These items should be limited. Try to avoid purchase of over-packaged items, and only give something away that will really be used. Avoid using plastic single-serve containers, foil, or other packaging destined for the landfill for food samples; opt for paper or compostable wax paper packaging instead.
Sample 1

Related to Event Preparation

  • Joint Preparation The preparation of this Agreement has been a joint effort of the parties and the resulting documents shall not, solely as a matter of judicial construction, be construed more severely against one of the parties than the other.

  • DOCUMENT PREPARATION The Transfer/Deed shall, save for the Land Transfer Tax Affidavit, be prepared in registrable form at the expense of Seller, and any Charge/Mortgage to be given back by the Buyer to Seller at the expense of the Buyer. If requested by Buyer, Seller covenants that the Transfer/Deed to be delivered on completion shall contain the statements contemplated by Section 50(22) of the Planning Act, R.S.O.1990.

  • Proposal Preparation The contractor shall assume all costs associated with preparation of proposals for task order awards under the proposal process as an indirect charge (B&P costs). The Government will not reimburse awardees for proposals as a direct charge.

  • Surface Preparation Clean the surface to be treated of all dust, dirt, clay, grass, sod and any other deleterious matter before application of the asphalt surface treatment.

  • Site Preparation Axon will provide a hardcopy or digital copy of current user documentation for the Axon Devices ("User Documentation"). User Documentation will include all required environmental specifications for the professional services and Axon Devices to operate per the Axon Device User Documentation. Before installation of Axon Devices (whether performed by Customer or Axon), Customer must prepare the location(s) where Axon Devices are to be installed ("Installation Site") per the environmental specifications in the Axon Device User Documentation. Following installation, Customer must maintain the Installation Site per the environmental specifications. If Axon modifies Axon Device User Documentation for any Axon Devices under this Agreement, Axon will provide the update to Customer when Axon generally releases it

  • Costs of negotiation, preparation etc The Borrowers shall pay to the Agent on its demand the amount of all expenses incurred by the Agent or the Security Trustee in connection with the negotiation, preparation, execution or registration of any Finance Document or any related document or with any transaction contemplated by a Finance Document or a related document.

  • Preparation; Reasonable Investigation In connection with the ------------------------------------- preparation and filing of each registration statement under the Securities Act pursuant to this Agreement, the Company will give the holders of Registrable Securities registered under such registration statement, their underwriters, if any, and their respective counsel and accountants, the opportunity to participate in the preparation of such registration statement, each prospectus included therein or filed with the Commission, and each amendment thereof or supplement thereto, and will give each of them such access to its books and records and such opportunities to discuss the business of the Company with its officers and the independent public accountants who have certified its financial statements as shall be necessary, in the opinion of such holders' and such underwriters' respective counsel, to conduct a reasonable investigation within the meaning of the Securities Act.

  • Preparation Awarded vendor shall not begin a project for which TIPS Member has not prepared the site, unless awarded vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in a purchase order. Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre-installation requirements. Registered sex offender restrictions: For work to be performed at schools, awarded vendor agrees that no employee of a sub-contractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present. Awarded vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the purchase order at the TIPS Member’s discretion. Awarded vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety measures: Awarded vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Awarded vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage.

  • Preparation Period During the preparation period, a teacher will have no other assignment except in an emergency situation. It is recognized that the preparation period is a scheduled part of the teacher's work day and the teacher is expected to be in his/her respective Building. If the teacher must leave the Building during his/her preparation and/or lunch period, he/she must notify the Building switchboard operator.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

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