IEP service log template: the seven columns that protect you
The service log is the SPED artifact that proves the IEP’s service grid actually happened. No federal regulation requires the log itself — what 34 CFR § 300.320(a)(7) requires is the promise: every service on the IEP carries a projected start date and an anticipated frequency, location, and duration. The log is how a provider shows the promise was kept, session by session, when a parent, an auditor, or a hearing officer asks about February. Below: the columns worth keeping (and the ones that waste your time), missed-session codes and the make-up question, and how the log differs by provider role.
The template: eight columns, one row per session
Build it in whatever your district runs — the platform’s service-tracking module, a spreadsheet, or paper on a clipboard. The format matters less than the columns and the discipline of a row per session, logged the day it happens:
| Column | Why it earns its space | Example entry |
|---|---|---|
| Date | The reconciliation key. Every dispute starts with a date range. | 10/14 |
| Minutes (or start–stop) | The unit the IEP grid promises (34 CFR § 300.320(a)(7) requires anticipated frequency and duration). Totals must be summable. | 30 (9:00–9:30) |
| Session type | Direct vs indirect/consult, push-in vs pull-out — mixed service grids fail audits when the log doesn't distinguish them. | Direct, pull-out |
| Group size | Individual vs group is often written into the service line; a 1:1 line delivered in a group of 4 is a delivery gap the log should surface, not hide. | 3 |
| Goal(s) addressed | Links the session to the IEP — and to the data sheet where the measurement lives. | R1 (decoding), R2 (fluency) |
| Focus note (one line) | Enough to reconstruct the session a year later; not a narrative. 'CVC-e words, 78% on exit check' beats a paragraph. | CVC-e word sort; exit check 7/9 |
| Provider initials | Accountability and coverage tracking — it shows who actually delivered the session, including sub-covered ones. | JM |
| Missed code + make-up date (when applicable) | SA = student absent, PA = provider absent, SC = school closure, T = testing. The code decides whether make-up is owed; the make-up date closes the loop. | PA — made up 10/17 |
What deliberately is not here: narrative session notes (they migrate into the one-line focus column or the data sheet), subjective ratings of how the session went, and anything already living on the data collection sheet. The log documents delivery; the data sheet documents learning. Merging them produces a document too heavy to keep daily — and a log that isn’t kept daily reconstructs itself from memory, which is the failure mode the whole artifact exists to prevent.
Missed sessions: the code column is the argument
Sessions get missed in every building. What separates a defensible year from an indefensible one is whether the log can say why, because the reason decides what is owed. The working distinction, in nearly every district framework: sessions missed because the system was unavailable — provider absent without coverage, pulled for meetings or testing administration, recurring schedule collisions — accrue as undelivered service the district generally needs to make up, because the IEP’s frequency commitment went unkept by the school. Sessions missed because the student was absent usually do not demand one-for-one make-up — though a long absence is an IEP-team conversation, not a logging question. Four codes cover it (SA, PA, SC, T), each with a make-up date column to close the loop. A February log reading “PA ×4, no make-ups” is a compensatory-services conversation waiting to happen — better that you find it in March than opposing counsel in June. The minute-level arithmetic of keeping a service grid deliverable in the first place is its own problem — our service minutes guide covers it.
The same log, four provider realities
| Provider | What changes |
|---|---|
| Resource / pull-out teacher | Log per block, not per student-goal. One row per session with the goal column carrying the shorthand; the data sheets carry the trials. |
| Push-in / inclusion support | The hardest to log honestly because the service blends into the room. Log the scheduled block and what the support actually was — proximity support during independent work is a different service than co-taught small group, and the IEP usually names one of them. |
| SLP / OT / PT and other related services | Usually the cleanest logs (session-based practice). The trap is consult minutes: indirect service lines need rows too — date, minutes, who was consulted, about what. Undocumented consult minutes are undelivered consult minutes. |
| Paraprofessional-implemented support | The para records raw session data; the supervising teacher owns the log and reviews it on a named cadence. Accountability follows the certification, not the seat. |
One boundary worth naming: districts that bill Medicaid for related services run separate billing documentation with its own rules and forms. That system does not replace the instructional service log, and the service log does not satisfy it — providers in billing districts keep both, and the district’s Medicaid coordinator, not this page, is the authority on the billing side.
The monthly reconciliation: where the log earns its keep
A log nobody reads is ritual, not protection. The case-manager move that converts it into protection is a monthly reconciliation pass: total the logged minutes per service line, set them against the grid’s commitment, and flag any line running short — then fix the schedule or reconvene the team, in that order. Ten minutes per student per month, and it changes the shape of the year: service drift surfaces in October as a scheduling fix instead of at the annual review as a compliance finding. The same pass feeds the file review checklist line on service delivery, and it is the evidence behind every progress report’s implicit claim that services occurred as written (34 CFR § 300.320(a)(3) sets the reporting duty; the SPED documentation checklist places the log among the other artifacts).
Frequently asked questions
Does federal law require IEP service logs?
No regulation in 34 CFR Part 300 requires a service log by name. What the IEP must contain is the commitment the log verifies: the projected start date and the anticipated frequency, location, and duration of every service and modification (34 CFR § 300.320(a)(7)), plus a description of how progress will be measured and when reports go home (§ 300.320(a)(3)). The log exists because those commitments are enforceable: when a parent, an auditor, or a due-process hearing officer asks whether the 90 weekly minutes on the service grid actually happened in February, the service log is the only document that answers with dates instead of memory. Districts and many states add their own documentation requirements on top — check yours — but the practical rule is universal: an undelivered service you can't disprove is treated as undelivered.
What should each row of a service log contain?
Seven columns cover what every later reader needs: (1) date; (2) minutes delivered, or start/stop times; (3) session type — direct, indirect/consult, or push-in vs pull-out; (4) group size; (5) the IEP goal or goals addressed, by shorthand; (6) a one-line activity or focus note; (7) the provider's initials. An eighth column earns its space in any building with real attendance churn: a missed-session code with a make-up date. That is a log a substitute could keep, an auditor could total, and a case manager could reconcile against the service grid in minutes.
What counts as a missed service, and do sessions have to be made up?
Federal regulation sets no make-up standard — this is district policy and, in some states, state guidance. The distinction that matters in nearly every framework is why the session was missed. When the provider was unavailable (absence with no coverage, meetings, scheduling collisions) or school operations canceled the session in a pattern, districts generally treat make-up or compensatory time as owed, because the IEP's frequency commitment went undelivered by the system. When the student was absent, most policies do not require one-for-one make-up, though extended absence may trigger the IEP team to reconvene. Log the reason code either way: a log that shows only delivered sessions cannot distinguish the two stories, and the distinction is the whole argument.
Who keeps the service log — the case manager or the provider?
Whoever delivers the session logs the session: the resource teacher for pull-out blocks, the SLP for speech sessions, the general education co-teacher or SPED teacher for push-in support as your district assigns it, and the supervising teacher for paraprofessional-implemented support (the para can record the raw data, but service accountability follows the supervising professional). The case manager's job is reconciliation, not transcription — a monthly pass comparing logged minutes per service line against the grid, so a drift of one weekly session surfaces in October rather than at the annual review.
Is a service log the same as the data collection sheet?
No, and merging them is a common failure. The data sheet measures the student — trials, prompts, accuracy against a goal criterion. The service log documents the delivery system — that the session occurred, for how long, in what format. A great data sheet with no minutes proves you measured a service you cannot prove you delivered; a great log with no data proves you delivered sessions with no evidence they worked. Two artifacts, two questions. Keep them linked (the log's goal column pointing at the data sheet) but separate.
How long should service logs be kept?
Treat them as part of the student's special education record and follow your district's records-retention schedule — retention periods are set by state law and district policy, not by IDEA. The floor worth remembering: logs should survive at least through the window in which the services they document could be disputed, and IDEA's due-process complaint window runs two years from when the parent knew or should have known about the alleged action — unless the state sets its own explicit time limit (34 CFR § 300.507(a)(2)). Ask your records custodian for the actual schedule rather than guessing; the log you shredded is the session you can no longer prove.
Related guides
- IEP service minutes — the arithmetic upstream of the log: what the grid commits and how schedules break it.
- SPED documentation checklist — every artifact a SPED file needs, the service log included.
- IEP data collection sheets — the sibling artifact: measuring the student, not the delivery.
Federal citations quote 34 CFR Part 300 as published by the eCFR. Make-up and retention rules are set by district policy and state guidance — confirm yours before relying on the general patterns described here. This page is practitioner guidance, not legal advice.