(1) A K-12 data governance group shall be established within the office of the superintendent of public instruction to assist in the design and implementation of a K-12 education data improvement system for financial, student, and educator data. It is the intent that the data system reporting specifically serve requirements for teachers, parents, superintendents, school boards, the office of the superintendent of public instruction, the legislature, and the public.

Ask a legal question, get an answer ASAP!
Click here to chat with a lawyer about your rights.

Terms Used In Washington Code 28A.300.507

  • Board: means the paraeducator board established in RCW 28A. See Washington Code 28A.413.010
  • Fiscal year: The fiscal year is the accounting period for the government. For the federal government, this begins on October 1 and ends on September 30. The fiscal year is designated by the calendar year in which it ends; for example, fiscal year 2006 begins on October 1, 2005 and ends on September 30, 2006.
(2) The K-12 data governance group shall include representatives of the education data center, the office of the superintendent of public instruction, the legislative evaluation and accountability program committee, the professional educator standards board, the state board of education, and school district staff, including information technology staff. Additional entities with expertise in education data may be included in the K-12 data governance group.
(3) The K-12 data governance group shall:
(a) Identify the critical research and policy questions that need to be addressed by the K-12 education data improvement system;
(b) Identify reports and other information that should be made available on the internet in addition to the reports identified in subsection (5) of this section;
(c) Create a comprehensive needs requirement document detailing the specific information and technical capacity needed by school districts and the state to meet the legislature’s expectations for a comprehensive K-12 education data improvement system as described under RCW 28A.655.210;
(d) Conduct a gap analysis of current and planned information compared to the needs requirement document, including an analysis of the strengths and limitations of an education data system and programs currently used by school districts and the state, and specifically the gap analysis must look at the extent to which the existing data can be transformed into canonical form and where existing software can be used to meet the needs requirement document;
(e) Focus on financial and cost data necessary to support the new K-12 financial models and funding formulas, including any necessary changes to school district budgeting and accounting, and on assuring the capacity to link data across financial, student, and educator systems; and
(f) Define the operating rules and governance structure for K-12 data collections, ensuring that data systems are flexible and able to adapt to evolving needs for information, within an objective and orderly data governance process for determining when changes are needed and how to implement them. Strong consideration must be made to the current practice and cost of migration to new requirements. The operating rules should delineate the coordination, delegation, and escalation authority for data collection issues, business rules, and performance goals for each K-12 data collection system, including:
(i) Defining and maintaining standards for privacy and confidentiality;
(ii) Setting data collection priorities;
(iii) Defining and updating a standard data dictionary;
(iv) Ensuring data compliance with the data dictionary;
(v) Ensuring data accuracy; and
(vi) Establishing minimum standards for school, student, financial, and teacher data systems. Data elements may be specified “to the extent feasible” or “to the extent available” to collect more and better data sets from districts with more flexible software. Nothing in RCW 43.41.400, this section, or RCW 28A.655.210 should be construed to require that a data dictionary or reporting should be hobbled to the lowest common set. The work of the K-12 data governance group must specify which data are desirable. Districts that can meet these requirements shall report the desirable data. Funding from the legislature must establish which subset data are absolutely required.
(4)(a) The K-12 data governance group shall provide updates on its work as requested by the education data center and the legislative evaluation and accountability program committee.
(b) The work of the K-12 data governance group shall be periodically reviewed and monitored by the educational data center and the legislative evaluation and accountability program committee.
(5) To the extent data is available, the office of the superintendent of public instruction shall make the following minimum reports available on the internet. The reports must either be run on demand against current data, or, if a static report, must have been run against the most recent data:
(a) The per-pupil expenditures of federal, state, and local funds including actual personnel expenditures and actual nonpersonnel expenditures of federal, state, and local funds disaggregated by source of funds, for each local educational agency and each school in the state for the preceding fiscal year;
(b) Number of K-12 students per classroom teacher on a per teacher basis;
(c) Percentage of classroom teachers per school district and per school disaggregated as described in RCW 28A.300.042(1) for student-level data;
(d) Average length of service of classroom teachers per school district and per school disaggregated as described in RCW 28A.300.042(1) for student-level data;
(e) The cost of K-12 education per student by school district sorted by federal, state, and local dollars; and
(f) Data on student growth to align with the every student succeeds act (129 Stat. 1802; 20 U.S.C. § 6301 et seq.).
(6) The superintendent of public instruction shall submit a preliminary report to the legislature by November 15, 2009, including the analyses by the K-12 data governance group under subsection (3) of this section and preliminary options for addressing identified gaps. A final report, including a proposed phase-in plan and preliminary cost estimates for implementation of a comprehensive data improvement system for financial, student, and educator data shall be submitted to the legislature by September 1, 2010.
(7) All reports and data referenced in this section and RCW 43.41.400 and 28A.655.210 shall be made available in a manner consistent with the technical requirements of the legislative evaluation and accountability program committee and the education data center so that selected data can be provided to the legislature, governor, school districts, and the public.
(8) Reports shall contain data to the extent it is available. All reports must include documentation of which data are not available or are estimated. Reports must not be suppressed because of poor data accuracy or completeness. Reports may be accompanied with documentation to inform the reader of why some data are missing or inaccurate or estimated.

NOTES:

FindingIntent2016 c 72: See note following RCW 28A.600.015.
Intent2009 c 548: See RCW 28A.150.1981.
Finding2009 c 548: See note following RCW 28A.410.270.
IntentFinding2009 c 548: See note following RCW 28A.305.130.