Nexus Education
Pātaka replaces the portals, spreadsheets and paper forms your staff fight daily. Built in a school, for schools.
A student information system here. A forms tool there. Relief on a whiteboard, budgets in a spreadsheet, trip approvals in an inbox. Every one of them needs its own login, and none of them know what the others did.
Pātaka was built because a school got tired of that. It is one place where the work actually happens, and everything in it already knows who you are, what you teach, and what you are allowed to see.
Every teacher's landing page. Timetable, relief, duties, notices and the forms waiting on them, all resolved for today before they have taken their coat off.
Roll marking that shows you who is missing, who has not entered, and which period it went wrong in. Filter by date, student or class without exporting anything.
Unit planners that hold knowledge and practice statements, shift by week, and open straight into Canvas.
Trips from first proposal to caregiver notification, with every approval step recorded in order.
Who is away, who is covering, which period. Staff see their own cover the moment it is set.
Leave, payroll details, onboarding. Multi-step approvals that route themselves and keep moving without a chaser email.
Faculty and house budgets with purchase orders against them, visible to the people spending the money.
Applications, approvals and a record of what staff have actually been to.
Contact and context for a student, in front of the staff member who needs it, when they need it.
Timetable, subject selection and the things students are meant to act on, in the same system their teachers use.
In practice
The same morning, in a school that runs on Pātaka.
Relief is allocated before the bell. Every covering teacher sees it on My Day, and the students' timetables already reflect it.
Attendance shows the three classes that have not marked yet. The office chases three people instead of sixty.
The Hunua tramp moves to the next approval step on its own. Caregivers are notified from the same screen that holds the risk assessment.
A head of faculty drags a unit back two weeks. The planner, the knowledge statements and the Canvas link all follow it.
Raised against a faculty budget that shows what is left, by someone who did not need to ask the finance office first.
No big-bang migration. Modules switch on when you are ready for them.
Pātaka authenticates against Microsoft Entra ID, so staff and students sign in with the account they already have, with your existing multi-factor policy applied. There is no separate user list to maintain.
Timetable, classes, staff, students and caregivers load in. Roles come from your groups, so a head of faculty sees faculty things and a classroom teacher does not.
Start where the pain is loudest. Most schools begin with relief or forms, because the saving is immediate and nobody needs training to notice it.
Staff request changes from inside the platform. Your processes stay yours, and the system bends to them rather than the other way round.
Pātaka is not trying to replace your identity provider, your LMS or your accounting system. It sits in the middle and makes them behave like one thing.
Security
Sign-in runs through Microsoft Entra ID. Your conditional access and multi-factor rules apply to Pātaka exactly as they apply to everything else. When a staff member is offboarded in your directory, their access ends.
What a person can see follows the job they do. A classroom teacher, a head of house and a deputy principal open the same page and get different amounts of it.
Designed against New Zealand privacy obligations for student information, with collection limited to what the school actually needs to run.
Approvals, submissions and changes carry who did them and when, so a question about a decision has an answer.
A demo is a working school, not a slide deck. Tell us roughly what your school is wrestling with and we will show you the part of Pātaka that deals with it.
hello@nexuseducation.co.nz
