How to Create a Problem Record in ServiceNow

Recommended Learning Path

How to Create a Problem Record in ServiceNow

 Step by Step

Table of Contents

An Incident helps restore a disrupted IT service. A Problem record is used when the support team needs to investigate why one or more incidents happened and how similar issues can be prevented or reduced.

For example, restarting a VPN service may resolve today’s Incident. But if employees experience the same VPN failure every Monday, the recurring issue may need deeper investigation through Problem Management.

If you are learning how to create Problem ServiceNow records, the most important skill is knowing when a Problem is justified, recording the issue clearly, connecting relevant Incidents, and validating the record before root-cause analysis begins.

Quick Answer: How Do You Create a Problem in ServiceNow?

In the documented standard interface, you can navigate to:

Problem → Create New

Complete the Problem form and select Submit.

You can also open an existing Incident and use Create Problem when that Incident requires deeper root-cause investigation.

A simple workflow is:

Identify recurring issue → Create Problem → Describe issue → Assign → Link Incidents → Submit → Validate

When Should You Create a Problem Record?

A Problem record becomes useful when an underlying cause needs investigation.

Examples include:

  • several Incidents showing the same failure,
  • a major Incident requiring root-cause analysis,
  • repeated application outages,
  • recurring network failures,
  • or a potential issue identified before a larger disruption occurs.

ServiceNow’s current Problem Management workflow specifically identifies recurring Incidents and major Incidents as common reasons to create a Problem.

Do not create a Problem simply because every Incident needs one. The Problem should represent an issue that requires deeper investigation or prevention work.

Start Your ServiceNow Learning Journey

Explore the ServiceNow Roadmap

Incident vs Problem: Know the Difference First

Before creating the record, understand what you are documenting.

Record

Main Question

Example

Incident

How do we restore service?

VPN is unavailable

Problem

Why is this happening?

VPN repeatedly fails every Monday

Incident Management is primarily about service restoration.

Problem Management investigates the underlying cause and looks for ways to reduce future disruption.

What Access Is Required?

For ServiceNow’s current documented standard creation process, supported roles include:

itil, sn_problem_write, admin, problem_admin, problem_manager, or problem_coordinator.

The permissions in your training or company instance may vary according to configuration.

Step 1: Open the Problem Form

Navigate to:

Problem → Create New

A new Problem form opens.

ServiceNow also supports creating a Problem from other sources, but manual creation through the Problem module is the clearest starting point for beginners.

Step 2: Write a Clear Problem Statement

The Problem Statement should describe the recurring or underlying issue clearly.

Weak example:

“Network issue.”

Better example:

“Corporate VPN authentication fails repeatedly every Monday morning for multiple users.”

The statement should identify the pattern that needs investigation rather than describe only one user’s Incident.

This is especially important when a Problem is created from an Incident. ServiceNow recommends reviewing inherited Incident information and updating the Problem Statement so it specifically describes the issue that requires root-cause analysis.

Step 3: Add a Detailed Description

Use the Description to add useful context.

For example:

“Network Support has received repeated VPN authentication Incidents during Monday morning login periods for the previous three weeks. Restarting the authentication service temporarily restores connectivity. Root cause is not yet confirmed.”

Useful details may include:

  • when the issue occurs,
  • which users or services are affected,
  • how frequently it happens,
  • temporary fixes already used,
  • and patterns noticed across related Incidents.

Do not claim a root cause before the investigation has confirmed it.

Step 4: Select Category and Subcategory

Choose the category that best represents the issue.

For example:

Category: Network
Subcategory: VPN

The exact choices vary between ServiceNow instances.

Correct categorization can make assignment, reporting, and future trend analysis easier.

Step 5: Select the Service or Configuration Item

If the affected service or component is known, select the appropriate Service, Service Offering, or Configuration Item (CI) where available.

A Configuration Item could represent an application, server, database, network component, or other managed item.

ServiceNow’s Problem form uses CI information to identify the component to which the Problem applies.

