School & learning · Practical guide

A preschool goodbye the child can rehearse

Rehearsal should make the sequence familiar, including the adult’s return. It should not require the child to pretend they feel cheerful when they are worried.

Happy Family Playing Outdoors in the Sun
Happy Family Playing Outdoors in the Sun. Illustrative photograph, not evidence of the event described. Pexels. See the photographer on the source page · Pexels license. Unmodified source photograph; displayed with responsive cropping. · Credits & license

The situation to understand

At home the child talks happily about preschool; at the classroom door they cling to the adult’s coat. Knowing the building and being able to separate from a caregiver are different challenges.

UNICEF’s preschool preparation guidance includes rehearsal and predictable goodbyes. Rehearsal should make the sequence familiar, including the adult’s return. It should not require the child to pretend they feel cheerful when they are worried.

A closer look at the practical details

Use a familiar object as the pretend preschool door and let the child play both roles. They may reveal a concern by making the toy parent disappear or the toy teacher seem frightening. Follow the story with curiosity rather than correcting the play immediately. Ask what would help the toy child know what happens next. On the actual day, hand over to the agreed staff member and avoid repeatedly returning after the goodbye. Stay available through the program’s normal communication arrangements. Ask staff what they observe once you leave, because a difficult doorway moment and a difficult entire session are different pieces of information.

Practice the moment that matters

One concrete approach is to use a toy or drawing to practice arriving, greeting the teacher and saying goodbye. If the action involves an unfamiliar sequence, talk through or demonstrate the part most likely to cause hesitation. Keep it brief and ordinary rather than turning it into a performance. Let the person ask what would happen if the first version does not work. A usable fallback can make the plan easier to try. Practice should clarify the action, not require somebody to display confidence they do not yet feel.

Use a specific example

When you agree with staff on one brief handover routine and the place the child can go afterward, anchor the explanation in one event or decision rather than a collection of general warnings. Describe enough of the sequence to make the issue understandable, then ask which part remains uncertain. Avoid bringing in every previous disagreement as supporting evidence. That can turn a practical conversation into a judgment of the person. One well-understood example often gives you a clearer starting point for the next action than a long retrospective.

Offer a choice that can be honored

You can describe pickup using a recognizable event in the day rather than an abstract clock time. Where a choice is appropriate, make each offered option realistic; a choice becomes frustrating when only one answer will actually be accepted. If part of the situation requires a firm limit, state that part plainly and identify where flexibility remains. This avoids disguising a settled decision as an open question. Follow through on the option chosen, or explain directly why circumstances require another conversation.

Words to begin with

A possible opening: “I will give you a hug, say goodbye, and come back after your afternoon story. Your teacher will help you choose where to start.”

A complication worth addressing

If the program changes its daily schedule, update the explanation. Promising a return after an event that does not happen can undermine the clarity you were trying to create.

What to notice next

Look for whether the child can describe what happens next and whether staff observe an easier recovery after the goodbye.

Sources & further reading

Source links support the factual context. Practical examples and suggested workflows are original editorial guidance. Sources checked October 5, 2026.

Spotted something we should correct? Send a correction. Read our editorial policy.