What it means
Service request management handles predefined, user-initiated requests through clear models, approvals, fulfillment steps, communication, and measurement.
Why it matters
Treating requests as incidents obscures demand and priority, while poorly controlled fulfillment can grant access, expose data, or create untracked configuration changes.
Practical focus
- Define request models with eligibility, required information, authorization, fulfillment, target times, and closure evidence.
- Automate stable low-risk steps while preserving identity, approval, logging, and exception handling.
- Review request demand and failure patterns to improve self-service, knowledge, capacity, and security.
- Preserve this evidence: Retain approved definitions, decisions, operating records, exceptions, test results, and change history that show how Service Request Management Practice works over time.
- Exercise this failure scenario: A self-service request bypasses required authorization and automatically grants access to a sensitive service.
Common mistakes
- Using Service Request Management Practice as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a diagram, policy, tool screen, or meeting as proof that Service Request Management Practice operates consistently in real work.
- Optimizing for a one-time review while leaving normal operating decisions, exceptions, and handoffs uncontrolled.
- Testing only the expected path and never rehearsing this failure condition: A self-service request bypasses required authorization and automatically grants access to a sensitive service.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: