RS7 submissions are a regular part of running an early learning centre in Aotearoa. While the process itself is familiar, the experience of preparing for RS7 can feel very different from one centre to the next.
Centres that feel confident heading into RS7 usually aren’t doing anything dramatic-they’re simply checking the right things early, fixing issues as they arise, and using systems that make compliance easier to manage over time.
This guide outlines the key steps centres take to prepare for RS7, the most common problem areas, and how centres reduce last-minute pressure before submission day.
What Is RS7 and Why It Matters for Centres
RS7 is a Ministry of Education return that collects essential data from early learning centres, including:
- Child enrolments
- Attendance and absences
- Funded Child Hours (FCH)
- Staffing information used in funding and qualification calculations
Because RS7 data directly affects funding outcomes, even small gaps-such as missing attendance or unsaved contact hours-can result in delays or follow-up from the Ministry.
Centres that treat RS7 as an ongoing data-quality process, rather than a twice-yearly task, tend to experience far fewer issues.
Start RS7 Preparation Earlier Than You Think
One of the most common challenges centres face is timing. Leaving preparation until the submission window opens often means trying to review months of data under pressure.
Centres that build regular attendance, staffing, and enrolment checks into their routine usually find RS7 much calmer.
This is where systems designed specifically for NZ ECE compliance can make a difference. Platforms like Juniorlogs are built around Ministry requirements and help centres spot potential RS7 issues well before submission periods open.
👉 If RS7 always feels rushed at your centre, it may be worth reviewing how your current system supports early checks. Many centres choose to book a short demo to see what proactive RS7 preparation can look like in practice.
Step 1: Review Attendance for Completeness
Attendance data underpins much of the RS7 return and is often the first place issues appear.
A good approach is to review attendance one month at a time and look for:
- Days where attendance hasn’t been marked
- Children with no present or absent status
- Patterns where marking may have been missed
When attendance gaps are found early, they’re usually quick to resolve.
Systems that provide clear monthly attendance views help centres spot missing data without trawling through individual child records. Juniorlogs, for example, highlights these gaps clearly so centres can correct them before they trigger RS7 alerts.
👉 If attendance checks currently take a lot of manual effort, seeing how Juniorlogs surfaces missing data may be helpful-many centres explore this via a quick demo.
Step 2: Confirm Contact Hours Are Accurate and Saved
Contact hours are another common RS7 pressure point.
Even when rosters are in place, contact hours still need to be reviewed and saved to reflect real-world changes such as:
- Lunch breaks
- Teacher leave
- Changes to hours worked
- Use of discretionary hours
Centres that regularly save contact hours throughout the year tend to avoid last-minute corrections later on.
Some systems-Juniorlogs included-intentionally separate rosters from saved contact hours. This gives centres a clear opportunity to make final adjustments and understand how staffing decisions affect funding-related calculations.
👉 If contact hours are often a source of confusion at RS7 time, a demo can help clarify how this is handled in Juniorlogs.
Step 3: Make Sure Temporary Closures Are Recorded
Temporary closures play an important role in RS7 validation.
These can include:
- Term breaks
- Planned closure days
- Unplanned or emergency closures
If closures aren’t recorded, systems may expect attendance on days when the centre wasn’t operating-leading to avoidable alerts.
Centres that record closures as they occur usually find this step straightforward during RS7 prep. In Juniorlogs, closures are checked early in the RS7 preparation flow, reducing the chance of unnecessary attendance errors.
Step 4: Validate Attendance and Funded Child Hours (FCH)
Once attendance and contact hours are up to date, centres can move on to validating the data that feeds directly into RS7.
Attendance Validation
For days that are not public holidays or recorded closures, attendance should be complete. Alerts generally indicate missing or inconsistent records that need attention.
Funded Child Hours (FCH)
FCH may need to be recalculated when:
- Bookings are changed after attendance is marked
- A 20 Hours ECE re-attestation occurs
- Enrolment details are updated
Systems that prompt centres to re-sync or recheck FCH help ensure submitted hours reflect the most current information. Juniorlogs does this automatically, guiding centres through recalculations when needed.
👉 Centres unsure how their system handles FCH recalculations often find it useful to see this process live in a demo.
Step 5: Review Daily Data and Funding Indicators
A daily data view helps centres identify funding-related issues across an entire month rather than day by day.
Things to watch for include:
- “Not Funded” (NF) indicators
- Funding alerts linked to 20 Hours ECE or Plus 10
- FAR-related funding issues
When alerts appear, funding analysis reports can help pinpoint the exact days and child records involved. Juniorlogs provides built-in funding analysis tools that allow centres to drill into these details quickly and with confidence.
Step 6: Check Qualified Ratios and Discretionary Hours
RS7 preparation also involves reviewing staffing information, including:
- Average qualified teacher ratios
- Discretionary hours used
Regularly reviewing these figures helps centres understand how staffing patterns interact with funding requirements and reduces surprises after submission.
Juniorlogs brings qualified ratios and discretionary hours into the same workflow as RS7 preparation, giving centres a clearer overall picture.
Is Your Centre RS7 Ready? – Quick Checklist
Use this short checklist to sense-check your readiness:
✅ Attendance is marked consistently for all children
✅ Contact hours are reviewed and saved
✅ Temporary closures are recorded
✅ FCH has been checked or re-synced where needed
✅ Daily data shows no unexplained funding loss alerts
✅ Qualified ratios and discretionary hours have been reviewed
If several of these still need work, starting early-or reviewing how your system supports RS7 preparation-can make a big difference.
Frequently Asked Questions (FAQs)
When should centres start preparing for RS7?
Ideally, preparation should happen continuously. However, running checks several weeks before the submission window opens gives centres time to resolve issues without pressure.
What’s the most common RS7 issue?
Missing attendance records are one of the most frequent causes of RS7 alerts, especially when attendance is entered retrospectively.
Why do contact hours need to be saved separately from rosters?
Saving contact hours allows centres to make real-world adjustments (such as leave or breaks) and ensures staffing data accurately feeds into funding calculations.
What does “NF” mean in RS7 checks?
NF means “Not Funded.” It indicates that funding criteria weren’t met for a specific day or child and should be investigated using a funding analysis report.
Can RS7 issues be fixed after submission?
Some corrections can be made, but it’s far easier-and less stressful-to resolve issues before submitting.
How can centres reduce RS7 stress long-term?
Centres often find that using systems designed around NZ ECE compliance-such as Juniorlogs-helps surface issues earlier and supports better preparation throughout the year.
Final Thoughts
RS7 doesn’t need to be a stressful event. With steady preparation, clear visibility of data, and systems that support early checks, centres can approach each submission period with confidence.
For centres reviewing their current processes, exploring how tools like Juniorlogs support RS7 readiness can be a valuable step-often starting with a simple demo to see what proactive preparation looks like in practice.
