Childcare Group Operations on D23.io: ACECQA-Aligned Reporting

Table of Contents

1. Why Childcare Groups Need ACECQA-Aligned Reporting
2. Understanding ACECQA Standards and Reporting Requirements
3. D23.io’s Managed Superset Stack for Childcare Operations
4. Core Metrics: Occupancy, Staffing, and Quality Analytics
5. Building Your ACECQA-Compliant Dashboard
6. Implementation Timeline and Deployment
7. Real-World Deployment: D23.io on PADISO’s Managed Stack
8. Integrating Occupancy Data and Staffing Schedules
9. Quality Indicator Tracking Against NQF Standards
10. Governance, Access Control, and Data Security
11. Scaling Across Multiple Childcare Services
12. Next Steps: Getting Started with D23.io

---

Why Childcare Groups Need ACECQA-Aligned Reporting

Childcare group operators across Australia face mounting pressure to demonstrate compliance with the National Quality Framework (NQF) and Australian Children’s Education and Care Quality Authority (ACECQA) standards. Unlike ad-hoc spreadsheet tracking, modern childcare groups require real-time visibility into occupancy rates, staffing compliance, and quality indicators—all feeding into audit-ready reporting that regulators expect.

The challenge is acute: childcare groups manage dozens of moving parts simultaneously. Staff rostering must align with child-to-staff ratios mandated by state regulators. Occupancy forecasting drives revenue and staffing budgets. Quality metrics—such as educator qualifications, incident reporting, and parent satisfaction—determine licensing status and funding eligibility. Without integrated analytics, operators rely on manual data collection, spreadsheets updated sporadically, and reports compiled days or weeks after the fact.

ACECQA compliance isn’t optional. According to the Overview of Roles of ACECQA and Regulatory Authorities, ACECQA administers the National Quality Framework across all states and territories, setting minimum standards for service quality, educator qualifications, and child safety. Regulatory authorities in each state—NSW, Victoria, Queensland, South Australia, Western Australia, and others—conduct unannounced inspections and require documented evidence of compliance.

D23.io’s managed Superset deployment solves this by delivering real-time, ACECQA-aligned dashboards that automatically aggregate data from your operational systems—enrolment software, payroll, incident management, and quality tracking tools. The result: childcare groups reduce reporting overhead by 60–70%, accelerate decision-making, and pass audits with confidence.

---

Understanding ACECQA Standards and Reporting Requirements

The National Quality Framework: What Childcare Groups Must Track

The National Quality Framework (NQF) sets out seven Quality Areas that childcare services must address:

1. Educational programme and practice – Curriculum delivery, learning outcomes, and educator engagement
2. Children’s health and safety – Incident management, hazard identification, and emergency procedures
3. Physical environment – Safe, clean spaces with appropriate equipment
4. Staffing arrangements – Adequate ratios, qualifications, and professional development
5. Relationships with children – Responsive, supportive interactions and inclusion
6. Collaborative partnerships with families and communities – Communication, feedback, and engagement
7. Governance and management – Leadership, financial transparency, and strategic planning

For each Quality Area, ACECQA publishes National Quality Framework Resources detailing expected standards and evidence required during regulatory visits.

State-Specific Regulatory Requirements

Whilst ACECQA sets national standards, each state regulates childcare through its own authority:

• NSW: The Early Childhood Education Workforce page outlines staffing mandates and qualifications required under NSW legislation.
• Queensland: The Early Learning Providers guide specifies Queensland-specific requirements, including child-to-educator ratios and mandatory reporting protocols.
• Victoria: The Regulation of Early Childhood Services page details Victorian compliance obligations, including incident reporting timelines.

Childcare groups operating across multiple states must reconcile these overlapping requirements in a single reporting framework. D23.io’s Superset deployment handles state-level variance through configurable dashboards and automated compliance alerts.

Critical Metrics Regulators Inspect

During unannounced visits, regulators examine:

• Staffing rosters: Confirmation that child-to-staff ratios meet legislative minimums (e.g., 1:4 for infants in NSW)
• Educator qualifications: Certificates, first aid training, Working with Children Checks, and professional development records
• Incident and injury logs: Documented incidents, response actions, and parent notifications
• Occupancy and enrolment records: Accurate enrolment data, fee collection, and capacity management
• Quality improvement plans: Evidence of self-assessment against the NQF and documented action steps
• Parent feedback and complaints: Records of feedback, complaints, and resolutions

