Association of multiple services to a single service request - Best practice

[Tommaso2]

Hi all,

I wonder if associating multiple services to a single service request is a best practice and why or why not.

E.g. 3 service requests to add a user to a specific group have been created for 3 different services and for each one the flow can be slightly different (creation of a different task, trigger of an additional email and so on), but logically the 3 service requests have been created for the same purpose, but different service.

Is it a best practice to create just one service request and allow the requestor to select the specific service to be associated (that triggers the specific flow) per each service request? So we would submit 3 times the same form, each time selecting and associating a different service.

Technically is doable, but I wonder if it is a best practice or it would be better to keep service requests singularly, one per each service.

If not, why?

Many thanks in advance

[pavani_paluri]

Hi @Tommaso2 ,

Separate service requests
Each service has its own request item.
Good because: clear ownership, easier reporting, and simpler to track SLAs.
Downside: users feel like they’re filling out the same form multiple times.

One service request with a service selector
A single request item, where the user chooses which service it applies to.
Good because: cleaner catalog, less duplication, easier for requestors.
Downside: fulfillment logic gets more complicated, harder to maintain if each service has unique steps.

What most teams do
If the services are truly different (different owners, reporting needs, or fulfillment processes), they keep them separate.
If the services are almost identical (same purpose, only minor variations like an extra email or task), they consolidate into one request item with branching logic.

Simple rule of thumb
Different service = different request item.
Same service with small variations = one request item with options.

So, technically you can consolidate, but best practice leans toward keeping them separate if the services are distinct. Consolidation is fine if you want to simplify the catalog and the differences are small — just be mindful that it can get messy to maintain over time.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[Tanushree Maiti]

Best approach  is to use a ServiceNow Order Guide. 

When to Use Order Guides:

• Multi-Item Requests: When a user needs to order a "bundle" of services or products.
• Shared Information (Cascading Variables): When the same information (e.g., User Name, Manager, Location) applies to multiple items, allowing data to flow from the guide to all included items.
• Rule-Based Bundling: When the items included depend on user input . a single RITM can be generated from from order guide.