Progress Monitoring and Data-Driven Communication

Why Progress Monitoring Matters

As a paraprofessional, you work closely with students every day. That daily contact puts you in a unique position: you often see small changes in a student's performance before anyone else does. Progress monitoring is the practice of collecting short, frequent measures of student skill and using that data to judge whether a student is on track to meet a goal. When done well, it removes guesswork and gives the supervising teacher real evidence to make instructional decisions.

Your role is to collect the data accurately, record it correctly, graph it clearly, and communicate what you see — not to diagnose a learning disability or change the instructional program on your own. Those decisions belong to the certified teacher or the intervention team. Knowing where your role ends is just as important as knowing how to run a probe.

Types of Probes Used in This Lab

Words Correct Per Minute (WCPM) fluency probes measure reading fluency. A student reads a passage aloud for exactly one minute. You follow along on your copy, mark any word read incorrectly, and count the number of words read correctly. That number is the WCPM score for that session.

Math computation probes measure calculation speed and accuracy. A student completes a timed sheet of problems — for example, two minutes of mixed addition and subtraction. You score by counting digits correct or problems correct, depending on the scoring rule given to you by the teacher. Use whichever rule the teacher specifies, and apply it the same way every time.

Both probes are brief (one to three minutes), standardized, and repeated frequently — typically three to five times per week during an intervention, or at least once per week for general progress checks.

Accurate Data Entry: The Foundation of Everything

A graph is only as good as the numbers entered into it. Before you type a single score into a spreadsheet:

• Double-check your hand-scored probe sheet against the score you plan to enter.
• Enter the score for the correct date column. A score entered in the wrong column shifts the entire trend line.
• Never round or adjust a score to make the graph look better. Record what the student actually produced.
• If you are unsure of a score — for example, you lost count during a fluency probe — note that and consult your supervising teacher before recording anything. An estimated score recorded as fact is misleading.

In the spreadsheet template provided for this lab, each row represents one school day. Columns hold the date, the WCPM score, and the math computation score. After entering all five days of data, use the charting function to produce a line graph. The goal line should be a straight horizontal line drawn at the target score level set by the teacher. Label the x-axis (horizontal) with the dates or session numbers and the y-axis (vertical) with the score unit (e.g., "Words Correct Per Minute").

Reading a Graph: Trend, Level, and Variability

When you look at a completed graph, you are asking three questions:

1. Trend — Is the line going up (improving), staying flat, or going down (declining)? A consistent upward slope over several data points suggests the student is responding to instruction.

2. Level — Where does the student's current performance sit relative to the goal line? If scores cluster well below the goal line across multiple sessions, the student may need a program adjustment.

3. Variability — Are scores bouncing sharply up and down each day, or are they relatively stable? High day-to-day variability can signal inconsistent effort, testing conditions, or a skill that is not yet consolidated.

Do not draw strong conclusions from one or two data points. Progress-monitoring research consistently emphasizes that you need at least six to eight data points before a trend is reliable enough to act on. In this lab you have five data points per student — enough to practice reading a trend, but in real practice you would want more before recommending a program change.

Writing a Professional Data Summary

A written data note sent to a supervising teacher should be brief, factual, and neutral in tone. Use numbers. Avoid emotional language or personal judgments about the student.

A strong paragraph includes:

• The student's identifier (never use a real student's full name in unsecured documents — use initials or a pseudonym as directed)
• The time period covered
• The metric reported and the goal
• A plain description of the trend
• One concrete instructional observation or recommendation, phrased as a question or suggestion for the teacher to consider

Example of appropriate language: "Over the five sessions recorded this week, Student A's WCPM scores ranged from 62 to 71, with an upward trend. The goal is 90 WCPM. Scores remain below goal. You may want to consider whether additional fluency practice time would be helpful."

Example of language to avoid: "Student A is really struggling and I think she has a reading problem." That crosses into diagnostic territory that is outside your role.

The Data Meeting Role-Play

Professional data meetings are a normal part of school-based intervention work. As an aide, you may be asked to present data you collected to a teacher, a reading specialist, or an intervention team. Practice these habits:

• Bring your printed or digital graph and your original probe sheets.
• State facts first, then observations: "Here is what the data shows" before "Here is what I noticed."
• Answer questions honestly. If you do not know, say so rather than guessing.
• Defer instructional decisions to the certified teacher: "That's something I'd want you to decide" is always appropriate.
• Maintain student confidentiality — data meetings happen in private spaces, not hallways.

Safety and Ethical Reminders

Student data is protected under FERPA (the Family Educational Rights and Privacy Act). Never share identifiable student data with anyone who does not have a legitimate educational need to know. Do not photograph student probe sheets with a personal device, do not store data in personal cloud accounts, and do not discuss student performance in public settings. Follow your district's specific data-handling procedures at all times.