Childcare centre software evaluation worksheet

A centre software review is easier to defend when every vendor is evaluated against the same scenarios. Use this worksheet with directors, administrators, educators, finance staff, and privacy or technology reviewers. Add requirements specific to your centre and jurisdiction before scoring a product.

Define the evaluation scale

Use a small, consistent scale for every requirement:

1. Not demonstrated.
2. Demonstrated with a workaround or important limitation.
3. Demonstrated in a clear workflow.
4. Demonstrated, documented, and aligned with an approved centre requirement.

Record evidence beside every score. A product tour statement is not the same as documentation, a tested workflow, or an approved contractual commitment.

Children, enrolment, and rooms

• Child and family records are organized around verified relationships.
• Enrolment status and effective dates are visible and reviewable.
• Room placement and changes have clear ownership.
• Waitlist or inquiry information is separated from active enrolment where appropriate.
• Exports and corrections can be completed through a documented process.

Staffing and daily operations

• Staff see the locations, rooms, and children connected to an active responsibility.
• Attendance changes are clear to the people who must act on them.
• Daily care entries use consistent, touch-friendly workflows.
• Supervisors can review records without giving every employee administrative access.
• Incident drafting, review, and acknowledgement responsibilities are explicit.

Family experience

• Families use a dedicated experience rather than the staff or management interface.
• Messages and provider-posted updates reach the appropriate relationship.
• Required forms, invoices, receipts, and acknowledgements are easy to locate.
• Essential childcare and safety communication is not hidden behind an optional family upgrade.
• Access changes promptly when a relationship or enrolment ends.

Administration and financial records

• Directors can review enrolment, room, staffing, form, and document status.
• Invoice and receipt records have clear states and correction paths.
• Payment processing availability, fees, settlement, and refunds are described accurately.
• Reports can be traced to the records and time period they summarize.
• Important administrative actions leave attributable evidence.

Privacy, security, and support

Ask the vendor to demonstrate and document:

• Tenant, location, room, assignment, and child-relationship boundaries.
• Authentication and account-recovery options.
• Trusted handling for sensitive changes.
• Support-access controls and auditability.
• Data location, subprocessors, retention, deletion, export, and incident processes.

Treat certifications, legal compliance, data residency, uptime, and security guarantees as claims requiring precise evidence and scope. Obtain qualified review for your organization rather than relying on a worksheet alone.

Onboarding and operational readiness

• The vendor provides an implementation owner and a clear responsibility map.
• Configuration can be tested with synthetic or otherwise approved information.
• Staff training reflects real roles and devices.
• Family invitations and support have a staged plan.
• Imports, reconciliation, go-live support, and rollback are documented.
• Unfinished capabilities and production-readiness conditions are identified plainly.

Complete a scenario review

Ask each vendor to demonstrate the same end-to-end scenarios:

1. Enrol a child and connect the appropriate family relationship.
2. Assign an educator to a room for a defined period.
3. Record attendance and a daily update.
4. Show what management, staff, and the connected family can each see.
5. Correct a record and review the resulting evidence.
6. End an assignment or relationship and verify that access changes.

Bring the scores, evidence, implementation effort, total cost, and unresolved risks into one decision record. A lower score may be acceptable when the limitation is explicit and manageable; an unsupported assumption should not be treated as a completed requirement.