Arkansas First Connections to Preschool: Family Guide

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

Map First Connections work to the school decision

Arkansas's First Connections rules describe periodic notice for toddlers approaching age three and a transition conference in the months before the birthday. The filed program rules identify First Connections as the state's Part C system and distinguish its eligibility from later education eligibility. Ask the service coordinator and school contact to list their separate actions, evidence, and due dates.

Build the calendar from the third birthday

Build the Arkansas calendar around the third birthday. Include the IFSP transition plan, scheduled notification cycle, family notice, conference invitation, conference, any permission to disclose records, school evaluation consent, assessments, eligibility decision, proposed IEP, receiving-program applications, final First Connections service, and first receiving service. Verify the operative rule and actual notice dates instead of estimating from age alone. The federal Part C transition rule supplies the national baseline for notification, late referrals, conferences, IFSP steps, and state options. Arkansas's effective sources and the family's current written notices control the working plan for this child.

Keep every decision with its actual owner

The Arkansas First Connections transition may involve Arkansas First Connections, preschool special education, Head Start, child care, a health plan, private clinicians, and community programs. The Part C team owns its coordination duties. The education agency decides school eligibility and services. Each community program controls enrollment. A clinician recommends within scope, and a payer decides coverage under the plan. Use separate tracker rows so one organization's approval never stands in for another's.

Compare the child's complete weekly routine

For the Arkansas handoff, place each proposed schedule beside caregiver work, siblings, medical visits, travel time, and the child's recovery needs. Ask what arrival, learning, play, meals, toileting, rest, transportation, therapy, and departure would look like. Visit the actual site when possible. Record which supports are confirmed, which evidence is missing, and who can resolve each gap. A program category does not show whether the child's day or the family's week will work.

Prepare a controlled transition packet

The Arkansas packet can include the current IFSP, recent evaluations, progress information, family priorities, and the health or safety information needed by the next setting. Describe speech, sign, gesture, movement, AAC, backup communication, partner response, and wait time in plain language. Add equipment, sensory, mobility, feeding, toileting, medication, allergy, and transportation details when relevant. Index what the family agreed to share, the recipient, the date sent, and confirmation of receipt.

Protect access during evaluation and visits

During Arkansas evaluations, meetings, and program visits, use the child's ordinary communication tools, interpreters, visual access, mobility supports, sensory accommodations, and health protections. Ask how the child can accept, decline, pause, request help, and show discomfort. Preserve food, water, bathroom access, movement, communication, prescribed care, and emergency help. Document an access failure as a system condition so it is not mistaken for evidence about the child's ability.

Control the transition packet field by field

Arkansas's rules address family consent for sharing identifying information, evaluation material, the IFSP, and medical information. Ask which records are required or proposed, why each recipient needs them, and whether a narrower packet will answer the purpose. Keep an index of the family's authorization, the items sent, delivery confirmation, and any correction. A broad packet should not substitute for a purposeful handoff.

A fictional Arkansas transition

Noah's family indexes 14 possible packet items. Eleven are approved, current, and confirmed received, for 11 of 14, or 78.6% packet readiness. An outdated medication page, a missing AAC summary, and an unsigned release remain open. The family fixes those records before using the packet for the school evaluation and preschool visit.

Questions for the next meeting

Which First Connections office owns the transition? When was the child included in school notification? When is the conference? Which attendees received notice? What records did the family authorize? Which school evaluation is required? When will Part B eligibility and any IEP be decided? Which community settings have separate enrollment? How will medication, AAC, mobility, feeding, and transportation information reach the right staff?

A final family checklist

Before the next Arkansas transition event, confirm the third birthday, sending-program contact, receiving-program contacts, IFSP steps, notification, family choices, consent, records, conference, evaluation, eligibility or enrollment, proposed plan, setting, schedule, communication access, health and safety supports, transportation, last Part C date, first receiving-service date, open issues, escalation route, and post-start check-in. Give every unresolved item one named owner and one next date. Keep counts beside percentages so unfinished work stays visible.

Turn the Arkansas packet index into a decision record

Build proof around the state-specific handoff, not merely a list of meetings. Arkansas DHS, First Connections Program Rules supplies the current primary framework for this Arkansas guide. List identifying information, evaluation material, the IFSP, medical or medication information, AAC summary, and every other proposed item separately. For each item, show the family's authorization, current version, purpose, recipient, sent date, receipt confirmation, and correction status. Link the packet to the school evaluation without treating it as the eligibility decision. A dated notice, signed consent, receipt, evaluation report, eligibility record, plan, or enrollment decision should close the corresponding tracker row. A scheduled event stays in progress until its result reaches the family.

Give every cross-system record an index entry with title, author, date, purpose, family permission, sender, recipient, sent date, receipt confirmation, correction, and next action. Keep earlier versions when they explain a decision, then mark the version the receiving team currently uses. Name one contact for the First Connections service coordinator and another for the school system. Ask the receiving contact to identify unreadable pages, missing attachments, stale health information, or new evaluation questions before the next decision meeting.

Use the Arkansas preschool visit to test the packet

Walk through the school or community site, medication and feeding procedures, AAC access, mobility, toileting, transportation, staff questions about the packet, child care, therapy, and the final First Connections service. Use the actual location and approximate travel time planned for the first day whenever a visit is available. 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 placement, program, or service route becomes workable when those connections have names and evidence.

Prepare a current medication page, usable communication summary, valid release, and receiving contact who can correct a missing or unreadable packet item before the visit. Record the travel duration, waiting time, inaccessible step, missing material, communication breakdown, fatigue signal, and question found during rehearsal. Assign every correction to an office or person able to act, then retest the highest-impact part. The backup should preserve safe care, a reliable communication method, necessary equipment, and one person who can coordinate the next decision.

Recover a late or conflicting Arkansas 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. First Connections owns Part C notice, transition planning, conference coordination, and authorized record transmission. The school owns Part B evaluation, eligibility, IEP, and implementation. Route a community enrollment question to that program and keep its record outside the school decision row. Ask the responsible system for its current procedural-safeguard, complaint, mediation, or review information when the concern remains unresolved. Keep conflicting answers in the record until the responsible offices reconcile them.

Contingency planning should identify real care and support without predicting a legal outcome. Ask the First Connections service coordinator, school system, 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 the separate authority of each system.

Review the first ten and thirty days in Arkansas

Noah's family begins the post-start review with 11 of 14 packet items are approved, current, and confirmed received; the outdated medication page, missing AAC summary, and unsigned release remain active until each has a decision and implementation proof. During the first ten days, check whether the school used the intended records, Noah's health and communication information reached the responsible staff, and each corrected packet item matches the version used in practice. Describe each observation with the routine, support, child's response, and practical impact. That record helps the receiving team preserve effective supports and investigate a repeated access problem.

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

Limits and immediate next steps for Arkansas 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, local contacts, and program capacity can change. Verify the operative source and assigned owner with the First Connections service coordinator and school system; seek qualified educational, legal, clinical, or benefits advice when a disputed or high-impact question requires it.

Next, place the third birthday and last current-service date on the family calendar. List every school, community, developmental-disability, 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, a usable first-day test, and a post-start review date.