# Read Project Analytics and Team Pulse

Canonical HTML: [https://collty.com/help/projects/read-project-analytics-and-team-pulse](https://collty.com/help/projects/read-project-analytics-and-team-pulse)
Audience: Project participants and owners
Reading time: 16 min
Updated: 2026-07-15T00:00:00.000Z

Read progress, schedule, workload, financial and collaboration signals, then turn them into concrete project actions.

## Delivery health has more than one dimension

Project Analytics combines progress, sprint history, task timing, specialist workload and, when enabled by the operating model, hours and commercial data. Team Pulse adds collaboration evidence that status fields alone cannot express.

The purpose is not to produce one reassuring score. Use the panels together to locate the task, sprint, specialist or collaboration pattern that needs attention.

## Know what each view answers

| Signal | Question it answers | Useful action |
| --- | --- | --- |
| Project progress | How much planned work is complete? | Open the incomplete or overdue tasks behind the percentage |
| Sprint timeline | Where is delivery accelerating or slipping? | Inspect the sprint and its dependent tasks |
| Task details | Which task creates the signal? | Open the task, owner, dates, status and Work Graph |
| Specialist workload | Is work concentrated or unbalanced? | Reassign work or confirm realistic availability |
| Hours and cost | Is tracked delivery following the operating model? | Review allocation, rate or invoice implications |
| Team Pulse | How does collaboration around the work feel? | Look for repeated tension, not a single isolated response |

## Read patterns before reacting

1. **Start with the project scope:** Confirm the selected project, planning period and operating model so the numbers have the right boundary.
2. **Compare progress with time:** A high completion rate late in the sprint is different from the same rate near the start.
3. **Open the underlying task:** Use task detail to verify status, owner, dates, dependencies and collaboration evidence.
4. **Check workload distribution:** A project can be on schedule while one specialist carries unsustainable concentration.
5. **Compare Pulse with delivery:** Warm collaboration with slipping delivery suggests a planning problem; tension with on-time delivery may signal hidden sustainability risk.
6. **Make one accountable change:** Update the task, owner, dependency, date or team conversation, then observe the next real signal.

## Use Team Pulse as collaboration evidence

- Pulse belongs to the work context where the experience occurred; it is not a public rating of a person.
- A single check-in is weak evidence. Read the score together with its response count and recency.
- Repeated cold or tense signals should trigger a calm conversation about blockers, clarity, workload or handoffs.
- Warm signals across assessed tasks can confirm a healthy collaboration pattern, but they do not replace delivery quality.
- Private Pulse detail remains inside the authorized project boundary; team-level views use prepared summaries.

## Examples of useful interpretation

| What you see | Possible meaning | What to do next |
| --- | --- | --- |
| Many tasks in progress, few done | Work is fragmented or acceptance criteria are unclear | Reduce parallel work and review task outcomes |
| One specialist owns most planned hours | Workload and continuity risk are concentrated | Rebalance or add a second owner before delay appears |
| Repeated blocked tasks across sprints | The dependency model or handoff is failing | Open Work Graph and change the sequence or ownership |
| On-time delivery with colder Pulse | The team may be absorbing hidden coordination cost | Discuss workload, clarity and decision latency |
| Warm Pulse with overdue work | The issue may be scope, estimates or external dependency rather than conflict | Review dates, scope and blockers |
| Cost or hours rise faster than progress | The current plan may be inefficient or under-scoped | Inspect the responsible tasks before changing the project budget |

## How Team Pulse is summarized

### Inside Collty: Fast summaries from event evidence

Pulse events are recorded at the task and project boundary. A prepared team summary can be updated as new pulse events arrive, allowing Teams Canvas and Project Analytics to read one current aggregate instead of recalculating every project on every load.

- A count is shown with the score so one response is not mistaken for a stable trend.
- Recent signals can be weighted more heavily than old ones.
- Private pulse detail remains inside the authorized project context.

## Related guides

- [How Team Intelligence Works](https://collty.com/help/teams/how-team-intelligence-works)
- [Work In Project Workspace](https://collty.com/help/projects/work-in-project-workspace)
- [Use Digital Pm Twin](https://collty.com/help/ai-agents/use-digital-pm-twin)