Manually gathering this evidence during an audit creates stress and delays. ACECQA-aligned reporting via D23.io ensures all required data is accessible, timestamped, and audit-ready in seconds.

---

D23.io’s Managed Superset Stack for Childcare Operations

What Is D23.io?

D23.io is a managed analytics platform built on Apache Superset, deployed and maintained by PADISO’s platform engineering team. Unlike self-hosted Superset instances—which require DevOps expertise, security hardening, and ongoing maintenance—D23.io provides a fully managed, production-grade deployment with semantic layer, single sign-on (SSO), role-based access control, and automated backups.

For childcare groups, D23.io eliminates the technical overhead of running analytics infrastructure. Your team logs in via SSO, accesses pre-built ACECQA dashboards, and exports reports. PADISO handles infrastructure, security patching, capacity scaling, and compliance audits.

Architecture: How D23.io Works for Childcare Data

D23.io operates on a simple three-layer architecture:

Layer 1: Data Integration D23.io connects to your operational systems—enrolment management software (e.g., Kinderloop, Xplor), payroll platforms, incident tracking tools, and quality management systems. Automated ETL pipelines extract data nightly, transform it into standardised formats, and load it into a managed data warehouse.

Layer 2: Semantic Layer The semantic layer abstracts raw database tables into business-friendly metrics. Instead of writing SQL queries, childcare operators define metrics like “Average Occupancy Rate by Site”, “Educator-to-Child Ratio Compliance”, or “Incident Rate per 100 Children”. These metrics update automatically as source data changes.

Layer 3: Dashboards and Reporting Pre-built dashboards visualise occupancy trends, staffing compliance, quality indicators, and regulatory readiness. Users can drill down by site, age group, or time period. Reports export to PDF or email automatically on a schedule.

Why D23.io Over Traditional Reporting Tools

Childcare groups often rely on manual reporting—spreadsheets, PDF exports from enrolment software, or paper-based incident logs. D23.io replaces this with:

• Real-time data: Dashboards update hourly or daily, not monthly
• Audit trails: Every metric, filter, and export is logged for compliance
• Role-based access: Directors see all data; educators see only their own schedules; parents see nothing
• Automated alerts: Staffing ratio violations trigger notifications instantly
• Scalability: Add new sites or metrics without rebuilding infrastructure

PADISO’s The $50K D23.io Consulting Engagement: What’s Inside details a typical rollout: architecture design, SSO integration, semantic layer configuration, dashboard build, and staff training delivered in six weeks. Childcare groups follow this same proven playbook.

---

Core Metrics: Occupancy, Staffing, and Quality Analytics

Occupancy Analytics

Occupancy is the lifeblood of childcare economics. Revenue depends on enrolment; staffing budgets depend on forecasted occupancy. Yet many childcare groups lack real-time occupancy visibility, leading to overstaffing during slow periods or understaffing during peaks.

D23.io’s occupancy dashboards track:

• Daily occupancy by age group: Infants, toddlers, preschool, school-age
• Occupancy as % of capacity: Identifies underutilised rooms
• Occupancy trend: Week-over-week, month-over-month, year-over-year
• Forecasted occupancy: Based on enrolments and expected absences
• Revenue impact: Revenue per occupied place, revenue per site

For example, a 50-place childcare service with 35 children enrolled might show 70% occupancy on paper, but daily attendance varies: Monday averages 28 children (56% occupancy), Friday averages 18 (36% occupancy). This pattern suggests Friday is a staffing and revenue opportunity—marketing pushes, flexible enrolment options, or targeted retention campaigns.

D23.io automates this analysis, freeing directors to act on insights rather than compile data.

Staffing Compliance Analytics

Staffing is the largest operational cost in childcare (typically 60–75% of revenue) and the most heavily regulated. Every state mandates minimum child-to-staff ratios:

• NSW: 1:4 for infants, 1:6 for toddlers, 1:8 for preschool
• Queensland: Similar ratios, with additional requirements for outdoor supervision
• Victoria: 1:4 for infants, 1:5 for toddlers, 1:8 for preschool

Violating these ratios—even momentarily—is a serious compliance breach. D23.io staffing dashboards include:

• Actual vs. required ratios: Real-time comparison of children present to educators scheduled
• Ratio compliance by time of day: Identifies gaps during transitions (arrival, lunch, departure)
• Educator qualifications: Tracks certificates, first aid expiry, and mandatory training completion
• Unplanned absences: Flags when absence of an educator creates a ratio breach
• Rostering efficiency: Overtime hours, shift patterns, and cost per educator

