Analytics

See exactly where work speeds up, and where it stalls.

Every workspace tracks how tickets actually move: throughput, the steps they pile up at, what they resolved as, and which channel they arrived through.

Start free View pricing
Per workspace

The numbers a process owner actually asks for

Volume in, volume out, and how long the middle takes. Each workspace has its own analytics view driven by its own workflow, so the stages being measured are the stages you drew.

KPIs with escalations kept separate from resolved, so the resolve rate is honest
Throughput over time: what came in and what actually closed
Cycle time from intake to resolution, not from when someone remembered to open it
Work Orders · analytics

38

Open

212

Resolved (30d)

9

Escalated

2.4d

Avg cycle

Throughput

Mon
Tue
Wed
Thu
Fri
Sat
Sun
Bottlenecks

Because the gate is usually a person

Work stalls at approvals and replies far more often than at anything technical. Dwell time is measured per node, so the answer to why is this taking nine days is a step name, not a hunch about the team being busy.

Average time parked at each step, ranked
Internal versus external waiting: your delay or theirs
Process-level only: RouteWrk measures steps, deliberately not per-employee scorecards
Bottlenecks · avg time parked

Manager approval

1d 6h

Await vendor reply

9h 20m

On-site checklist

3h 05m

Manager approval is holding work longer than every other step combined.

What you can break the work down by

Every ticket carries enough context to be counted honestly.

Outcomes, not just "closed"

Resolve nodes carry an outcome (Completed, Denied, Cancelled, Duplicate, No action needed) and the Outcomes card breaks resolved work down by which one it was. Closed and solved are not the same number.

Escalations split out of Resolved

An escalated ticket is not a win. It is counted separately, so your resolve rate means what it says.

Bottlenecks by node

Dwell time per step across the workflow, so the stage everything piles up at is visible instead of suspected.

Channel and source

Where the work came from (email, automation, or created by hand), so you can see which intake path actually carries the volume.

SLA clocks, if you want them

An org admin can turn on first-response, resolution and per-gate wait clocks. They are business-hours aware and add breach badges. Tracking and display only: an SLA never changes what a workflow does.

A workflow map with live counts

The Dashboard Workflow Map lens draws each workspace as a swimlane with the current ticket count sitting on every node.

Dashboard
My WorkOperationsWorkflow Map

Work Orders

4

Triage

7

Approval

2

On-site

0

Resolve

Accounts Payable

3

Intake

5

Approval

1

Paid

0

Resolve

Across workspaces

One dashboard over every process

The Dashboard sits above the workspaces with three lenses: My Work for everything needing a human right now, Operations for org-wide throughput, cycle time and bottlenecks, and Workflow Map for a swimlane of each workflow with live counts. Click any ticket to open it where it lives.

My Work: approvals, checklists and draft reviews across every workspace, sorted priority then age
Operations: org-wide health, including SLA compliance when SLA is switched on
Workflow Map: where every ticket in the organization is standing right now

More of the platform

Find the step that's costing you a week.

Start free. Analytics come with every workspace.