Gain a centralized view to track the progress of an opportunity across all stages, from idea through deployment, and take stage-specific actions. Clear status indicators highlight the required criteria for each stage, enabling users to quickly see what is complete and what is blocking progression.

From the workflow section, users can submit, approve, disapprove, hold, reset, retire, or cancel an opportunity based on its current state and permissions. Overall, the workflow tab ensures governance, consistency, and visibility throughout the entire opportunity lifecycle.

The workflow tab manages how an opportunity progresses through its lifecycle. Each stage has mandatory requirements that must be completed before advancing. These requirements are validated with stage-specific checks displayed on the right side of the workflow tab. An opportunity cannot move forward until all blocking requirements for both the current and target stages are satisfied.

Idea to Pipeline

This transition confirms that the idea is sufficiently qualified to be evaluated as a potential automation opportunity.

What must be completed: Before moving from idea to pipeline, ensure the following pipeline stage requirements are completed and display a green checkmark:

  • Forecasted savings: This is the estimated annual savings calculated based on the values entered in the labor cost fields in the Details tab.
  • Process complexity: Defines the complexity score. Make sure the process complexity section is completed in the Details tab.
  • Strategic alignment: Provides the strategic alignment percentage. Make sure the strategic alignment section is completed in the Details tab.

Action to move forward:

  • Once all pipeline requirements are satisfied, use the available workflow action (for example, Send for approval or Advance to Pipeline, depending on configuration).
  • If approval is required, the opportunity must be approved before it officially enters the Pipeline stage.

Pipeline to Build

This transition confirms that the opportunity is approved and ready to move into design and development.

What must be completed: Before moving to build, the following Build Stage Requirements must be completed and display a green checkmark:

  • Non-Automation benefits: Enter any additional benefits not directly tied to automation.
  • Additional costs: Enter the estimated implementation or supporting costs.
  • Activities: At least one activity must be defined and associated with the opportunity.

Action to move forward:

  • Once all Build requirements are satisfied, use the available workflow action (for example, Send for approval or Advance to Build, depending on configuration).
  • If approvals are enabled, the opportunity might need to be first submitted and approved before the button becomes available.

Build to Deploy

This transition confirms that the automation has been built and is ready or approved for deployment.

What must be completed: Before moving to deploy, all Deploy Stage Requirements must be satisfied and display a green checkmark:

  • Automations: At least one automation must be mapped to the opportunity.
  • Developer: A developer must be assigned.
  • Implementation date: The implementation (go-live) date must be specified.
  • Failed execution cost: The cost of failed executions must be entered and cannot be zero.
  • Business unit target: Business unit savings or performance targets must be defined.

Action to move forward:

  • Resolve all blocking deployment requirements.
  • Submit for approval if required.
  • Once approved, the opportunity advances to Deployed.

Deployed

Once an opportunity reaches the Deployed stage, it is considered live.

Available actions:

  • Hold: Temporarily pauses the opportunity without closing it.
  • Reset: Reverts the workflow state (to be used cautiously, typically for corrections).
  • Retire: Used when an automation has been deployed but is no longer active.
  • Cancel: Used when the opportunity should not proceed to deployment (typically before deployment).

Disapproval

Disapproval is used when an opportunity does not meet approval criteria at a given stage. A Disapproval Note must be entered. The Disapprove button remains disabled until a note is provided. When an opportunity is disapproved, the opportunity does not progress. The opportunity owner is notified. The owner can either address feedback and resubmit or cancel the opportunity.

Convert to process

Administrators can change the automation type of an existing opportunity to process automation using the Convert to Process option. This conversion is available when the opportunity is in the idea, pipeline, or build stage. Once saved, the opportunity automatically switches to the process template, preserving and recording all previously submitted labor costs.

You can continue configuring the process, including defining process paths and associated automations without needing to recreate the opportunity. Process automation opportunities are also included in the main dashboards and are treated the same as other opportunities for key metrics such as forecasted savings, realized benefits, and missed benefits. Metrics are dynamically rolled up when lower-level process opportunities or related opportunities are mapped to a parent process opportunity.