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.

Reporting Scope Sample Clauses

Reporting Scope. This section describes the custom reports to be delivered by Workday under this SOW based on the information provided by Customer and the parties’ understanding as of the SOW Effective Date. During delivery, and upon further discovery, the parties may agree that changes are required to meet Customer’s requirements, which changes shall be affected via a Change Order.
Reporting Scope. No reporting in scope.

Related to Reporting Scope

  • Reporting Schedule Consultant shall report regularly, and not less frequent than once per week, to the Company his actions on behalf of the Company.

  • 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.

  • Periodic Reporting (a) The Company will promptly deliver to each Blackstone Entity when available one copy of each annual report on Form 10-K and quarterly report on Form 10-Q of the Company, as filed with the SEC. In the event the Company is not required to file an annual report on Form 10-K or quarterly report on Form 10-Q, the Company may, in lieu of the requirements of the preceding sentence, deliver, or cause to be delivered, the following to each Blackstone Entity: (i) as soon as available, but not later than ninety (90) days after the end of each fiscal year of the Company, a copy of the audited consolidated balance sheet of the Company and its Subsidiaries as of the end of such fiscal year and the related statements of operations and cash flows for such fiscal year, setting forth in each case in comparative form the figures for the previous year, all in reasonable detail; (ii) commencing with the fiscal period ending after September 30, 2010, as soon as available, but in any event not later than forty five (45) days after the end of each of the first three fiscal quarters of each fiscal year, the unaudited consolidated balance sheet of the Company and its Subsidiaries, and the related statements of operations and cash flows for such quarter and for the period commencing on the first day of the fiscal year and ending on the last day of such quarter; (b) The Company shall deliver or cause to be delivered to each Blackstone Entity: (i) to the extent otherwise prepared by the Company, operating and capital expenditure budgets and periodic information packages relating to the operations and cash flows of the Company and its Subsidiaries; and (ii) such other reports and information as may be reasonably requested by any Blackstone Entity; provided, however, that the Company shall not be required to disclose any privileged information of the Company so long as the Company has used its best efforts to enter into an arrangement pursuant to which it may provide such information to the Blackstone Entities without the loss of any such privilege.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • 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.

  • Performance Reporting The State of California is required to submit the following financial reports to FEMA:

  • Reporting Compliance Grantee represents and warrants that it will submit timely, complete, and accurate reports in accordance with the grant and maintain appropriate backup documentation to support the reports.

  • 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.

  • Reporting Period Project progress including a summary of progress, findings, data, analyses, results and field-test results from all tasks carried out in the covered period.

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.