Reporting Mechanisms Sample Clauses

Reporting Mechanisms. The Partnerships in Action Cheshire East Executive Board shall report progress on an annual basis to the wider LSP Assembly. Additionally partners will regularly report progress under their own governance arrangements. The Cheshire East Sustainable Community Strategy will be the key document for the Partnership. Its broad principles, and identified issues and actions, will provide the basis for establishment of Thematic Groups or to commission existing Thematic Groups to deliver policies, action and meet agreed targets.
Sample 1Sample 2
AutoNDA by SimpleDocs
Reporting Mechanisms. Complaints can be reported to federal authorities as follows:
Sample 1
Reporting Mechanisms. All of which is agreed this day of March 2006. Signed on behalf of the NBA: Signed on behalf of HEABC: Agreed Upon Provision SECTION 2 – COMMUNITY- BASED SERVICES Article 57 – General Conditions Proposal: Revise Article 57.02(C) as follows:
Sample 1
Reporting Mechanisms. 9.1 Subject to clause 9.3, reporting mechanisms by the Customer must be via the e-mail address supplied by the Company to receive reports from the Customer, which will be monitored during Support Hours.
Sample 1
Reporting Mechanisms. A mid-term progress report will be prepared by each Theme Group for submission to the Community Planning Board in October of each year. This will allow partners to review progress being made towards achieving SOA outcomes and targets and to make recommendations on any remedial action necessary at that stage. Progress on SOA outcomes, strategic objectives and targets will be reported to a wider audience in November of each year through the Council‟s public performance reporting mechanisms. An Annual SOA Report will be produced and submitted to the Scottish Government in September of each year, reporting on activities and progress relating to the preceding financial year. This will allow sufficient time for the Partnership to gather data relating to the indicators.
Sample 1
Reporting Mechanisms. For an evaluator to test a principal mechanism using protocols developed by procedures given here, certain information about the principal mechanism must be reported before the simulations take place. These reports become part of the basis for choices the evaluator must make in judging the mechanism. In this chapter we describe this mechanism-related information and outline how the evaluator must report it as part of his evaluation documen- tation. For new mechanisms formulated under EPA sponsorship, the mechanism developer would have the responsibility for creating most of the information that needs to be reported, and the evaluator’s role would become one of subsequent quality assurance of the material supplied by the developer. For existing mechanisms, however, it is the responsibility of the evaluator to gather, organize, and report the needed information. For most existing reaction mechanisms, the evaluator can glean the required information from final reports on the development effort and perhaps, if needed, even by discussion with the mechanism’s authors. There is also the situation in which the evaluator is the mechanism developer. That the evaluator is evaluating his own mechanism does not change what he must report about the mechanism. And in fact, because the evaluator is so familiar with the development of the principal mechanism, he should be even more careful to follow the guidelines to avoid under-reporting the principal mechanism.
Sample 1

Related to Reporting Mechanisms

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

  • Reporting Frequency During any period of time when you are subject to the requirement in paragraph 1 of this award term and condition, you must report proceedings information through XXX for the most recent five year period, either to report new information about any proceeding(s) that you have not reported previously or affirm that there is no new information to report. Recipients that have Federal contract, grant, and cooperative agreement awards with a cumulative total value greater than $10,000,000 must disclose semiannually any information about the criminal, civil, and administrative proceedings.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Reporting TIPS Sales Vendor must report all TIPS Sales to TIPS. If a TIPS sale is initiated by Vendor receiving a TIPS Member’s purchase order from TIPS directly, Vendor may consider that specific TIPS Sale reported. Otherwise, with the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.

  • Child Abuse Reporting Requirement Grantee will:

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

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