Childcare software in Australia: what a centre group can build beside registered CCS software

Why can’t a childcare group just build its own CCS system?

Because Child Care Subsidy is transacted through registered software, and the registration, testing and warranty sit with the vendor. The Department of Education’s register says providers can use third party software to access the Child Care Subsidy System (CCSS), and that each listed vendor has warranted its product has been tested for use with the CCSS and the Inclusion Support Management System. A product that wants to transact has to go through Services Australia’s software provider process first.

For a centre group, that settles the build or buy question for the core: enrolment notices, session reports, absences and subsidy payments stay in the registered product. Writing your own would mean taking on registration, ongoing government interface changes and the liability the department explicitly declines to carry. The useful question is what the registered product does badly for your group, and whether a narrow build fixes it.

At the time of writing (November 2026), the department’s list includes these products, among others:

Product (as listed)	Service types listed	Question to ask for a group
Xplor	Centre based day care, OSHC	What enrolment and room data its API exposes
QikKids	Centre based day care, OSHC	Whether data is reachable outside the product
OWNA CCS	Centre based day care, OSHC	How family app data links to enrolments
HubWorks!	Centre based day care, OSHC, FDC, IHC, Registered Care	Whether you need its family day care and in home care coverage
XAP	Centre based day care, OSHC	How it shares data with Storypark, which now markets Storypark + Xap
Kidsoft, Kangarootime, Harmony Web, Fully Booked, smartcentral	Varies by product	Whether every service type you run is listed

The department says listing is not an endorsement. Before a group signs, check the current list, the vendor’s API or export options, and whether it supports every service type you run. Our build vs buy guide sets out the wider test.

The CRM gap between an enquiry and an enrolment

Most registered systems are strong once a child is enrolled and weak before that. Enquiries arrive from the website, phone calls, childcare directories and walk ins. Tours are booked in a calendar, waitlists live in a spreadsheet per centre, and offers go out by email. For a single centre that is manageable. For a group of ten centres it means nobody can answer simple questions: how many families are waiting for a Tuesday nursery place in one suburb, which centre converts tours best, and how long a family waits for an offer.

A custom enrolment CRM usually covers:

1. One enquiry inbox across centres, with source tracking so marketing spend can be judged.
2. Tour booking tied to each centre director’s availability, with reminders.
3. Waitlists by room, day and start date, ranked by rules the group sets (siblings, staff children, priority of access).
4. Offers and acceptances with deadlines, and automatic movement down the list when an offer lapses.
5. Handover to the registered system when a family accepts, through the vendor’s API where one exists, or a structured export where it does not.

The handover is the part to confirm early. If the CCS product exposes enrolment and room data, the CRM can show live vacancies. If it does not, vacancies are updated on a schedule. That is the CRM integration work we would scope first.

The 3 Day Guarantee affects this layer. Since 5 January 2026 every CCS eligible family gets at least 72 hours of subsidised care a fortnight, and 100 hours in some situations, such as caring for an Aboriginal or Torres Strait Islander child or more than 48 hours of recognised participation. Families who previously booked two days because of the activity test may now ask for three. A CRM that records requested days against offered days shows the group where demand has moved.

Ratios and rosters: what a roster tool has to know

Ratios under the National Quality Framework are calculated across the whole centre, not room by room, and some of them differ by state. ACECQA’s ratio page sets 1:4 for birth to 24 months everywhere, 1:5 for over 24 months to under 36 months (1:4 in Victoria), and between 1:10 and 1:11 for 36 months to preschool age depending on the state. Educators count only when they are working directly with children.

That makes a group roster harder than a café roster. A useful custom roster or forecasting tool:

• Reads expected attendance by age band from the CCS system’s bookings.
• Applies the right state ratios and early childhood teacher requirements for each centre.
• Flags gaps before the day, not during it.
• Costs the roster under the Children’s Services Award (MA000120), which covers long day care, family day care, OSHC, kindergartens and other children’s services.

