Course
A course is a named piece of training somebody can attend: Forklift Safety, ISO 9001 Internal Auditor, Supervisory Skills. The list lives here, and the training module then plans, schedules and records attendance against it.
What it is for
A course has to exist as a record before anything can be done with it. A training need points at a course. A schedule runs a course on dates. Attendance is recorded against a course. An employee's training history is a list of courses. All of that needs one list with one spelling per course.
This screen is that list, and it is deliberately thin: a code, a name and a family. Everything about how a course is delivered, who runs it, what it costs and how long it takes belongs to the training module. See Training Course for that side of it.
Every field, in plain words
Course
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Course | The short code for the course. | FORK-SAFE | Required. Must be unique. |
| Name | The course written out as it appears on the calendar. | Forklift Safety and Operation | Required. Translations are kept per language. |
| Course Group | The family the course belongs to. | SAFETY - Health and Safety | Pick it from the list. See Course Group. |
| Block | Retires a course no longer offered. | Leave clear while the course runs. | Ticking it stops the course being offered on new schedules and needs. Employees who attended it keep their history. |
How to configure it
- Create the families on Course Group first.
- List the courses the client actually runs or buys. Last year's training calendar is the best source.
- Create each course with a code, the name as it appears on the calendar, and its group.
- Save, then set up the delivery detail in the training module on Training Course.
- Record which employees have already attended on Employee Courses, so the training history starts from what is known rather than from go live.
Scenario
We run the same course four times a year
One course record. The four runs are four schedules in the training module, each with its own dates, trainer and attendance list. Creating four courses would break the training history into four unrelated pieces.
What it is connected to
- Needs Course Group to exist first.
- Employee Courses records which courses an employee has attended.
- The training module reads the course throughout: Training Need, Training Schedule, Training Attendance, Training Assessment, Training Feedback, Training Bond and Training Course all point at a course created here.
If something looks wrong
- "The course list is empty when scheduling training" - no courses have been created, or all of them are blocked.
- "The same course appears twice" - two records with different codes. Keep one, block the other, and expect the training history to be split across both for past attendance.