Multi-Site Training Delivery Consistency: A COO's Guide

Multi-site training delivery consistency doesn't mean running every site the same way. It means fixing the few things an external body will test (standard coverage, assessment judgements, self-review evidence, records and sub-contractor accountability) and letting everything else flex to the site and the learner. Most costly drift sits in the first group, not the second.

Why this lands on your desk

You own the operating model. That decides whether three campuses, a workplace-delivery arm and a sub-contractor deliver the same programme to the same standard. Under the NZQA rules in force from 19 January 2026, the PTE stays fully responsible for its sub-contractors.

You also carry a reporting load. iQAF makes self-review a standing deliverable. Providers submit an annual self-review summary report to NZQA and meet NZQA to discuss the improvement plan. That report is only as good as the comparable data each site feeds into it.

Then there's TEC. You answer for the accuracy of SDR and IND submissions on the Data Exchange Platform. When one site records things differently from another, you pay for it in rework.

The external test has moved

The consistency question is now answered in a different place. NZQA's consultation proposed ending consistency reviews from 1 January 2026, in favour of a broader approach to consistent graduate outcomes. NZQA has since confirmed that no new EER processes or assuring consistency reviews begin from 1 January, although those already underway will be completed.

Meanwhile, the Industry Skills Boards (ISBs) started on 1 January 2026 and the Workforce Development Councils closed on 19 December 2025. ISB functions include developing qualifications and standards, endorsing programmes, and moderating assessments for consistency across providers.

So the reviewer who once visited and sampled has partly been replaced by a standing mechanism that compares you with other providers. Your evidence has to be ready all year, not assembled before a visit.

What to fix and what to flex

The useful test for any process is simple. Would an external moderator, NZQA or TEC look at this? If yes, fix it. If no, let sites adapt it.

Fix these

• Standard coverage. Every site delivers and assesses against the same unit standards or qualification requirements, with the same evidence that coverage is complete.
• Assessment judgements. Sites should apply the same decision rules for "achieved" and "not yet achieved". Moderators compare judgements across providers, so differing site interpretations show up as drift.
• Self-review evidence. Use one template and one set of measures, so site data rolls up into the annual iQAF summary report without hand-reconciling.
• Records and data returns. Use common record-keeping practices, matched to the TEC Data Specifications for SDR 2026 v3.1.
• Sub-contractor accountability. Give partners the same quality expectations you hold yourself to, with clear lines of responsibility back to you.

Flex these

• Teaching sequence and pacing for a given cohort
• Examples, scenarios and workplace context
• Support for learners with different language, literacy and numeracy needs
• Room use, scheduling and local employer relationships
• Delivery mode, provided the assessment evidence meets the same standard

The flex list isn't a concession. Good delivery adapts to the learner in front of it. The risk is when adaptation leaks into the fix list, such as a site quietly changing what counts as sufficient evidence because its cohort struggles with the task.

Partners and sub-contractors are inside your boundary

Sub-contracting rules now sit in the Quality Assurance of Tertiary Education Providers Rules. An application must include the rationale, a copy of the sub-contracting arrangement, and evidence of internal quality assurance approval by the Chief Executive or a delegated senior manager. SAARA, an industry body, summarises that NZQA will only approve if the PTE remains fully responsible for the sub-contractor meeting all obligations.

The Pastoral Care Code points the same way. It covers activities provided or organised by or on behalf of a provider, in New Zealand or offshore. A partner site's pastoral care failure is your failure.

Operationally, that means a partner shouldn't be a black box that sends results back at the end of term. You need visibility of coverage, judgements and records while delivery is happening.

What we don't know yet

The research behind this piece doesn't show how ISB moderation works day to day. We couldn't find sampling approaches, timing or what an ISB expects you to submit. It also didn't establish what replaces EER ratings for visa purposes. Immigration New Zealand says it will keep using existing EER ratings for 12 months from early 2026.

There are eight ISBs, and providers working across sectors may deal with more than one. Sources also disagree on whether creative and tech standards sit under an ISB or with NZQA, so check which body applies to yours. Then ask that body directly how moderation will run and what it wants to see.

One date to confirm as well: NZQA's enquiries page says Pastoral Care Code self-review and attestations are due 1 November for PTEs and Wānanga, but the page may be dated. Check the 2026 date with NZQA.

A first step this quarter

Pick one programme delivered at more than one site or partner. Then trace one unit standard from assessment judgement through to the SDR record and the self-review summary.

Write down where the process differs between sites, and who holds the knowledge of how it actually works. Sort every difference into "an external body would test this" or "this is local context". The first pile is your standardisation backlog, and it's usually shorter than expected.

Our take

Chasing uniformity is the wrong goal and also the expensive one. Standardise everything and you stifle the local judgement that makes delivery work for real learners, while still missing the handful of controls that matter. Standardise nothing and you hand-build every report and defend every judgement from scratch.

The middle path takes more design effort than either extreme. You have to decide, on purpose, where the line sits and write it down so it survives staff turnover. In a year when the bodies that set and moderate standards are changing, process knowledge that lives in one coordinator's head is the biggest operational risk you can fix cheaply.

Key takeaways

• Fix what an external party will test: standard coverage, assessment judgements, self-review evidence, data returns and sub-contractor accountability.
• Flex delivery context: pacing, examples, learner support and local scheduling.
• NZQA is not starting new assuring consistency reviews from 1 January 2026, while ISBs now include moderation across providers in their remit.
• iQAF's annual self-review summary report means consistency must be evidenced routinely from every site.
• The PTE remains fully responsible for sub-contractors, and the Pastoral Care Code extends to activity organised on a provider's behalf.
• Confirm with your ISB how moderation works, because public material doesn't spell it out.

FAQ

Do NZQA consistency reviews still happen?

NZQA confirms no new EER processes or assuring consistency reviews begin from 1 January 2026. Those already underway will be completed. ISBs now include moderation of assessment across providers in their functions.

Who moderates our assessments now?

ISBs have moderation of assessments for consistency across providers within their remit, and they started on 1 January 2026. The research doesn't detail day-to-day procedures, so confirm the process with the ISB covering your standards.

Are we responsible for what our sub-contractors do?

Yes. NZQA will only approve sub-contracting if the PTE remains fully responsible for the sub-contractor meeting all obligations, per SAARA's summary of the rules in force from 19 January 2026. Applications also need the rationale, a copy of the arrangement and internal quality assurance approval evidence.

How does multi-site consistency affect TEC reporting?

TEC funding data goes through the SDR and IND on the Data Exchange Platform, against Data Specifications for SDR 2026 v3.1. Common record-keeping practices across sites keep submissions clean and reduce rework.