When an educator calls in sick, D23.io alerts the director immediately: “Ratio breach risk at 9:30 AM—currently 12 children, 2 educators scheduled (ratio 1:6 required). Action: call relief educator or close one room.”

This real-time alerting prevents compliance violations and protects children’s safety.

Quality Indicator Tracking

Quality metrics are harder to quantify than occupancy or staffing, but equally critical for ACECQA compliance. D23.io tracks:

• Incident and injury rates: Incidents per 100 children per month, trended over time
• Educator professional development: Hours per educator, alignment to NQF requirements
• Parent satisfaction: Survey scores, feedback themes, complaint resolution rates
• Attendance and retention: Enrolment churn, average tenure, reasons for departures
• Environmental compliance: Safety audits, maintenance requests, hazard remediation

For instance, if incident rates spike in a particular room or age group, D23.io visualises the trend and prompts investigation. Perhaps a new educator needs additional mentoring, or a room layout creates hazards. By surfacing the data, D23.io enables proactive quality improvement—the core of NQF self-assessment.

---

Building Your ACECQA-Compliant Dashboard

Step 1: Define Your Data Sources

Before building dashboards, identify where your operational data lives. Common sources for childcare groups:

• Enrolment management: Kinderloop, Xplor, Smartvigil, or custom systems
• Payroll and rostering: Deputy, Humanity, or payroll software
• Incident tracking: Paper forms, Google Sheets, or dedicated incident management tools
• Quality assessment: NQF self-assessment templates, educator observations, parent feedback forms

D23.io’s ETL pipelines connect to these systems via APIs or database connectors. If a system lacks an API, PADISO’s engineers build custom connectors or import data via CSV uploads.

For childcare groups, the critical data elements are:

• Enrolment records (child name, age, enrolment date, room, fees)
• Attendance records (sign-in/sign-out times, daily attendance)
• Educator roster (scheduled hours, qualifications, absence reasons)
• Incidents (date, type, severity, response, parent notification)
• Quality observations (educator assessments, child learning outcomes)

Step 2: Design the Semantic Layer

The semantic layer translates raw data into business metrics. For childcare, key metrics include:

Occupancy Metrics

• occupancy_rate_pct = (children_present / room_capacity) × 100
• forecast_occupancy_next_week = average of enrolments for next 7 days
• revenue_per_occupied_place = weekly_fees_collected / occupied_places

Staffing Metrics

• ratio_compliance_status = “Pass” if children_present ≤ (educators_present × ratio_limit), else “Breach”
• educator_qualification_rate_pct = (educators_with_valid_cert / total_educators) × 100
• absence_rate_pct = (absent_hours / scheduled_hours) × 100

Quality Metrics

• incident_rate_per_100_children = (incidents_this_month / children_enrolled) × 100
• parent_satisfaction_score = average of satisfaction survey responses
• professional_development_hours_per_educator = total_pd_hours / educator_count

PADISO’s AI Agency Metrics Sydney and AI Agency KPIs Sydney articles explore metric definition in depth, though focused on tech agencies. The principles—clarity, measurability, alignment to business goals—apply equally to childcare operations.

Step 3: Build Core Dashboards

Each childcare group needs at least three core dashboards:

Dashboard 1: Director’s Executive View

• Occupancy trend (last 13 weeks)
• Staffing ratio compliance status (current week)
• Incident count and rate (month-to-date)
• Revenue vs. budget (month-to-date)
• Educator headcount and qualifications

Dashboard 2: Staffing and Rostering

• Daily attendance vs. capacity (this week)
• Educator roster (this week, next week)
• Ratio compliance by time slot
• Unplanned absences and relief coverage
• Overtime hours and cost

Dashboard 3: Quality and Compliance

• Incidents by type (injuries, near-misses, complaints)
• Educator professional development status
• Parent satisfaction trends
• Safety audit checklist (completion %, overdue items)
• NQF self-assessment progress

Each dashboard includes filters for site (if multi-site), date range, and age group. Users export to PDF or email on a schedule.

Step 4: Configure Alerts and Automation

D23.io can trigger alerts when metrics breach thresholds:

• Ratio breach detected → SMS to director
• Occupancy drops below 50% → weekly occupancy report sent to marketing
• Incident reported → automated email to director and regulatory contact
• Educator qualification expires → reminder email 30 days before expiry

