Progress report season: a workflow for the whole caseload

By the IEP Atlas editorial teamLast updated November 1, 2026

Short answer

Progress report season goes faster when you work in batches over three weeks instead of student by student in the last two days. Set a data cutoff, collect providers' sections early, graph every goal, sort goals by type, write narratives in batches, check each report once, then send and log them. Most of the time saved comes from the data being current before you start.

Progress reports are due for every goal on every IEP, as often as each IEP says, usually with report cards.^[1] For a caseload of 18 students with 3 or 4 goals each, that is 55 to 70 goal reports in the same week. The writing is not the hard part. The hard part is chasing missing data and switching between students.

This page is the season-level workflow. How to write a single report well is covered in how to write an IEP progress report. The calendar for the year is in the case manager's handbook.

What you need before you start

The due date for reports going home, from the district calendar.
A list of every goal on the caseload and who reports on it (you, the SLP, the OT, the counselor).
Current data sheets for every goal. The free data sheets match each kind of goal.
Your district's progress codes. See IEP progress report codes.

The steps and the time each takes

Step	When	Time for an 18-student caseload
1. Set the data cutoff and tell providers	15 school days before due	15 min
2. Fill data gaps	Days 15 to 10	2 to 3 h of probes, spread across lessons
3. Collect provider sections	By day 8	15 min to send; follow-up as needed
4. Graph every goal	Days 8 to 7	1 h 30 min
5. Sort goals by type and status	Day 6	30 min
6. Write narratives in batches	Days 6 to 3	4 to 5 h
7. Check each report once	Day 2	1 h 30 min
8. Send, log and follow up	Due date	1 h

Times are illustrations from a fictional caseload, not standards. They assume data was collected through the quarter.

Step-by-step

Step 1: Set a data cutoff

Pick a date, about 3 weeks before reports go home, after which new data goes into the next report. Tell providers and paras the cutoff and the date you need their sections.

Step 2: Fill data gaps

Scan every data sheet. Any goal with fewer than 3 data points since the last report gets a probe this week. A short probe takes 2 to 5 minutes inside a lesson. Use the method the goal names; the measurement guide lists each one. Brief, repeated measures taken the same way each time are what progress monitoring is built on.^[2]

Step 3: Collect provider sections

Ask related service providers for their goals' current level, code and one or two sentences. Give them your template so the reports read as one document.

Step 4: Graph every goal

A graph shows the trend faster than a column of numbers. Plot the baseline, the target line and every data point. The aimline guide shows how.

Step 5: Sort goals by type and status

Make three piles: on pace, behind, and met or nearly met. Within each pile, group by goal type (reading fluency, math, behavior). You will write all "behind" fluency goals together, using the same structure.

Step 6: Write narratives in batches

Each narrative needs the current level, the comparison with baseline and target, and what happens next. Writing 12 fluency narratives in a row is much faster than switching from fluency to behavior to writing for each student. The progress report comment examples give sentence frames.

Step 7: Check each report once

Read as a parent: is there a number, does it compare with the start, and is the next step clear? Check names, dates and codes.

Step 8: Send, log and follow up

Send by the method each family prefers and log the date. For any goal coded as not on track, call the family before the report arrives. Nobody should learn that from a form.

Worked example: one student's report in one season

Amara is a fictional 3rd grader with 3 goals. Reports go home January 30.

Date	Step	Amara's goals
Jan 9	1	Cutoff set at Jan 23; SLP asked for her section by Jan 20
Jan 12	2	Fluency goal has 6 points; math goal only 2, so 2 probes added Jan 13 and 15
Jan 20	3	SLP section in: articulation 68% accuracy on /r/ in sentences (baseline 35%, target 80%)
Jan 21	4	Fluency graphed: 61 words correct per minute (baseline 44 in September; target 90 by June); above the aimline
Jan 22	5	Math: 9 of 20 two-step problems correct (baseline 6 of 20; target 16 of 20); below the aimline, sorted "behind"
Jan 26	6	Narratives written in batches with 5 other fluency goals and 3 other "behind" math goals
Jan 28	7	Checked; code "making progress, may not meet goal" on math
Jan 29	8	Called her mother about math before the report went home; agreed to a team check in 4 weeks

Time on Amara's report: about 35 minutes, most of it the math probes. The phone call took 8 minutes and was the most useful part of the season.

Common mistakes

Weak: Starting reports 2 days before they are due. Better: Set a cutoff 3 weeks out and work in steps.
Weak: "Making progress" with no number. Better: "61 words correct per minute, up from 44 in September."
Weak: Writing each student's report start to finish. Better: Batch by goal type and status.
Weak: Letting a "not on track" code arrive cold. Better: Call first, then send.
Weak: Chasing provider sections on the due date. Better: Ask for them a week before you write.

Tools that help

The progress report glossary entry lists what each report must show. The free service log answers the question families often ask alongside progress: were the minutes delivered? If you want graphs and draft narratives generated from session data, IEP Atlas Pro builds a batch of progress reports in one PDF. When goals are behind, see IEP goal not met on a progress report. For the same batching applied to IEP writing, see the IEP writing process.

Frequently asked questions

How can I write IEP progress reports faster?

Keep data current through the quarter, set a cutoff about three weeks before reports are due, graph every goal, and write narratives in batches by goal type instead of one student at a time.

What if I do not have enough data for a progress report?

Take short probes on the goal before the cutoff, using the measure the goal names. If data is still thin, report what you have, say when it was collected, and fix the collection schedule for next quarter.

Use it in IEP Atlas

Sources

34 CFR §300.320: Definition of individualized education program, Legal Information Institute, Cornell Law School
Progress Monitoring: Data & Goal Setting, National Center on Intensive Intervention

Written and checked by the IEP Atlas editorial team under our editorial policy. This guide describes general practice and federal rules. It is not legal advice; your state may add requirements, and the IEP team makes the decisions for each student.