Petition Process Sample Clauses

Petition Process a. Release from First-year Student Live-on-campus Requirement. Student may request that CU Boulder release the requirement that first-year students live on campus by completing a petition available in the MyCULiving portal and submitting it to Housing & Dining in accordance with the directions on the form. Housing & Dining will review submitted petitions and respond to Student within 10 business days. b. Grounds for Release from First-year Student Live-on-campus Requirement. CU Boulder will approve release from the live-on campus requirement under the following circumstances: (1) Student notifies Housing & Dining and provides support documentation that they are military reservist who was called to active status during a national or state emergency; (2) Student has a Medical Marijuana card and provides a copy of the card to Housing & Dining; (3) Student has a concealed carry permit, provides Housing & Dining with the permit, and notifies Housing & Dining that Student wishes to carry a handgun in accordance with the permit; (4) Student wishes to resides at a permanent address and commute a reasonable distance (as determined by CU Boulder) and provides Housing & Dining documentation establishing permanent residency; (5) Student is married and provides Housing & Dining a copy of a marriage or domestic partnership license; (6) Student provides documentation to Housing & Dining establishing Student is not a first-year student; and (7) Student has provided evidence that Housing & Dining deems appropriate to establish that Student should be released from the requirement.
AutoNDA by SimpleDocs
Petition Process a. Release from First-year Student Live-on-campus Requirement. Student may request that CU Boulder release the requirement, if applicable, that they live on campus by completing a petition available in the MyCULiving portal and submitting it to Housing & Dining in accordance with the directions on the form. Housing & Dining will review submitted petitions and respond to Student within 10 business days. Releases are not granted until Housing & Dining communicates written approval to Student. b. Grounds for Release from Live-on-campus Requirement. CU Boulder will approve release from the live-on campus requirement under the following circumstances: (1) Student notifies Housing & Dining and provides support documentation that they are a military reservist who was called to active status during a national or state emergency;
Petition Process 

Related to Petition Process

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

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

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Arbitration Process Any arbitration will be conducted pursuant to the applicable rules (the “Arbitration Rules”) of the American Arbitration Association, as modified herein, to the extent such modifications are not prohibited by the Arbitration Rules. The arbitration will be conducted in Indianapolis, Indiana. The parties will select a single arbitrator, but in the event that the parties are unable to agree, the arbitrator will be appointed pursuant to the Arbitration Rules. The arbitrator will be a practicing attorney with significant expertise in litigating and/or presiding over cases involving the substantive legal areas involved in the dispute. The parties to the arbitration will not request, and the arbitrator will not order, that any discovery be taken or provided, including depositions, interrogatories or document requests, except to the extent the amount in controversy exceeds $50,000. The arbitration will be concluded within three months of the date the arbitrator is appointed. The arbitrator’s findings, reasoning, decision, and award will be stated in writing and based upon applicable law. Judgment on the arbitration award may be entered in any court having jurisdiction. In the event that the arbitration results in an award which imposes an injunction or contains a monetary award in excess of $100,000, the award will be reviewable on appeal initiated by filing notice of appeal with the AAA office within 30 days of the award, governed by the AAA Optional Appellate Arbitration Rules and conducted by a panel of three new arbitrators, ruling by majority, under the procedure for appointment from the national roster of arbitrators. Unless the applicable Arbitration Rules require otherwise, arbitration fees and costs will be shared equally by the claimant(s) and respondent(s), respectively, in any arbitration proceeding. Should the AAA be unavailable, unable or unwilling to accept and administer the arbitration of any claim under these arbitration provisions as written, the parties will agree on a substitute arbitration organization, such as JAMS, that will enforce the arbitration provisions as written. Because this Agreement memorializes a transaction in interstate commerce, the Federal Arbitration Act governs the interpretation and enforcement of these arbitration provisions. More information about arbitration, including the Arbitration Rules, is available at xxx.xxx.xxx or by calling 0-000-000-0000.

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Complaints Process The School shall establish and adhere to a process for resolving public complaints which shall include an opportunity for complainants to be heard. The final administrative appeal shall be heard by the School's Governing Board, except where the complaint pertains to a possible violation of any law or term under this Contract. The complaints process shall be readily accessible from the School’s website, as described in Section 11.4.1.

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Litigation; Proceedings Except as specifically disclosed in Schedule 3.1(g), there is no action, suit, notice of violation, proceeding or investigation pending or, to the best knowledge of the Company, threatened against or affecting the Company or any of its Subsidiaries or any of their respective properties before or by any court, governmental or administrative agency or regulatory authority (federal, state, county, local or foreign) which (i) relates to or challenges the legality, validity or enforceability of any of the Transaction Documents, the Shares or the Underlying Shares, (ii) could, individually or in the aggregate, have a Material Adverse Effect or (iii) could, individually or in the aggregate, materially impair the ability of the Company to perform fully on a timely basis its obligations under the Transaction Documents.

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