Opening and closing checklists
Routine tasks for each classroom, ticked off in order and visible to the operations manager at a glance.
A preschool teacher app gives lead teachers, assistant teachers and the operations manager one shared list of assigned work, classroom checklists and internal updates. SIZ Group designs and builds it as a custom mobile app that works on a classroom tablet or a staff member's phone.
A preschool classroom runs on a rhythm most offices never see: circle time, snack, outdoor play, a rest period and a handoff at pickup. Each block has tasks attached, such as wiping tables, restocking the art bin, logging snack and checking the fire exit. When those tasks live on sticky notes, one busy afternoon can leave a room unready for the next morning.
The operations manager is usually responsible for the whole building, so they rely on the lead teacher's word that routines were completed. That trust is fragile when a teacher is out sick and an assistant covers the room. A shared task list with a named owner for each block turns that trust into a record.
The first release should cover the work the operations manager checks every day: opening and closing checklists, the snack and meal log and the handoff note from one teacher to the next. Those three flows cover the routines families notice and the building checks that protect the license.
Photo capture and a supply request form can wait. Both are useful, but each adds storage, privacy questions and training time. A small first release that every teacher uses on the first day beats a full one that only the director opens.
At the start of the morning, an assistant teacher opens the app on the classroom tablet and sees the opening checklist with a note from the night before. They tick off the safety items, mark the sand table as cleaned and request more paint. The operations manager sees the room marked ready on the building view.
At lunch, the teacher records what each child ate and flags one child who refused the main dish. At the afternoon handoff, the lead teacher writes a short note for the next shift, which appears at the top of the incoming assistant's list. By closing time, the closing checklist shows which tasks are done and which carry over to tomorrow.
Routine tasks for each classroom, ticked off in order and visible to the operations manager at a glance.
Quick entries by child and by day, with a flag for any refusal or allergy note the lead teacher should see.
A short note from one teacher to the next, pinned to the top of the incoming shift's list.
Fire exit, outdoor play and playground checks with a time stamp and the name of the person who completed them.
Teachers request paint, paper or cleaning supplies from the phone, and the request reaches the person who orders stock.
Many preschools run a childcare or school management system for enrollment and billing, and some keep attendance and rosters in spreadsheets. The staff app should share the child and class lists with those tools rather than build its own. We check what each vendor allows before promising a live connection, and we say clearly where a manual step remains.
Staff schedules may sit in a shift tool, a spreadsheet or a payroll provider, and the staff app only needs the day's room assignments. Email and text stay where they are. The app keeps internal notes internal, so a teacher's handoff note never ends up in a parent's inbox by mistake.
Before the build, the school should supply its room list, the daily routine for each classroom, the checklist content and the names of the people who sign off each block. Example checklists from a typical week, even handwritten ones, help us turn real habits into the first set of screens.
Access follows the role. Lead teachers manage their own room, assistants see what they are assigned and the operations manager sees the building. Anything touching a child's health or allergy record stays with the director, and the staff app shows only what a teacher needs to do the job.
The most common mistake is writing checklists nobody on the floor would write. If a teacher has to tick twelve boxes for a five-minute task, the boxes get ticked without looking. Start from the routine the classroom already follows, then trim it. Short lists that match reality get used every day.
The second mistake is expecting the app to fix a staffing shortage. It makes the gaps visible, which helps, but it cannot place a second adult in a room at nap time. Use the app to show gaps to the director early, and keep decisions about cover with the people who run the school.
Yes. Classroom tablets work well for checklists and meal logs, and each teacher signs in with their own account. The app keeps only the day's data on the device, so a shared tablet shows the right room without exposing anyone else's notes.
Unfinished tasks stay open on the list and show as carried over at closing time. The operations manager sees them on the building view the next morning, and the director can reassign them. Nothing disappears silently.
Checklists and logs keep working on the device and sync when the connection returns. Anything still waiting to sync is marked, so the operations manager knows which entries have reached the server.
Usually the school's class and enrollment list, and sometimes the scheduling tool for staff assignments. We confirm each connection during scoping. Where a link is not possible, a daily file import covers the essentials.
Teachers adopt a tool faster when it replaces a task they already dislike, such as the paper snack log. We start with one classroom, run the paper version alongside for a short overlap and ask the lead teacher to report what gets in the way.
Book a free scoping call with SIZ Group in Austin. We will walk through one classroom's routine with your team and agree the first release.