Make the program facts and next office step clear.

Explain the location and next step.

Present operator-approved ages, schedules and contact information. Distinguish a tour request, waitlist inquiry and confirmed enrollment. An acknowledgment should confirm receipt without reserving a place or implying acceptance.

Try a two-location example.

In this fictional example, a family asks about two locations and receives two acknowledgments. Staff need to see whether these are alternatives for one inquiry or separate requests before creating waitlist records.

Preserve the agreed location preferences and timing, identify the responsible office and allow staff to correct the record. Do not silently merge people based only on a matching name or automatically offer a place.

Separate initial interest from enrollment records.

The operator approves the minimum information for the first inquiry. Child health, custody, pickup permissions and supporting documents need a separately approved protected process. Leadership and qualified advisers decide consent, safeguarding, licensing and retention requirements.

Check each staff-system step.

Identify the office request record, confirmed tour in the calendar and approved enrollment state in the enrollment system. Decide which system owns each status and who follows up when a connection is unavailable.

Use fictional checks.

Try duplicates, a full tour slot, a changed location preference and a failed update. Check approved access restrictions and ensure public availability information is not presented as guaranteed enrollment. Keep tests away from real family records and messages.

Choose a maintainable first scope.

A page or routing repair may resolve the problem. A private portal or system replacement needs its own records, migration, access and support plan. Assign routine content and unresolved-request ownership.