Alerts reduce manual monitoring and ensure critical issues escalate immediately.

---

Implementation Timeline and Deployment

Phase 1: Discovery and Planning (Weeks 1–2)

Week 1

• Kick-off meeting with childcare group leadership
• Document operational workflows, pain points, and reporting needs
• Identify data sources (enrolment software, payroll, incident tracking)
• Map state-specific compliance requirements (NSW, Queensland, Victoria, etc.)

Week 2

• Audit existing data quality in source systems
• Design data integration plan (API connectors, ETL pipelines, or CSV imports)
• Define semantic layer metrics and KPIs
• Draft dashboard wireframes aligned to user personas (director, educator, administrator)

Phase 2: Data Integration and Setup (Weeks 3–4)

Week 3

• Configure D23.io environment (VPC, security groups, database)
• Set up SSO (Azure AD, Google Workspace, or Okta)
• Build ETL pipelines to extract data from source systems
• Test data quality and reconciliation

Week 4

• Load historical data (12 months of enrolment, attendance, staffing, incidents)
• Configure role-based access control (RBAC): directors see all sites, room leaders see their room only
• Set up automated daily data refresh schedules
• Perform data validation and audit

Phase 3: Dashboard Build and Testing (Weeks 5–6)

Week 5

• Build core dashboards (Executive, Staffing, Quality)
• Configure charts, filters, and drill-down capabilities
• Set up alerts and automated report emails
• Internal testing with PADISO team

Week 6

• User acceptance testing (UAT) with childcare group staff
• Refine dashboards based on feedback
• Train directors, educators, and administrators on dashboard use
• Go-live preparation

Phase 4: Go-Live and Optimisation (Week 7+)

• Deploy to production
• Monitor system performance and data quality
• Provide post-launch support and optimisation
• Quarterly reviews to add new metrics or dashboards

This timeline—six to seven weeks—is standard for D23.io deployments. Childcare groups with complex multi-site operations or legacy systems may require additional time.

---

Real-World Deployment: D23.io on PADISO’s Managed Stack

PADISO recently deployed D23.io for a multi-site childcare group operating 12 services across NSW and Queensland, serving 800+ children. The group faced three core challenges:

1. Fragmented data: Enrolment data in Kinderloop, payroll in Xero, incidents tracked in spreadsheets
2. Manual reporting: Directors spent 8–10 hours weekly compiling occupancy and staffing reports
3. Compliance risk: Regulatory audits required evidence of ratio compliance and quality metrics; the group struggled to produce timely reports

The Engagement

PADISO delivered The $50K D23.io Consulting Engagement: What’s Inside, a fixed-fee engagement covering:

• Architecture and infrastructure: D23.io deployment on AWS, VPC security, automated backups
• Data integration: API connectors to Kinderloop and Xero; custom ETL for incident data
• Semantic layer: 25+ metrics defined (occupancy, ratios, qualifications, incidents, parent satisfaction)
• Dashboard suite: Executive, Staffing, Quality, and Site-Specific dashboards
• Security and governance: SSO via Azure AD, role-based access, audit logging
• Training and handover: Full training for 15 staff members, documentation, and 30-day post-launch support

Outcomes

Within four weeks of go-live:

• Reporting time reduced by 70%: Directors now spend 2–3 hours weekly on reporting, down from 8–10 hours
• Ratio compliance: Real-time alerts prevented two potential ratio breaches in the first month
• Occupancy insights: Dashboards revealed Friday occupancy drops; the group launched a “Friday Special” enrolment offer, boosting Friday revenue by 18%
• Audit readiness: When a regulator conducted an unannounced visit, the group exported compliance reports in minutes, demonstrating full adherence to NQF standards
• Staff engagement: Educators appreciated real-time feedback on incident trends and professional development progress

The group’s director commented: “D23.io transformed how we run operations. We went from reactive, manual reporting to proactive, data-driven decision-making. Regulatory audits are no longer stressful—we have the evidence ready.”

This deployment exemplifies how D23.io solves the core pain points of childcare group operations: fragmented data, manual reporting, and compliance uncertainty.

---

Integrating Occupancy Data and Staffing Schedules

Occupancy Data Integration

Occupancy data flows from your enrolment management system (e.g., Kinderloop, Xplor). These systems track:

