State Performance Plan 2005-2012 - Part B - Arkansas Department Of Education Page 265

ADVERTISEMENT

Arkansas Department of Education Special Education Unit
Part B State Performance Plan
management protocols. The Special Education Data Manager is also the single point of contact for districts
and APSCN for any data corrections, updates, or clarifications of required special education data.
The ADE-SEU partnership with the University of Arkansas at Little Rock College of Education, which
began in 2005 is in its sixth year of operation. The partnership established the Arkansas IDEA Data &
Research Office, whose mission is to provide quality data management, analysis, technical assistance, and
research for the enhancement of the Arkansas Department of Education's general supervision of local
education agencies' special education programs by ensuring accurate, valid, and timely data to meet all state
and federal reporting. That Office strives to promote IDEA research among faculty and students of UALR
for a greater understanding of policy, procedures, and practices across the state.
Baseline Data for FFY 2004 (2004-2005)
a. Submitted on or before due dates (February 1 for child count, including race and ethnicity, and
placement; November 1 for exiting, discipline, personnel; and February 1 for Annual Performance
Reports): 100% compliance
b. Accurate: 100% compliance
Discussion of Baseline Data
Report
Measurable and Rigorous Target
Year
In 2004-05, all reports were submitted to OSEP on or before the due dates. However, the
FFY 2004
December 1 child count report had to be resubmitted after an error was identified. Although
the totals matched, there was a misalignment in the data table. The correction was made and a
new data table was submitted to Westat and OSEP.
The State takes great strides to ensure the data is timely and accurate. Districts have the
opportunity to review and correct their data after submitting to APSCN via the special
education website. Reports are generated directly from the special education SQL server
using Crystal Reports. The staff then cross-references each report looking for inconsistencies
within the data tables.
a. Submitted on or before due dates (February 1 for child count, including race and
FFY 2005
ethnicity, placement; November 1 for exiting, discipline, personnel; and February 1 for
Annual Performance Reports): 100% compliance
b. Accurate: 100% compliance.
a. Submitted on or before due dates (February 1 for child count, including race and
FFY 2006
ethnicity, placement; November 1 for exiting, discipline, personnel; and February 1 for
Annual Performance Reports): 100% compliance
b. Accurate: 100% compliance.
a. Submitted on or before due dates (February 1 for child count, including race and
FFY 2007
ethnicity, placement; November 1 for exiting, discipline, personnel; and February 1 for
Annual Performance Reports): 100% compliance
b. Accurate: 100% compliance.
a. Submitted on or before due dates (February 1 for child count, including race and
FFY 2008
ethnicity, placement; November 1 for exiting, discipline, personnel; and February 1 for
Page | 263

ADVERTISEMENT

00 votes

Related Articles

Related forms

Related Categories

Parent category: Legal
Go
Page of 277