Execution Plans An execution plan describes how a catalog item is procured, configured, and installed. Execution plans enable you to describe simple, linear processes. Each execution plan contains one or more tasks. For example, an organization could create an execution plan for delivering a corporate standard PC that contains these tasks: Procure the PC from a supplier. Configure the PC according to requester specifications. Deliver the PC to the requester. An execution plan is not specific to any one catalog item. There could be many different models of PC that a user can order, all using the same execution plan. It is not necessary to create a new execution plan for each individual catalog item in a mature service catalog. Note: Execution plans are not as powerful or flexible as workflows, and cannot be designed using a graphical editor. Execution plans are useful in some circumstances, for example, if you want to build your processes programmatically or through imports. ServiceNow recommends using workflows for request fulfillment processes. Create an execution planAdministrators and catalog administrators can create and manage execution plans and the associated variable tasks.Execution plan tasksAn execution plan contains one or more execution plan tasks, such as for obtaining approval. Execution plan tasks are assigned to a fulfillment group.Creating execution plan tasksAn execution plan contains one or more task templates. Each task template defines work that can be completed by a specific fulfillment group.Service catalog execution plansService catalog enables you to associate execution plans with catalog items.