The basics: classes, sessions and learners
Four words to know before anything else, why a class and a session are two different things, and how that shapes the way Skovrum works.
Your words may differ. Each workspace can choose its own words: a class might be a cohort, program or group, a learner a participant, trainee or new hire, a session a module or lesson. These guides use the default words. The steps are the same whatever your workspace calls them. Change your workspace's words
Almost everything in Skovrum is built from four ideas. Learn these and the rest of the app follows from them.
| Word | What it is | For example |
|---|---|---|
| Class | One run of training, from its first day to its last | New Hire Onboarding, Group 14: ten days in October |
| Session | One dated meeting of a class | Day 3: Wednesday, 9:00 to 12:00 |
| Learner | A person being trained. Learners never sign in. | Maya, a new support agent in Group 14 |
| Trainer | The person who runs a class or a session | You, if you're teaching Day 3 |
Your workspace may use other words, such as program for class or module for session. The ideas stay the same. See Your workspace may use different words.
A class and a session are different things
A class is the whole run. A session is one day of it. A two-week onboarding is one class with ten sessions; a one-off workshop is one class with a single session.
They're kept separate because different things belong to each:
Kept on the class: the whole run
- Roster: who's enrolled
- Curriculum: what should be covered
- Certifications: what learners can earn, and their scores
- Primary trainer: who's responsible overall
- The report: progress across every day
Kept on Day 3: Wed, Oct 7
- Attendance: who came that day
- Topics covered that day
- Notes and observations written that day
- Who led it, if not the primary trainer
- The survey learners fill in afterwards
Why Skovrum is set up this way
You teach one session at a time. During training you work in the session in front of you: today's topics, today's attendance, today's notes. The session screen shows only what you need for that day, so it stays quick to use while you're teaching.
Progress is judged over the whole class. One good or bad day doesn't decide whether someone is ready. Each session's attendance, notes and ratings add up on the class and on each learner, so the class report and the certification decisions look at the whole run.
Plans change, and your notes follow. Because notes belong to the session, they move with it. If Day 3 moves to Thursday, its notes and attendance move too. If a colleague covers Day 3 for you, they lead that session without taking over the class.
People outlast classes. A learner has one profile, however many classes they join. Someone who finishes onboarding in October and takes a workshop next spring keeps a single history, so the next trainer or their manager sees the whole picture. See The learner profile.
Write it once
Because of this structure, nobody copies anything. You write an observation about Maya during Day 3, and it appears in that session, on Maya's profile, in the class report and in her handoff packet when training ends. You wrote it once, in the session where it happened.
The one exception is a private note: only you see it, and it never appears in a report.
Where to go next
- How everything connects goes further: courses, certifications, the shared lists every class uses, and who can see what.
- Find your way around shows where these things live on screen.
- Then pick your reading path: Your first week as a trainer, For managers and supervisors or Set up your workspace.