Task quality (drift)
See your backlog decay before it happens.
A 0–100 score for backlog hygiene.
The problem
Quality breaks before code is written.
Everything is marked urgent, dates are impossible, tasks drift away from the project's purpose. That invisible debt comes back as delays at the end of the sprint.
AI in this module
A quality score for every task.
- Semantic drift: the meaning distance between a task and the average of the project's last 20 tasks
- AI assessment of scope, description quality and technical conflict
- Rule-based signals for priority inflation, impossible dates and workflow violations
What you can do
8 weighted signals
Semantic drift 20, scope 15, description quality 15, workflow violation 15, wrong-flag rate 10, priority inflation 10, impossible date 10, technical conflict 5.
Levels
70+ red, 40+ yellow, otherwise green.
Priority inflation
Flagged when more than half of the last 10 tasks are high priority.
Impossible dates
When estimated effort doesn't fit the remaining days, or the due date is after the project end.
Alert on red
The PM and department manager are notified when a task turns red.
Visible everywhere
On the task card, task detail and drift banner; wrong-flag score on the person's profile.
Who uses it and how
PM / Quality
Fixes red tasks before the sprint starts.
Team Lead
Sends poorly described tasks back to be rewritten.
Department Manager
Sees which projects quality drift concentrates in.
Frequently asked
What does the drift score measure?
How well a task is defined and how well it fits the project. Not code quality — the quality of the work's definition.
When is it calculated?
In the background when a task is created and updated.
See it with your own data.
Open a free workspace, or let's schedule a demo with your team.