The risk isn't that you take leave. It's that nobody else could run your next self-review without you. Under NZQA's iQAF, compliance is a year-round discipline, so a single person holding the knowledge is no longer a quirk of the role. It's a continuity test you can run on yourself this week.
Why this lands on your desk
You're probably the named contact for NZQA. The annual self-review summary report has to identify areas for improvement, set out a plan to address them, and confirm compliance with the Act, NZQA rules and the Code. Someone has to stand behind that confirmation. If it falls due while you're on leave, or after you've resigned, or while you're unwell, that someone needs to exist and know what they're signing.
With EER gone, there's no single review event to prepare for and then recover from. NZQA's Quality Assurance of Tertiary Education Providers Rules 2026 expect an up-to-date quality management system, annual self-reviews, monitoring, sub-contracting requirements and assessment records retention. Readiness now has to hold all year, including the weeks you aren't there.
You've probably felt the everyday symptom already. Every document review and evidence request routes through you. That's not diligence. It's ownership that lives in a person rather than in the way the organisation works.
What iQAF changed, and what it didn't say
NZQA's integrated Quality Assurance Framework went live after consultation through 2025 and approval of the updated rules (NZQA, 15 January 2026). From 1 January, NZQA isn't beginning new EER processes or assuring consistency reviews, though those already underway will be completed. The 2026 Rules came into force on 19 January 2026 and replace the 2022 EER rules.
Providers must submit an annual self-review summary report and meet NZQA to discuss the improvement plan. The report also describes practice against themes in an annual schedule published on NZQA's website. Code self-review reporting is combined with that submission, so you keep reviewing practice against the Education (Pastoral Care of Tertiary and International Learners) Code of Practice 2021.
Here's the honest caveat. NZQA hasn't described this as a key-person problem. That's our inference from the rules: year-round evidence and clear ownership look like an expectation, and a provider whose knowledge sits with one person is exposed. We found no NZ data on how common single-owner compliance roles are, or on audit failures caused by someone's absence. The argument rests on the rules, not on a measured trend.
Where the knowledge actually hides
It's rarely in one dramatic place. It's in small, ordinary ones:
- Your inbox. NZQA has emailed providers whose training schemes need review since January 2025. Each review is due on the date the scheme was first approved. An email to one inbox, or a due date held in one memory, is a continuity risk.
- Your calendar. The PTE Rules 2026 replace the PTE Registration Rules 2025 and the PTE Enrolment and Academic Records Rules 2022, and remove the annual fee. Non-funded PTEs provide annual financial returns biennially unless NZQA notifies otherwise. These are dates and obligations that need a named owner and a backup.
- Your personal folders. Evidence scattered across drives and spreadsheets makes sense to the person who filed it. Nobody else can reconstruct it quickly.
- Your head. Which obligation sits where, who holds which record, and why a policy reads the way it does.
Under the Programme Approval, Recognition and Accreditation Rules 2026, NZQA may also carry out special reviews of programme approvals and accreditations with reasonable notice. Notice of that kind doesn't wait for your return date.
Reform adds to the tracking load. Legislation passed in October 2025, and ten regional polytechnics and eight Industry Skills Boards became operational on 1 January 2026. The Industry Skills Boards replace workforce development councils, and Te Pūkenga is a transitional entity until it's disestablished on or before 31 March 2027. If you alone map what that means for your programmes and relationships, that's more to hand over.
The leave test: five questions
Treat this as a test of your system, not of you. Answer each honestly.
- Could a colleague run the next annual self-review without calling you?
- Could they find every training scheme review date and the evidence behind it?
- Could they complete the Code self-review section from records, not recollection?
- Does anyone besides you receive NZQA correspondence?
- Could they answer an NZQA request, including a special review notice, within the timeframe?
Every "no" is a place where your absence becomes a registration risk. That's the useful finding. It's also a list of fixes, in order of urgency.
Making the handover real this quarter
Start with the one step the research makes clear: confirm your submission date and the annual themes directly with NZQA. NZQA has said it will provide self-review templates over the coming months, and we couldn't locate the themes schedule. One PTE's commentary suggests a mid-2026 start with first reports running to mid-2027, but we couldn't confirm that on an NZQA page. Don't plan around it. Ask.
Then do three small things:
- Name an owner and a backup for every dated obligation: self-review, each training scheme review, Code reporting, financial returns.
- Move NZ QA correspondence to a shared mailbox so no obligation arrives in one inbox only.
- Run a real handover drill. Take a week's leave, or simulate one, and let a colleague handle a live evidence request. Note where they got stuck.
The drill shows you what's undocumented faster than any audit of your own files will.
Key takeaways
- iQAF and the 2026 Rules make compliance a year-round expectation. The annual self-review report must confirm compliance with the Act, NZQA rules and the Code.
- Single-person knowledge is a continuity risk. That's our inference from the rules, not an NZQA finding or a measured NZ trend.
- Inboxes, memories and personal folders are where dates like training scheme reviews go missing.
- The test: could a colleague run your next self-review, training scheme review and Code check without you?
- First step: confirm your submission date and themes with NZQA, then name an owner and backup for each obligation.
Our take
Bus factor gets framed as a personal failing, and that's wrong. Most compliance managers hold everything because they were the only person asked to. The knowledge pooled around you because the organisation let it.
Our view is that the fix is also a fairer deal for you. A compliance function that works without its manager is one where you can take leave, and one where you're no longer the bottleneck for every document review. Being indispensable feels like job security. Under year-round assurance, it's a risk to the provider's registration and to you.
FAQ
Does NZQA require a backup for the compliance manager role?
We found nothing in the sources that says so. But the annual self-review summary report must confirm compliance with the Act, NZQA rules and the Code, so someone has to be able to stand behind it whenever it falls due. A backup is a sensible response to that, not a rule.
What has iQAF changed for PTEs?
From 1 January, NZQA isn't beginning new EER processes or assuring consistency reviews, though those underway will be completed. PTEs now need an up-to-date quality management system and an annual self-review summary report, with Code self-review reporting combined into the same submission.
Which dates should have a named backup?
At minimum: the annual self-review submission, each training scheme review, Code reporting, and annual financial returns for non-funded PTEs (biennial unless NZQA notifies otherwise). Training scheme reviews are due on the date the scheme was first approved.
How do I find out my submission date and themes?
Ask NZQA directly. NZQA publishes the annual themes schedule on its website, but we couldn't locate it and it hasn't been confirmed on an NZQA page. NZQA has also said self-review templates will follow over the coming months.
If you took leave tomorrow, what's the first thing that would stall? Fix that one first.