Utah Baby Watch to Preschool: Family Transition Guide

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Use the current Baby Watch policy and live program page

Utah's current Baby Watch page links the OSEP-approved transition policy, parent rights, program contacts, and the state transition agreement. The transition policy treats children enrolled from 27 through 36 months as potentially eligible for planning purposes and describes notification through state data systems at 27 months or upon a later initial IFSP. Verify the current local contacts and forms.

Build one age-three control calendar

Track the initial IFSP transition discussion, later plan updates, referral-notification notice, any opt-out, conference decision, LEA invitation, record authorization, evaluation consent, assessments, eligibility, IEP, final Baby Watch service, and first receiving service. The transition policy says Part C exits no later than the third birthday; a district eligibility and service timeline remains a separate Part B responsibility. The federal Part C transition rule provides the shared baseline for notification, late referral, conferences, and IFSP transition steps. Use Utah's current effective source and the family's own notices for operational dates, responsible offices, and available state choices.

Separate decisions before comparing routes

The Utah Baby Watch transition can touch Utah Baby Watch Early Intervention Program, the education agency, Head Start, child care, community preschool, health-plan services, and private clinicians. The Part C team coordinates its exit work. The education team decides school eligibility and services. Each early learning program decides enrollment. Clinicians recommend within scope, and payers decide coverage. Give every decision a separate row, source, owner, due date, and status.

Test the child's actual week

For a Utah receiving route, map arrival, instruction, play, meals, toileting, rest, transportation, therapy, and departure. Put that schedule beside caregiver work, siblings, health appointments, travel, and recovery time. Visit the actual setting when possible. Record the communication, sensory, mobility, feeding, health, and staffing supports that are confirmed. A program label or eligibility category does not show whether the child's day will be accessible.

Build a purposeful record handoff

Gather the current IFSP, relevant evaluations, progress information, family priorities, and the health or safety information the next Utah setting needs. Describe speech, sign, gesture, movement, AAC, backup communication, partner response, and wait time. Add equipment, sensory, mobility, feeding, toileting, medication, allergy, and transportation details as applicable. Index family authorization, the exact records sent, recipient, delivery date, and confirmation of receipt.

Preserve access during every transition activity

During Utah evaluations, conferences, and visits, use the child's usual communication tools, interpreters, visual supports, mobility access, sensory accommodations, and health protections. Give the child a reliable way to accept, decline, pause, request help, and show discomfort. Preserve food, water, bathroom access, movement, prescribed care, and emergency help. Record an access failure as a system condition so it is not misread as the child's performance.

Separate declining the conference from every other decision

The Utah State Board of Education preschool page links technical guidance for families who decline the transition conference. A conference decision does not automatically answer notification, referral, record disclosure, school evaluation, eligibility, or services. Ask Baby Watch and the LEA to state which actions continue, which require separate consent, and how a family can contact the district directly.

A fictional Utah handoff

Kai's family declines the conference but tracks eight remaining actions. Six have a documented status, giving 6 of 8, or 75% clarity. The district referral receipt and evaluation-consent request remain open. The family records the conference choice separately and asks for the direct LEA route in writing.

Questions for the next transition meeting

When was transition introduced in the IFSP? Was referral notification sent, or did the family opt out? Is the family accepting or declining the conference? Which actions continue after that choice? Has the LEA received a direct referral? What records and evaluation consent apply? When will eligibility and any IEP be decided? How will communication, sensory, feeding, medication, mobility, and transportation access work? Which safeguard fits a missed action?

A final control checklist

Before the next Utah transition event, confirm the birthday, sending contact, receiving contacts, IFSP steps, notification, family choices, consent, records, conference, evaluation, eligibility or enrollment, plan document, setting, weekly schedule, communication access, health and safety supports, transportation, last Part C date, first receiving-service date, unresolved tasks, escalation route, and post-start review. Assign every open task one accountable owner and one next date. Show counts beside percentages.

Keep Utah's conference choice separate from referral follow-through