Plenty of groups already run rostering in a workforce product, and if it handles ratios well, keep it. Custom work makes sense when the roster has to combine bookings, ratios and award costs in one view that no single product provides.

The child safety reforms, as a software problem

The 2025 and 2026 reforms turned several safety duties into things a service must be able to evidence, and evidence lives in systems. ACECQA’s summary lists changes already made: policies for safe use of digital technologies and online environments from 1 September 2025, earlier notification of physical and sexual abuse, and a strengthened child safety focus in Quality Areas 2 and 7 from 1 January 2026. From 27 February 2026, new National Law requirements set out that children’s safety, rights and best interests are the paramount consideration in every decision, and add rules on devices.

Requirement	What a system can do	Owner of the decision
Images of children taken only on service supplied devices in centre based care	Device register, image storage with access logs, retention rules	Approved provider
Personal devices not in possession while working directly with children, with limited exceptions	Exception log for excursions, transport, emergencies and authorised purposes	Nominated supervisor
Mandatory national child safety training in Geccko	Training matrix by role, due dates, reminders	Approved provider
Earlier notification of abuse allegations	Incident workflow with timers and escalation	Approved provider and regulator

The training rules are specific. The department says foundation training is mandatory for everyone working or volunteering in a regulated service, with a deadline of 27 August 2026 for existing staff; people in relevant roles before 30 September 2026 must complete advanced training by 31 March 2027; and refresher training is due every 2 years. A group of several hundred staff and volunteers needs a matrix that knows each person’s role and dates. Geccko delivers the courses; your system tracks who has done what.

CCTV is not settled. Education Ministers commissioned a national assessment in August 2025, over 300 services took part, and Ministers are due to consider findings in November 2026. We would not build CCTV storage until the guidelines land, and when they do, privacy and retention design will matter as much as the cameras.

Family communication: keep the vendor app or build your own?

Keep the vendor’s family app unless your group has a reason it cannot meet. Storypark (now marketed with XAP) and the family apps that come with products such as Xplor and OWNA already handle learning stories, daily updates and messages. Educators know them and families have them installed.

Reasons a group might build anyway:

• Centres run different CCS products after acquisitions, and families of siblings at two centres get two apps.
• The group wants enquiry, tour, enrolment and first day onboarding in one journey before a child is even enrolled.
• The group’s brand and parent community features matter enough to fund an app and its upkeep.

If you do build, the web and mobile apps work is the easy part. The harder part is image handling that respects the device and retention rules above, and parental consent that is recorded, specific and easy to withdraw.

What do these builds cost?

Indicative market ranges for childcare builds run from about $25,000 for a group dashboard to $150,000 for a branded family app (AUD, ex GST). Conduct’s cost guide puts mid sized Australian agencies at roughly $150 to $330 an hour, which is the arithmetic behind these planning figures.

Build	Indicative range (AUD, ex GST)	Main cost drivers
Group reporting dashboard (occupancy, waitlist, roster cost, training status)	$25k to $70k	Number of centres and source systems, data quality
Enrolment and waitlist CRM integrated with registered CCS software	$30k to $90k	Vendor API access, priority rules, number of centres
Branded family app across centres	$60k to $150k	Number of CCS products, image handling, consent design

These are ranges for planning, not quotes. Hosting, vendor API fees and maintenance sit on top. Reporting work is described on our data analytics service page.

How AWLabs would approach a childcare project

We start with a 15 minute Development Consult to understand your centres and the systems you already run. If custom work looks justified, the Discovery Audit maps your registered CCS product’s integration options, your waitlist rules and the evidence your approved provider needs, and the fee is credited in full against the build. You then get a fixed price Schedule of Work with three options: The Minimum, The Recommended and The Complete. Senior engineers lead every build, with updates every Tuesday and Friday, and code and IP are assigned to you as they are paid for.

To be plain about it: we have not yet delivered a project for a childcare provider, we are not a registered CCS software vendor, and nothing we build claims subsidy. Your approved provider and nominated supervisors own the regulatory decisions; we build the tools that help them evidence those decisions. The education page and our education and RTO software page cover adjacent work.