Process Analytics & Load Balancing

Most tools show task or sprint charts. Z-Workflow goes further and analyses your approval processes: where each one is slow, and who carries the approval load.

Open Admin → Workflows and switch to the Analytics tab. Choose a time window (30 / 90 / 180 days).

By workflow

A table of every workflow with, over the selected window:

• Requests — how many were filed.
• Pending / Approved / Rejected — the outcome mix.
• Avg cycle — average time from submission to final decision.

Use it to see which processes are busiest and which take the longest end-to-end.

Bottleneck steps

For each workflow, every approval step is shown as a chip with the average time that step takes. The slowest step is highlighted in red, and a step with requests stuck on it shows the stuck count. This pinpoints exactly where a process stalls — usually a single step or approver.

Approver load

A table of approvers with:

• Pending — how many requests are waiting on them right now (current load).
• Acted — how many they have processed in the window.
• Avg time to act — how quickly they respond.
• Oldest pending — the longest-waiting request on their desk (shown in red when over three days).

This makes load imbalance obvious — who is a bottleneck and who has spare capacity.

Load balancing (one-click rebalance)

Below the tables, Z-Workflow proposes concrete load-balancing suggestions: when someone is overloaded, it recommends delegating to a lighter colleague who already approves the same kinds of requests. Each suggestion shows:

• the overloaded approver and their pending count,
• the suggested lighter approver and theirs,
• the workflows they have in common,
• and, when AI is enabled, a short plain-language summary of the recommendation.

Click Delegate 14 days to apply it instantly — this creates a temporary delegation so the overloaded approver's items route to the lighter colleague for two weeks. No manual setup required.