An enquiry asks for information. A waitlist entry records interest under your admissions process. A possible opening still needs confirmation. An offer sets out a particular place and the conditions for accepting it. Use those distinctions consistently in your messages and records.

These are suggested communication labels, not a prescribed admissions policy. Apply your actual process and local requirements, including any rules for waiting lists, fees, priority, and personal information.

The distinction should exist in your records as well as your email. If a colleague sees “accepted”, they should be able to tell whether that means a request was added to a list or an actual place was accepted. Record the program, requested schedule, start period, last contact, and next promised action using your approved system.

Decide who can confirm a place and who can only discuss a potential one. Otherwise, a helpful reply from one team member can unintentionally become a promise the person managing enrolment cannot fulfil.

Explain how your actual priority and matching rules work. If age group, requested days, or start date affect which opening a family can be considered for, say so. A list position and an expected start date answer different questions. Give any position information your rules require, and explain what it can and cannot tell the family about timing.

For a fictional provider with separate Monday–Wednesday–Friday and Tuesday–Thursday requests, a vacancy in one schedule may not fit a family requesting the other. That example explains why matching matters; it is not permission to invent priorities or move families outside your published process. Show the relevant policy and apply it consistently.

Local requirements can be specific. Ontario prohibits licensed centre and home child care agency waiting-list fees or deposits solely for placement on a waiting list. Its centre guidance also addresses written waiting-list policies and how families can ascertain position while preserving privacy. Check the applicable requirements, including arrangements for centrally administered lists, before adapting these messages.

A useful response identifies the request on file, provides the position/status information applicable to that process, and names the next event that could change it. If you cannot estimate a start date, say that plainly. Avoid percentages or month estimates unless you have a sound basis for them. Frequent check-ins should not be implied to change priority unless that is genuinely part of a lawful, published process.

Source: Ontario licensing manual: waiting-list fees and policies

Use this only once you have recorded the request. Remove any field your process does not use. For a home provider, you can use “group” in place of “room”.

Choose a response date that fits your actual process. If a non-response has consequences under that process, explain them plainly and provide a way to correct a missed message.

A response deadline needs an actual operational reason and an accurate consequence. Decide how the team handles bounced messages, changed contact details, and requests received after that date. If your process requires reminders or another contact method, include that work before marking a request inactive. Silence alone does not explain a family’s intentions.

Name what remains unconfirmed. If you already have an approved, specific offer, send the actual offer and terms rather than using a tentative message.

Give an update on the date you promised even if the condition remains unresolved. For example: “The room transition has not yet been confirmed. We cannot offer the place today. Our next update will be [date].” This keeps the family’s planning information current without manufacturing certainty.

Use this when you can discuss a different schedule under your admissions process. Make clear whether keeping the original request active is possible; do not imply that declining the alternative removes their priority unless the applicable policy actually says so.

Use one reply method and name the person or team receiving it. If you ask a family to complete a form, explain what it is for and only request the information needed for that step. Use your approved channel for sensitive information.

After sending a message, record its stage and any promised follow-up date. Before the next reply, check whether the requested schedule has changed. A shorter list with current information can be easier to use than a long list whose entries you cannot interpret.

Read the message as a parent seeing it for the first time. Could they mistake it for an offer? Would they know whether to reply? Does a deadline explain the consequence? Can a colleague tell what has already been promised?

Track clarification requests and missed follow-ups to find wording or process problems. These templates are a starting point; we have not tested or claimed an enrolment improvement from them.

Try two internal examples before using the templates: a parent replies after the update deadline, and a parent interprets a possible-opening message as a confirmed place. Can the team identify the previous promise and send a consistent answer? Repair ambiguous language and missing process decisions together; a template cannot resolve a policy nobody has agreed on.