Development and Approval Process Sample Clauses

Development and Approval Process. Any Party can present an Administrative Agreement, or an amendment or supplement thereto, or termination thereof, to the City for approval by way of the Joint Administrative Review Process. Once an Administrative Agreement receives City’s Administrative Approval, then, with respect to the Participating Agencies, an Administrative Agreement may be presented to the Metro Commission for review and a first reading. Sixty (60) days or more after the first reading, after the Metro Commissioners have had opportunity to consult with their respective agency staff and governing boards, the Administrative Agreement may be presented for a second reading and approved upon an affirmative vote by no less than two-thirds of the members of the Metro Commission during a duly noticed public meeting (in other words, upon the affirmative vote of no less than eight of the twelve members of the Metro Commission, irrespective of how many Metro Commissioners are present at the meeting, unless the number of Participating Agencies changes). If the second reading does not occur within One Hundred and Twenty (120) days of the first reading, the proposed Administrative Agreement shall no longer be in consideration. An Administrative Agreement, amendment thereto, or termination thereof, must receive City’s Administrative Approval and no less than a two-thirds vote by the Metro Commission before it is effective.

Development and Approval Process. 5.1 Developer agrees to develop the Title with Publisher in accordance with the terms of this Agreement and Exhibit A, and to deliver the Title and the Deliverable Items set forth in the Exhibit B to Publisher for approval, in Publisher’s sole discretion, in the manner and on the dates specified in the Delivery Schedule. Developer and Publisher agree that no major additional enhancements to the Specifications set forth in Exhibit A will be required or made by Developer without the parties’ prior mutual consent. 5.2 Upon receipt of each Deliverable Item except the alpha, beta, or golden master of a Title, Publisher shall, within ten 5.2.1. written approval of the Deliverable Item; or 5.2.2. a written list of changes that must be made before Publisher will approve such Deliverable Item. 5.3 No Deliverable Item shall be considered to be approved by Publisher and no payment will be made for completion of such Deliverable Item until Developer has received written confirmation of such approval from Publisher, or a failure to approve or provide a written list of changes has occurred, and all preceding Deliverable Items have been approved by Publisher. If any Deliverable Item requires changes before it will be approved by Publisher, the steps set forth above shall be repeated until such Deliverable Item is accepted, or until Publisher exercises its termination or completion rights under section 5.7 below. 5.4 The alpha, beta, and golden masters of a Title must be fully tested by Developer for conformity with the Specifica- tions prior to delivery to Publisher, and must meet the following criteria: 5.4.1 The initial alpha candidates must be delivered on or before the date set forth in Exhibit B, and must be fully feature and content complete, according to the description set forth in the Specifications.

Development and Approval Process. Content Developer agrees to develop the Content in accordance with the terms of this and to deliver the Content and the Deliverable Items to AVT for approval, said approval to be at AVTs sole discretion , in a manner and on the dates specified in Delivery Schedule.