Catalog task templates pre-fill sc_task records with assignment groups, descriptions, and other standard fields when someone orders a catalog item. You'll set up a reusable template that generates consistent tasks for fulfillment teams.
Why manual task creation breaks down
Without task templates, fulfillment teams manually create sc_task records after catalog orders come in. The person handling the request has to figure out the right assignment group, write descriptions from scratch, and set priority levels — all while the requester waits. This manual step introduces delays, inconsistent task details, and the occasional request that falls through the cracks when someone forgets to create the follow-up task.
How task templates automate fulfillment
A catalog task template is a pre-configured sc_task record attached to a catalog item. When someone orders the item, ServiceNow automatically creates one sc_task per sc_req_item using your template's field values. The template defines assignment group, short description, description, priority, and other task fields. You can attach multiple templates to one catalog item if different teams need to handle different parts of the fulfillment. The key insight: templates clone themselves per request item, not per entire request.
Building production-quality templates
A basic template sets assignment group and description. Production templates use variable substitution to pull catalog form data into task descriptions, set realistic due dates based on SLAs, and include clear instructions for fulfillment teams. Advanced setups use conditional templates (via workflow or flow) to create different task types based on what the user ordered. The best templates eliminate guesswork for fulfillment teams and provide enough context that tasks can be completed without going back to the original request.
Before you start
- •catalog_admin role or equivalent
- •Existing catalog item to attach the template to
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to the catalog item
Go to Service Catalog > Catalog Definitions > Maintain Items and open the catalog item that needs task templates. You need to configure templates at the item level, not on categories or the general catalog settings.
If you can't find the item in the list, use the Name or Sys ID filter — the list can be long in production instances.
Open the Task Templates tab
Click the Task Templates tab in the catalog item form. This tab shows existing templates and lets you create new ones. If you don't see this tab, you're likely missing the catalog_admin role.
Create a new task template
Click New to create a template record. The template form looks like an sc_task record because that's essentially what you're pre-configuring. Focus on fields that your fulfillment teams need to know before they start work.
Set the assignment group
Choose the Assignment group that should handle tasks created from this template. This is usually the most important field because it determines which team sees the work. Don't set an Assigned to individual unless you're certain that person handles all requests for this item.
Configure the descriptions
Fill in Short description with a template-friendly summary like 'Provision laptop access for ${requested_for}'. In Description, write detailed instructions for the fulfillment team. Use variable substitution (${variable_name}) to pull catalog form data into these fields automatically.
Set priority and due date
Choose appropriate Priority and State values. For Due date, either set a fixed offset (like 5 business days) or leave it blank to inherit from SLA rules. Priority should reflect the actual business impact, not just make everything 'High'.
Save and test the template
Click Submit to save the template, then test by ordering the catalog item from the service portal. Check that the resulting sc_task has the right assignment group, descriptions with proper variable substitution, and other fields populated correctly.
Best practices
Use variable substitution in descriptions to pull request data into tasks — ${requested_for}, ${request_number}, and catalog variable names work.
Don't set Due date to a specific calendar date in the template — it becomes stale and confusing when tasks are created months later.
Create separate task templates for different fulfillment teams rather than one generic template that requires manual sorting later.
Test your templates by actually ordering items — variable substitution errors and missing assignment groups only show up during real execution.
Set realistic Priority values based on actual business impact — if everything is High priority, nothing is.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue