Reporting and Documentation Requirements Sample Clauses

Reporting and Documentation Requirements. 1. Contractor agrees to provide monthly member level data reporting to include: a. month reported; b. date of service; c. type of service; d. service setting; e. disposition; f. For those served, identifying and socio-demographic data including: i. name; ii. date of birth;
AutoNDA by SimpleDocs
Reporting and Documentation Requirements. III-3 3.1.4
Reporting and Documentation Requirements. In consideration of the promises and other good and valuable consideration acknowledged and exchanged between the parties and as set forth in the executed Committed Line of Credit Facility Note and Security Agreement, together with this and all other relevant attachments, addenda, exhibits and/or schedules (collectively, the “Agreement”), entered into by and between MINISTRY PARTNERS INVESTMENT CORPORATION (the “CUSO”) and MEMBERS UNITED CORPORATE FEDERAL CREDIT UNION (“Members United”), CUSO pledges all of its property, rights and interest in: If the Collateral used to secure this Credit Facility and any other Credit Facility is specifically the CUSO’s commercial real estate mortgage loans portfolio, as described herein, therefore the Maximum Advance Amount as compared to the total value of all of the Collateral can never be more than 90% of the Maximum Advance Amount of this Credit Facility or any other cross-collateralized Credit Facility as calculated by Members United in its sole discretion. CUSO hereby agrees and covenants to provide and supplement detailed lists and/or balance sheet of the majority of then outstanding pledged Collateral herein or all pledged Collateral in the case of Installment Loans, together with and subject to, all further requirements below, as indicated by Members United, as such may be amended from time to time in Members United’s sole discretion, as if said additional requirements were set forth in full in the substantive text of the Agreement. The parties hereby acknowledge that any documentation and/or listing required herein is solely for the benefit of Members United and, except for Installment Loans pledged as collateral herein, said documentation and/or listing provided herein will not in any way limit, reduce or minimize the Collateral pledged by CUSO in connection with this Credit Facility.
Reporting and Documentation Requirements. 1. Subcontractor agrees to use the form provided by the county to provide monthly member level data reporting, for clients who received services paid for by this grant to include: i. month reported; ii. date of service; iii. type of service; iv. service setting; v. disposition; vi. For those served, identifying and socio-demographic data including: 1. name;
Reporting and Documentation Requirements. 2. Data Requirements: All required data and reports will be agreed upon by contractor and the State upon award based on details and scope of project proposal. Contractor shall submit a monthly report with invoice in an excel document that matches the template is in this contract: Contractor shall submit a quarterly report that matches goals and objectives of strategic plan as agreed upon by the State prior to contract execution. A. Metrics chosen for report should be SMART (specific, measurable, achievable, relevant, and time-bound). B. Contractors are encouraged to choose outcome-based metrics such as: a. prevalence rate of mental illness in jail population; b. length of time an individual is in jail before being assessed for mental illness and referred to appropriate community resources; c. connections to community-based treatment, services, and supports; d. recidivism rates; and e. readmission rates. C. Contractors are encouraged to choose measures that evaluate efficacy of pooled funding. D. Contractors are required to report on challenges and barriers to spending the entire amount allotted to them through this funding. 1. Contract funding is allocated as follows: January 1, 2020 to June 30, 2021 in the amount of 2. Funds received will not be used to pay for services that can be billed to Medicaid, Block Grant, or other State General Fund programs. 3. Program funds will not be used to supplant existing funding from sources other than County and Tribal Matching Grant. 4. Monthly invoices will be submitted in required format for previous month by the 30th day of the following month. 5. Member level data will be submitted with each monthly invoice. Data submission is required prior to approval of invoice. 6. Budget includes all costs associated with each component of the project. 7. Contractor certifies existence of funding match for expenditure. 8. Payment for questioned costs may be withheld pending resolution of the disputed costs and may require rebilling by the Contractor. 9. The Contractor must submit all final claims and corrected invoices for the preceding fiscal year by September 30th. 10. All invoices received must have back up documentation for the amount that is being requested and must have back up documentation of the matching funds that are being paid by the contractor. 11. If contractor receives both County and Tribal Matching Grant and Mobile Crisis Unit Program funds, they shall submit an individual invoice for each program respectively....
Reporting and Documentation Requirements. 1. Data Requirements: All required data and reports will be agreed upon by contractor and the State upon award based on details and scope of project proposal. Contractor shall submit a monthly report of member level data with invoice in an excel document that matches the template that is in this contract: a. Monthly you will be required to turn in member level data as per RFP requirement on a template that will be provided electronically by the state. b. Quarterly you will be required to turn in and outcome report as per RFP requirement on a template that will be provided electronically by the state. Data and Report Template
Reporting and Documentation Requirements. Provider shall submit reports and documentation in accordance with each Work Order and the QAPP.
AutoNDA by SimpleDocs
Reporting and Documentation Requirements 

