ServiceNow Learning Plan Explained

What Is a Learning Plan?

A Learning Plan is a structured curriculum that guides users through a series of learning activities. Which learning content types are available, such as courses, lessons and certifications, depends on the products licensed and the release, so confirm what your own instance includes. A Learning Plan organises these learning activities into a sequence. New IT staff might follow a Learning Plan that starts with ServiceNow fundamentals, then progresses to role-specific skills. Users complete activities in the plan and track their progress.

Learning Plans support organisational training and development. Rather than leaving staff to figure out what to learn, organisations define clear paths. This structured approach ensures consistent training and helps staff develop required skills systematically.

Where Learning Plans Live in ServiceNow

Where learning plans are managed depends on the licensed product and release, so confirm the location in your own instance. Organisations can create custom Learning Plans tailored to roles: an administrator Learning Plan might cover system setup and configuration; a user Learning Plan might cover common workflows and self-service options. Administrators assign Learning Plans to staff; staff complete activities in the plan and track progress through dashboards.

Learning Plans can be assigned in bulk: when a new team joins the platform, assign them a Learning Plan to get them trained. When someone changes roles, assign them the Learning Plan for the new role. This scalability makes Learning Plans useful for large organisations with frequent staff changes.

Worked Example: Onboarding New Users

When a new support desk analyst joins the organisation, they’re assigned a “Service Desk Analyst” Learning Plan. The plan includes modules on ServiceNow fundamentals, incident management workflows, customer communication and escalation procedures. As they complete each module, the system tracks progress. When they finish the plan, they’re ready to work independently on most common issues.

The Learning Plan uses built-in content where available and links to external resources where needed. Some organisations record videos or write documentation specific to their use of ServiceNow; these can be added to Learning Plans alongside ServiceNow’s standard content. This mix of generic and organisation-specific training helps new staff understand both how ServiceNow works and how the organisation uses it.

Common Misunderstandings

A common misunderstanding is thinking Learning Plans replace manager-led onboarding. Learning Plans support onboarding but don’t eliminate the need for a manager to help new staff understand their role, meet the team and get situated. A Learning Plan provides structured access to information; mentorship and management guidance remain essential.

Another confusion arises from mixing Learning Plans with Certifications. Certifications are formal validations that someone has learned something (they pass a test). Learning Plans are paths to learning. A Learning Plan might prepare someone to take a Certification exam, but completing a Learning Plan doesn’t automatically grant a Certification.

Related Concepts

Courses are collections of lessons on a topic. A Learning Plan organises Courses into a learning path. Lessons are specific learning modules: videos, documents, interactive exercises. ServiceNow’s learning module support varies; some content is built-in, some is linked from external sources. Understanding these pieces helps you build effective Learning Plans.

Assessments measure whether learning was successful. After completing a course, an assessment might test understanding. Learning Plans can include assessments, providing validation that learners understood the material. This feedback helps organisations know whether training is effective.

Building Effective Learning Plans

Effective Learning Plans start with learning objectives: what should someone know or be able to do when they finish? Clear objectives help select appropriate content and assess whether learning succeeded. A Learning Plan for new administrators might have objectives like “configure user roles,” “create approval workflows” and “manage service catalogues.”

Sequencing matters. Foundational content should come first: ServiceNow basics before advanced features, general concepts before role-specific details. Realistic pacing prevents overwhelm: new learners need time to absorb information. Including both conceptual content (why things work) and practical exercises (doing things) helps multiple learning styles.

Tracking Progress and Identifying Issues

Learning Plans provide tracking so organisations can see who is progressing through training and who is falling behind. Managers can follow up with staff who aren’t progressing, identifying barriers: maybe the content is unclear, maybe the staff member is too busy, maybe they don’t understand why the training matters. This visibility supports successful training.

Learning Plans also provide feedback about content effectiveness. If many people get stuck on a particular module, it might need improvement. If most people skip a module, it might not be relevant. Feedback from learning data helps organisations continuously improve training.

Who a learning plan is really for

A learning plan earns its keep when the people following it have a clear job to do afterwards. The plan that works is written for a named role, such as a service desk analyst taking their first live shift or a catalog owner about to edit their first order flow. A plan written for “everyone who uses the platform” tends to satisfy the training team and do little for the person in the chair. Start by deciding which tasks a learner must perform unaided by the end of the plan, then build the path backwards from those tasks.

That order also exposes plans that should not exist. If a learner only needs to know where one form lives, a short article or an onboarding checklist does the job. A plan is justified when the sequence matters, when prerequisites exist between topics, and when the same path will be assigned to many people over time.

Plan design	Suits	Watch for
One plan per role, assigned at role change	Teams with stable job families and a steady flow of new starters	Plans that drift from the role over time as tasks change, with nobody assigned to notice
A shared core plan plus short role add-ons	Organizations where many roles share the same platform basics	Core content that becomes a dumping ground, so every add-on has to repeat it
Project-specific plan for a rollout	A new module going live to a defined group within a fixed window	Plans that outlive the rollout and keep being assigned to people who never need the module
Refresher plan after a platform change	Existing users who must relearn one changed workflow	Learners who finish the refresher but are never checked on the changed task itself

Designing a plan from the task backwards

