Daily Job Reports 6.7.2.1 Developer shall maintain, at a minimum, at least one (1) set of Daily Job Reports on the Project. These must be prepared by Xxxxxxxxx's employee(s) who are present on Site, and must include, at a minimum, the following information:
Progress Reports The Recipient shall submit to the OPWC, at the OPWC's request, summary reports detailing the progress of the Project pursuant to this Agreement and any additional reports containing such information as the OPWC may reasonably require.
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.
Progress Reports and Invoices The goals of this subtask are to: (1) periodically verify that satisfactory and continued progress is made towards achieving the project objectives of this Agreement; and (2) ensure that invoices contain all required information and are submitted in the appropriate format. The Recipient shall: • Submit a monthly Progress Report to the CAM. Each progress report must: o Summarize progress made on all Agreement activities as specified in the scope of work for the preceding month, including accomplishments, problems, milestones, products, schedule, fiscal status, and an assessment of the ability to complete the Agreement within the current budget and any anticipated cost overruns. See the Progress Report Format Attachment for the recommended specifications. • Submit a monthly or quarterly Invoice that follows the instructions in the “Payment of Funds” section of the terms and conditions, including a financial report on Match Fund and in-state expenditures. Products: • Progress Reports • Invoices
Usage Reports The Contractor shall submit usage reports on an annual basis to the assigned Deputy Purchasing Agent of the County of Orange user agency/department. The usage report shall be in a format specified by the user agency/department and shall be submitted 90 days prior to the expiration date of the contract term, or any subsequent renewal term, if applicable.
Daily Reports On each Business Day, the Servicer, with prior notice, shall prepare and make available at the office of the Servicer for inspection by the Trustee a record setting forth (i) the aggregate amount of Collections processed by the Servicer on the preceding Business Day and (ii) the aggregate amount of Receivables as of the close of business on the preceding Business Day.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-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: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
Monthly Progress Reports During the Construction Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report on progress of the Construction Works and shall promptly give such other relevant information as may be required by the Independent Engineer.
Utilization Reports Both the Contractor and Subcontractor shall complete Quarterly Utilization Reports (or similar type documents containing the same information) and submit them to the Contracting Officer and to the Bureau within ten (10) business days at the end of each quarter. This information will be used to determine the actual dollar amount paid to Subcontractor and will also serve as a record of fulfillment of Contractor’s Small Diverse Business and Small Business Commitments. If there was no activity during the quarter, then the form must be completed by stating “No activity in this quarter.” A late fee of $100.00 per day may be assessed against the Contractor if its Utilization Report is not submitted in accordance with the schedule above.
Progress Report 10.1 If required, you shall submit progress reports in connection with the Service (“Report”) on at least a monthly basis, or as we may require. The Report shall include a summary of the activities and accomplishments during the previous reporting period.
