Appearance
Driving School Overview
The Driving School module manages the full learner lifecycle: product setup, student intake, enrollments, lessons, assessments, permit applications, certificates, payments, waiting lists, follow-ups, and agent commissions.
Use this module when the business sells driving courses or permit-related services and needs one operational view of training progress, student balances, authority money, certificates, and follow-up work.
How The Module Is Organised
Driving School has two main work areas:
- Setup defines driving products and reviews the vehicles that can be used for scheduling.
- Operations manages students, enrollments, lessons, assessments, permit applications, certificates, payments, waiting list entries, follow-up tasks, and commissions.
The student record itself comes from the party/client register. Driving School adds the training context: products selected, progress, payment plan, instructor activity, permit status, and follow-up history.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Products | Driving School -> Setup -> Products | Configure driving courses, permit services, pricing, lesson rules, authority charges, and commission behavior. |
| Students | Driving School -> Operations -> Students | Review or select party/client student records and driving context. |
| Enrollments | Driving School -> Operations -> Enrollments | Create student enrollments, track course progress, balances, owner agent, and status. |
| Lessons | Driving School -> Operations -> Lessons | Schedule lessons, assign instructor and vehicle, and record attendance. |
| Assessments | Driving School -> Operations -> Assessments | Record theory, practical, mock, or completion assessments. |
| Permits | Driving School -> Operations -> Permits | Track permit applications and authority money where applicable. |
| Certificates | Driving School -> Operations -> Certificates | Issue completion certificates after requirements are met. |
| Payments | Driving School -> Operations -> Payments | Record student payments and authority-payment handoff context. |
| Waiting List | Driving School -> Operations -> Waiting List | Track prospects or students waiting for availability. |
| Follow-ups | Driving School -> Operations -> Follow-ups | Create payment, lesson, permit, visit, or general follow-up tasks. |
| Commissions | Driving School -> Operations -> Commissions | Review agent commissions linked to ownership and payments. |
Standard Workflow
A typical flow is:
- Configure driving products with vehicle class, transmission, lessons, pricing, government charges, and enrollment rules.
- Confirm training vehicles are active and correctly classified.
- Register or select the student.
- Create an enrollment for the selected product.
- Record payments and keep the payment plan current.
- Schedule lessons, assign instructor and vehicle where needed, then record attendance.
- Record theory, practical, or mock assessments.
- Create permit applications where the product includes authority charges.
- Issue certificates after completion requirements are met.
- Use follow-up tasks and waiting lists to manage students who are not ready to progress.
- Review and pay agent commissions where commission rules apply.
Key Business Concepts
Driving product: The item sold to the student, such as a course, permit service, bundle, or other driving-school service. It defines class, transmission, lessons, pricing, and optional authority charges.
Enrollment / student subscription: The learner's enrollment on a product. It tracks agreed fee, amount paid, balance, sessions completed, status, assigned user, owner agent, and payment progress.
For a concrete learner journey, see Learner Enrollment To Certificate.
Authority charge: Money collected from the student on behalf of a permit authority. This is not school income. It is held separately until paid out through the authority payment workflow.
Owner agent: The user who receives commission for a student. The owner should be assigned before the first payment because commission records can lock owner changes.
Follow-up task: A dated action for staff, such as a payment reminder, missed lesson follow-up, permit follow-up, call, visit, or general note.
Operational Controls
Driving School depends on good sequencing. Users should avoid issuing certificates or progressing permit work when enrollments, lessons, assessments, payments, or authority charges are incomplete.
Use these checks before moving a student forward:
- The selected product is active and allows enrollment.
- The student has the correct subscription and assigned owner where commission applies.
- Payment amounts match the product pricing rules.
- Lessons and attendance are updated before assessments and completion.
- Authority charges are collected before paying the permit authority.
- Follow-up tasks are closed, rescheduled, or clearly documented.
Financial Impact
Driving payments can split into school income and authority payable. Discounts reduce the income side, not the authority payable side. Authority payments later clear the payable when the collected authority money is paid out.
This distinction helps finance users understand why a student payment may not all appear as driving-school income.