Track request workflows and measure cycle time across the requisition process.
Beeline Analytics enables Program Management Office (PMO) users to analyze request-related workflows and measure cycle time across their contingent workforce program. It captures how requests move through key stages—from request creation and release to suppliers through candidate offer—using structured workflow data.
Request Cycle Time visualizations show the sequence of activities within each request, including workflow cases, events, and steps, along with when actions occur and who completes them.
| Element | Description |
|---|---|
| Workflow Case | An instance of an object (such as an amendment or a milestone payment) processed through a workflow. A predictable, repeatable sequence of tasks or steps where the exact sequence of steps needed to complete the task is unknown at the start and can vary on an individual basis. Workflow cases usually comprise one or more workflow events. However, project workflow cases comprise a single event that completes a given task, as amending a project or a milestone payment. Because a project may be amended multiple times before it’s complete, a Project ID might trigger multiple workflow cases. |
| Workflow Event | An occurrence that happens during a specific process, such as amending a project or a milestone payment. A workflow event comprises one or more workflow steps. A workflow event includes start (Assigned Date) and end (Completed Date) dates used to calculate average event cycle time in days. |
| Workflow Step | Individual tasks in a workflow event, such as a specific user approving an amendment to a milestone payment. A workflow step can:
A workflow step includes start (Assigned Date) and end (Completed Date) dates used to calculate average step cycle time in days. |
Request Cycle Time visualizations display approve and reject workflow events and steps. You can analyze workflow types such as approve, reject, approval task, and task, along with their outcomes, including approved, rejected, and completed results.
The visualizations also provide detailed workflow data, including approvers, rejected steps, impersonated actions, approval timing, approval methods, approver organization data, and overall workflow performance measures.
Request Count
What is it? Shows you the total distinct count of Request IDs for which an approve or reject action was initiated within the trend period you define.
Why would I use it? Distinct count refers to the number of unique or different items in a dataset. Distinct counts using the Request ID help you quantify the number of times an individual request was associated with an action that was approved or rejected before the request was completed or closed.
What’s a good value? Low or high numbers might be good based on your business requirements and model.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Approvers per Case Average
What is it? Shows you the total distinct count of users involved in completing a workflow case with approval actions initiated within the trend period you define. It reveals the mean number of approvers involved in completing the sequence of events in a given workflow case, such as a request approval being processed through Enterprise.
Why would I use it? Distinct count refers to the number of unique or different items in a dataset. Distinct counts help you quantify the variety or diversity of candidates within the dataset. Examining this value might help you determine whether your workflows involve an appropriate number of approvers.
What’s a good value? Low values are good. They indicate your workflows are processed smoothly with an appropriate number of designated steps required to process an object through Enterprise.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Approvers per Event Average
What is it? Shows you the total distinct count of users involved in completing a workflow case with approval actions initiated within the trend period you define. It reveals the mean number of approvers involved in completing the tasks in a given event, such as a Hiring Manager approving an amendment before the amendment moves to a Program Office user.
Why would I use it? Distinct count refers to the number of unique or different items in a dataset. Distinct counts help you quantify the variety or diversity of candidates within the dataset. Examining this value might help you determine whether your events involve the appropriate number of approval steps.
What’s a good value? Low values are good. They indicate your workflows are processed smoothly with an appropriate number of designated approvers required to complete the task associated with an event.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Case Count
What is it? Shows you the total number of active objects (requisitions) processed through Enterprise with actions initiated within the trend period you define.
Why would I use it? Helps you understand how many requisition transactions are processed through Enterprise during the trend period you define.
What’s a good value? Low or high numbers might be good based on your business requirements and model.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Event Count
What is it? Shows you the total number of active events, such a request approval processed through Enterprise with actions initiated within the trend period you define.
Why would I use it? Helps you understand how many types of requisition transactions are processed through Enterprise during the trend period you define. Analyzing this value might help you quantify the number of requisitions tracked through Enterprise.
What’s a good value? Low or high numbers might be good based on your business requirements and model.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Step Count
What is it? Shows you the total number of active steps, such as an individual approver’s action on an amendment, processed through Enterprise with actions initiated within the trend period you define.
Why would I use it? Helps you quantify the number of tasks required to complete an event. Examining this value might uncover process deviations and areas for improvement.
What’s a good value? Low or high numbers might be good based on your business requirements and model.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Approve/Reject Count
What is it? Shows you the total number of approve or reject steps, such as an individual approver’s action on an amendment, being processed through Enterprise with actions initiated within the trend period you define.
Why would I use it? Helps you quantify how many steps in a requisition workflow were approved and how many were rejected. Examining this value might uncover process deviations and areas for improvement, such as adjusting the information you capture in your workflow.
What’s a good value? Low or high numbers might be good based on your business requirements and model.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps per Case Average
What is it? Shows you the mean number of steps completed in any given requisition workflow case where steps were initiated within the trend period you define.
Why would I use it? Helps you quantify how many steps are required to fully resolve a requisition workflow case. Examining this value might help you identify bottlenecks limiting the speed at which your program runs.
What’s a good value? Low values are good. They indicate your workflows are processed smoothly with an appropriate number of events, tasks and designated approvers.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps per Event Average
What is it? Shows you the mean number of steps required for any given requisition workflow event where steps were initiated within the trend period you define.
Why would I use it? Helps you quantify how many steps are required to fully resolve a requisition workflow case. Examining this value might help you identify bottlenecks limiting the speed at which your program runs.
What’s a good value? Low values are good. They indicate your workflows are configured with an appropriate number of events, tasks and designated approvers.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Rejected Count
What is it? Shows you the total number of rejected steps processed through Enterprise with actions initiated within the trend period you define.
Why would I use it? Helps you quantify the number of changes to requisitions being declined. Examining this value may help you think through and test rejection behavior, review any associated messages and re-submission actions, which might help you improve your workflows.
What’s a good value? Low values are good. They indicate that changes to requisitions are being processed smoothly.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Impersonated Count
What is it? Shows you the total number of steps started by a user proxying as another user with actions initiated within the trend period you define.
Why would I use it? Helps you understand how many steps are being completed by another user. This value might give you insight into whether your workflow steps are assigned to the correct personnel.
What’s a good value? Low values are good. They indicate your workflows include the appropriate users required to complete tasks.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Delegated Count
What is it? Shows you the total number of steps reassigned to another user with actions initiated within the trend period you define.
Why would I use it? Helps you understand how many steps are being completed by another user. This value might give you insight into whether your workflow steps are assigned to the correct personnel.
What’s a good value? Low values are good. They indicate your workflows include the appropriate users required to complete tasks.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Rejected Percentage
What is it? Shows you the proportion of workflow steps declined by a user with actions initiated within the trend period you define.
Why would I use it? Helps you quantify the portion of changes to requisitions being declined. Examining this value may help you think through and test rejection behavior, review any associated messages and re-submission actions, which might help you improve your workflows.
What’s a good value? Low values are good. They indicate that changes to requisitions are being processed smoothly.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Impersonated Percentage
What is it? Shows you the proportion of workflow steps approved or rejected by a user proxying/impersonating another user with actions initiated within the trend period you define.
Why would I use it? Helps you quantify the portion of changes to requisitions being acted on by a user other than the designated approver. This value can help you understand whether personnel are following the specified approval workflow. This value might also give you insight into whether your workflow steps are assigned to the correct personnel for approval.
What’s a good value? Low values are good. They indicate that your processes and workflows are being adhered to and complied with, and your workflows are assigned to the correct approvers.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Steps Delegated Percentage
What is it? Shows you the proportion of workflow steps reallocated to another user to approve or reject with actions initiated within the trend period you define.
Why would I use it? Helps you quantify the portion of changes to requisitions being acted on by a user other than the designated approver. This value can help you understand whether personnel are following the specified approval workflow. This value might also give you insight into whether your workflow steps are assigned to the correct personnel for approval.
What’s a good value? Low values are good. They indicate that your processes and workflows are being adhered to and complied with, and your workflows are assigned to the correct approvers.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Case Cycle Time
What is it? Shows you the average time it takes to complete requisition workflow cases that include more than one step initiated within the trend period you define.
Why would I use it? Workflow case cycle time shows you how long it takes to process requisitions through Enterprise and can help you and your teams understand their level of efficiency. Examining this value might help you identify bottlenecks limiting the speed at which your program runs.
What’s a good value? Low values are good. They indicate your team is efficiently completing requisition workflows, which helps you outrun your competition and retain top talent.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Event Cycle Time
What is it? Shows you the average time it takes to complete a requisition event, such as an approval, that includes more than one step initiated within the trend period you define.
Why would I use it? Shows you how long it takes to process a single requisition event through Enterprise and can help you and your teams understand their level of efficiency.
What’s a good value? Low values are good. They indicate your team is efficiently completing requisition events, which may affect your contingent talent program.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
Workflow Step Cycle Time
What is it? Shows you the average time it takes to complete a requisition task, such as acting on an approval, that includes steps initiated within the trend period you define.
Why would I use it? Shows you how long it takes to process a single requisition task and may help you and your teams understand their level of efficiency.
What’s a good value? Low values are good. They indicate your team is efficiently completing requisition events.
What value drives or constrains the trend period interval? The assigned date for the workflow steps must occur within the trend period you define.
| Persona Program office users, | Modules Beeline Analytics | Documentation release Beeline Enterprise | Q4 2024 | Feedback? Email us: |