Build proof around the state-specific handoff and actual receiving site. Utah Baby Watch, Transition to Preschool and Other Programs Policy supplies the primary Utah framework for this guide. Track the initial IFSP transition discussion, later plan updates, referral-notification notice, opt-out choice, conference decision, LEA invitation when applicable, record authorization, district referral receipt, evaluation-consent request, assessments, eligibility, IEP, final Baby Watch service, and first receiving service. Mark the conference declined without closing any remaining district or Part C action. Close a row only with the dated notice, consent, receipt, report, decision, plan, or start evidence that matches its purpose. A scheduled meeting stays in progress until the family receives its result.

Index every record by title, author, date, purpose, family authorization, sender, recipient, delivery date, receipt confirmation, correction, and next action. Keep earlier versions when they explain a decision and mark the copy currently in use. Name one contact for the Baby Watch service coordinator and another for the local education agency. Ask the receiver to identify unreadable pages, missing attachments, stale health information, and new evaluation questions before the next decision meeting.

Test the Utah direct LEA route after a declined conference

Use the actual district contact, preschool site, transportation route, AAC, feeding or medication support, mobility, sensory needs, child care, therapy, family work, and birthday calendar. Ask the LEA how it will receive and act on the direct referral when no transition conference supplies a shared meeting record. Confirm who meets the child, who can use the communication system, where equipment and health information go, and how the family reaches the responsible person during the day. A program becomes workable when those connections have names, dates, and evidence.

Prepare a dated direct-referral contact, accessible record set, communication backup, transportation alternative, safe care schedule, and a named owner for evaluation consent. Record travel duration, waiting, an inaccessible step, missing material, communication breakdown, fatigue, or an unanswered question found during rehearsal. Assign every correction to an office or person able to act, then retest the highest-impact condition. The backup should preserve safe care, reliable communication, necessary equipment, and one person who can coordinate the next decision.

Recover a late or conflicting Utah action

When a target date passes, send a short written recap naming the action, source for the expected date, family steps already completed, current impact, requested response, and next follow-up. Baby Watch owns its transition plan, referral-notification choice, conference offer, authorized records, and Part C exit. The LEA owns referral receipt, evaluation, eligibility, IEP, and school implementation. Ask each owner to proceed with its remaining actions regardless of the family's separate conference decision. Ask for the current procedural-safeguard, complaint, mediation, or review information when the concern remains unresolved. Retain conflicting answers until the responsible offices reconcile them.

Contingency planning should identify real care and support without predicting a legal outcome. Ask the Baby Watch service coordinator, local education agency, community program, clinician, and payer to state their own end or start dates and interim responsibilities. Mark the first affected date for any gap in care, communication, transportation, equipment, or family coverage. This gives the next meeting a concrete problem while preserving each system's authority.

Review the first ten and thirty days in Utah

Kai's family begins the review with 6 of 8 actions remaining after the conference choice have a documented status; the district referral receipt and evaluation-consent request remain active until each has decision and implementation proof. During the first ten days, check whether the direct LEA route produced the expected evaluation and plan, Kai's conference choice remained accurately recorded, and the first-day supports matched the written decision. Describe each observation with the routine, support, child's response, and practical impact. The receiving team can then preserve effective supports and investigate repeated access problems.

At the Utah day-30 review, compare the actual week with the accepted IFSP, IEP, enrollment plan, waiver status, authorization, or family schedule. Check attendance, delivered services, location, transportation, communication, equipment, health and safety procedures, provider coordination, family workload, and the child's participation or recovery. Send a gap between the written plan and delivered support to the local education agency or other office that can correct it and assign a response date. Record strengths beside gaps because a successful Utah partner or routine tells the team what to preserve.

Limits and immediate next steps for Utah families

This draft organizes transition work. It cannot determine an individual child's eligibility, placement, service, coverage, right, or deadline. Current law, the child's record, written notices, family consent, and the responsible agency, program, or payer control those decisions. State options, manuals, portals, contacts, and capacity can change. Verify the operative source and assigned owner with the Baby Watch service coordinator and local education agency; seek qualified educational, legal, clinical, or benefits advice for disputed or high-impact questions.

Next, place the third birthday and last current-service date on the calendar. List every school, community, waiver, and clinical route under consideration, then name its decision owner. Choose the closest unresolved consent, record, evaluation, meeting, site visit, transportation, or start action and request its date in writing. Keep the tracker open until the family has a confirmed receiving plan, usable first-day test, and post-start review date.