Jidoka sits beside the systems you already use, shows your team who needs attention and why, and prepares the next step. A person approves anything that reaches a student.
3 things need you todayDone. Nothing went out without you.
Ask Jidoka
Samuel's fee payment is 3 weeks late"Hi Samuel, a quick reminder your payment is due. Need a payment plan? Just reply."Reply readyApproveSent
Daniel's enrolment is missing one formReply readyApproveSent
Tom asked about the March start dateReply readyApproveSent
0 of 3 done
We speak RTO.Works beside what you already run. Nothing to migrate.
USI
LLN
CoE
RPL
AVETMISS
CRICOS
Smart and Skilled
VET Student Loans
training.gov.au
Standards for RTOs 2025
Student management system
LMS
Payment plans
Intake dates
Education agents
Evidence packs
USI
LLN
CoE
RPL
AVETMISS
CRICOS
Smart and Skilled
VET Student Loans
training.gov.au
Standards for RTOs 2025
Student management system
LMS
Payment plans
Intake dates
Education agents
Evidence packs
The problem
Most RTOs Don't Lose Students in One Big Moment. They Leak.
The work is spread across the student system, inboxes and spreadsheets. Nobody has a clear view of who needs attention today, so the quiet cases slip.
1Enquiries go coldForms, emails and missed calls wait overnight or over the weekend. By the time someone replies, the applicant has enrolled somewhere else.
2Enrolment files stallUSI, ID, LLN and funding paperwork sit incomplete. Staff chase the same documents from the same students every intake.
3Fees drift overdueThe overdue report runs to hundreds of rows with no clear order, and half of it is already out of date.
Before JidokaWhat admin looks like at most RTOs today
In education, the most responsible system isn't the one that does the most on its own. Jidoka drafts, flags and prepares. Qualified staff stay responsible for anything that affects a student.
Built around ASQA's five AI principles
Governance
Human oversight
Secure information
Equity and access
Fit with the training product
ASQA does not certify vendors, and neither do we. Your RTO stays responsible for its obligations.
Read-Only by Default
We connect only where you say, and only to the fields a job needs. Writing back is a separate decision you switch on.
Nothing Sent Without Approval
Every message to a student is drafted, then approved by a person. Or it doesn't go.
A Full Audit Trail
What was flagged, what was drafted, who approved it and when. Ready for any conversation with a student or auditor.
Your Data Stays Yours
Records stay in the systems you run. Never pasted into consumer chat tools, never used to train a general model.
A note from ZariZariyat HasanCo-founder & CEO
A note from Zari
Most AI pitches to RTOs start with the technology. We start with Monday morning: the inbox, the overdue list, the enrolment file that's still waiting on a USI.
Jidoka is named after an old idea from Toyota's factories: let machines do the repetitive work, and have them stop and call a person the moment something needs judgement. That's the whole philosophy. Nothing we build sends to a student without someone on your team saying yes.
We're a small team in Sydney. If you get in touch, you'll talk to Sam or me. And if AI is the wrong answer for your problem, we'll tell you.
Most of my first conversations with RTOs start the same way: a team buried in follow-ups, and fair suspicion of anything with 'AI' in the name.
My job is to make the first step small and clear. We look at one process together, agree what a good result looks like, and put a one-page scope in front of you before anything gets built. No pressure, and no twelve-month platform.
If it isn't the right fit, I'll tell you straight. You'll always know who you're talking to and what happens next.
Follow one morning at Summit Training Institute, a synthetic RTO we built for demos. See the queue, the reason behind each item, the draft, the approval and the audit trail.
Do we have to replace our student management system?
No. Your student management system stays the record, and we do not migrate anything out of it. Jidoka sits beside it, reading course, student, fee and document status so it can flag and prepare work accurately. Writing anything back is a separate decision you switch on deliberately. By default, access is read-only.
Is this replacing our admin or admissions team?
No. It takes the repetitive half of the job: working out who needs attention, preparing the follow-up, chasing documents, pulling the weekly numbers. Your team keeps the conversations, the judgement calls and the difficult cases. The aim is that staff spend more time on the work they were hired for.
Is our student data safe?
It stays in the systems you already run. Nothing moves somewhere you have not approved, and nothing is copied into a place you cannot see or get back. We connect only where you say so, read-only by default, and only to the fields a job needs. Your data is not used to train a general model, and we never put student records into consumer chat tools. If you stop, your records are untouched.
Are we allowed to use AI in an RTO?
Yes, with proper governance. ASQA's principles for responsible AI in VET are about how you use it: strong governance, human oversight, secure information, equity, and fit with the training product. We build to that shape by default, which is why student-affecting decisions always stay with your people. We are not a compliance product and we do not certify anything. Your RTO remains responsible for its obligations.
How do we start, and what does it cost?
Start with a 30-minute discovery call about one process, usually enquiries, enrolment files or fee follow-up. Whatever you decide afterwards, you'll leave with the bottleneck named, a clear fix and the first step. If AI is the wrong answer for that process, we'll say so. If it's right, we scope one pilot so you can see it working before it goes near the rest of your operation. Price depends on scope, and you get it in writing on one page before anything is built.
Less Admin. Fewer Students Slipping. Staff in Control.
Book a 30-minute discovery call. We'll map one process with you and find where it leaks. Whatever you decide, you'll leave with a clear fix for your biggest admin bottleneck and the first step to get there.
