How to Plan Transportation for Extended School Year Services

Confirm the IEP and route decision

Ask whether Lucas needs transportation to receive the approved ESY program and where the service is documented. 34 CFR 300.34(c)(16) says transportation includes travel to and from school and between schools, travel in and around buildings, and specialized equipment when required for special transportation. The IEP team applies the individual facts.

Specify every handoff

Record Lucas's pickup point, time window, authorized adult, identity check, driver and monitor roles, vehicle, seat or mobility equipment, AAC, health information, belongings, arrival receiver, attendance confirmation, dismissal release, and backup. Give families and staff one current contact route. Avoid relying on unwritten familiarity from the regular school year.

Model ride time and missed instruction

Track actual pickup, departure, arrival, service start, dismissal, drop-off, and exception dates. Report ride duration separately from waiting and missed ESY minutes. Current law or local policy may set other requirements; 34 CFR 300.106 itself contains no universal federal maximum ride time. Review student experience and health effects as well as averages.

Prepare for failures and incidents

Define response for a missed bus, late vehicle, inaccessible equipment, wrong release, route change, health event, lost AAC, or inability to reach an adult. Protect immediate safety first. Record the event, notifications, attendance and service impact, interim transport, correction, and retest. Repeated transport failure may require an IEP-team review of ESY implementation.

Prepare Lucas's route review

For transportation for extended school year services, map Lucas's actual home-to-program and return trip with time windows, authorized adults, vehicle, equipment, health and AAC access, arrival confirmation, contacts, and backup. Test each handoff without placing Lucas in danger. Record unclear roles or missing information as readiness failures and resolve them through the responsible school and IEP roles.

Build Lucas's source-attributed ESY record

Create a restricted ESY transportation plan for Lucas's IEP need, route, vehicle, equipment, driver, monitor, pickup, drop-off, authorized adult, health, AAC, time, attendance, incident, and backup. Give every field a source, event or observation date, author, status, owner, next action, due date, correction, and closure evidence. Keep Lucas's direct statement, family report, school record, private-provider observation, transport record, and interpretation separately attributed.

Within the ESY transportation plan, separate individualized ESY need, IEP content, school implementation, private clinical recommendation, health-plan authorization, provider capacity, family or student choice, records disclosure, transportation, and delivered service. A shared schedule or goal never combines those authorities.

Protect Lucas's access and ordinary needs

Give Lucas accessible information, AAC or another communication mode, privacy, enough time, useful choices, breaks, and a way to decline or correct a nonemergency discussion. The ASHA AAC portal says AAC users should always have access to communication tools or devices. Record the student's message separately from adult prediction or interpretation.

Preserve Lucas's food, water, bathroom access, mobility, prescribed care, rest, relationships, preferred activities, and emergency help. The BACB Ethics Code guides covered behavior analysts on communication, consent and assent when applicable, competence, assessment, documentation, risk, and referral. It does not assign IEP, school, payer, transportation, or legal authority.

Ask eight ESY evidence questions for Lucas

Use these questions in the ESY transportation plan:

• Which student need and FAPE question is the IEP team deciding?
• What does Lucas want, value, question, or decline?
• Which current state criterion and record supports the decision?
• What service, schedule, setting, staff, transport, and technology are required?
• Which opportunity, support, prompt, source, and period produced the evidence?
• Which school, clinical, payer, family, or transport owner controls each action?
• What current access or interim support is needed while a decision remains open?
• What evidence and student feedback will close or revise the action?

Classify Lucas's fields as complete, failed, pending, declined, disputed, or inapplicable with a reason. Pending work stays visible and blocks only the dependent action.

A fictional ESY example for Lucas

Lucas is fictional and involved in a summer route between home and a regional ESY site. Reviewers freeze 33 transportation and handoff fields and complete 26 of 33 by the checkpoint. Missing student, school, provider, transport, AAC, health, privacy, or implementation evidence remains in Lucas's denominator with an owner, age, and next action.

The ESY transportation plan reports evidence completion separately from IDEA compliance, FAPE, clinical quality, coverage, student choice, service delivery, educational benefit, and satisfaction. Reviewers preserve the original cohort and all failed or pending states. They do not infer that ESY or one support caused change when instruction, health, access, schedule, experience, and time changed together.

Use compatible ESY denominators for Lucas

For Lucas's ESY transportation plan, report completed decisions divided by decisions due; required IEP elements documented divided by elements reviewed; service minutes delivered divided by approved service minutes due; accessible communication checks passed divided by checks due; transport arrivals completed by target divided by scheduled rides; and validated corrections divided by corrections due.

Segment Lucas's results by school, program, service, setting, provider, communication access, transportation, decision state, missed-service reason, and source version when useful. Publish raw counts with percentages and age open items. Keep different definitions, service units, and maturity windows in separate measures.

Create Lucas's dated ESY path

List Lucas's request, evidence cutoff, IEP review, decision, notice, IEP update, staffing, transport, AAC readiness, health handoff, first service, missed service, progress review, correction, last service, fall handoff, and retest in chronological order. Distinguish proposed, scheduled, event, entry, receipt, decision, and effective dates.

The joint FERPA-HIPAA guidance classifies records by holder and capacity. Use the current school, state, provider, payer, and student-specific source for each decision. Share purpose-needed information through the applicable route and preserve authorship, receipt, corrections, and privacy.

Explain ESY source scope for Lucas

For Lucas, 34 CFR 300.106 provides the federal ESY rule: services must be available as necessary for FAPE, the IEP team decides individually, and the public agency cannot use the prohibited categorical or unilateral limits. The general FAPE rule supports this educational duty; it neither authorizes private care nor decides Lucas's individualized ESY plan. Current state criteria, procedures, calendars, and dispute routes can add important detail and require direct verification.

The CASP organizational overview supplies broad operations and risk framing for page 6 in this cluster. Give Lucas and the authorized adult an accessible summary of decisions, evidence, owners, dates, limits, and review triggers. Keep the page draft and noindex pending named review.