Childcare Check-In Kiosk Setup: Devices, Wi-Fi and a Front-Desk Test

A childcare check-in kiosk is ready when an authorized adult can complete the intended arrival or departure step, staff can verify the attendance record, and everyone knows what to do when the device stops working. Turning on a tablet is only the first step.

Use this guide before a new kiosk opens or an existing device moves to another entrance. It is a testing plan for your chosen system, not a promise that every device, browser or offline mode is supported.

Start with the arrival process

Write down who uses the kiosk, where staff supervise arrivals, and how the program verifies an adult's authority to collect a child. Keep the check-in record separate from that authorization decision. A name appearing on a screen does not, by itself, establish permission to pick up a child.

Choose an owner for opening checks and a backup for busy periods. Decide who will help a family that cannot use the screen. A staff-assisted option should follow the same identity and attendance process as the kiosk.

For the record itself, use the childcare attendance tracking guide. If you are changing systems, compare the handoff tasks in digital and paper attendance.

Check the device before buying accessories

Confirm the supported operating system, browser or app, minimum screen requirements and update policy with your provider. Test the exact combination you plan to use. Do not assume that an old tablet works because it can open the home page.

Place the device where families can reach and read it without blocking an exit or obscuring staff sightlines. Check glare, text size, touch targets and the route for someone who needs assistance. Secure the stand and keep power cables out of walking paths. Follow the device maker's cleaning instructions.

If you use an iPad, Apple describes Guided Access as a way to temporarily restrict the device to a single app. Test its configuration and exit procedure with the staff who manage the station. Device restrictions do not replace your software's access controls or establish kiosk compatibility.

Test Wi-Fi at the actual entrance

Run the test where the kiosk will stand, with the usual doors closed and ordinary building activity underway. Check that the device reconnects after sleep and restart. Confirm that guest-network sign-in pages or scheduled network changes will not interrupt the opening routine.

Do not deliberately interrupt an active arrival session. Schedule recovery testing outside arrival hours, using provider-approved test records. Avoid entering real attendance events just to see what happens.

Run a complete front-desk test

Use a fictional scenario in an approved test environment and record the expected result before each step:

• Open the kiosk from a restarted device. The intended screen should load without exposing staff administration pages.
• Complete an arrival. An authorized staff member should find the correct child, date and time in the attendance record.
• Complete a departure. Staff should verify that the record reflects the intended departure rather than a duplicate arrival.
• Try an incomplete submission. The user should understand whether anything was saved.
• Repeat a tap or refresh after a delay. Verify the actual result and learn the correction process; do not assume duplicate prevention.
• Finish a transaction and begin another. Check that the next family cannot see information the previous family left behind.
• Ask a staff member unfamiliar with the setup to use the written help procedure.

Mark each test pass, fail or not tested. A failed test needs an owner and a retest, not just a note that the screen looked fine afterward.

Prepare for an interruption

Write a short fallback procedure using your approved attendance process. Identify who starts it, where records are kept, how staff continue to account for children, and who reconciles records when service returns. Do not assume offline submissions will synchronize later unless the provider explicitly supports that behavior and you have tested it.

For example, if a submission appears to stall, staff should verify whether it saved before entering it again. After recovery, compare the fallback record with the system record and resolve omissions or duplicates through the authorized correction process. Keep the original event time distinct from the time a correction was entered.

Use the worksheet to make an opening decision

The example row shows a restart test with a fictional failed result. Replace it with your own test cases. Record the device, software version, network location, expected result, observed result, owner and retest date. Keep passwords and family information out of this worksheet.

Open the kiosk only after the people responsible agree that the tested workflow and fallback are ready. To see how attendance fits into the wider school day, explore Bloomily for preschools and bring your device and arrival scenario to the demonstration.

Common questions

Will any tablet work? Check the provider's supported devices and test your exact setup before purchase.

Can a kiosk replace staff supervision? No. Treat it as a record-entry tool within your arrival and departure process.

What if Wi-Fi fails? Follow the fallback you tested; reconcile records after recovery instead of assuming an offline feature exists.

Download the worksheet

Download the editable CSV worksheet. Open it in Excel, Google Sheets, or another spreadsheet application. The first data row is a fictional example; delete it before entering your own records. The file has no automatic calculations. Keep completed copies in your approved staff storage, not on a public link.