Analyzing Student Data – Tips for Teachers, Educators and Schools

At i-LEADR, Inc., our online data and documentation platform, RtI: Stored! streamlines the process of collecting, analyzing, and storing student data as part of an MTSS & RtI framework. However, the effectiveness of our platform is only as effective as its use, so we recommend the following tips for using it strategically and successfully:

Tips for Using a Systematic Data and Documentation Platform to Accurately Analyze Student Data

  • Check the adequacy of the data—While using documentation software, educators should ask whether appropriate screening measures were used to determine a student’s level of success with reading and mathematics. They should also determine if the screening measure aligns with the learning expectations for that year, and if any scoring was verified.
  • Plan adjustments—If large numbers of students are performing in the risk range, educators should analyze the adequacy of the core instruction. After certain adjustments have been made, the screening should be repeated to identify the effect of the adjustments.
  • Manage individual interventions—Before using individual data to make decisions about a personalized intervention, educators should investigate the effectiveness of the intervention for the group. Educators should also ask whether the intervention was implemented to fidelity, and if the intervention was adjusted accordingly to match student progress.
  • Use data to allocate instructional resources—If implementation steps are well-defined for classrooms and the school as a whole, and the platform allows educators to track the effects of interventions, any data can be used as a basis for providing additional resources in the classroom, small groups, or to individual students.
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true );