Reporting Practices Sample Clauses

The Reporting Practices clause establishes the requirements and standards for how parties must provide information and updates to each other during the course of an agreement. Typically, it outlines the frequency, format, and content of reports, such as financial statements, progress updates, or compliance documentation, that one party must deliver to the other. By setting clear expectations for communication and documentation, this clause ensures transparency and accountability, helping to prevent misunderstandings and disputes related to information sharing.
Reporting Practices. The District and the Association share a mutual belief that best educational practice is to report student progress in a conscientious and timely manner. Secondary school teachers shall update student assignment grades regularly (at a minimum every ten (10) school days) on the District’s online reporting system for viewing by students and their families. All assignments and tests shall be graded as soon as reasonably possible, but in no event more than fifteen (15) school days after the assignment or test is turned in. All assignments received within twenty (20) school days of the end of the first semester must be posted within twelve (12) school days. Teachers experiencing difficulties with this provision shall be provided support and assistance and shall not be subject to discipline. Concerns regarding timely reporting practices, however, may be included in a teacher’s performance evaluation beginning in 2012-13. At the beginning of each semester, District administrators will communicate to parents and students the expectations for grading and posting information online; this communication will be jointly developed with BEA. The intent of the electronic gradebook is to make information accessible, not to change teachers’ grading practices. At the beginning of each school year, school administrators and a BEA representative will conduct a joint presentation to school staff on grade reporting practices. Topics will include, but not be limited to, School Board policies, grade reporting research regarding best educational practice and other relevant topics. At the request of the teacher, the principal/supervisor will work to resolve situations in which there is a disagreement between the teacher and the parent/student about grade reporting requirements.
View SourceView Similar (4)
Reporting Practices. The Issuer will not make any change in reporting practices, except as may be required or permitted by GAAP.
View SourceView Similar (2)

Related to Reporting Practices

  • Reporting Procedures Enter in the ▇▇▇ Entity Management area the information that ▇▇▇ requires about each proceeding described in paragraph 2 of this award term and condition. You do not need to submit the information a second time under assistance awards that you received if you already provided the information through ▇▇▇ because you were required to do so under Federal procurement contracts that you were awarded.

  • General Reporting Requirements The MA-PD Sponsor agrees to submit to information to CMS according to 42 CFR §§423.505(f), 423.514, and the "Final Medicare Part D Reporting Requirements," a document issued by CMS and subject to modification each program year.

  • Financial Reporting Requirements The Charter School shall follow the financial requirements of the Charter Schools Section of the Department’s Financial Management for Georgia Local Units of Administration Manual. The Charter School shall submit all information required by the State Accounting Office for inclusion in the State of Georgia Comprehensive Annual Financial Report.

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

  • Safeguarding requirements and procedures (1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls: (i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems). (ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute. (iii) Verify and control/limit connections to and use of external information systems. (iv) Control information posted or processed on publicly accessible information systems. (v) Identify information system users, processes acting on behalf of users, or devices. (vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems. (vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse. (viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals. (ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices. (x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems. (xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. (xii) Identify, report, and correct information and information system flaws in a timely manner. (xiii) Provide protection from malicious code at appropriate locations within organizational information systems. (xiv) Update malicious code protection mechanisms when new releases are available. (xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.