Event Specific Communication Sample Clauses

Event Specific Communication. The provisions of this Section are subject to California and Federal law governing confidential information.
AutoNDA by SimpleDocs
Event Specific Communication. To promote the health and well-being of individual tenants and to prevent evictions, Owner and Property Manager will promptly notify MCBH should an event putting an NPLH or MHSA tenant's health, safety, or housing are at risk. In the event of an emergency where an NPLH-Eligible Household or MHSA-Eligible Household is a danger to him or herself or to others (5150 situation), Owner or Property Manager will contact the police and notify MCBH. Owner and Property Manager will also copy MCBH on all warning letters and all notices sent to an NPLH-Eligible Household or MHSA-Eligible household. Warning letters and notices will contain an appropriate referral for services sheet that outlines service resources (with contact information) available to the tenant. MCBH may assist the NPLH-Eligible Household or MHSA-Eligible Household in curing or resolving any lease violation. Within 72 hours of a warning letter, Property Manager and MCBH will meet with the applicable household (subject to the consent of the household). The Parties agree to work together to find resolutions that avoid eviction of NPLH-Eligible and MHSA-Eligible Tenants whenever possible. If an eviction is imminent, Owner will communicate with MCBH regarding the process of notices, responses and court dates, and if eviction is successful, regarding the lockout date.

Related to Event Specific Communication

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • When Must Electronic Communications Be Retained? Email that qualifies under FOIA as a public record will need to be stored pursuant to the Local Records Act, only if it is evidence of the District's organization, function, policies, procedures, or activities or contains informational data appropriate for preservation (Local Records Act, 50 ILCS 205/). An example is any email from a Board officer concerning a decision made in his or her capacity as an officer. If a Board member uses his or her personal email, he or she must copy this type of email to the appropriate District office where it will be stored. If made available, Board members should use their email accounts provided by the District and the District will automatically store the official record messages. The District will delete these official record messages as provided in an applicable, approved retention schedule. Of course, email pertaining to public business that is sent or received by a Board Member using a District-issued device or email address will be subject to FOIA, even if the email does not need to be retained under the Local Records Act.

  • PUBLIC COMMUNICATION Neither the Contractor nor any of its Staff shall make any statement to the press or issue through any media of communication any statement bearing on the Services performed or data collected under this Agreement, without the prior written approval of OSC.

  • Electronic Communication (a) Any communication to be made between the Agent and a Lender under or in connection with the Finance Documents may be made by electronic mail or other electronic means, if the Agent and the relevant Lender:

  • Consent to Electronic Communications Trend Micro may send You required legal notices and other communications about the Software and Services, including Updates, upgrades, special offers and pricing or other similar information, customer surveys or other requests for feedback (“Communications”). Trend Micro will send Communications via in-product notices or email to registered email addresses of named contacts, or will post Communications on its Websites. By accepting this Agreement, You consent to receive all Communications through these electronic means only and acknowledge and demonstrate that You can access Communications on Websites.

  • Board Member Use of Electronic Communications For purposes of this section, electronic communications includes, without limitation, electronic mail, electronic chat, instant messaging, texting, and any form of social networking. Electronic communications among a majority or more of a Board-quorum shall not be used for the purpose of discussing District business. Electronic communications among Board members shall be limited to:

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • Electronic Communications Notices and other communications to the Lenders and the L/C Issuer hereunder may be delivered or furnished by electronic communication (including e-mail and Internet or intranet websites) pursuant to procedures approved by the Administrative Agent, provided that the foregoing shall not apply to notices to any Lender or the L/C Issuer pursuant to Article II if such Lender or the L/C Issuer, as applicable, has notified the Administrative Agent that it is incapable of receiving notices under such Article by electronic communication. The Administrative Agent or the Borrower may, in its discretion, agree to accept notices and other communications to it hereunder by electronic communications pursuant to procedures approved by it, provided that approval of such procedures may be limited to particular notices or communications. Unless the Administrative Agent otherwise prescribes, (i) notices and other communications sent to an e-mail address shall be deemed received upon the sender’s receipt of an acknowledgement from the intended recipient (such as by the “return receipt requested” function, as available, return e-mail or other written acknowledgement), provided that if such notice or other communication is not sent during the normal business hours of the recipient, such notice or communication shall be deemed to have been sent at the opening of business on the next business day for the recipient, and (ii) notices or communications posted to an Internet or intranet website shall be deemed received upon the deemed receipt by the intended recipient at its e-mail address as described in the foregoing clause (i) of notification that such notice or communication is available and identifying the website address therefor.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

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