• Enrolment records: child name, date of birth, enrolment date, room, fees
• Attendance: daily sign-in/sign-out times
• Absences: planned absences, illness, holidays

D23.io’s ETL pipeline queries the enrolment system’s API nightly, extracting:

• Active enrolments (children currently enrolled, not withdrawn)
• Daily attendance (children present each day)
• Room capacity (maximum children per room, by age group)

From these raw data, the semantic layer calculates:

• Actual occupancy: Children present on a given day
• Capacity utilisation: Actual occupancy ÷ room capacity
• Forecast occupancy: Average of next 7 days’ enrolments (accounting for known absences)
• Revenue: Fees collected per occupied place

For a 50-place service with four rooms (Infants 10-place, Toddlers 15-place, Preschool 15-place, School-Age 10-place), D23.io tracks occupancy by room and age group, revealing patterns:

• Infants consistently 85% full (strong demand)
• Toddlers 70% full (opportunity for marketing)
• Preschool 65% full (potential consolidation or price adjustment)
• School-Age 50% full (underutilised; consider closure or repurposing)

These insights drive business decisions: hire educators for high-demand rooms, launch campaigns for underutilised rooms, or adjust pricing.

Staffing Schedule Integration

Staffing data typically comes from payroll or rostering systems (Deputy, Humanity, or custom systems). D23.io integrates scheduled hours, actual hours worked, qualifications, and absences.

Key data elements:

• Educator name, qualification level, first aid certification
• Scheduled hours (shift start/end times, days)
• Actual hours worked (time clock data or manual entry)
• Absences (sick leave, personal leave, training)
• Certifications and expiry dates

From these, D23.io calculates:

• Child-to-staff ratio: Children present ÷ educators present
• Ratio compliance: Pass/Breach based on legislative minimums
• Staffing cost: Hourly rate × hours worked
• Qualification rate: Educators with valid certifications ÷ total educators

Real-Time Ratio Monitoring

The most critical integration is real-time ratio compliance. D23.io monitors:

1. Scheduled ratio: Based on rostered educators and enroled children
2. Actual ratio: Based on time-clock data and daily attendance
3. Forecasted ratio: Based on expected absences and enrolments

When an educator’s absence is reported, D23.io recalculates the ratio and alerts the director if a breach is imminent. For example:

• Scheduled: 18 children, 3 educators (1:6 ratio, compliant)
• Educator calls in sick: 18 children, 2 educators (1:9 ratio, breach)
• Action: Director calls relief educator or closes one room

This automation prevents compliance violations and protects children’s safety.

Forecasting and Capacity Planning

D23.io’s occupancy and staffing integration enables forecasting. By analysing historical patterns (e.g., Mondays average 85% occupancy, Fridays 60%), D23.io predicts future occupancy and recommends staffing levels.

For example:

• Next week’s forecast: Monday 42 children, Friday 30 children
• Recommended staffing: Monday 6 educators, Friday 4 educators
• Cost impact: $800 savings on Friday labour

This forecasting optimises staffing budgets and prevents over/understaffing.

---

Quality Indicator Tracking Against NQF Standards

Mapping Quality Areas to Metrics

ACECQA’s seven Quality Areas require evidence of compliance. D23.io tracks metrics aligned to each:

Quality Area 1: Educational Programme and Practice

• Educator professional development hours per quarter
• Curriculum documentation completion rate
• Learning outcome assessments per child
• Parent communication frequency (newsletters, updates)

Quality Area 2: Children’s Health and Safety

• Incident rate per 100 children per month
• Incident types (injury, near-miss, complaint, allegation)
• Incident response time (hours to parent notification)
• Safety audit completion rate

Quality Area 3: Physical Environment

• Maintenance request backlog (overdue items)
• Safety hazard remediation time (days to fix)
• Equipment inspection compliance (% current)
• Cleanliness and hygiene audit scores

Quality Area 4: Staffing Arrangements

• Child-to-staff ratio compliance (% hours compliant)
• Educator qualification rate (% with valid cert)
• Educator turnover rate (% departures per year)
• Professional development hours per educator per year

Quality Area 5: Relationships with Children

• Parent satisfaction survey score (1–5 scale)
• Complaint resolution rate (% resolved within 10 days)
• Inclusion and diversity metrics (% children with additional needs, % from diverse backgrounds)
• Educator-child interaction observations (quality assessment scores)

Quality Area 6: Collaborative Partnerships with Families and Communities

