What it covers
Review Sales cycle, Task delivery, Service resolution and Project delivery over a 30, 90 or 180-day window, subject to source permissions.
Reporting and data
Process Intelligence
Compare throughput, cycle time and overdue work across supported business processes.
How it works
See where work is slowing down
Process Intelligence brings a comparable view of supported workflows into Reports. Choose a 30, 90 or 180-day window to review active work, items needing attention, completed throughput and the change from the preceding window. Completed cycle time is shown as a median and a slower-quartile measure, so a typical completion time does not hide a long tail of delayed work. Sales, tasks, service and projects keep their own definitions. A process appears only when you can view its source area; the report does not create broader access to operational records.
In practice
The figures describe recorded work. An overdue deal, late task, breached service resolution target or at-risk project has a defined attention rule. Invalid completion durations and unfinished records are excluded from completed-cycle percentiles.
When to use it
Useful situations
- Compare this quarter’s completion pace with the preceding period.
- Look for a long tail of delays that a single average would conceal.
- Review current overdue work before deciding where the team needs attention.
A working path
How the work moves
Choose a useful window
Open Process Intelligence in Reports and select the period that fits the discussion. Use the same window when comparing processes, and remember that each process has its own completion event and attention rule.
Read volume and pace together
Review throughput alongside active work and attention counts. Check both the median and the 75th-percentile cycle time. A rise in completed volume may reflect higher demand rather than a more effective process.
Investigate before deciding
Use the result to focus a conversation with the people responsible for the work. Review the relevant operational records and circumstances before changing staffing, ownership or a workflow. The report supplies evidence, not a causal diagnosis.
Illustrative scenario
A delivery review
A manager sees stable median project completion but a rising slower-quartile time. They review overdue and at-risk projects with their owners to understand the delays before deciding whether the delivery process needs changing.
Before you start
What to check
- Cycle time runs from record creation to the recorded completion or outcome; missing historical events can limit the evidence available.
- The view does not infer individual performance or prove that one person, team or decision caused a delay.
Can we define our own processes?
The current view measures four fixed processes: Sales cycle, Task delivery, Service resolution and Project delivery. You can choose the reporting window, while the completion and attention rules remain consistent.
Why is a process missing?
The report shows only source areas available through your current workspace permissions.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.