Many learning plans are built the other way around: the content exists, so it gets bundled. Reversing the order produces shorter, more useful plans and makes it obvious when a module has no purpose. The sequence below is the one most training owners find workable in practice.

1. List the tasks the learner must perform unaided at the end of the plan, and the people who will check that they can.
2. For each task, identify the knowledge it depends on, and the point at which a learner would be stuck without it.
3. Map those dependencies into an order, placing foundational concepts first and role-specific practice after them.
4. Attach a practical exercise to each module that uses a sandbox or a test record, not a slide that describes a screen.
5. Add an assessment only where a wrong understanding would cause real damage, such as approval handling or data access.
6. Pilot the plan with two or three learners who fit the role, and note every point where they had to ask a colleague for help.

Failures that make a learning plan look finished but do nothing

• The plan is assigned in bulk when people join, and nobody checks whether the tasks were then performed on the job.
• Modules describe the interface in detail but never walk through the approval or escalation path the learner will meet first.
• Content still shows an old screen after a change, so experienced learners learn to distrust the whole plan.
• Managers are not told which plan their team member is following, so they assign conflicting work in the same week.
• Completion is treated as the goal, which rewards clicking through modules at speed.

The fix for most of these is an owner who reviews the plan on a schedule and a sponsor who agrees with the manager which tasks the learner will take on after completion. Without those two, a plan can become a record of who clicked what.

How to tell a plan is working

Completion rates are the easiest number to read and the least informative. Pair them with two questions that show whether learning transferred. First, are the tasks the plan targets being performed by the people who finished it, and are they being performed without escalation? Second, have the errors that the plan was meant to prevent become less frequent in the queues those people work in? Compare the same measures for a group that did not follow the plan, where that comparison is fair.

Feedback from learners is also useful when it names a specific module. A comment that a step is out of date is worth more than a satisfaction score across the whole plan, and it should go to the content owner the same week.

Questions organizations ask before they assign a plan

Should contractors and temporary staff follow the same plan as employees?

Give them the same tasks and the same checks, but review the access and the data they will see. A plan that covers how to request access to a record needs a different ending for someone whose access is time limited. Keep one plan and add a short variant rather than building a second path that drifts.

How often should a learning plan be reviewed?

Review it when a module it depends on changes, and at a regular interval set by how quickly the platform and the process change. A plan for a stable process can go longer between reviews than one for a fast-moving service. The trigger that matters most is a change to a task the plan teaches.

Can a plan require a passing result before the learner is given access?

It can, and for high-risk tasks it often should. Be careful to tie the gate to a practical check, not a multiple-choice quiz alone, and make sure there is a route for a learner who needs more time without penalizing them.

What is the difference between a learning plan and a knowledge article?

A plan sequences learning for a person over time, with checks along the way. An article answers one question at the moment someone needs it. Many good plans link to articles for reference, which keeps the plan short and lets the article be updated without touching the sequence.

Next step if your onboarding relies on a plan that nobody owns

If plans have been assigned for years without an owner, start with a short audit: which plans are assigned, to which roles, and whether the tasks they teach still match the work. Retire what no longer fits before adding new content. For the role-based design approach, the role-based training plan article covers the structure in more depth, and the user training assessment piece covers measuring readiness beyond attendance. The employee onboarding guide shows how onboarding work is designed around roles.

Learning plan assignment: tables, roles and values to check

A learning plan is an ordered set of learning activities that an administrator assigns to people, typically by user or by group. The deciding fact is that assignment rests on ordinary platform records, so who receives the plan and who sees the results is a user and group question before it is a content question.

These are common out-of-box records and roles that learning assignment relies on. Check them on your own instance and release, because labels and defaults change between releases.

Item	Common name	Why it matters for a plan
People table	sys_user	Each learner is a user record, so a plan can only follow people who exist here.
Group table	sys_user_group	A group is the natural unit for a team that starts together.
Membership table	sys_user_grmember	Keeping membership current is what keeps a group-based plan pointed at the right people.
Fulfiller role	itil	Often held by service desk analysts, so a plan written for that job tends to target the people who hold it.
Knowledge table	kb_knowledge	Where a short article lives when the need is a single answer and not a sequence.

Example (hypothetical): a service desk team starts four analysts on the same Monday. Where your release supports assigning a plan to a group, the plan owner creates one group for the cohort, adds the four user records to it, and assigns the plan to the group instead of to four individuals. Six weeks later a fifth analyst joins mid-cohort and is added to the group, and the owner checks that the new member can see the same plan.

For onboarding that mixes learning with access and equipment steps, see employee onboarding and lifecycle events. The wider programme around a plan is covered by training and adoption services and user adoption and training.

Who should own a learning plan after it goes live?

Name one person by role, usually the training lead or the team manager, and record that name beside the plan. Without an owner, content goes stale and nobody notices when a changed screen no longer matches the modules. Review the plan whenever the process it teaches changes.

What should I check first when a learner cannot see their plan?

Check that the user record is active, that the person belongs to the group the plan was assigned to, and that the plan is in a state that lets learners see it. Then impersonate a sample user from the same group to see what they see.

How do I report on who finished a plan?

Start from the list of assigned users, then filter by group so each manager sees only their own people. Agree what counts as finished before the first report, and pair it with a check on the job, since completion alone shows clicks, not skill.