Explain the difference between an Incident, a Problem, a Change Request, and a Service Request.

Why This Comes Up in Interviews

This question tests your ITIL fundamentals. Every ServiceNow admin and developer needs to know these four record types cold — they're the backbone of ITSM.

The Four Pillars

• Incident: Something is broken or not working as expected RIGHT NOW. Focus: restore service as quickly as possible. Not about finding root cause — just get things working again. 'The printer on floor 3 isn't printing.'
• Problem: The investigation into WHY incidents keep happening. Focus: find the root cause and eliminate it permanently. 'Floor 3 printer fails every Monday because the print spooler service crashes during the weekly backup.'
• Change Request: A planned modification to the IT environment that goes through approval and risk assessment. Focus: minimize disruption while implementing necessary changes. 'Schedule a maintenance window to move the print spooler to a separate server so the backup doesn't crash it.'
• Service Request: A standard, pre-approved request for something the user needs. No break/fix, no investigation, no risk assessment — just fulfillment. 'I need a new toner cartridge for the floor 3 printer.'

A Scenario That Connects All Four

// MONDAY 9:00 AM
// 15 employees report: 'I can't access the CRM application'
// → 15 Incidents created (INC0045001 through INC0045015)
// → Service Desk applies workaround: restart the app server
// → All 15 incidents resolved

// TUESDAY 9:00 AM
// Same thing happens again! 12 new incidents.
// → Service Desk creates a Problem (PRB0002001)
//   'CRM application crashes every morning around 9 AM'
// → Problem team investigates: the database connection pool
//   exhausts at peak login time because the pool size is too small

// WEDNESDAY
// → Problem team creates a Change Request (CHG0003001)
//   'Increase CRM database connection pool from 50 to 200'
// → Change goes to Change Advisory Board (CAB) for approval
// → Approved for Thursday night maintenance window

// THURSDAY NIGHT
// → Change implemented, tested, closed successful
// → Problem resolved, linked to Change
// → All related Incidents auto-updated

// MEANWHILE (unrelated)
// → Employee submits a Service Request: 'I need CRM admin access'
//   (RITM0006001) — goes through standard approval workflow

Key Relationships

• Multiple Incidents can be linked to one Problem
• A Problem can generate a Change Request as its fix
• A Change Request resolves the Problem, which closes the Incidents
• Service Requests are independent — they're about fulfilling needs, not fixing issues