Skip to main content

Getting Started: Role-Based Training

Learn how to build, assign, and track training for each Role in Opus, so every team member has the skills their position needs.

Written by Ben Brunken

Role-Based Training gives each team member the skills their position needs, then builds on them as they grow. Build one Module per Role, assign it automatically by Role, and track progress Role by Role.

✅ Before you start: Admins, and Managers whose Role has the Create Content permission, build training in the Opus dashboard.

Automations and Paths need the Manage Library and Update Automations and Library Access permissions, which Admins have by default.

Table of Contents:


Plan Your Role-Based Training

Start with the basics, then add depth over time. Most Role-Based Training grows in two phases:

  • Core skills: what a team member needs to work their position on their own.

  • Levels and cross-training: the next skill level in the same Role, or the skills of another position or station.

To plan the first phase:

  1. List the Roles that need their own training.

  2. Write down the core skills for each Role.

  3. Group those skills into topics you can build training around.

💡 Keep onboarding separate: Build New Hire Onboarding as its own Module, and keep Role-Based Training in separate Modules. You can then assign onboarding once to every new hire and move each team member into their Role's training when they finish.

➡️ Learn more:


Build Training for Each Role

Build one Module per Role, around one learning outcome: what a team member in that Role can do when they finish. Fill it with Courses, Check-ins, and Resources that get them there.

Use each content type for the job it does best:

  • Show: demonstrate the task with short videos and photos in a Course, or a Resource your team can come back to.

  • Tell: explain the steps and the reasons behind them in a Course.

  • Do: have a Manager watch the team member perform the task in a Check-in.

  • Review: confirm what stuck with quiz questions in a Course, and sign off on the skill in a Check-in.

💡 Start with what you have: Add your existing SOPs and job aids as Resources first, then replace them with Courses as you go.

🎯 Example: A "Line Cook" Module holds short Courses on station setup, food safety, and each menu item, a Check-in where a Manager watches a full ticket from order to plate, and the recipe cards as Resources.

➡️ Learn more:


Assign Training by Role

Set up assignments once, and Opus keeps the right training going to the right Roles as your team changes.

Assign Core Training with Automations

Create an Automation on each Role's Module so every team member in that Role gets it, including new team members as they join. Automations can also select by Location, Department, Brand, Franchise, Region, and hire date.

Build Levels and Cross-Training with Paths

A Path assigns the next Module when a team member completes one, so each level unlocks after the one before it. Add a Time delay step to space levels out, or a Filter step to send the next Module only to certain Roles.

Use a separate Path for cross-training, starting from the Module that finishes a team member's core training.

Keep Skills Fresh

Check that your team still remembers what they learned, not just that they finished it once:

  • 30, 60, and 90 day Check-ins: assign a follow-up Module with a Check-in using an Automation set to Days after hire.

  • Refreshers: turn on Auto reassign in an Automation to reassign core training at the interval you set.

  • Knowledge Checks: send daily quiz questions from Courses each team member has completed.

➡️ Learn more:


Track Progress by Role

Go to Reporting and open the User Completion Grid. Choose the Role's training under Content, then filter by Roles to see where each team member stands.

Ask Managers what they see on shift, too, and update your training where the grid and the floor don't match.

➡️ Learn more:


FAQ

Can different Locations get different training for the same Role?

Yes. Build a Module for each version, then create an Automation that pairs the Role with the Locations that should get it.

What happens when a team member changes Roles?

When you add a new Role to their profile, Opus checks your Automations again and assigns that Role's training.

How often should I update Role-Based Training?

Review it at least once a year, and whenever a process, menu, or piece of equipment changes.

Did this answer your question?