90%, 85%, 70%, Then NZQA Knows. The Attendance Escalation That Eats Your Admin Staff Alive

The Real Problem

It's a Tuesday morning at a private English language school in central Auckland. You run a 70-student PTE. Three of those students are at 88% attendance, four are at 84%, one is at 67%, and a Korean student named Min-jun has not turned up to class for nine working days.

Your office manager Sarah is staring at the Axis portal. The attendance percentages refresh once a day from the roll. Sarah knows that under the school's policy, written from the Education (Pastoral Care of Tertiary and International Learners) Code of Practice 2021, every one of those students needs a different letter today:

• The three at 88% need an email reminder
• The four at 84% need a Formal Attendance Warning 1 (or Warning 2 if they already had Warning 1 in this trimester)
• The student at 67% needs a Review of Enrolment letter today, the moment they cross 70%, no waiting
• Min-jun, absent two consecutive weeks, automatically hits Review of Enrolment, and his visa file goes onto the "Immigration NZ may need to know" pile

Sarah opens five Word templates. She copy-pastes the student's name, ID, current attendance percentage, the trimester start date, the warning history, the "Show Cause" deadline (5 working days), and the appeal pathway. Each letter is two pages. She sends them by email to the student's school address (UClive in many schools' case), and BCCs the Academic Director. Then she logs the action in the student management system, and updates the pastoral care register.

If the student is under 18, the parent gets a copy. In a different language, ideally.

This is two hours of admin per day, for a 70-student school. At a 200-student school it's a full-time job. And one missed letter on the wrong day, especially the day a student crosses 70%, opens the school up to an NZQA Code review and, in the worst case, removal from the register of approved providers.

The cost of getting this wrong is enormous:

• A student whose visa is revoked because of an attendance issue the school never escalated has a clean negligence claim against the school for refunded tuition (typically NZD $4,000 to $12,000 per student)
• A pattern of late escalation across multiple students triggers an NZQA Code review (a Self-Review or Provider-Initiated Review costs internal time of 80 to 200 hours)
• Loss of NZQA Category status (currently Category 1, 2, 3 or 4) downgrades the school's ability to enrol student-visa holders, and category drop is a public listing on the NZQA provider register
• Repeated failure can lead to deregistration, which is the end of the business

For a 70-student school running three trimesters a year, getting attendance escalation wrong on even five students per year is a NZD $20,000 to $60,000 hit, and that is before any NZQA action.

Why Existing Tools Don't Solve This

The NZ language school sector has reasonable attendance software:

• SEATS is purpose-built for NZ tertiary and PTE compliance. It logs attendance, and its visa and immigration module tracks engagement data. It does not draft letters.
• Wisenet (used widely by NZ PTEs) is a strong student management system with attendance percentage tracking and a hold/flag feature. It does not draft letters.
• Class.com (formerly Class for Education) is widely used by language schools. It tracks attendance. It does not draft escalation letters.
• KAMAR is the dominant secondary-school product and is used by some schools enrolling international learners. It tracks attendance. It does not draft letters.
• Axis (used by UC International College and a handful of others) shows the percentage to staff and the student. It does not draft letters.

In every case the gap is the same: the system tells you the student is at 84%, but nobody walks across the office to a printer and presses the right button on the right day with the right reasons.

The result is the manual workflow Sarah is doing right now. Five Word templates, daily copy-paste, manual sender logs, manual pastoral care register entries.

There is also a second gap: the parent letter for under-18 students. Most NZ language schools enrol some learners under 18, especially during agent-driven group enrolments from China, Vietnam, Thailand, and Korea. The Code requires the school to "contact parents" for any attendance issue. That contact must be in a language the parent reads. Sarah does not speak Korean, and Google Translate of a legal-style attendance warning letter is not appropriate.

This is exactly the kind of work AI is good at: rules-based, document-heavy, time-sensitive, and language-aware.

How AI Solves This

You set up an AI Agent AI workflow that runs once an hour against your student management system. The AI does not record attendance. It reads the attendance the system already records, and acts on it.

For every active international student the AI checks:

1. The current trimester attendance percentage
2. The number of formal warnings already issued in the current trimester (warning 1, warning 2)
3. Consecutive absent days
4. The student's age (under 18 triggers parent communication)
5. Whether an Explained Absence Form has been received and approved for any of the missed days
6. Whether a Show Cause Notice is currently pending response (and the 5-working-day clock)

When a student crosses a threshold, the AI:

Drafts the appropriate letter for today, with the student's name, the exact percentage, the trimester start and end dates, the specific course and contact hours, the warning history, and the next action required (5 working days to respond, the appeal pathway, the office address).

The letter is queued for the Academic Director's electronic signature. Nothing goes out without a human reviewing it. But the human reviewer's job is now thirty seconds (read and approve) instead of forty minutes (write).

Here is what the AI handles automatically:

• Below 90%: an email reminder draft, plain language, "you are at 88%, here is what counts as an explained absence, here is the form"
• Below 85% (first time): Formal Attendance Warning 1, full template populated, 5-working-day deadline calculated, Explained Absence Form attached
• Below 85% (second time, after Warning 1): Formal Attendance Warning 2
• Below 85% (after Warning 2 with no improvement): Review of Enrolment letter, Show Cause Notice attached, appeal pathway included
• Below 70% at any point: Review of Enrolment letter, regardless of warning history, immediately
• Two consecutive weeks absent without an Explained Absence Form: Review of Enrolment letter
• Under 18 student at any threshold: a translated copy of the same letter to the parent in their preferred language, plus a phone-call task assigned to the pastoral care lead

Every action is logged: the timestamp, the threshold that triggered it, the document that was generated, the staff member who signed off, the channel it went out through, and the student's response (if any) within the deadline window.

This single change does three things at once:

1. Sarah saves 8 to 10 hours a week because she stops drafting letters and starts reviewing drafts
2. The Academic Director gets a clean dashboard of who is approaching which threshold instead of getting forwarded screenshots from Sarah at 9am every day
3. The school is audit-ready every day, not just in the lead-up to an NZQA Self-Review. Every escalation has a complete paper trail, every letter went out on the day the threshold was crossed, every parent contact for an under-18 student is logged with the language used and the response

How We Set This Up

The AI on its own is just a chat window. The bridge between the AI and your school's existing systems is what BestAI builds: a custom integration program that we write specifically for your school's setup.

For a NZ language school or PTE, that program does the following:

• Reads attendance records from your student management system (SEATS, Wisenet, Class.com, KAMAR, Axis, or a custom database) once an hour, on a schedule
• Reads enrolment status, course timetable, contact hours, age, parent contact details, and warning history from the same system
• Reads any Explained Absence Forms submitted to your front desk inbox or shared drive
• Calculates the current attendance percentage exactly as your policy defines it (some schools count contact hours, some count class periods, some weight by course)
• Detects the threshold crossing and selects the correct letter template
• Drafts the letter using your school's letterhead, your Academic Director's signature block, and your specific compliance language (with the right NZQA Code reference, the right Education and Training Act 2020 section, the right appeal pathway)
• Translates the parent copy for under-18 students into the parent's preferred language (Mandarin, Korean, Vietnamese, Thai, Japanese, Spanish, Arabic, Russian, Portuguese)
• Queues the draft for the Academic Director's review
• Sends the approved letter through your existing email system with the school's domain (so it does not go to spam)
• Logs the action in your pastoral care register and the student management system

Our process is the same one we use for trades, hospitality, and healthcare clients:

1. We map your current attendance escalation policy. We sit down with the Academic Director and the office manager, and we walk through every threshold, every letter template, every deadline, every form your school uses today. If your policy is documented, we read it. If it is in your office manager's head, we write it down.
2. We build the connections. Our developers write the integration program that talks to your student management system. We do not replace your existing system. We add a layer that reads from it and writes back to it.
3. We test end-to-end with anonymised student data. Every threshold gets tested. Every letter gets reviewed by your Academic Director before going live. We test the parent translations with native speakers on our team before they go to a real parent.
4. We maintain it. When the Code of Practice is amended (the last revision was 2021, the next refresh is being consulted on now), we update the letter templates and the threshold logic. When you change your trimester structure or add a new course, we update the calculator.

You don't need to be technical. The Academic Director keeps doing their job. The office manager keeps doing their job. The AI takes the part that was always going to be done by a junior compliance officer the school could not afford to hire, and does it consistently, on the day, every day.

The Result

A 70-student PTE running this workflow typically sees:

• 8 to 10 admin hours per week returned to the office manager (~NZD $200 to $300 per week, or NZD $10,000 to $15,000 per year at NZ private-school admin rates)
• Zero missed escalations: every threshold crossing has a letter on file with the correct date
• NZQA Self-Review prep cut from 200 hours to 40: the audit trail already exists, it just needs to be exported
• A measurable drop in student attendance issues, because earlier intervention (the 88% email reminder) catches drift before the student is in real trouble. Schools we have spoken to estimate this saves 1 to 3 student visa terminations per year
• Better Code Category positioning at the next NZQA review, because the school can demonstrate consistent, documented pastoral care escalation. For a school sitting at Category 2, an upgrade to Category 1 is worth real money in agent commission rates and student-visa appeal

The pricing for this kind of workflow integration program at BestAI is NZD $999 setup plus $300 per month for ongoing maintenance and template updates. That includes the integration program, the letter templates, the parent translations, the pastoral care register link, and any change of policy or threshold for the duration of the contract.

If even one student visa termination is avoided in the first year, the workflow has paid for itself.

What AI Can't Do Here

• AI cannot decide to terminate a student's enrolment. The Academic Director makes that decision after the Show Cause response. The AI prepares the paperwork.
• AI cannot judge whether an Explained Absence is a genuine compassionate ground. A student saying "my grandmother died" with a foreign-language death certificate is a human judgment, with the Manager of Admissions and Student Services. The AI surfaces it, the human decides.
• AI cannot replace the in-person pastoral care conversation. When a student is at 67% because they are homesick or struggling with anxiety, the AI's job is to flag it, not to counsel. The school's pastoral care lead does the counselling.
• AI follows the policy you give it. If your policy says "90%, 85%, 70%", that is what AI uses. If NZQA changes the Code, you tell us, and we update the system. AI does not interpret regulation.

Who This Is For

• NZ private training establishments (PTEs) and English language schools enrolling between 30 and 400 international students
• Schools with one full-time office manager (not a dedicated compliance officer) handling pastoral care escalations alongside admissions, enrolment, and student services
• Schools that have had an NZQA Self-Review or Provider-Initiated Review in the last three years, and felt it as a heavy paperwork hit
• Schools with significant under-18 enrolment (group bookings from China, Vietnam, Thailand, Korea), where parent communication in language is currently done by hand
• Schools that lost a student to visa termination in the last year and want to make sure the next time the paper trail is clean
• Auckland and Christchurch PTEs that already use SEATS, Wisenet, Class.com, KAMAR, or Axis and want a layer on top, not a replacement

Sources

• Education (Pastoral Care of Tertiary and International Learners) Code of Practice 2021, NZQA. The current code, in force since 1 January 2022, framed under the Education and Training Act 2020.
• Immigration NZ "Code of practice for pastoral care". Confirms an approved education provider must sign and follow the Code, and Immigration NZ relies on this for student visa decisions.
• UC International College Attendance Policy v4.4. Public NZ PTE policy that codifies the 90% / 85% / 70% threshold structure used in this case study.
• Immigration NZ "English Language Student Visa". Confirms attendance and "satisfactory progress" are required visa conditions.
• NZQA "Find a Provider" public register. The category status that schools are working to protect.
• GetApp NZ listing for SEATS. The dominant NZ tertiary compliance product, illustrating that attendance recording is solved but escalation drafting is not.