How to choose a management system for home tutoring and juku
Choose management software for home tutor dispatch and juku operations by testing matching, lesson records, parent reports, tutor pay, and personal data controls.
Home tutor dispatch services and juku have substantial work around each lesson. The agency receives an enquiry, confirms the student’s needs, selects a tutor, and arranges the time. After the lesson come the teaching record, parent update, tutor pay, and next booking. When choosing a management system, examine whether this complete flow can continue without losing information. A long feature list says little about the handoffs your staff perform every day.
Begin by drawing one lesson from your own operation on paper. Include the path from enquiry to first lesson, a normal reschedule, an absence, a tutor change, and service closure. At each stage, name the person who enters information, the person who approves it, and the person who communicates with the family. Ask every vendor to demonstrate this same case. You will then compare candidates under equal conditions.
Keep tutor matching and scheduling on one record
Subject and school year are only part of tutor matching. The agency may need teaching area, online availability, travel time, preferred weekday, school curriculum, and the family’s communication language. Search results built from stale details lead to poor offers. Look for a flow where tutors update availability and the agency checks what becomes visible. Keep the date and author of each change.
Travel time matters for in-person dispatch. A tutor cannot finish in Setagaya at 17:00 and begin in Yokohama at 17:30. When a system holds addresses, access needs strict limits. A scheduler may only need an area for early matching. The tutor can receive the necessary visit details after confirmation. Test how the system reveals and withdraws that information.
| Operation | Demonstration to request | Condition to avoid |
|---|---|---|
| Trial lesson | Follow enquiry, tutor candidates, consent, and result on one student record | Student names differ between the sales sheet and lesson calendar |
| Recurring lesson | Create a schedule with conflicts, closure dates, make-up lessons, and time zones | A coordinator finds clashes by sight alone |
| Tutor change | Record reason, handover, family approval, and removal of the former tutor’s access | A former tutor continues to see student information |
| Lesson report | Move through tutor submission, senior review, approval, and parent delivery | Unreviewed wording sends automatically |
| Tutor pay | Build pay from delivered lessons, cancellation rules, travel cost, and correction history | Finance rebuilds the month in another sheet |
| Personal data | Show consent, access, export, deletion, and activity history | The agency cannot explain who viewed a record |
Use delivered lessons as the source for reports and pay
Separate a confirmed booking from a delivered lesson. After delivery, the tutor records the duration, teaching focus, next task, and any cancellation status. A senior staff member completes the required review and approves the parent-facing update. When tutor pay begins from that same delivery record, the agency reduces cases where a report says the lesson happened while the pay sheet marks an absence.
The parent update should state what was covered, the evidence observed, the current difficulty, and the next action. Artificial intelligence may assist with a draft. Agency approval should happen before delivery. Compare the draft with the original teaching record and check for another student’s details or internal comments. Preserve the approver’s name and time.
Test tutor pay and billing rules through exceptions
Check tutor-specific rates, lesson length, travel expenses, late cancellations, group lessons, and withholding treatment. Ask a qualified tax adviser to settle tax questions. The system should apply the agency’s chosen rules consistently and preserve values before and after a correction. Use a case with five month-end changes. Ask who approves each one and how the final payment list changes.
Parent billing and tutor pay remain separate records even when the amounts resemble each other. Lesson packs, monthly tuition, and pay-as-you-go services may recognise revenue at different times. Tutor payment follows the contract. Linking both records to a lesson identifier lets finance explain the difference. If software is priced per active student, define active status and the treatment of paused students before signing.
Test personal information and safety controls in daily use
Many students are minors. Records may include an address, school, grades, or family circumstances. Separate access by job responsibility. Tutors should see the information needed for their assigned students. End access when a tutor leaves or the assignment changes. Record the parent’s permission, who collected it, the time, and the processing it covers. Seek professional review of your duties under Japan’s Act on the Protection of Personal Information and your own security measures.
- Export student data and confirm that core fields and attachments remain readable.
- Disable a tutor account and verify that assigned student access ends immediately.
- Correct a teaching record and confirm that the prior value, reason, and editor remain visible.
- Withdraw a parent’s consent and verify that the covered processing stops and reaches the responsible staff member.
- Create a failed parent-report delivery and find the retry path and owner of the unresolved item.
Run a four-week trial shaped like a busy period
Include in-person and online delivery, recurring and one-off lessons, Japanese and English communication, and different tutor rates. Measure coordinator time, schedule corrections, report approval time, and pay corrections from before the trial. Ask tutors and parents to use their phones, then record each point where they hesitate. Keep vendor questions and answers in one decision log.
Test the end of the relationship during the trial. Export all trial records. Remove one staff member’s access. Close one fictional student account under the proposed retention policy. Confirm what remains, what is deleted, and who can authorise each step. An exit test gives the agency evidence about control of its records before a large migration makes the answer expensive.
- Does a small home tutoring agency need a management system?
- Student count alone cannot decide. Measure time spent copying records, changing schedules, checking reports, and correcting pay. The point where shared sheets can no longer control those tasks safely is a concrete signal to review a system.
- Can existing spreadsheet data be migrated?
- Give each vendor a sample and map students, tutors, lessons, consent, and pay rates. Import a small group first. Reconcile record counts and important fields before moving the complete file.
- Can parent reports be sent automatically?
- Use a flow that sends after agency approval. A draft can contain an error or internal information. Record the approver, approval time, and exact version delivered.