ServiceNow ITSM Modules Explained (with Examples)
A clear breakdown of every core ServiceNow ITSM module — Incident, Problem, Change, Request, Knowledge, and CMDB — and how they connect.
3 min read
ServiceNow ITSM Modules Explained
ServiceNow ITSM is best understood as a set of connected processes that share one database. Each module owns a distinct job, but they constantly hand work to one another. This guide gives you a working mental model of each, and points to the deep-dive for every topic.
New to the platform? Start with What is ServiceNow ITSM? first.
The task table: the common backbone
Almost every ITSM record — incidents, problems, changes, catalog tasks — is stored in a table that extends the Task table. That shared parent is why they all have familiar fields like Number, State, Assignment group, Assigned to, and Work notes. Learn the Task table once and you understand the shape of every process record.
The main exception is Knowledge: knowledge articles live in the kb_knowledge table and do not extend Task.
Incident Management
Goal: restore normal service as quickly as possible when something breaks.
An incident is an unplanned interruption or degradation of a service. Incidents are prioritized using Impact × Urgency, routed to an assignment group, worked through a state model (New → In Progress → On Hold → Resolved → Closed), and — when they are high-impact — escalated through Major Incident Management. Incident is the highest-volume, most time-sensitive process in ITSM.
Problem Management
Goal: find and eliminate the root cause behind incidents.
Where incident management is about speed, problem management is about permanence. A problem investigates why incidents happen, records a workaround, documents a known error, and often triggers a change to implement the fix. Problems deliberately are not rushed — the aim is a lasting solution, not a fast close.
Change Management
Goal: introduce changes to the IT environment with minimal risk.
Change management adds control: change types (standard, normal, emergency), change models, risk assessment, conflict detection against blackout and maintenance windows, and approvals through a Change Advisory Board (CAB). Modern ServiceNow uses configurable change models and approval policies so low-risk changes move fast while risky ones get scrutiny.
Request Management & Service Catalog
Goal: let people order services and items through a self-service storefront.
The Service Catalog presents catalog items, record producers, and order guides. When a user orders something, it creates a Request (sc_request), one or more Requested Items (sc_req_item / RITM), and Catalog Tasks (sc_task) for fulfilment. Variables, variable sets, and Catalog UI policies control the order forms; Flow Designer handles the fulfilment workflow.
Knowledge Management
Goal: capture solutions once and reuse them everywhere.
Knowledge bases hold articles that resolve issues directly or deflect them before a ticket is ever created (via contextual search on forms and portals). Articles move through a publish/retire lifecycle with approvals, and roles like knowledge_manager and knowledge_admin govern who can contribute and publish.
Configuration Management Database (CMDB)
Goal: know what you have and how it connects.
The CMDB stores Configuration Items (CIs) — servers, applications, services — and the relationships between them. Those relationships power dependency views and impact analysis used by Incident, Problem, and Change. The Identification and Reconciliation Engine (IRE) keeps it clean by preventing duplicates and protecting trusted data sources, and CSDM provides the standard structure.
How they connect (the big picture)
| Trigger | Leads to |
|---|---|
| Repeated incidents | A problem investigation |
| A problem needing a fix | A change request |
| A change altering an asset | A CMDB update |
| A resolved incident/problem | A knowledge article |
| A user needing something | A catalog request |
This interconnection is exactly what the CIS-ITSM exam tests: not just each module in isolation, but how work flows between them.
Deep-dive into each module
- Incident Management
- Problem Management
- Change Management
- Service Catalog & Request Management
- Knowledge Management
- CMDB & Configuration Management
Then test what you know with a free practice test.
Ready to test yourself?
Take a free CIS-ITSM practice test with instant scoring and explanations.
Go to practice tests →