Registered on paper vs. the service you actually run

A registration certificate lists a specific service type — full-day care, part-time, sessional, drop-in, school-age — plus an age range, a capacity, a set of rooms, and opening hours. None of that is decorative. If the service model on the ground has moved past what's on the certificate — a room converted, capacity crept up, a new age band added informally — that's a registration and compliance gap, not an administrative footnote.

Tusla's own inspection notebook checks registered details before it checks anything else: name, address, registered provider, person in charge, age profile, service type, maximum numbers, rooms, hours. The comparison an inspector runs in five minutes should already be one the service runs on itself, monthly, not something built for the first time the week before an inspection.

The rule for anything that changes — a new room, an outdoor area, a different address, an ownership change, a materially different set of hours — is to treat it as a registration event, not paperwork. Tusla's inspection notebook is explicit that changes to registered details need written notice at least 60 days ahead, subject to the regulations' own exceptions. A landlord swap or a "we've started opening an extra hour" decision that feels administrative can still be a notifiable change.

Bloomffy doesn't try to be the registration filing itself, but it does try to stop the drift going unnoticed. Every room in the schema declares its own program type — full day care or ECCE/sessional — because that distinction feeds the ratio bands that actually apply to it; a room quietly operating differently from how it's registered doesn't just risk a compliance letter, it starts computing the wrong ratio. Keeping that declaration accurate at the room level is a smaller habit than an annual registration audit, but it's the one that catches drift while it's still cheap to fix.