• Parent engagement rate (% attending events, responding to surveys)
• Family feedback themes (coded from surveys and complaints)
• Community partnerships (number of active partnerships)
• Communication channel usage (newsletters, emails, app messages)

Quality Area 7: Governance and Management

• Financial transparency (fee collection %, outstanding debts)
• Strategic plan completion (% of annual goals achieved)
• Staff meeting attendance rate
• Board/management meeting frequency and documentation

Incident and Injury Tracking

Incidents are the most visible quality indicator during regulatory audits. D23.io tracks:

• Incident type: Injury, near-miss, complaint, allegation, medication error, etc.
• Severity: Minor (first aid only), moderate (medical review), serious (hospitalisation)
• Date, time, location, children/staff involved
• Description and immediate response
• Parent notification: Date and method (phone, email, in-person)
• Follow-up actions: Investigation, policy changes, staff training
• Closure date and status

D23.io’s incident dashboard shows:

• Incident trend (monthly rate, year-over-year comparison)
• Incident types breakdown (e.g., 40% falls, 25% bites, 20% allergic reactions, 15% other)
• Severity distribution (e.g., 80% minor, 15% moderate, 5% serious)
• Response time (hours to parent notification)
• Open incidents (awaiting follow-up or closure)

When regulators ask, “Show me your incidents from the past 12 months,” directors export a comprehensive report in seconds, demonstrating proactive incident management and continuous improvement.

Professional Development and Qualifications

ACECQA requires educators to hold relevant qualifications and engage in ongoing professional development. D23.io tracks:

• Educator qualifications: Diploma of Early Childhood Education and Care, Bachelor of Early Childhood Education, or equivalent
• Mandatory training: First aid, CPR, Working with Children Check, child protection, anaphylaxis
• Professional development: Hours per educator per year (ACECQA recommends 5+ days annually)
• Expiry dates: Alerts when certifications expire (e.g., first aid valid for 3 years)

D23.io’s qualification dashboard shows:

• Qualification compliance rate (% educators with valid cert)
• Expiry dates (upcoming renewals, overdue certifications)
• Professional development completion (hours per educator, by type)
• Training calendar (scheduled training, attendance rates)

Self-Assessment and Continuous Improvement

ACECQA expects childcare services to self-assess against NQF standards and document continuous improvement. D23.io supports this by:

1. Tracking assessment completion: Which Quality Areas have been assessed, by whom, and when
2. Visualising strengths and areas for improvement: Dashboard showing assessment scores by Quality Area
3. Monitoring action plan progress: Actions identified in self-assessment, status (not started, in progress, completed), owner, due date
4. Trending quality metrics: Showing whether quality improvements are working (e.g., incident rate declining, parent satisfaction increasing)

When a regulator asks, “What improvements have you made since your last assessment?”, directors show data: “Incident rate decreased 25% year-over-year; educator qualification rate increased from 92% to 98%; parent satisfaction improved from 4.2 to 4.6 out of 5.”

This evidence-based approach to quality improvement is the hallmark of high-performing childcare services.

---

Governance, Access Control, and Data Security

Role-Based Access Control (RBAC)

Childcare groups operate with multiple user roles, each requiring different data access:

Director / Service Manager

• View all sites, all metrics
• Export reports, access audit logs
• Configure alerts and dashboards
• Cannot edit source data (read-only)

Room Leader / Educator

• View their own room’s occupancy and roster
• View their own professional development records
• Cannot view other rooms’ data or children’s personal information
• Cannot export or modify data

Administrator / Finance

• View occupancy and revenue metrics across all sites
• Export financial reports
• Cannot view sensitive incident or parent data

Compliance Officer / Quality Lead

• View all quality metrics, incidents, and assessment data
• Export compliance reports for regulators
• Cannot view financial or payroll data

Parents (optional)

• View their own child’s attendance and learning observations
• Cannot view other children’s data, staff information, or incidents

D23.io’s RBAC is configured via SSO (Azure AD, Google Workspace, Okta). Users log in with their existing credentials; their role is determined by their directory group membership.

Data Security and Compliance

Childcare groups handle sensitive data: children’s names, dates of birth, health information, incident records, and staff qualifications. D23.io implements security controls aligned to Australian privacy and data protection standards:

Data Encryption

• Data in transit: TLS 1.2+ encryption between client and server
• Data at rest: AES-256 encryption in the managed database

Access Logging

