Drop-In Childcare First-Visit Checklist

- Before a first drop-in visit begins, confirm registration is complete, the requested visit fits, the pickup plan is recorded, and the receiving staff member has what they need.
- Treat registration submitted and visit booked as separate statuses, because a family can have an account without a reservation or a request nobody has confirmed.
- Assign a named role to each arrival step, from registration review to room handoff and attendance entry, so an unfinished step is not mistaken for completed work.
- Split the checklist into front-desk checks and a room handoff, and log every open question, such as an extension request, with an owner until it is resolved.
A first drop-in visit needs a clear handoff from the arriving adult to the staff member accepting the child. Before care begins, confirm that registration is complete under your center's procedures, the requested visit can be accommodated, the pickup plan is recorded, and the receiving staff member has the information needed for that visit.
A scanned registration form is one step in that process. It does not by itself confirm admission or tell the room team that a new child has arrived.
This checklist is for an established drop-in program reviewing its arrival workflow. Use your own approved admission, supervision, health, emergency-contact and authorized-pickup procedures. Requirements differ by jurisdiction and program type; ChildCare.gov links to the relevant state and territory agencies.
Send first-visit instructions before the family reaches the door
Give families one short first-visit message. It should explain where to register, how a visit is confirmed, what to bring under your policies, and where to ask a question.
Avoid treating “registration submitted” and “visit booked” as the same status. A family may have an account without a reservation. Another may have requested a time that nobody has confirmed. The same booking states help later, when a family cancels or changes a visit.
Public drop-in providers make these distinctions in different ways. For example, Giggles publishes first-visit registration and pickup procedures. Its rules belong to that program. The useful lesson is to make your own steps visible before a family arrives.
Here is original wording to adapt:
“Before your first visit, please complete [registration link] and review [center policies]. Your visit is confirmed when [your confirmation step]. Bring [your center's approved packing list]. At arrival, speak with [role or desk location] before completing check-in. We will confirm the visit and pickup arrangements with you. Questions? Contact [channel].”
Remove any instruction your program does not actually use. Do not say a booking is guaranteed when it is still awaiting review.
Assign an owner to each arrival step
A busy front desk can have several people helping one family. Assign responsibility explicitly so an unfinished step is not mistaken for someone else's completed work.
| Step | Responsible role | Evidence of completion |
|---|---|---|
| Registration review | Designated registration reviewer | Required review marked complete |
| Visit confirmation | Person authorized to accept bookings | Approved arrival and due-out time |
| Arrival check | Front desk or designated receiver | Correct child and visit selected |
| Room handoff | Receiving care staff member | Receipt of the child acknowledged |
| Attendance entry | Assigned check-in operator | Actual arrival recorded |
These are example roles. A small center may assign several to one person, provided its staffing and supervision procedures remain satisfied.
Keep the confirmation in the shared record your team uses. A verbal “you're all set” should match a recorded decision another staff member can see.
Use a two-part arrival checklist
Separate what the desk needs to verify from what the room team needs to receive. This helps prevent administrative tasks from obscuring the actual transfer of care.
At the front desk
- Locate the existing family record before creating another one
- Confirm the child and the correct date and visit
- Check registration completion against the center's own requirements
- Review current availability for the entire requested stay
- Confirm the agreed pickup time and the contact route during the visit
- Verify pickup arrangements using the center's authorized-pickup process
- Explain the charge basis and any approved additional items
- Route unresolved questions to the person authorized to decide them
Do not ask families to send payment card details through ordinary email or a shared checklist. Direct them to your approved payment service.
If a family needs help with a phone, language, or form, use the assistance route your center has prepared. An incomplete digital step should trigger help and review rather than an improvised exception.
With the receiving staff member
- Identify the child using the center's procedure
- Point the receiver to the current information they need in the restricted-access record
- Confirm the visit's due-out time and any approved arrangements
- Confirm where labeled belongings will go
- Acknowledge that the handoff has occurred
- Record actual attendance in the designated system
This is a workflow checklist, not a substitute for active supervision or the center's admission procedure. Staff should not leave children unattended to complete a form or resolve a payment question.
Keep first-visit exceptions visible until someone resolves them
Imagine a fictional arrival: Visit A is requested for 10 a.m. to noon. The family has registered, but the request is still pending. At the door, the adult asks to stay until 1 p.m.
There are two decisions to resolve: whether the original visit is approved and whether the longer stay can be accommodated. Completing registration does not answer either question. A drop-in utilization worksheet shows how to check the full requested stay against existing bookings.
Use a compact exception record:
| Field | Fictional example |
|---|---|
| Visit reference | Visit A |
| Question | Requested extension from noon to 1 p.m. |
| Owner | Booking lead |
| Current status | Awaiting review |
| Family told | Original request is not yet confirmed |
| Final decision | Record only after the authorized review |
Do not mark a pending request as confirmed to keep the line moving. Staff can give the family a clear next step without promising an outcome.
A pickup-person change needs the same discipline. Follow the existing authorization process and update the authoritative record. A note saying “different pickup today” is not authorization on its own.
Make the next visit easier without skipping the checks
Returning families should not have to recreate the same account each time. Staff still need to select the correct visit and check whether contact details, pickup arrangements or other relevant information have changed.
A useful return-visit question is: “Has anything changed that we need to know for today's visit?” The answer should be recorded through the approved process, not left in an individual staff member's memory.
Keep sensitive information in the center's access-controlled system. A public arrival poster can explain the steps, but should never display a child's record or a list of family contact details.
Rehearse the first-visit workflow with fictional visits
Before changing your arrival process, walk through three examples with staff:
- A new family with completed registration and a confirmed visit
- A new family with a pending request and an unanswered question
- A returning family asking to change today's pickup arrangements
For each, ask who accepts the child, who resolves the open question, and what the next staff member will see. A useful rehearsal exposes unclear ownership without involving a real family's information.
Review recurring questions after the first week of using the checklist. Improve the instructions where people repeatedly need help. Do not remove an important review step merely because it takes time.
Try the first-visit arrival workflow in Bloomily
Explore Bloomily for drop-in centers, with QR registration at the door, kiosk check-in, and arrival and due-out information. Walk through a fictional first visit in a demo and check how staff distinguish a registered family, a pending request and a child actually checked in.