Comfortable Transition Sample Clauses

Comfortable Transition. All of the team groups are important because we push sponsors and upline leaders to do their best as leaders but they can't if they are not given the chance to reach out to each of their downline… and we are not talking just direct downline... we are talking about ALL downline in their team… which includes the newest all the way at the bottom of their downline list. It is important to be a member of each team group in your upline leader hierarchy to ensure that in the event you should choose to leave Party Time Mixes that your downline has formed a secure bond or connection with your Sponsor and Upline Leaders. We require sponsors and upline leaders to be active with all of their downline because we never know when a sponsor with a large team will either forget their $10 quota or may have to leave because of health issues or family issues and we don't want the downline of the leaving sponsor to move up to the upline leader next in line only to not have any kind of relationship or connection with them. It's a hard transition for those being moved up and we don't want that. We want transitions to be seamless and easy and comfortable for those being moved up. It's hard enough to lose your sponsor... imagine losing your sponsor just to be under someone you don't even know. We are not trying to be problematic by making this a requirement! We are being protective of downline to make sure that no one is ever left feeling lost, forgotten, unloved or untended! This requirement is our effort to protect all downline from the difficult experience of losing their sponsor for whatever reason they leave. Some consultants may not appreciate being required to be in all team groups offered from their sponsor all the way up to their top upline leader! We don’t like having to make it a requirement either, but it is a necessity. How do we know it’s a necessity… it’s because we saw what happened when we didn’t make it a requirement and many downline left because they didn’t feel comfortable with the upline leaders they were moved up to because they didn’t feel connected or bonded with them! That’s why it is imperative this Upline Leader connection is formed with as many of their downline as xxxxxxxx.Xx’s ok that other DS companies do not require this... as we have said many times…we are different from them in every way! All downline have the right to contact their Upline Leaders all the way to the top under the company! We obviously cannot force you to be a member of these team...
AutoNDA by SimpleDocs

Related to Comfortable Transition

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • Community Engagement Integration Activities The SP will support the HSP to engage the community of diverse persons and entities in the area where it provides health services when setting priorities for the delivery of health services and when developing plans for submission to the LHIN including but not limited to CAPS and integration proposals.

  • Transition Period Due to the nature of our purchasing process, the District often requires an existing service provider to continue to provide goods and/or services while the District is in the process of advertising, evaluating, and awarding a contract for the provision of the same goods and/or services in the future. To accommodate this process, the Contractor shall agree to maintain the same terms and conditions set forth in this Agreement for a period up to ninety (90) days after the automatic termination of this Agreement at the end of its term, if requested by the District, as a transition period. In addition, if the Contractor is not the successful bidder for a future solicitation for the same or similar services, he or she shall agree to provide the same goods and/or services provided in this Agreement for a period up to ninety (90) days to allow for an orderly transition to the new provider. The District and the Contractor may mutually agree to a longer transition period.

  • Transition Seller will not take any action that is designed or intended to have the effect of discouraging any lessor, licensor, customer, supplier, or other business associate of the Company from maintaining the same business relationships with the Company after the Closing as it maintained with the Company prior to the Closing. The Seller will refer all customer inquiries relating to the business of the Company to the Purchaser from and after the Closing.

  • Actions We May Take if You Engage in Any Restricted Activities If we believe that you’ve engaged in any of these activities, we may take a number of actions to protect PayPal, its customers and others at any time in our sole discretion. The actions we make take include, but are not limited to, the following: • Terminate this user agreement, limit your account, and/or close or suspend your account, immediately and without penalty to us; • Refuse to provide the PayPal services to you in the future; • At any time and without liability, suspend, limit or terminate your access to our websites, software, systems (including any networks and servers used to provide any of the PayPal services) operated by us or on our behalf, your PayPal account or any of the PayPal services, including limiting your ability to pay or send money with any of the payment methods linked to your PayPal account, restricting your ability to send money or make withdrawals; • Hold your money to the extent and for so long as reasonably needed to protect against the risk of liability. You acknowledge that, as a non-exhaustive guide: • PayPal’s risk of liability in respect of card-funded payments that you receive can last until the risk of a chargeback closing in favour of the payer/buyer (as determined by card scheme rules) has passed. This depends on certain factors, including, without limitation:

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • DEPENDENT PERSONAL SERVICES 1. Subject to the provisions of Articles 16, 18 and 19, salaries, wages and other similar remuneration derived by a resident of a Contracting State in respect of an employment shall be taxable only in that State unless the employment is exercised in the other Contracting State. If the employment is so exercised, such remuneration as is derived therefrom may be taxed in that other State.

  • Required Activities 1. Biometrics measuring blood pressure, weight and height for BMI, fasting cholesterol (total and LDL) and fasting glucose 33% 2. Completion of the online Health Survey 33%

  • Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-­‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.

Time is Money Join Law Insider Premium to draft better contracts faster.