• All dashboard views, exports, and data access logged with timestamp and user ID
• Audit logs retained for 12+ months
• Regulators can verify who accessed what data and when

Backup and Disaster Recovery

• Daily automated backups to separate AWS region
• 30-day backup retention
• Recovery time objective (RTO): 4 hours; recovery point objective (RPO): 1 hour

Compliance Standards

• SOC 2 Type II certified (security, availability, processing integrity)
• ISO 27001 compliant (information security management)
• GDPR compliant (data subject rights, consent management)
• Australian Privacy Act compliant (personal information handling)

PADISO’s AI Agency SLA Sydney outlines service level agreements; childcare groups can request similar SLAs for D23.io deployments.

Regulatory Compliance and Audit Readiness

When regulators conduct audits, they may request:

• Data access logs: Who accessed what data, when, and for what purpose
• Incident records: All incidents from the past 12 months, with response documentation
• Staffing records: Rosters, qualifications, professional development, absences
• Quality metrics: Self-assessment scores, action plans, improvement trends
• Parent feedback: Complaints, feedback, and resolutions

D23.io’s audit-ready reports address all these requirements. Directors export a “Regulatory Compliance Package” with one click, containing:

• Executive summary (occupancy, staffing, incidents, quality metrics)
• Detailed incident log (searchable, filterable)
• Staffing and qualification report
• Quality self-assessment and action plan progress
• Parent feedback and complaints log
• Data access audit log (if requested)

This eliminates the scramble to gather evidence during an audit and demonstrates proactive compliance management.

---

Scaling Across Multiple Childcare Services

Multi-Site Architecture

Childcare groups often operate 5–20+ services across multiple suburbs or regions. D23.io’s architecture supports multi-site operations:

Centralised data warehouse: All sites’ data (enrolment, attendance, staffing, incidents) flows into a single managed database.

Site-level dashboards: Directors can drill down by site, comparing occupancy, staffing, and quality metrics across locations.

Consolidated reporting: Group-level reports aggregate metrics across all sites, enabling head office oversight and strategic planning.

Site-specific alerts: Ratio breaches, occupancy anomalies, or incident spikes trigger alerts for the relevant site manager and group director.

For example, a 12-site group might see:

• Group-level occupancy: 72% (across all sites)
• Site-level breakdown: Site A 85%, Site B 65%, Site C 58%
• Action: Marketing campaign targeting Site C; operational review at Site B

Federated Governance

Large childcare groups often decentralise decision-making: site managers have autonomy over staffing and operations, whilst head office maintains oversight and compliance standards.

D23.io supports this federated model:

Site managers can:

• View their site’s dashboards and metrics
• Adjust local alerts and thresholds
• Export site-specific reports
• Cannot view other sites’ data

Head office / Group director can:

• View all sites’ dashboards
• Set group-wide policies and alerts
• Compare performance across sites
• Identify best practices and share across sites

Compliance team can:

• Monitor compliance metrics across all sites
• Identify sites at risk of regulatory breach
• Generate group-wide compliance reports

This structure balances autonomy with accountability.

Adding New Sites

When a childcare group acquires or opens a new service, integrating it into D23.io is straightforward:

1. Data integration: Connect the new site’s enrolment, payroll, and incident systems to D23.io (API or CSV import)
2. Historical data load: Import 12 months of historical data for baseline metrics
3. Dashboard provisioning: Create site-specific dashboards; add site manager to RBAC
4. Testing: Validate data accuracy and dashboard functionality
5. Go-live: Activate monitoring and alerts for the new site

Timeline: 1–2 weeks per new site, depending on data integration complexity.

Consolidation and Rationalisation

D23.io also supports consolidation: when a group closes or merges sites, historical data is archived and consolidated into parent site dashboards. This enables trend analysis across service lifecycles.

---

Next Steps: Getting Started with D23.io

Assessing Your Readiness

Before engaging with PADISO on a D23.io deployment, childcare groups should assess their readiness:

Data readiness

• Do you have an enrolment management system (Kinderloop, Xplor, etc.) with API access or database exports?
• Is your payroll/rostering data in a system (Deputy, Humanity, Xero) or spreadsheets?
• Are incidents tracked consistently (even if in spreadsheets or paper forms)?
• Can you export 12 months of historical data for baseline metrics?

Organisational readiness

• Is there executive sponsorship (director or head of operations committed to the project)?
• Do you have a project lead to liaise with PADISO and coordinate internal resources?
• Are staff willing to learn new tools and change reporting processes?
• Is there budget allocated for the engagement (typically $40K–$60K for a 6-week deployment)?