Choose the CI only when it genuinely represents the affected component.

Step 6: Assign the Problem

Select the appropriate Assignment Group.

For a recurring VPN issue, this might be:

Network Support

Then select an appropriate Assigned To user or Problem Coordinator if the responsible individual is already known.

The exact assignment process depends on the organisation’s configuration.

A useful principle is:

Assignment Group = responsible team

Assigned To = responsible individual

Step 7: Review Impact, Urgency, and Priority

If your Problem form includes these fields, evaluate them according to the actual business situation.

Impact considers the effect on business operations.

Urgency considers how much delay can be tolerated.

Priority helps indicate how quickly the Problem should receive attention.

Do not automatically set every recurring Problem to the highest priority.

Step 8: Create a Problem Directly from an Incident

Sometimes the easiest method is to start from an existing Incident.

Open the Incident that requires deeper investigation.

Use the context action:

Create Problem

ServiceNow can copy configured Incident attributes into the new Problem record. Which fields are copied can be controlled through a Problem Management system property.

This can save time, but do not submit the Problem without reviewing the inherited information.

An Incident description may say:

“User unable to access VPN.”

The actual Problem Statement may need to say:

“Recurring VPN authentication failures affecting multiple employees.”

The second version better describes the investigation.

Get Ready to Crack ServiceNow Interviews

Explore the ServiceNow Interview Guide

Step 9: Link Related Incidents

A Problem may represent multiple Incidents.

For example:

INC001: Employee A VPN failure
INC002: Employee B VPN failure
INC003: Department-wide VPN authentication error

Connecting related Incidents helps the Problem team understand the scale and pattern of the issue.

ServiceNow specifically supports adding multiple Incidents to a single Problem so teams do not create separate Problems for the same underlying issue.

Step 10: Submit the Problem

Review the record before submission.

Check:

  • Problem Statement,
  • Description,
  • Category,
  • affected service or CI,
  • Assignment Group,
  • Assigned To,
  • Impact and Urgency where relevant,
  • and related Incidents.

Then select Submit.

ServiceNow creates the Problem record.

Under the current documented state-management process, it initially enters New. If the required assessment information is already complete, the record can move directly to Assess.

What Happens After Problem Creation?

The applicable Problem lifecycle progresses through:

New → Assess → Root Cause Analysis → Fix in Progress → Resolved → Closed.

Creation is therefore only the starting point.

During later stages, teams can:

  • relate additional Incidents,
  • investigate the root cause,
  • document Cause Notes,
  • record a workaround,
  • create Known Error information,
  • create Problem Tasks,
  • and connect a Change Request when a permanent fix requires controlled implementation.

How Do You Validate the Problem Record?

After submission, reopen the record and check it carefully.

Verify that:

  • a Problem number was created,
  • the Problem Statement describes the recurring issue,
  • the correct group owns the record,
  • the correct service or CI is selected,
  • related Incidents are connected,
  • inherited Incident information is accurate,
  • and the expected State appears.

If assignment rules, Business Rules, Flows, or other automation exist in the training instance, confirm that they behaved as expected.

Validation prevents a badly described Problem from entering root-cause analysis.

Creating a Problem in Service Operations Workspace

ServiceNow also supports Problem creation through Service Operations Workspace.

A Problem can currently be created from a Problem list by selecting New, or directly from an Incident through the Create problem action.

In the workspace flow, complete the Details information and select Save rather than relying on the classic-interface Submit procedure.

The screen may look different, but the core reasoning remains the same.

Practical Example: Recurring VPN Failure

Suppose Network Support receives six similar Incidents over three weeks.

Users experience the same VPN authentication failure every Monday morning.

Restarting a service temporarily restores access.

A useful Problem record could contain:

Field

Example

Problem Statement

Recurring VPN authentication failures on Monday mornings

Category

Network

Subcategory

VPN

Assignment Group

Network Support

Description

