Franchisee Operational and Staff Requirements Sample Clauses

Franchisee Operational and Staff Requirements. (a) Franchisee shall operate an Approved Broker Management System pursuant to paragraphs 9.02(b) and 9.02(c) hereof in a competent manner and failure to do so constitutes a material breach of this Agreement. (b) All Locations shall remain open on a full-time and continuous basis, except Seasonal Locations (which may be designated as Seasonal Locations only upon the prior written consent of Franchisor and which are subject to the operational restrictions set forth in the Operations Manual), except as caused by acts of God or other matters beyond the control of Franchisee (other than Franchisee’s inability to procure money). (c) Once a Location is Abandoned, it may not be reopened by Franchisee except as a new Additional Location, after compliance with all procedures and payment of fees applicable to Additional Locations. (d) Upon expiration of the limited period of operation, unless extended by Franchisor in its sole discretion, a Satellite Office shall be either converted into an Additional Location pursuant to paragraph 4.03 hereof (with all required, applicable fees paid to Franchisor in such event) or closed (pursuant to paragraph 4.02). (e) Franchisee shall provide Franchisor with an estimate of the period of operation of each Subdivision Sales Office and a summary of any other pertinent details requested by Franchisor. A Subdivision Sales Office may be established by Franchisee only upon the written consent of Franchisor, which consent shall not be unreasonably withheld but which consent may be subject to certain conditions at commencement of operations or any time thereafter, including (i) limitations on the authorized period and scope of operation and (ii) a requirement to operate and utilize an Approved Broker Management System or such other real estate software system specified in the Operations Manual for use in Subdivision Sales Offices. (f) Franchisee acknowledges that the System provides the opportunity to participate in a referral service that promotes broker-to-broker referrals of business on a nationwide basis between Franchisee and other brokers (currently Prudential Referral Services, Inc.) and agrees that Franchisee is obligated to observe all terms, conditions and general referral policies at any time applicable to participants in such services. Franchisee agrees to confirm its participation on these terms by executing the document captioned “Broker to Broker Referral Terms and Condition attached hereto as Exhibit C. Franchisee further ...
Sample 1Sample 2
AutoNDA by SimpleDocs
Franchisee Operational and Staff Requirements. Section 9.01(b) of the Franchise Agreement is hereby deleted and replaced with the following: “All Locations, including Restricted Purpose Locations, shall remain open on a full-time and continuous basis (generally understood to be a minimum of five (5) days a week), except as caused by acts of God or other matters beyond the control of Franchisee (other than Franchisee’s inability to procure money).”
Sample 1Sample 2

Related to Franchisee Operational and Staff Requirements

  • Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct the following activities in accordance with the indicated procedural and operational requirements: a. LPHA must operate its Communicable Disease program in accordance with the Requirements and Standards for the Control of Communicable Disease set forth in ORS Chapters 431, 432, 433 and 437 and OAR Chapter 333, Divisions 12, 17, 18, 19 and 24, as such statutes and rules may be amended from time to time. b. LPHA must use all reasonable means to investigate in a timely manner all reports of Reportable Diseases, infections, or conditions. To identify possible sources of infection and to carry out appropriate control measures, the LPHA Administrator shall investigate each report following procedures outlined in OHA’s Investigative Guidelines or other procedures approved by OHA. OHA may provide assistance in these investigations, in accordance with OAR 333-019-0000. Investigative guidelines are available at: xxxx://xxx.xxxxxx.xxx/oha/PH/DiseasesConditions/CommunicableDisease/ReportingCommuni cableDisease/ReportingGuidelines/Pages/index.aspx c. As part of its Communicable Disease control program, LPHA must, within its service area, investigate the Outbreaks of Communicable Diseases, institute appropriate Communicable Disease control measures, and submit required information in a timely manner regarding the Outbreak to OHA in Orpheus (or Opera for COVID-19 Cases and XXXXX for COVID-19 contacts) as prescribed in OHA CD Investigative Guidelines available at: d. LPHA must establish and maintain a single telephone number whereby physicians, hospitals, other health care providers, OHA and the public can report Communicable Diseases and Outbreaks to LPHA 24 hours a day, 365 days a year. LPHA may employ an answering service or 911 system, but the ten-digit number must be available to callers from outside the local emergency dispatch area, and LPHA must respond to and investigate reported Communicable Diseases and Outbreaks. e. LPHA must attend Communicable Disease 101 and Communicable Disease 303 training. f. LPHA must attend monthly Orpheus user group meetings or monthly Orpheus training webinars.

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Listing and Maintenance Requirements Compliance The Company has not in the two years preceding the date hereof received written notice from any stock exchange, market or trading facility on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing, maintenance or other requirements of such exchange, market, trading or quotation facility. The Company has no reason to believe that it does not now or will not in the future meet any such requirements.

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

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