AAC access on school field trip activities should remain available during travel, transitions, instruction, social time, meals, bathroom use, health care, and emergencies. Prepare the student's primary system and an effective backup, relevant vocabulary, charging, connectivity, mounting, weather protection, privacy, and partner response. Test access in the actual trip conditions. Device custody or safety rules should preserve communication rather than remove it for convenience.

Prepare vocabulary for the itinerary

With Ilya, review people, places, transport, activities, animals, food, bathroom, pain, allergies, stop, help, lost, weather, choice, refusal, and emergency messages. Add needed vocabulary without scripting what Ilya should say. Preserve familiar organization and access. Confirm that a partner can find urgent messages only when Ilya wants support.

Protect primary and backup systems

The ASHA AAC portal says AAC users should always have access to communication tools or devices. For Ilya, define custody, carrying, mounting, charging, battery, connection, protective case, rain cover, volume, headphones, and backup. Test both systems outdoors, on the vehicle, and at the activity site.

Train partner response

Identify how adults wait, recognize Ilya's message, confirm unclear content, respond, and preserve privacy. Record prompting and interpretation separately from Ilya's selections. Avoid requiring speech, eye contact, or a different response before honoring a recognizable message. A partner may assist access while leaving authorship with Ilya.

Plan recovery after failure

If the device is lost, damaged, wet, uncharged, locked, disconnected, or briefly hazardous, activate the effective backup and protect immediate safety. Record discovery time, student impact, interim access, search or repair owner, family notice, evidence, restoration, and retest. Recurring failure should trigger review by the responsible school team.

Prepare Ilya's access review

Bring Ilya's field-trip AAC continuity plan, current itinerary or activity rules, direct student input, school plan, and focused evidence. Ask each school, health, transport, private-clinical, payer, or legal role to decide only within its authority. End with specific supports, owners, dates, backups, written decisions, and a student-feedback checkpoint. For AAC access on school field trip, preserve all unresolved conditions instead of relying on a general promise of inclusion.

Build Ilya's source-attributed activity record

Create a restricted field-trip AAC continuity plan for Ilya's device, owner, custody, vocabulary, access method, backup, charge, connection, mount, weather, privacy, partner, emergency, incident, and recovery. Give every field a source, event or observation date, author, status, owner, next action, due date, correction, and closure evidence. Keep Ilya's direct statement, family report, school record, venue information, transport record, health record, provider observation, and interpretation separately attributed.

Distinguish school activity rules, IEP decisions, Section 504 decisions, student or family choices, health orders, transportation, private clinical recommendations, payer decisions, records disclosure, incident findings, and delivered supports. A shared plan never collapses those authorities.

Protect Ilya's access, choice, and ordinary needs

Give Ilya accessible information, AAC or another communication mode, privacy, useful choices, enough time, 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 Ilya's food, water, bathroom access, mobility, prescribed care, rest, relationships, and emergency help. The BACB Ethics Code guides covered behavior analysts within its scope. It does not assign school, IEP, 504, health, transport, payer, activity, or legal authority.

Ask eight activity-access questions for Ilya

Use these questions in the field-trip AAC continuity plan:

  • What is the activity's purpose, itinerary, essential rule, and decision date?
  • What does Ilya want, prefer, question, or decline?
  • Which current source and authorized role governs each decision?
  • Which aid, modification, staff support, transport, health plan, or AAC access is needed?
  • What evidence shows readiness at the actual site and time?
  • Which privacy, consent, supervision, or emergency route applies?
  • What is the backup when a critical dependency fails?
  • What participation and student-experience evidence will close or revise the plan?

Classify Ilya'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 school-activity example for Ilya

Ilya is fictional and involved in an outdoor farm trip with rain forecast. Reviewers freeze 29 AAC continuity controls and complete 23 of 29 by the checkpoint. Missing student, school, venue, transportation, AAC, health, privacy, or implementation evidence remains in Ilya's denominator with an owner, age, and next action.

The field-trip AAC continuity plan reports evidence completion separately from legal compliance, equal opportunity, clinical quality, student choice, service delivery, safety, meaningful participation, and satisfaction. Reviewers preserve the original cohort and all failed or pending states. They do not infer that one support caused an outcome when access, peers, itinerary, staff, environment, and time changed together.

Use compatible activity-access denominators

For Ilya's field-trip AAC continuity plan, report accessible invitations divided by invitations due; completed individualized reviews divided by reviews due; supports ready divided by approved supports due; accessible rides divided by scheduled rides; activities attended divided by chosen and eligible activities; and validated corrections divided by corrections due.

Segment Ilya's results by school, activity, site, decision path, communication mode, support, transport, health need, participation state, incident type, and source version when useful. Publish raw counts with percentages and age open items. Keep selection, access, attendance, duration, role, and satisfaction as separate measures.

Create Ilya's dated activity path

List Ilya's invitation, request, review, decision, plan, staff briefing, transport test, AAC check, health handoff, departure, participation, incident, return, family communication, correction, 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, venue, transport, 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 source scope for Ilya

For Ilya, 34 CFR 300.107 addresses equal opportunity in nonacademic and extracurricular services, while 34 CFR 300.117 addresses participation with nondisabled children to the maximum extent appropriate and IEP-team-determined supplementary aids and services. The current OCR page adds civil-rights context. Current state and school requirements still need direct verification.

The IEP-content rule connects approved services, aids, modifications, and staff supports to extracurricular participation. The implementation rule requires responsible teachers and providers to know their duties. For Ilya, translate both into the actual itinerary or activity rather than relying on a generic plan reference.

The CASP organizational overview supplies broad operations and risk framing for page 3 in this cluster. Give Ilya 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.

Related resources

Sources

Finni resources

Ready for the next step?

Find ABA care near you