Compliance readiness

• Do you understand ACECQA standards and your state’s specific requirements?
• Have you identified gaps in your current compliance reporting?
• Are you prepared to implement alerts and monitoring based on D23.io insights?

If you’ve answered “yes” to most questions, you’re ready to move forward.

Engaging PADISO for D23.io Deployment

PADISO offers a structured engagement model for childcare groups:

Phase 1: Discovery Call (30 mins, free) Discuss your operational challenges, data sources, and compliance requirements. PADISO assesses fit and scope.

Phase 2: Proposal and Scoping (1 week) PADISO delivers a detailed proposal outlining:

• Data integration scope and timeline
• Dashboard specifications
• Training and handover plan
• Fixed fee and timeline

Phase 3: Engagement (6–8 weeks) PADISO delivers the deployment following the timeline outlined earlier (Discovery, Data Integration, Dashboard Build, Go-Live).

Phase 4: Post-Launch Support (30 days) PADISO provides support, optimisation, and training.

Phase 5: Ongoing Optimisation (quarterly reviews) PADISO and your team meet quarterly to review metrics, add new dashboards, and optimise performance.

To get started, visit PADISO’s AI Agency Services Sydney or contact the team directly at PADISO. PADISO also publishes case studies and insights on AI Agency Reporting Sydney and related topics.

Building Internal Capability

Whilst D23.io is managed by PADISO, childcare groups benefit from building internal analytics capability:

Designate a metrics owner: A team member (director, administrator, or operations manager) becomes the primary user and advocate for D23.io. This person learns dashboard navigation, interprets metrics, and drives action based on insights.

Train your team: PADISO provides training during deployment; ensure all relevant staff (directors, room leaders, administrators) attend. Training covers dashboard navigation, metric interpretation, and report generation.

Establish review cadences: Schedule weekly director reviews of staffing and occupancy dashboards, monthly quality reviews, and quarterly strategic reviews of trends and improvements.

Document your processes: Create runbooks for common tasks (e.g., “How to respond to a ratio breach alert”, “How to export a compliance report”). This ensures consistency and knowledge retention.

Measuring Success

After D23.io deployment, track these success metrics:

Operational efficiency

• Time spent on reporting (target: 70% reduction)
• Time to respond to ratio breaches (target: <30 mins)
• Audit preparation time (target: <2 hours for full compliance report)

Business impact

• Occupancy improvements (target: +5–10% through targeted marketing)
• Staffing cost optimisation (target: 5–8% reduction through better forecasting)
• Revenue per occupied place (target: +3–5% through pricing optimisation)

Quality and compliance

• Incident rate trend (target: stable or declining)
• Educator qualification rate (target: >95%)
• Regulatory audit outcomes (target: “Exceeding” or “Meeting” standards, zero breaches)
• Parent satisfaction (target: 4.5+ out of 5)

PADISO’s AI Agency ROI Sydney and AI Agency Performance Tracking articles detail ROI measurement frameworks applicable to D23.io deployments.

---

Conclusion: ACECQA Compliance Made Operational

Childcare group operations are complex: occupancy and revenue management, staffing compliance, quality improvement, and regulatory audit readiness all demand real-time visibility and proactive decision-making. Manual spreadsheets and fragmented systems create risk, inefficiency, and stress.

D23.io’s managed Superset deployment solves this by centralising childcare operational data into audit-ready dashboards. Occupancy analytics drive revenue optimisation. Staffing dashboards ensure ratio compliance and prevent breaches. Quality metrics demonstrate continuous improvement against ACECQA standards.

For childcare groups across NSW, Queensland, Victoria, and beyond, D23.io isn’t a luxury—it’s operational necessity. It transforms compliance from a reactive, audit-driven burden into a proactive, data-driven practice.

PADISO’s venture studio and AI digital agency expertise, combined with proven D23.io deployment methodology, delivers outcomes: childcare groups reduce reporting overhead by 70%, improve occupancy by 5–10%, and pass regulatory audits with confidence.

If your childcare group is ready to modernise operations and embed ACECQA-aligned reporting, contact PADISO to discuss your D23.io deployment. PADISO also offers broader AI Strategy & Readiness services for organisations modernising with data and analytics.

Your children, educators, and regulators deserve nothing less than operational excellence. D23.io makes it possible.