Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.
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.
Registration Process In connection with the registration of the Registrable Securities pursuant to Section 5.2.1, the Company shall: (a) Prepare and file with the SEC the Registration Statement and such amendments (including post effective amendments) to the Registration Statement and supplements to the prospectus included therein (a “Prospectus”) as the Company may deem necessary or appropriate and take all lawful action such that the Registration Statement and any amendment thereto does not, when it becomes effective, contain an untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein, not misleading and that the Prospectus forming part of the Registration Statement, and any amendment or supplement thereto, does not at any time during the period commencing on the effective date of the Registration Statement and ending on the date on which all of the Registrable Securities may be sold to the public without registration under the Securities Act in reliance on Rule 144 (the “Registration Period”) include an untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein, in light of the circumstances under which they were made, not misleading; (b) Comply with the provisions of the Securities Act with respect to the Registrable Securities covered by the Registration Statement until the earlier of (i) such time as all of such Registrable Securities have been disposed of in accordance with the intended methods of disposition by each Purchaser as set forth in the Prospectus forming part of the Registration Statement or (ii) the date on which the Registration Statement is withdrawn; (c) Furnish to each Purchaser and its legal counsel identified to the Company (i) promptly after the same is prepared and publicly distributed, filed with the SEC, or received by the Company, one copy of the Registration Statement, each Prospectus, and each amendment or supplement thereto, and (ii) such number of copies of the Prospectus and all amendments and supplements thereto and such other documents, as the Purchaser may reasonably request in order to facilitate the disposition of the Registrable Securities; (d) Register or qualify the Registrable Securities covered by the Registration Statement under such securities or “blue sky” laws of such jurisdictions as the Purchasers reasonably request, (ii) prepare and file in such jurisdictions such amendments (including post effective amendments) and supplements to such registrations and qualifications as may be necessary to maintain the effectiveness thereof at all times during the Registration Period, (iii) take all such other lawful actions as may be necessary to maintain such registrations and qualifications in effect at all times during the Registration Period, and (iv) take all such other lawful actions reasonably necessary or advisable to qualify the Registrable Securities for sale in such jurisdictions; provided, however, that the Company shall not be required in connection therewith or as a condition thereto to (A) qualify to do business in any jurisdiction where it would not otherwise be required to qualify, (B) subject itself to general taxation in any such jurisdiction or (C) file a general consent to service of process in any such jurisdiction; (e) As promptly as practicable after becoming aware of such event, notify each Purchaser of the occurrence of any event, as a result of which the Prospectus included in the Registration Statement, as then in effect, includes an untrue statement of a material fact or omits to state a material fact required to be stated therein or necessary to make the statements therein, in light of the circumstances under which they were made, not misleading, and promptly prepare an amendment to the Registration Statement and supplement to the Prospectus to correct such untrue statement or omission, and deliver a number of copies of such supplement and amendment to each Purchaser as such Purchaser may reasonably request; (f) As promptly as practicable after becoming aware of such event, notify each Purchaser (or, in the event of an underwritten offering, the managing underwriters) of the issuance by the SEC of any stop order or other suspension of the effectiveness of the Registration Statement and take all lawful action to effect the withdrawal, rescission or removal of such stop order or other suspension; (g) Take all such other lawful actions reasonably necessary to expedite and facilitate the disposition by the Purchaser of its Registrable Securities in accordance with the intended methods therefor provided in the Prospectus which are customary under the circumstances; (h) In the event of an underwritten offering, promptly include or incorporate in a Prospectus supplement or post-effective amendment to the Registration Statement such information as the underwriters reasonably agree should be included therein and to which the Company does not reasonably object and make all required filings of such Prospectus supplement or post-effective amendment as soon as practicable after it is notified of the matters to be included or incorporated in such Prospectus supplement or post-effective amendment; (i) In connection with any underwritten offering, deliver such documents and certificates as may be reasonably required by the underwriters; and (j) Cooperate with the Purchasers to facilitate the timely preparation and delivery of certificates representing Registrable Securities to be sold pursuant to the Registration Statement, which certificates shall, if required under the terms of this Agreement, be free of all restrictive legends, and to enable such Registrable Securities to be in such denominations and registered in such names as any Purchaser may request and maintain a transfer agent for the Common Stock.
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.
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.
Offering Process In connection with the Offering, each of the Co-Managers will: a. Familiarize itself to the extent it deems appropriate with the business, operations, financial condition and prospects of the Client, including the artwork to be beneficially owned by the Client and information relating to the acquisition of the artwork by Client and its affiliates; b. Review to its satisfaction the final offering circular filed with the United States Securities and Exchange Commission (“SEC”) pursuant to Rule 253(g) (the “Offering Circular”) and such other documents to be used by such Co-Manager (the “Offering Materials”) in connection with the offering of the Securities; and c. Review to its satisfaction the active and planned operational practices and procedures of the Client in the conduct of the Offering and assist the Client to meet certain applicable rules and regulations promulgated by, and guidance issued by, the SEC and Financial Industry Regulatory Authority, Inc. (“FINRA”). If each of the Co-Managers is satisfied with the results of its due diligence of Client, each Co-Manager Adviser will then be authorized to: a. Identify and contact possible high net-worth, ultra-high net-worth, and institutional investors, which might have an interest in receiving the Offering Materials and evaluating participation in the Offering; b. Engage in conversations with potential investors that express an interest in learning more about the Offering (and similar transactions) via the Masterworks Platform and were directed to the Co-Manager by the Masterworks Platform, which is controlled by an affiliate of the Client; c. Use the Offering Circular (and any other Offering Materials approved by the Client and such Co-Manager) for solicitation purposes, which the Client will distribute via the Masterworks Platform to each potential investor concurrently with or in advance of any oral communication by a registered representative with such potential investor; d. Attend meetings with Client and potential investors, and assist the Client in responding to due diligence requests from potential investors; e. Ensure to its satisfaction that Anti-Money Laundering (“AML”) procedures are implemented for all potential investors in the Offering; f. Ensure to its satisfaction that suitability assessments are conducted for all potential investors with which such Co-Manager has any communications; and g. Generally assist the Client in its sale of securities to those potential investors accepted by Client in the Offering.
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).
CENTRAL GRIEVANCE PROCESS The following process pertains exclusively to grievances on central matters that have been referred to the central process. In accordance with the School Boards Collective Bargaining Act central matters may also be grieved locally, in which case local grievance processes will apply.
Ordering Process 6.4.1 CLEC, or CLEC's agent, shall act as the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC's End User Customers contacting Qwest in error will be instructed to contact CLEC; and Qwest's End User Customers contacting CLEC in error will be instructed to contact Qwest. In responding to calls, neither Party shall make disparaging remarks about each other. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party seeking such information. 6.4.2 CLEC shall transmit to Qwest all information necessary for the ordering (Billing, Directory Listing and other information), installation, repair, maintenance and post-installation servicing according to Qwest's standard procedures, as described in the Qwest Product Catalog (PCAT) available on Qwest's public web site located at xxxx://xxx.xxxxx.xxx/wholesale/pcat. Information shall be provided using Qwest's designated Local Service Request (LSR) format which may include the LSR, End User Customer and resale forms. 6.4.3 Qwest will use the same performance standards and criteria for installation, Provisioning, maintenance, and repair of services provided to CLEC for resale under this Agreement as Qwest provides to itself, its Affiliates, its subsidiaries, other Resellers, and Qwest retail End User Customers. The installation, Provisioning, maintenance, and repair processes for CLEC's resale service requests are detailed in the Access to OSS Section of this Agreement, and are applicable whether CLEC's resale service requests are submitted via Operational Support System or by facsimile. 6.4.4 CLEC is responsible for providing to Qwest complete and accurate End User Customer Directory Listing information including initial and updated information for Directory Assistance Service, white pages directories, and E911/911 Emergency Services. The Ancillary Services Section of this Agreement contains complete terms and conditions for Directory Listings for Directory Assistance Services, white pages directories, and E911/911 Emergency Services. 6.4.5 If Qwest's retail End User Customer, or the End User Customer's New Service Provider orders the discontinuance of the End User Customer's existing Qwest service in anticipation of the End User Customer moving to a New Service Provider, Qwest will render its closing xxxx to the End User Customer, discontinuing Billing as of the date of the discontinuance of Qwest's service to the End User Customer. If the Current Service Provider, or if the End User Customer's New Service Provider orders the discontinuance of existing resold service from the Current Service Provider, Qwest will xxxx the Current Service Provider for service through the date the End User Customer receives resold service from the Current Service Provider. Qwest will notify CLEC by Operational Support System interface, facsimile, or by other agreed-upon processes when an End User Customer moves from the Current Service Provider to a New Service Provider. Qwest will not provide the Current Service Provider with the name of the New Service Provider selected by the End User Customer. 6.4.6 CLEC shall provide Qwest and Qwest shall provide CLEC with points of contact for order entry, problem resolution and repair of the resold services. These points of contact will be identified for both CLEC and Qwest in the event special attention is required on a service request. 6.4.7 Prior to placing orders on behalf of the End User Customer, CLEC shall be responsible for obtaining and having in its possession Proof of Authorization (POA), as set forth in the POA Section of this Agreement. 6.4.8 Due Date intervals for CLEC's resale service requests are established when service requests are received by Qwest through Operational Support Systems or by facsimile. Intervals provided to CLEC shall be equivalent to intervals provided by Qwest to itself, its Affiliates, its subsidiaries, other Resellers, and to Qwest's retail End User Customers.