The IEP Season Pipeline: Process All Your Annual Reviews in Half the Time

What This Builds

A systematic pipeline that lets you process your entire IEP annual review caseload in a structured, repeatable workflow — batching students by review date, generating draft documentation for each in under 10 minutes, and tracking completion with a Google Sheet dashboard. School OTs managing 40–60+ students who adopt this pipeline typically complete their spring reviews 2–3 weeks earlier with significantly less burnout.

Prerequisites

• Claude Pro ($20/month) — Projects feature required for persistent assistant context
• Google Sheets (free) — for student tracking dashboard
• A list of all your students with their upcoming annual review dates
• 2 hours to build the system before IEP season starts (build in January/February)

The Concept

The IEP pipeline turns a chaotic, deadline-driven process into an assembly line. Instead of each student's review being a one-off project you start from scratch, you process students in batches through a consistent workflow: collect data → generate draft documentation → review and edit → enter into IEP software → mark complete. The Claude Project serves as your consistent documentation engine — loaded with your district's standards, goal format preferences, and your own professional style — so the 5th student you process is just as easy as the first.

Build It Step by Step

Part 1: Create Your IEP Season Claude Project

Follow the Level 3 guide "Survive IEP Season with an AI Writing Workflow" to set up your basic Claude context. For this advanced version, add these enhancements to your Project Instructions:

## IEP Annual Review Pipeline Mode

When I say "Pipeline mode — [student name/ID]," I will provide a structured data form. Output three documents in this exact format:

--- DOCUMENT 1: PRESENT LEVEL OF PERFORMANCE ---
[3-4 sentences describing current performance in OT areas, written for IEP documentation]

--- DOCUMENT 2: ANNUAL GOALS ---
[2-4 goals in this format:
Goal [#]: Given [condition], [student] will [observable behavior] with [criteria] in [context] as measured by [method] by [annual review date].]

--- DOCUMENT 3: PROGRESS SUMMARY ---
[1-2 paragraphs summarizing progress on previous year's goals, appropriate for the Annual Review meeting]

After outputting these three documents, say "Ready for next student" so I know to proceed.

## My District's Goal Format Requirements
[Paste an example of a well-accepted goal from a previous IEP — this trains Claude on exactly what your district expects]

## Service Eligibility Language
When educational impact needs to be stated, always connect OT needs to: [describe your district's typical framing — e.g., "access to and participation in grade-level curriculum" or "school-based activities of daily living"]

Part 2: Build Your Student Data Dashboard

Create a Google Sheet with these tabs:

Tab 1: Master List

Tab 2: Student Data Forms For each student, maintain a form with the fields Claude needs:

• Grade, disability, placement
• Current performance observations
• Previous goals
• Progress on previous goals
• Target areas for next year
• Teacher/parent priorities

You'll fill these out as you see students in the weeks before review season. The more complete these forms are, the faster the Claude pipeline runs.

Part 3: Set Up the Processing Workflow

Once your Project and spreadsheet are ready, here's your session workflow during IEP season:

Monday Planning Session (15 minutes):

1. Sort your spreadsheet by "Days Until Review"
2. Identify students with reviews in the next 2 weeks
3. Mark those as this week's batch

Processing Session (2–3 hours, 1–2 times/week):

1. Open Claude to your IEP project
2. Start with: "I'm starting an IEP season processing session. I'll give you 8 students to process."
3. For each student, paste: "Pipeline mode — [Student ID]: [complete data form]"
4. Claude produces all 3 documents → copy each into a temp document for review
5. After each student: mark "Draft Generated" in your spreadsheet

Review Session (separate — not same session):

1. Read each draft carefully for accuracy
2. Edit anything that doesn't match the student's actual performance
3. Mark "Reviewed" in spreadsheet

Entry Session:

1. Copy approved text into your IEP software
2. Mark "Entered" in spreadsheet

Part 4: Process Your First Batch

Let's test with your next 3 students. In your Claude Project:

I'm starting IEP season processing. I'll provide 3 students. Output all three documents for each student before moving to the next.

Pipeline mode — Student JD-4:
Grade: 4th
Disability: Autism Spectrum Disorder
Placement: General education with resource support
OT services: 30 min direct weekly
Current performance: [your data]
Previous goals: [list]
Progress: [describe]
Target areas: [describe]
Parent/teacher priorities: [any]
Annual review date: [date]

Review the output. Does it match your district's format? Adjust Project Instructions as needed.

Real Example: School OT with 48 Students

Setup: OT has 48 students, 22 with annual reviews in April and May. Without a system, this would mean 22 individual writing sessions totaling 12–15 hours of documentation during the school day.

With the pipeline:

• Week 1 (Feb): Build spreadsheet, enter all student data forms during prep periods
• Week 2–6 (Mar–Apr): Three processing sessions of 8 students each (90 min per session)
• Each session: 22 minutes per student → 3 hours per session → all 22 students processed in 9 hours
• Review sessions: 5 min per student → 2 hours total for all reviews
• Entry into IEP software: 8 min per student → 3 hours total

Total time: ~14 hours (vs. 12–15 hours under the old system, but now spread over 6 weeks with no deadline crunch)

The real benefit isn't total hours — it's the elimination of the March/April documentation crisis.

What to Do When It Breaks

• Claude's goals don't match district format → Paste 3 examples of perfect goals from previous IEPs into the Project Instructions; this is the fastest calibration method
• PLOP language is too clinical for IEP document → Add to Instructions: "Write PLOP language that parents can easily understand — avoid technical OT assessment terminology; describe function in plain language"
• Processing sessions take too long → Your student data forms are incomplete; the more complete the input, the faster the output
• Goals are too challenging or too easy → Add specific guidance to your Instructions: "For students with [disability type], goals should focus on [approach]; typically achievable in [timeframe]"

Variations

• Simpler version: Use the basic Level 3 workflow (no Project) but batch process 5 students per Claude session using the same session context
• Extended version: Add a Zapier integration that emails you a reminder 45 days before each student's annual review date, automatically triggered by your Google Sheet's review date column

What to Do Next

• January (before IEP season): Build the spreadsheet and Claude Project; run 2–3 test students
• February: Complete all student data forms while seeing students; update forms as you collect data
• March–April: Process reviews in weekly batches; aim to have all drafts complete 3 weeks before the last review date
• May: After season, review what worked; update your Claude Project Instructions for next year

Advanced guide for occupational therapist professionals. Requires Claude Pro ($20/month) for Projects feature.