Evidence that delivery may be going wrong: overdue milestones, off-track status, a build-up of late tasks.
Operations intelligence for Asana
Know where to focus before projects become problems.
Pulse reads your Asana delivery data and returns one ranked attention queue — the projects that need you, why they need you, and the evidence behind each finding. No custom fields. No black box.
Read-only, least-privilege Asana access
Attention queue
Four projects need attention
Scoped to 2 portfolios · synced 3 hours ago
- 100 Urgent
Northwind billing migration
Milestone “Go-live” is 5 days overdue.
Risk 82 Confidence 90 Due 26 JulR006Overdue milestone
“Go-live” was due 26 Jul and is not complete.
Suggested check — confirm the revised go-live date with the project lead.
Evidence from Asana · observed 3 hours ago
- 58 Review
Atlas mobile rollout
No status update in 22 days.
Risk 24 Confidence 70 Due 14 Aug - 47 Review
Customer portal refresh
3 of 12 active tasks are overdue.
Risk 40 Confidence 95 Due 29 Aug - 22 Monitor
Data warehouse consolidation
Project has no recorded owner.
Risk 0 Confidence 55 Data quality
The problem
Asana shows you everything. It rarely tells you what needs you.
A busy workspace holds hundreds of tasks, dozens of projects and a scatter of status updates. The sign that a project is slipping is in there — buried under everything that is fine. Pulse prioritises what requires attention, rather than showing you more data.
How it works
Three steps, no configuration project.
- 01
Connect Asana
Authorise Pulse with read-only access, then choose the teams, portfolios and projects it should watch. Nothing is written back.
- 02
Pulse assesses
Eleven deterministic rules read native project and task data and record what they find — each signal carrying its evidence, a rule code and the time it was observed.
- 03
You act
Work the ranked attention queue and an on-demand weekly brief. Every item links straight to the project in Asana.
The rules
Eleven checks. No black box.
Every signal Pulse raises comes from one of eleven deterministic, versioned rules. You can always see why a project is in the queue — not just that it is.
- R001 Project is past its due date Delivery
- R002 Project is due soon with active tasks open Urgency
- R003 Latest Asana status is “at risk” Delivery
- R004 Latest Asana status is “off track” Delivery
- R005 Status update is missing or stale Governance
- R006 A milestone is overdue Delivery
- R007 Overdue tasks are piling up Delivery
- R008 A due task is held by an unresolved dependency Delivery
- R009 Project has no recorded owner Data quality
- R010 Active tasks are unassigned Data quality
- R011 Active tasks have no due date Data quality
Three signals, kept separate
Poor housekeeping isn’t poor delivery.
Pulse scores every project three ways and never blends them into one number that hides the evidence.
How urgently you should look — delivery risk sharpened by genuine time pressure.
How far to trust the read. A missing owner or an absent update lowers confidence; it does not inflate risk.
Trust
Read-only from day one.
- Least-privilege OAuth — six read scopes, and nothing is written back to Asana.
- Access tokens are encrypted and kept server-side.
- Every customer’s data is isolated by tenant.
- Stale or missing data is shown as such — Pulse never invents certainty.
Early access
See your delivery the way Pulse does
Pulse is in a private pilot with a small number of delivery teams. Tell us about your Asana setup and we’ll be in touch.
Read-only Asana access · no pricing commitment · pre-release