A template gives you a consistent structure for scoring health. The missing piece is the evidence behind each number and a way to keep it current. Husn supplies both.
Dependencies dropped from green to amber after an upstream team moved a delivery date by nine days.
Risk
Scope grew by four tickets this sprint with no matching change to the schedule rating.
Changed
Throughput has held steady, but blockers are aging and will pull the score down if untouched.
Watch
5 dimensions scored - evidence in every row - refreshed from live work
The problem
Project health score template
Most teams start with a health template, fill it in once, and watch it go stale by the second week. The dimensions are sound, but the scores are still a person's best guess on the day, with no evidence pinned to them and no way to tell when the underlying work has moved away from the rating.
A blank template scores nothing on its own, so the quality still depends on whoever fills it in.
Each dimension gets a number with no evidence attached, so nobody can question or trust it later.
The scorecard reflects the day it was filled in, not the work as it stands now.
Why this gets hard at scale
Why a template alone is not enough
01
Scoring five or six dimensions honestly for one project takes time, and that time multiplies across a portfolio until corners get cut.
02
Without evidence in the row, two reviewers score the same project differently and neither can defend their number.
03
A trend column is only useful if last period's scores were honest, so one soft entry quietly corrupts the whole trend.
How Husn helps
Step 01Husn fills each dimension from real signals in Jira, Slack, and docs, so schedule, scope, dependencies, blockers, and throughput are scored from the work rather than from memory.
Step 02Every score carries its evidence in the same row, the slipped date or aging blocker that drove it, so the number can be questioned and defended.
Step 03Husn watches each dimension as the work moves and flags a slipping score early, while there is still room to act before it becomes an incident.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Scored dimensions, covering schedule, scope, dependencies, blockers, and throughput so health is built from concrete parts rather than one overall feeling.
02Rating scale, a consistent green, amber, red basis applied the same way to every project for fair comparison.
03Evidence column, the specific signal behind each score, such as a slipped date or an aging blocker, so the number can be defended.
04Trend, how each dimension moved since the last period, so a slow slide is visible before it turns red.
05Owner, the person accountable for each dimension and the next action when it drops.