Training institutes

How to digitize training institute management, one cohort at a time

A step by step plan for moving programs, cohorts, trainers and certificates out of separate spreadsheets and into one system, without stopping live courses.

· 5 min read

Most professional training institutes go digital in pieces. The course list lives on the website, each cohort has its own spreadsheet, trainers keep registers on paper or in a chat group, the accounts person has a separate fee file, and certificates come from a word processing document that someone edits and prints. Each piece works well enough on its own. The trouble starts when an employer asks how the five people they sponsored are doing, or an awarding body asks for a trainee's attendance from last spring, and three people have to open five files to answer.

This guide is for the centre manager or owner who wants training institute management in one place. It follows a fictional institute, Ashford Professional Institute, which runs accounting and IT programs from two training centres. For example, it has 9 live cohorts, 14 trainers and about 210 trainees. The numbers are illustrative, and the order of work suits most institutes.

Map your programs, cohorts and centres on paper

Every institute has a structure, even when it lives only in the manager's head. Put it on paper first, because every later step depends on it.

Programs and modules

A program is what a trainee signs up for, such as a certificate in payroll accounting or a networking foundation course. Most programs are made of modules. Ashford's payroll program has, for example, five: bookkeeping basics, employee deductions, payroll software, a practical project and a final assessment. List the modules of every program and mark which are compulsory and which are optional. A one-day workshop is still a program, with a single module.

Cohorts

A cohort, or batch, is a group of trainees who start a program together. Give cohorts a naming rule that tells staff what they are looking at: the program, the start month and the pattern. "Payroll March weekday" is far easier to read on a register than "Group 7". Agree the rule now, since renaming forty cohorts later is slow and invites mistakes.

Training centres and rooms

If you train in more than one place, decide what each location keeps for itself. Ashford's two centres share trainers, but each has its own rooms and its own front desk where fees are paid, so the institute treats them as separate locations that share some staff.

Move the records in this order

Trying to move everything in one weekend is a common reason a switch stalls. Ashford moved in four steps over about six weeks, and staff kept the old files open, read-only, until each step had been checked.

  1. The structure: the training year, programs, modules, live cohorts and rooms. Nothing else can be placed until these exist.
  2. The people who work there: trainers and office staff, each with what they are allowed to do. A trainer needs the registers and marks for their own cohorts, and the accounts person needs fees.
  3. Current trainees, imported from your spreadsheets and placed in their cohorts. Clean the sheet first, with one row per trainee, one column per detail, and the sponsor's contact on the same row as the trainee they pay for.
  4. Money: what each trainee or sponsor still owes, brought in as an opening balance. From that day on, new payments are recorded only in the new system.

Finished cohorts can wait. Put their spreadsheets in a folder nobody edits, and bring a past cohort across only if people keep asking about it.

Switch each cohort at a clean starting point

A cohort is easiest to move at the start of a module, when the register and the marks begin from zero. Moving halfway through a module means copying half a register by hand, and copied registers are where mistakes hide.

Ashford moved its weekday cohorts first and its weekend cohorts two weeks later. The two trainers who teach both patterns learned the new register on a quiet Tuesday before they had to use it on a busy Saturday. For the first fortnight the office checked every register at the end of the day. By then the gaps had stopped, so the check dropped to once a week.

Settle the certificate rules before anyone prints one

A certificate is the part of your work that trainees and employers keep. It is also the step institutes tend to leave until last, which causes trouble when a trainee finishes on a Friday afternoon and wants the certificate before leaving the building. Agree these points while you set up the system:

  • who may issue a certificate, and whose signature it carries;
  • what a trainee must meet first, such as an attendance threshold and a pass in the final assessment;
  • the wording for each program, and whether it lists the modules;
  • how an employer checks that a certificate is genuine;
  • what happens when a certificate was issued by mistake.

Old certificates keep their old numbers. Keep the register of past certificates safe, since people will ask you to confirm them for years, and start a new numbered series for everything issued from the new system. Attendance and assessment rules need careful wording of their own, and our guide to tracking attendance and assessment against certificate rules works through them with an example cohort.

Where SkoolBro comes in

SkoolBro is an education management platform for schools, academies, colleges and training institutes. Its screens use school words today, so a training institute maps its own terms onto them once and then works in its usual way. Ashford used this mapping:

Your wordIn SkoolBro
Training centreCampus
Training yearAcademic year
Program or courseGrade level
Cohort or batchClass section
ModuleSubject
TrainerTeacher, on a staff record
TraineeStudent
Sponsor or employer contactGuardian
AssessmentExam, with a paper for each module

Each new cohort starts with the modules of its program, and each module in a cohort has its own trainer. Trainers mark attendance on their phones for the cohorts they teach, and the register still saves when the training room's internet drops. Trainees, staff and opening fee balances come in from Excel or CSV files. The accounts person handles course fees, receipts and concessions, and each concession needs approval before it applies. Notices can go to a whole program or to one cohort, and staff at one centre can be limited to that centre. The setup of programs, trainee records and trainer allocation is covered step by step in managing courses, trainees and trainers.

Certificates use a template of the "other" kind, written in your institute's own wording. Each certificate gets a number and a code that anyone can check online, and you can revoke one issued by mistake. SkoolBro does not issue a certificate automatically when a trainee completes a program. Your office checks attendance and results, then issues it.

A few things a training institute may expect are not built yet. There are no course materials or video lessons, no online tests, and trainees and sponsors cannot pay fees online. Notices go by email and in the app, and text messages and WhatsApp are coming. The features section lists every module, and the pricing section explains the plans. To see how each organization's records are kept apart from every other's, read how SkoolBro keeps each organization's data safe.

Questions

Should we move finished cohorts into the new system?

Not at first. Move live cohorts and current trainees, keep the files of finished cohorts in a folder nobody edits, and bring a past cohort across only when people keep asking about it.

Can SkoolBro issue a certificate automatically when a trainee completes a program?

No. You write a certificate template in your own wording, and your office issues each certificate after checking attendance and results. Every certificate gets a number and a code that anyone can check online.

Our institute talks about programs, cohorts and trainers. Does it matter that SkoolBro uses school words?

You map your terms once: a program is set up as a grade level, a cohort as a class section and a module as a subject. Write that mapping on one page for your staff before anyone enters data.