Loading
Because status is self-reported, and reporting amber invites scrutiny. Everything is green until it is unarguably red, which is usually too late to do anything cheap about it.
Delivery risk flags projects showing measurable signs of trouble, naming the specific signal rather than issuing a score.
It watches the record: phases with no logged hours, tasks blocked beyond a threshold, margin eroding against plan, dependencies slipping, approvals overdue. Each flag names its trigger and links to it.
A phase due in nine days has three blocked tasks and no hours logged in a fortnight. That flags with those three facts attached, which is a conversation nobody can wave away.
It will not predict a risk with no trace in the record. A client about to cancel for reasons nobody has written down is invisible to it, and it does not pretend otherwise.
Tasks, dependencies, timesheets, margin and client approvals — everything already on the project.
Yes, per project or template.
It names signals rather than a colour, because a colour hides its reasoning.
The project owner, and whoever you nominate for escalation.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.