Related to Reporting and Documentation Requirements

  • Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following: 1. Total premiums reported on IRS Form 8963;

  • Information Requirements The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder and take such further reasonable action as any Holder may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company’s most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Compliance with Safeguarding Customer Information Requirements The Servicer has implemented and will maintain security measures designed to meet the objectives of the Interagency Guidelines Establishing Standards for Safeguarding Customer Information published in final form on February 1, 2001, 66 Fed. Reg. 8616, and the rules promulgated thereunder, as amended from time to time (the “Guidelines”). The Servicer shall promptly provide the Seller information regarding the implementation of such security measures upon the reasonable request of the Seller.

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave. 2. If the event necessitating the Family Leave becomes known to the employee less than thirty (30) calendar days prior to the employee's need for Family Leave, the employee must provide as much notice as possible. In no case shall the employee provide notice later than five (5) calendar days after he or she learns of the need for Family Leave. 3. For foreseeable leave due to a qualifying exigency, an employee must provide notice of the need for leave as soon as practicable, regardless of how far in advance such leave is foreseeable. 4. When the Family Leave is for the purpose of the scheduled medical treatment or planned medical care of a child, parent, spouse or registered domestic partner, the employee shall, to the extent practicable, schedule treatment and/or care in a way that minimizes disruption to agency/department operations.

  • Certification Requirements The applicant will provide Vista Laboratories, Inc. with all product information for the evaluation of the product to be certified and warrant that the information provided is accurate and complete so that Vista Labs may perform the services requested. If the product was tested at an external laboratory, the applicant must provide the complete test report to Vista Labs. If the external testing facility is not ISO 17025 accredited, or does not have the proper scope, Vista Labs must determine if the test report can be used for certification activities. The applicant’s information is used to perform a product review and evaluation to determine the product’s compliance to the specific certification requested. Throughout the process, the client agrees to make claims regarding certification consistent with the scope of certification. The applicant agrees to supply the required number of product samples, to be determined by Vista Labs, to the laboratory for testing, measurement, and evaluation purposes. The client understands that certain tests may damage or destroy the sample and acknowledge that Vista Labs is not responsible for such damages. Samples will be returned only upon request by the applicant and at the applicant’s expense, after the completion of certification. Samples will be disposed of after six months if not requested for return by applicant. The product is ineligible for certification if it has been modified by the client after testing or certification. Changes to the product must be approved by Vista Laboratories. Vista Labs reserves the right to re- evaluate the product as a result of information that raises questions concerning the conformance of the product. Certified products maintain fulfilment of product requirements if the certification applies to ongoing production. If the client provides copies of the certification documents to other parties, the documents are reproduced in their entirety, or as specified in the certification scheme. In making reference to its product certification in media, such as brochures or advertisement, the client complies with the requirements of the Vista Labs or as specified by the certification scheme. The client complies with any requirements that may be prescribed in the certification scheme relating to the use of marks of conformity, and on all product correspondences and product related information. Vista Labs reserves the right to revise or withdraw the requirements as required in order to maintain conformance with FCC rules and regulations governing the product. The product may continue with certification and receive certification upon demonstration of compliance with the revised requirements, to the satisfaction of Vista Laboratories.

  • Documentation Required The certificates and endorsements shall be received and approved by the District before Work commences. As an alternative, the Contractor may submit certified copies of any policy that includes the required endorsement language set forth herein.

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

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