Service catalog best practices
Quick answer
Design catalog items people can complete without help, and fulfilment that does not depend on heroics.
Key takeaways
- Name items in user language, not system language
- Default everything you can from the user record
- Reference variables prevent free text cleanup later
- Retire unused items, catalog bloat hurts findability
Write for the requester
Name items the way users describe the need, not the way IT names systems. Ask only for what fulfilment genuinely requires, and default everything you can from the user record.
Variables and reuse
Use variable sets for repeated blocks, keep variable names stable because flows and reports depend on them, and use reference variables so free text does not create data cleanup work later.
Fulfilment design
The form is the easy part.
- Model the fulfilment steps as tasks so work is visible and measurable
- Set realistic delivery times and publish them on the item
- Review abandoned submissions, they usually indicate confusing questions
- Retire items with no requests in a year, a bloated catalog hides the useful items
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What signals a confusing catalog item?
- A. High request volume
- B. High abandonment on the form
- C. Many variables sets
- D. Long delivery time
Show answer
B. High abandonment on the form
People starting and not finishing means the questions are unclear.
Which variable type reduces later data cleanup?
- A. Single line text
- B. Reference
- C. Multi line text
- D. Label
Show answer
B. Reference
Reference variables store real records instead of typed strings.