Operations template
A board for the administrative side of running a childcare centre: opening and closing, cleaning and supplies, enrolment paperwork, notices to families, and how a concern gets routed to the centre's designated lead — each drafted, approved and then briefed to staff.
No account and no email needed. Opens in Excel or Google Sheets.
Twelve tasks across five stages, each with a completion criterion and its own checklist, plus a suggested day. The first stage is a gate on purpose: nothing is rolled out until the centre lead and a qualified reviewer have approved it, and children's information never goes on the board.
A childcare centre's admin is mostly held by one or two people who have done it for years. The routines work, but they are not written anywhere, so cover is fragile, new staff learn by imitation, and the one process that must never be improvised — what happens when someone raises a concern — is the least documented of all.
What that looks like
The person who runs the administration of a small childcare centre, rather than the people delivering care.
Group is the stage of the routine set: scope and gate, daily routines, enrolment and families, safety and concerns, approval and review. Status and priority already use the product's own fixed values, so they map without edits.
Download the CSV
It opens in Excel or Google Sheets. Edit the tasks first if you like, or import it as it is.
Create a board in TaskSiddhi
Give it a name, such as the week, the project or the client.
Open the spreadsheet import
Upload the CSV. Columns are matched automatically; map Group, Done when and Checklist to a text column or to custom fields.
Preview, then import
Check the rows before anything is written, then import.
Make it yours
Clear the gate in stage one before drafting anything else, then brief all staff on the approved version. Keep children's and families' information in your own records system.
All twelve tasks, with their completion criteria and checklists. Owner and due date are left blank on purpose.
12 tasks in 5 groups, 43 checklist items
State plainly that children's names, photographs, health or allergy details, pick-up arrangements, incident details and staff screening records are not to be typed here, and name the centre's approved, access-controlled system for them.
Done when
The rule and the approved-system reference are approved before board creation, and staff acknowledgement is recorded outside this board before staff receive access.
Checklist0 of 4 ticked
List each routine and name the role that owns it and the role that steps in when the owner is away, using role names rather than individuals wherever they are enough.
Done when
Each routine has an owner role and a back-up role, and the list has been shared with all staff.
Checklist0 of 3 ticked
Point staff to the centre's existing approved procedure and designated lead for raising any concern about a child. If there is none, leave this task open and ask the centre director to establish one. Never describe a concern here.
Done when
The centre's approved concern-raising procedure and designated lead role are referenced and known to all staff, or the task stays open until the centre director has established one; no concern details are on the board.
Checklist0 of 4 ticked
Record who does the opening walk and in what order, and link to the centre's own approved safety checklist by reference; do not write safety rules here.
Done when
The draft names the owner role and the order of the walk and links to the centre's approved safety checklist by reference, without restating safety rules. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 3 ticked
Cover cleaning and consumables only: the areas and supplies to be checked, who is responsible for each and how often, with frequencies taken from the centre's own procedures and local requirements; use recurring tasks if the app supports them.
Done when
The draft lists the areas, an owner role for each, and frequencies taken from the centre's own procedures, with recurring or dated tasks chosen according to what the app supports. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 4 ticked
Assign each part of the end-of-day closing to a role and include a final walk-through by the last person leaving. Security arrangements, codes and alarm steps belong in the restricted procedure; link only its reference.
Done when
The draft names who is responsible for each part of closing and a last-person-out check and links to a restricted procedure reference; no codes or security details are on the board. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 4 ticked
List the document types the centre requires and the role that checks each. Track individual enrolments and document status only in the centre's approved system; put no enrolment references or per-child statuses on this board.
Done when
Document types, owner roles and the approved system's procedure reference are listed, and no individual enrolment is represented on the board. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 4 ticked
Decide who approves wording, who sends notices such as closures and events, and how a notice is kept general, with no information about any individual child.
Done when
The draft names who approves and who sends notices and states that notices contain no information about any individual child. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 3 ticked
List only non-technical observations that an approved procedure already assigns to administrative staff, and route any fault through that procedure; this is not a safety inspection and servicing is not assigned here.
Done when
The draft lists only observations already assigned to administrative staff by an approved procedure, with faults reported through that procedure. It is marked draft, not for operational use, until approval and briefing.
Checklist0 of 3 ticked
Put every draft in front of the centre lead and a reviewer qualified in local licensing and safeguarding requirements. Note their approval or required changes, and hold each routine back until both have approved it.
Done when
The centre lead and a qualified reviewer have each recorded approval, or required changes have been completed and the revised draft approved, before any routine is released.
Checklist0 of 3 ticked
Once approved, note each routine's identifier, version and approval date and set its effective date. Brief all staff on the approved version, and release routines only after every briefing is complete.
Done when
Each routine has an identifier, version and approval date, its effective date follows approval, and a check against a staff record kept outside this board confirms all staff were briefed on the approved version before release.
Checklist0 of 4 ticked
Set a start and end date and the routines to test. Afterwards record whether each was usable, using staff feedback without child-related examples. If a routine fails, stop using that version and send its revision back through approval and briefing.
Done when
Pilot dates and tested routines are set beforehand; afterwards each tested routine is recorded as usable or not, justified changes have owners and due dates or a no-change reason is recorded, the next review date is set, and no child-related examples appear in comments or attachments. Any routine that failed is withdrawn, staff are referred to the centre's approved procedure, and the revision goes back through approval and briefing before re-release.
Checklist0 of 4 ticked
Open a task to see what counts as finished and its checklist. Ticks here are just to try it out and are not saved.
The same rows as a CSV. Columns in the file: Task, Group, Status, Priority, Owner, Due date, Suggested day, Done when, Checklist, Notes.
Download daycare operations (CSV)The measured demand behind this template, and what it does not prove. We publish it so the page cannot be mistaken for a forecast.
| Keyword | India | US | UK | UAE |
|---|---|---|---|---|
| daycare checklist(target) | 10 | 170 | 10 | 10 |
Mismatched, and we say so plainly. The measured query looks mostly parent-facing — people choosing or preparing for a daycare — while this template is written for the person running the centre's administration. It is published for operators who arrive here, and no traffic is expected from the term.
What we hold this page to
Thin or mismatched demand — no traffic expectation
Not checked for this template.
No. It is for the person running a centre's administration. If you are a parent comparing settings or preparing for a first day, this board will not help you — it covers staff routines, enrolment paperwork and approvals.
No. It records that a concern is routed to the centre's designated lead and that the routine was followed. What the requirements are, who the designated lead must be, and how concerns must be handled all come from your jurisdiction and your own qualified reviewer.
No. Keep children's, families' and staff records in the system your setting has approved for them. The board holds routines and whether they ran, nothing about an individual child.
Because in a childcare setting an unapproved routine briefed to staff is a real risk, not a documentation problem. The gate forces approval by the centre lead and a qualified reviewer before anything reaches the floor.
The setup task writes the routine once. The daily running of it should be a recurring or dated task, so each day's opening and closing is its own record.
See automationImport the template, assign owners and see what is overdue at a glance. Free, with no paid plan.
Not sure it fits? See who TaskSiddhi is for
