Loading…For IT, vocational, corporate and skills training: course batches, trainee records, course fees and certificates an employer can check. Built around a course, not a school year.
Training runs in courses that start when enough people sign up and end when the course ends. Software built around a school calendar fights that on every screen.
A course runs for eleven weeks, and the system only understands a year.
A trainee takes two courses at once, or comes back for a second one, and the record cannot express either.
A corporate client sends fifteen people and wants one invoice and one attendance report.
The certificate at the end is the product, and it is produced in Word.
An employer asks whether a certificate is genuine and there is no way to check.
Trainers are paid per session or per course, and the payroll assumes a monthly salary.
Trainee and trainer records, course batches, fees and the certificate that outlives the course.
Courses run as batches with their own start and end dates, days and times, independent of any academic year. A trainee sits in more than one at a time, or returns for another later, without becoming a second person in your records.
Numbered completion certificates are issued from the trainee's own record, with a public verification page, so an employer can confirm one is genuine without calling you. This is the part of your product that outlives the course.
Fee heads and structures, invoices generated in runs, payments recorded against them, concessions, refunds and late fines. Every reversal needs a reason and keeps its trail, so the books reconcile rather than merely balance.
Permissions are set per role and per person, and enforced on the server on every request. Hiding a button is not security here: a request crafted by hand gets the same answer as one that came from a click.
Full staff records with departments, designations and qualifications, one leave flow that marks attendance when it is approved, and Nepal payroll with PF, SSF, TDS and festival allowance.
Bulk import with a dry run first: validate, see exactly what would change, fix it in a grid, then commit. Guardian records are de-duplicated and Bikram Sambat dates are detected rather than mangled.
Your data is backed up nightly to storage held with a different provider in a different jurisdiction, encrypted before it leaves our servers, and we practise restoring it. A backup nobody has restored from is a hope, not a backup.
A course is priced as a package with instalments counted from the course start, rather than as a share of an annual fee, so an eleven-week course bills like an eleven-week course.
Your course catalogue and your certificate go in first. Everything else follows them.
Tell us how your courses run and what your trainees need at the end.
Send us the trainee and trainer records you already keep, in whatever form they are in.
We validate them before anything is written and show you exactly what would change.
Your courses, batch dates and fee packages are set up to match your schedule.
Trainee records, fees, attendance and certificates all run from the same place.
Show us how your training institute works today, registers, spreadsheets or another system, and we will show you what moving across actually looks like. No pressure, and a straight answer on price.