We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Data day structured meetings Sample Clauses

Data day structured meetings. The Charter School will analyze curricular and instructional outcomes during Data Days, scheduled three times each academic year. The system will allow the Charter School faculty to closely monitor the needs and progress of students. Classroom teachers, coaches, administrators, and interventionists will discuss trends and concerns, modify learning groups, suggest possible interventions for students, and share best practices.

Related to Data day structured meetings

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Currency and Foreign Transactions Reporting Act The operations of the Company are and have been conducted at all times in compliance with (i) the requirements of the U.S. Treasury Department Office of Foreign Asset Control and (ii) applicable financial recordkeeping and reporting requirements of the Currency and Foreign Transaction Reporting Act of 1970, as amended, including the Money Laundering Control Act of 1986, as amended, the rules and regulations thereunder and any related or similar money laundering statutes, rules, regulations or guidelines, issued, administered or enforced by any Federal governmental agency (collectively, the “Money Laundering Laws”) and no action, suit or proceeding by or before any court or governmental agency, authority or body or any arbitrator involving the Company with respect to the Money Laundering Laws is pending or, to the Company’s knowledge, assuming reasonable inquiry, threatened.

  • Transactions Requiring Instructions In addition to the actions requiring Proper Instructions set forth herein, upon receipt of Proper Instructions and not otherwise, Chase, directly or through the use of a Securities Depository or Book-Entry System, shall: (a) Execute and deliver to such persons as may be designated in such Proper Instructions, proxies, consents, authorizations, and any other instruments whereby the authority of the Fund as owner of any securities may be exercised; (b) Deliver any securities held for the Fund against receipt of other securities or cash issued or paid in connection with the liquidation, reorganization, refinancing, merger, consolidation or recapitalization of any issuer of securities or corporation, or the exercise of any conversion privilege; (c) Deliver any securities held for the Fund to any protective committee, reorganization committee or other person in connection with the reorganization, refinancing, merger, consolidation, recapitalization or sale of assets of any issuer of securities or corporation, against receipt of such certificates of deposit, interim receipts or other instruments or documents, and cash, if any, as may be issued to it to evidence such delivery; (d) Make such transfers or exchanges of the assets of the Fund and take such other steps as shall be stated in said instructions to be for the purpose of effectuating any duly authorized plan of liquidation, reorganization, merger, consolidation or recapitalization of the Fund; (e) Release securities belonging to the Fund to any bank or trust company for the purpose of pledge or hypothecation to secure any loan incurred by the Fund; provided, however, that securities shall be released only upon payment to Chase of the monies borrowed, or upon receipt of adequate collateral as agreed upon by the Fund and Chase which may be in the form of cash or obligations issued by the U.S. government, its agencies or instrumentalities, except that in cases where additional collateral is required to secure a borrowing already made, subject to proper prior authorization, further securities may be released for that purpose; and pay such loan upon re-delivery to it of the securities pledged or hypothecated therefore and upon surrender of the note or notes evidencing the loan; (f) Deliver securities in accordance with the provisions of any agreement among the Fund, Chase and a broker-dealer registered under the Securities Exchange Act of 1934 (the "Exchange Act") and a member of The National Association of Securities Dealers, Inc. ("NASD"), relating to compliance with the rules of The Options Clearing Corporation and of any registered national securities exchange, or of any similar organization or organizations, regarding escrow or other arrangements in connection with transactions by the Funds; (g) Deliver securities in accordance with the provisions of any agreement among the Fund, Chase and a Futures Commission Merchant registered under the Commodity Exchange Act, relating to compliance with the rules of the Commodity Futures Trading Commission and/or any Contract Market, or any similar organization or organizations, regarding account deposits in connection with transactions by the Fund; (h) Deliver securities against payment or other consideration or written receipt therefore for transfer of securities into the name of the Fund or Chase or a nominee of either, or for exchange or securities for a different number of bonds, certificates, or other evidence, representing the same aggregate face amount or number of units bearing the same interest rate, maturity date and call provisions, if any; provided that, in any such case, the new securities are to be delivered to Chase; (i) Exchange securities in temporary form for securities in definitive form; (j) Surrender, in connection with their exercise, warrants, rights or similar securities, provided that in each case, the new securities and cash, if any, are to be delivered to Chase; (k) Deliver securities upon receipt of payment in connection with any repurchase agreement related to such securities entered into by the Fund; and (l) Deliver securities pursuant to any other proper corporate purpose, but only upon receipt of, in addition to Proper Instructions, a certified copy of a resolution of the Board of Trustees or of the Executive Committee signed by an officer of the Funds and certified by the Secretary or an Assistant Secretary, specifying the securities to be delivered, setting forth the purpose for which such delivery is to be made, declaring such purpose to be a proper corporate purpose, and naming the person or persons to whom delivery of such securities shall be made.

  • Publication of Procurement Contract 48.1 Within fourteen days after signing the contract, the Procuring Entity shall publish and publicize the awarded contract at its notice boards, entity website; and on the Website of the Authority in manner and format prescribed by the Authority. At the minimum, the notice shall contain the following information: a) name and address of the Procuring Entity; b) name and reference number of the contract being awarded, a summary of its scope and the selection method used; c) the name of the successful Tenderer, the final total contract price, the contract duration. d) dates of signature, commencement and completion of contract; e) names of all Tenderers that submitted Tenders, and their Tender prices as read out at Tender opening;

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Per-­‐Registrar Transactions Report This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 02 iana-­‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Cooperative Master Contract Sales Reporting. Contractor shall report total Cooperative Master Contract sales quarterly to Enterprise Services, as set forth below. Cooperative Master Contract Sales Reporting System. Contractor shall report quarterly Cooperative Master Contract sales in Enterprise Services’ Cooperative Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Cooperative Master Contract. If there are no Cooperative Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Cooperative Master Contract Sales Reporting. Quarterly Cooperative Master Contract Sales Reports must be submitted electronically by the following deadlines for all Cooperative Master Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.5 percent on the purchase price for all Cooperative Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Cooperative Master Contract sales invoiced (not including sales tax) x .015. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Cooperative Master Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Cooperative Master Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Cooperative Master Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Cooperative Master Contract sales, to submit a timely Cooperative Master Contract sales report, or to remit timely payment of the VMF to Enterprise Services, may be cause for Enterprise Services to suspend Contractor or terminate this Cooperative Master Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Cooperative Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Cooperative Master Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Cooperative Master Contract sales report. Such report shall include, at a minimum: the Goods/Services sold (including, as applicable, item number or other identifier), per unit quantities sold, items and volumes purchased by Purchaser, shipment/delivery locations by Purchaser, and Cooperative Master Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Cooperative Master Contract.

  • Transactions in Foreign Custody Account (a) Except as otherwise provided in paragraph (b) of this Section 3.8, the provision of Sections 2.2 and 2.7 of this Contract shall apply, mutatis mutandis to the foreign securities of the Fund held outside the United States by foreign sub-custodians. (b) Notwithstanding any provision of this Contract to the contrary, settlement and payment for securities received for the account of each applicable Portfolio and delivery of securities maintained for the account of each applicable Portfolio may be effected in accordance with the customary established securities trading or securities processing practices and procedures in the jurisdiction or market in which the transaction occurs, including, without limitation, delivering securities to the purchaser thereof or to a dealer therefor (or an agent for such purchaser or dealer) against a receipt with the expectation of receiving later payment for such securities from such purchaser or dealer. (c) Securities maintained in the custody of a foreign sub-custodian may be maintained in the name of such entity's nominee to the same extent as set forth in Section 2.3 of this Contract, and the Fund agrees to hold any such nominee harmless from any liability as a holder of record of such securities.

  • Agency Cross Transactions From time to time, the Advisor or brokers or dealers affiliated with it may find themselves in a position to buy for certain of their brokerage clients (each an "Account") securities which the Advisor's investment advisory clients wish to sell, and to sell for certain of their brokerage clients securities which advisory clients wish to buy. Where one of the parties is an advisory client, the Advisor or the affiliated broker or dealer cannot participate in this type of transaction (known as a cross transaction) on behalf of an advisory client and retain commissions from one or both parties to the transaction without the advisory client's consent. This is because in a situation where the Advisor is making the investment decision (as opposed to a brokerage client who makes his own investment decisions), and the Advisor or an affiliate is receiving commissions from both sides of the transaction, there is a potential conflicting division of loyalties and responsibilities on the Advisor's part regarding the advisory client. The Securities and Exchange Commission has adopted a rule under the Investment Advisers Act of 1940, as amended, which permits the Advisor or its affiliates to participate on behalf of an Account in agency cross transactions if the advisory client has given written consent in advance. By execution of this Agreement, the Trust authorizes the Advisor or its affiliates to participate in agency cross transactions involving an Account. The Trust may revoke its consent at any time by written notice to the Advisor.

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm