Yes — I want to help the industry become a better place, with the support system it deserves.Yes — count me in
PrototypeThis site shows the lived experience of Simply Safe Group™ — workflows, language and screens are real; on-screen data is illustrative.
Operational workflows

Open a role to see how a real day moves through the system.

Each role has its own surface — what appears on sign-in, the rhythm of the day, what arrives as a notification, what stays intentionally hidden, and how accountability flows out to other roles.

On the iPad — Educator view
Floor-level · assigned room only
Educator

On the floor with children. The system stays out of the way until it's needed — then it's two taps, in context, never off-floor.

See the iPad · day in the life →
On the iPad — Room Leader view
Room operations · all educators in room
Room Leader

Coordinates the day's rhythm — staff in room, ratios, handovers, and the room's open loops. Light coordination, not surveillance.

See the iPad · day in the life →
On the iPad — Educational Leader view
Pedagogy across all rooms
Educational Leader

Holds the pedagogical thread across the centre. Sees patterns and learning cycles — not raw documentation about individual children.

See the iPad · day in the life →
On the iPad — Director view
Centre-wide oversight
Director

Calm operational oversight of the whole centre. Sees pulse, signals, compliance — not raw documentation about individual children.

See the iPad · day in the life →
On the iPad — Casual Educator view
Single shift · auto-expiring access
Casual Educator

Arrives, finds the room, supports the day. Access is time-bound to the shift — when the shift ends, scope expires automatically.

See the iPad · day in the life →
On the iPad — Chef view
Kitchen · menus · dietary
Chef

Kitchen and dietary safety are not an afterthought — allergies are first-class data, surfaced everywhere food meets a child.

See the iPad · day in the life →
On the iPad — Admin view
Enrolments · operations · documents
Admin

Workflows, not surveillance. Enrolments, billing, compliance documents, casual onboarding — kept separate from pedagogy and floor work.

See the iPad · day in the life →
On the iPad — Approved Provider view
Multi-centre · governance & risk
Approved Provider

Calm oversight across every centre under your approval — pulse, compliance horizon and risk signals, never raw documentation about individual children.

See the iPad · day in the life →
On the iPad — Family view
Their child only · warm, curated
Family

One calm thread about your child — not a feed, not a surveillance camera. Real moments, real words, in plain English.

See the iPad · day in the life →
On the iPad — Cleaners & Contractors view
Tasks only · no child information
Cleaners & Contractors

A simple checklist of what needs doing, where and when. No child information, no documentation, no surveillance — just clean, signed, audit-trailed work.

See the iPad · day in the life →
Role-based access

Eight roles. One philosophy: see only what serves your work.

Access is shaped by responsibility, not seniority. A casual on a 4-hour shift sees today's room. A director sees the centre's pulse — never raw documentation about a single child.

01
Educator
Assigned room only

Their children, today's plan, observations, incidents

Floor-level. Quick capture. Minimal taps.

02
Room Leader
Room operations

Ratios, planning, room handover, staff in room

Light coordination. Day rhythm.

03
Ed. Leader
Pedagogy across rooms

Learning cycles, observations, framework alignment

Reflective. Cross-room patterns.

04
Director
Centre-wide

Operational pulse, compliance, wellbeing, incidents

Calm oversight. Aggregated, not invasive.

05
Admin
Enrolments & ops

Bookings, families, billing, compliance docs

Workflows, not surveillance.

06
Chef
Kitchen & menus

Allergies, dietary plans, menus, supply

Allergy-first. Always visible.

07
Casual
Day-shift only

Today's room, key children info, allergies, incidents

Temporary scope. Auto-expires.

08
Parent
Their children only

Daily moments, learning story, comms, incidents about their child

Warm. Curated. Never raw data.

Permission matrix

Access shaped to responsibility.

A static read of who can do what across modules. The actual system also respects time-bound access — casual staff scope expires when their shift ends.

ModuleEducatorRoom LeaderEd. LeaderDirectorAdminChefCasualParent
Assigned Room···
All Rooms·····
Child Observations··
Learning Cycles···
Incidents (create)··
Incidents (review)····○*
Handovers···
Rostering·····
Cleaning checklists···
Allergies / menus·
Enrolments······
Compliance docs····
Parent comms··
Excursions·
Wellbeing signals······
Full access Create / contribute Read-only / scoped· No access○* Parent sees only incidents involving their own child
Day-in-the-life

Three role journeys.

Same system. Three very different surfaces. Each shaped to one rhythm.

Educator · 8h shift
  1. 0107:30 · Sign in → today's room loads with my children
  2. 0209:10 · Quick observation captured at the easel
  3. 0311:00 · Allergy banner visible at lunch handover
  4. 0413:45 · Incident form, two taps, reviewed by Room Leader
  5. 0515:00 · Handover note auto-prompts unfinished items
  6. 0616:00 · Sign out · zero off-floor admin
Director · centre day
  1. 01Morning · Operational pulse: ratios green, 1 incident open
  2. 02Mid-morning · Wellbeing signal flags an over-extended room
  3. 03Lunch · Compliance window for excursion approval
  4. 04Afternoon · Reviews aggregated learning-cycle progress
  5. 05Late · Sign-off on incident outcome to family
  6. 06End of day · Tomorrow's roster auto-rebalanced
Parent · trust loop
  1. 01Morning · A short, warm note from the room
  2. 02Mid-morning · A short written moment from the room
  3. 03Lunch · 'ate well, slept 11:40–12:55'
  4. 04Afternoon · Learning story moment added to journal
  5. 05If needed · Incident shared with care, never raw form
  6. 06Evening · One thread, not five apps