Similar VPN Incidents reported repeatedly; temporary restart restores service

Related Incidents

Six matching VPN Incidents

Root Cause

Not yet confirmed

Notice that the Root Cause is not invented during record creation.

The Problem exists specifically because deeper investigation is required.

Common Problem-Creation Mistakes

Do not create a Problem for every Incident.

Avoid copying an Incident description without rewriting it around the broader recurring issue.

Do not write the suspected cause as a confirmed root cause without evidence.

Avoid leaving related Incidents disconnected when they clearly belong to the same Problem.

Finally, do not assume every ServiceNow instance has exactly the same fields or states. Forms, roles, assignment logic, plugins, and Problem models can be configured. ServiceNow also supports custom Problem models for different lifecycle requirements.

Build Your Learning Plan Around Practice

Start with three related Incidents describing the same VPN failure.

Create one Problem from an Incident, update the Problem Statement, connect the remaining Incidents, select the correct CI and Assignment Group, and validate the record.

Use this learning cycle:

Recognize → Create → Connect → Assign → Validate

Then continue the same Problem into Root Cause Analysis instead of creating another unrelated practice record.

FLM’s ServiceNow learning curriculum currently includes ITSM and a practical Problem Management project covering problem-lifecycle workflows, forms, and custom modifications.

FLM Perspective: Create Problems Around Patterns, Not Tickets

Use this simple framework:

Pattern → Problem → People → Proof → Proceed

Pattern: Are several Incidents connected?
Problem: What broader issue needs investigation?
People: Which team should own it?
Proof: What Incident history supports the Problem?
Proceed: Is the record ready for assessment and root-cause analysis?

This keeps Problem creation focused on investigation rather than simply generating another ticket.

Related Career Guides

  • What Is Problem Management in ServiceNow?
  • What Is Incident Management in ServiceNow?
  • How to Create an Incident in ServiceNow Step by Step
  • How to Assign and Reassign Incidents in ServiceNow
  • What Is Change Management in ServiceNow?

Conclusion

Creating a Problem record in ServiceNow starts with recognising that an Incident—or several related Incidents—needs deeper investigation.

Create the Problem manually through Problem → Create New or generate it from an Incident. Describe the broader issue clearly, connect relevant Incidents, identify the affected service or CI, assign ownership, and validate the saved record.

The strongest Problem records begin with evidence and a clear investigation question rather than an assumed root cause.

Once the record is created correctly, learners can move into assessment, Root Cause Analysis, workarounds, Known Errors, Changes, and permanent resolution.

Frequently Asked Questions

1.How do I create a Problem in ServiceNow?

A.Navigate to Problem → Create New, complete the Problem form, and select Submit in the documented standard interface.

2.Can I create a Problem from an Incident?

A.Yes. Open the Incident and use Create Problem. ServiceNow can copy configured Incident fields into the new Problem record.

3. When should a Problem be created?

A.A Problem is appropriate when an underlying cause requires investigation, particularly for recurring Incidents or after a major Incident.

4.What should I write in the Problem Statement?

A.Describe the broader issue that needs root-cause analysis. Avoid copying a single user’s Incident description without adapting it.

5.Can multiple Incidents be linked to one Problem?

A.Yes. ServiceNow supports associating multiple Incidents with one Problem when they represent the same underlying issue.

6.What State does a new Problem enter?

A.In the current documented best-practice lifecycle, a new record normally enters New. It may move directly to Assess when the necessary assessment information is already complete.

7.What are the ServiceNow Problem lifecycle states?

A.For the applicable current state-management model, they are New, Assess, Root Cause Analysis, Fix in Progress, Resolved, and Closed.

8.Should I enter the root cause while creating the Problem?

A.Only if it has already been genuinely established. Otherwise, record the observed issue and investigate the root cause during the appropriate Problem Management stage.

Build Your Career in ServiceNow

Read How to Become a ServiceNow Developer

First 2M+ Telugu Students Community