Compliance & accountability
Compliance you run from live data — not a quarterly scramble.
Designed and built in New Zealand, for New Zealand providers — with TEC, NZQA and Ministry of Education reporting understood and built in from the ground up, not bolted on.
NZQA Pastoral Care Code
The Code self-review, running all year round.
Outcomes 1–12 tracked with evidence, actions and RAG status — with much of the evidence gathered automatically from wellbeing check-ins, pastoral-care cases and attendance. Keep the evidence organised for staff review and attestation.
Incidents logged with severity, response and follow-up — feeding the relevant outcome automatically.
Complaints tracked end to end, with resolution timelines visible at attestation.
AI reviews your evidence against each outcome and flags where you're thin — before NZQA does.
TEC & MoE reporting
Returns generated from the data you already run on.
No rebuilding returns in spreadsheets. Generate supported return files from your records, check the validation results and review them before submission. The numbers in your returns are the numbers in your enrolments, because they're the same records.
Drafted from live enrolment data and validated before you submit — no re-keying.
Every return with its own event history — what was generated, checked and exported, when.
Student records structured for the National Student Index. Direct access requires provider credentials and setup.
F23/QE1 exports generated from your gradebook, in the format NZQA expects.
Verification-of-study evidence produced from enrolment records.
Attendance captured daily is attendance reportable — no reconstruction.
Pallara prepares supported reporting files for staff review. Direct TEC and NSI connections require provider setup; further agency connections and conformance work are listed on the roadmap.
Operational accountability
See exactly who did what, and when.
Review important changes in a readable activity log. Authorised staff can follow recorded actions and open further detail when they need to investigate.
Support day-to-day oversight and preparation for audits.
Security & trust
Governance controls that hold up to scrutiny.
Database controls help keep each institution’s information separate.
Staff see what their role allows, down to individual capabilities.
Multi-factor authentication for staff accounts.
Sensitive student records restricted to named roles — with access itself logged.
Integration credentials and tokens encrypted at rest, managed by your own admin.
Changes to shared AI teaching guidance require approval. Other features provide suggestions or act within staff permissions, depending on the task.