The Drone Training Management System is an integrated operating platform for training institutions. An online store, student enrolment, class scheduling, teaching attendance and financial settlement all live in one back office — from selling a course to settling at course end, one chain runs through, with no numbers shuttled between four or five spreadsheets.
Project background
A drone training institution has a longer business chain than a normal shop: sell courses online, open classes offline, students clock in, teachers are scheduled, and channel and referral commissions are settled. Any link left on a spreadsheet becomes a reconciliation that never closes. Change a course price and the mini program still shows the old one; a student switches class and the attendance sheet is out of date; at month end the recruitment, referral and channel sheets do not agree.
The client wanted “sell — enrol — schedule — teach — settle” inside one back office, and that back office has to drive the front-end mini program directly: change a price or open a class and the student side follows at once, without editing both sides.
Design goals
- Store and courses joined up — a course is a product: price, stock and listing status share one source in the back office and the mini program, so changing one place gets both right.
- Scheduling that runs — class opening, class, class dates, teacher and assistant are configured on one sheet, and students can book by class straight away.
- Attendance you can trace — clock-ins match student attendance records one to one, and a class change leaves a record.
- Money that adds up — enrolment fees, channel commission and referral commission are collected by rule under one definition, so month-end no longer reconciles three sheets.
System architecture
The system is organised into nine areas — system administration, infrastructure, payment management, daily operations, student management, teacher management, the store, teaching arrangements and finance — with permissions, content, transactions, academic affairs and finance each owning their ground.
Core modules
Below, module by module. Each maps to the part of an institution’s day that consumes the most people’s time.
Permissions and organisation
Users, roles, menus, departments, positions and dictionaries are all present, with menu permissions ticked to button level and data permission selectable across five bands: all, own department and below, own department, specified departments, or self only.
Store and courses
Training courses are managed as products: price, stock, listing status, category, brand, attributes and professional level are maintained separately, and courses are sold by job type and by five-day, ten-day or twenty-day session.
Orders and after-sales
Orders are filtered by status and channel, with source, payment method, amount paid and delivery type on one line; refunds and transaction settings form their own group, so an odd order does not mean scrolling back through chat logs.
Students and enrolment
The student list and enrolment records are maintained separately, linking student account, mobile number, source channel and enrolment history; historical students can be imported in bulk instead of created one by one.
Classes and scheduling
Class management pairs the class name, course product, teacher, teaching assistant and start and end dates; one course can open several classes, and students book their class time on their side.
Teaching attendance
Student class records correspond to class change history; teaching clock-ins are counted by class and session, so who attended, who missed and who switched class are all on record.
Marketing and distribution
Banners, article categories and content management support the home page; distribution and shop management cover channel recruitment, with referral relationships and commission rates filed in the system.
Financial settlement
Enrolment fees, channel sales commission and referral commission are counted separately yet reconcile; with one definition of settlement, the export can go straight to finance.
Interface examples
The screenshots below are from the live system; test data has been anonymised.
Outcome
- Courses, prices, stock and listing are maintained in one place, with the mini program and back office on the same source; a price change no longer means two edits.
- Opening a class generates a bookable session, and students pick their date in the mini program, so academic staff no longer phone each one to confirm.
- Enrolment fees, channel commission and referral commission are collected by rule, turning month-end settlement from reconciling three sheets into exporting one.
- Menu and data permissions are controlled in five bands, so recruitment, academic affairs and finance each see their own data and over-reach is blocked at the system level.
Need a similar management system?
We have delivered in retail, property, education, healthcare and finance. Tell us your own scenario and we will start from there.