The start of a term is when a caseload quietly drifts. Plans edge toward their deadlines, data goes stale over a break, a signature never got collected. A short, repeatable audit catches that drift while there is still time to act. This checklist is twelve points you run on every student, each with a one-line pass standard so it works as an actual checklist and not a vague reminder. It comes with a filled example row, a triage table for deciding what to fix first, and a plan to run the whole thing in a single 90-minute block.
How to use the twelve points
Each point below has a pass standard: the specific condition that lets you mark it pass and move on. If a student does not meet the standard, you mark it a gap and carry it to triage rather than stopping to fix it mid-audit. The discipline is to check fast and fix later, so the whole caseload gets reviewed in one sitting instead of one student eating the whole block.
The single most common way this audit fails is the urge to fix a gap the moment you find it. You open a file, notice the data is stale, and start logging or emailing, and forty minutes later you have helped one student and audited none of the rest. Resist it. The audit is a triage pass, like a nurse checking every patient before treating anyone. You cannot prioritize what you have not finished surveying. Mark the gap, move on, and fix in ranked order after the full sweep.
The 12-point per-student check
Run these in order for each student. The pass standard is the bar; anything short of it is a gap.
- IEP or 504 is current. Pass: the plan in the file is the active one and has not expired.
- Next annual review date is known and not near-overdue. Pass: the review date is on your calendar and is not inside the next few weeks without a meeting scheduled.
- Reevaluation timeline is on track. Pass: any reevaluation due this year has a date and a plan, not a surprise.
- Goals are current and match the active plan. Pass: the goals you are tracking are the ones in the current document, not last year's.
- Each goal has a baseline. Pass: every goal shows a starting point you can measure progress against.
- Each goal has a measurement type. Pass: every goal names how it is measured (a count, a rating, a percentage), not just a vague aim.
- Data is recent. Pass: there is at least one data point in the last 10 school days for active goals.
- Data is enough to show a trend. Pass: there are enough points to read direction, not a single lonely entry.
- Accommodations are being delivered. Pass: the accommodations listed in the plan are actually happening in the rooms that owe them.
- Accommodation delivery is logged. Pass: there is evidence of delivery, not just an assumption it happened.
- Communication log is current. Pass: family contact matches your stated cadence and recent contacts are recorded.
- Required signatures and dates are in place. Pass: consents, meeting signatures, and dates are present and line up with the plan.
A filled audit row
A composite student we will call J.R. The case manager's term-start row, checked against the twelve points:
- IEP current: pass
- Next review not near-overdue: pass (review in March)
- Reevaluation on track: pass (none due this year)
- Goals match active plan: pass
- Each goal has a baseline: pass
- Each goal has a measurement type: pass
- Data recent (last 10 school days): FAIL, last point is six weeks old
- Data enough for a trend: FAIL, only two points exist this year
- Accommodations delivered: partial, extended time yes, preferential seating unclear
- Delivery logged: FAIL, nothing recorded
- Communication log current: pass
- Signatures and dates: pass
Eight pass, three fail, one partial. The data and delivery-logging gaps are the ones that carry real risk, so they go to the top of the fix list before anything cosmetic.
Triage: fix the riskiest gaps first
A list of gaps is not a plan until it is ranked. Sort by the risk each gap carries, then work top down. This table maps common gaps to the risk and a sensible fix-by window. Treat the windows as a working default, not a legal deadline, since your district and state set the binding timelines.
| Gap found | The risk it carries | Fix by |
|---|---|---|
| Plan expired or review near-overdue | Services running on a lapsed document; the first thing a review flags | This week |
| Required signature or consent missing | A meeting or service may not be properly authorized | This week |
| No recent data on an active goal | No evidence of progress; a thin annual review | Within days; start logging now |
| Accommodation not being delivered | The plan is not being followed in practice | This week; confirm with the rooms involved |
| Delivery happening but not logged | No proof the accommodation was provided | Within two weeks; add a logging routine |
| Goal missing a baseline | Progress cannot be measured cleanly | Within two weeks |
| Goal wording vague (no measurement type) | Hard to score; needs a team fix | Next team meeting |
| Communication log behind | Lower risk, but a parent-relations gap | Within two weeks |
The order is the point. A lapsed plan or a missing consent outranks a behind-on-notes log every time. Closing the top of this list first means that if the term gets busy before you finish, the gaps you left are the ones that carry the least risk.
It helps to read the table in two bands. The top band, timelines and authorizations, is about whether services are legally and properly in place at all. A gap there can mean a student is being served under a document that no longer governs, which is the kind of thing a review treats as serious. The middle band, data and accommodation delivery, is about whether the plan is actually being carried out and whether you can prove it. The bottom band, baselines and logs, is about the quality and completeness of the record. All three matter, but a term that runs out of time should always leave the bottom band unfinished, never the top. The fix-by windows here are a sensible working default; your district and state set the binding deadlines, so check local rules and treat those as the real clock.
Running the whole audit in one 90-minute block
You do not need a day for this. With files in front of you and the twelve points memorized or printed, a full caseload audit fits in a single focused block.
- Set up the block (about 10 minutes). Pull every student's file or open the records, print the twelve points, and make a simple grid: students down the side, the twelve points across. Silence notifications.
- Speed-check each student (about 4 minutes per student). Run the twelve points fast, marking pass, gap, or partial. Do not fix anything yet. For a 14-student caseload this is the bulk of the block, roughly an hour.
- Rank the gaps (about 10 minutes). Pull every gap into the triage table and sort by risk. The riskiest gaps across all students rise to the top.
- Schedule the fixes (about 10 minutes). Put a date and an owner on each gap. The this-week items go on the calendar now; the team-meeting items go on the next agenda.
If your caseload is larger than about fifteen, split the speed-check across two blocks rather than rushing the per-student pass. The number that matters is four minutes of honest checking per student, not finishing in one sitting.
A few things make the block go faster every time you run it. Keep the grid from last term so you can see at a glance which points a student keeps failing. Audit in a quiet block, not between classes, because the speed-check depends on uninterrupted attention. And do the ranking and scheduling steps the same day, while the gaps are fresh. An audit that surfaces gaps but never schedules the fixes is just a list of worries. The value is in the dated, owned to-dos that come out the other side.
Keeping the audit useful
The audit earns its place because it is the same every term, which makes each run faster and the trends easier to spot. A student who failed the data point last term and passes this term is visible progress. A student who keeps failing the same point is a signal to change something, not just to re-flag it.
Pair the audit with two neighbors. The SPED documentation starter kit sets up the system this audit checks, and the substitute and coverage handoff one-pager keeps logging alive when you are out so the next audit has data to find. Run the twelve points, triage by risk, fix the top of the list, and the caseload record holds up term over term.
Common questions
How often should I run this audit?
At the start of each term at minimum, and again before any annual review or big meeting. A term-start pass catches the gaps that built up over a break while there is still time to fix them. Running it more often than once a term is rarely worth the time unless a specific student's file is unstable.
What if I find a gap I cannot fix myself?
Log it, note who can fix it, and put a date on it. Some gaps, like an overdue review or a wording problem in a goal, need a team meeting or another staff member. The audit's job is to surface and prioritize the gap, not to require you to close every one alone in the same sitting.