Consistency
Consistency
Consistency gives each person a daily score from 0 to 100 for how steadily they are working, and can nudge people whose score has slipped (module consistency). It reads what people actually did: activity, tasks and time tracked.
In the sidebar under Projects → Consistency. Needs: Tasks and Time.
How the score works
A day's score blends four parts, each from 0 to 100. Each looks back over a window of working days, 28 days unless changed:
- Engagement: the working days in the window on which the person did something recorded in the activity trail.
- Follow-through: tasks assigned to them that they finished in the window, against finished plus overdue.
- Time: the working days on which they tracked any time. Only judged for people who track time at all.
- Hygiene: how much of their open assigned work has been touched recently. A task untouched for 14 days counts as stale.
A part with nothing to judge, such as time for someone who never uses timers, shows as a dash rather than a zero, and the score is blended from the parts that remain. The window never reaches back past the day the person joined. Days are counted in UTC.
The starting weights are engagement 35, follow-through 30, time 20 and hygiene 15. The working week starts as Monday to Friday. A streak counts consecutive working days with activity. Days off are stepped over, and a missed working day ends it.
What you see
The screen shows your own record.
- Totals: Current streak, Best streak, Latest score (with your average), Active days in the window, and tasks Finished.
- A table with one row per scored day: Date, Score, Engaged, Follow-through, Time, Hygiene, Finished and Streak.
- People who can manage consistency see a Score yesterday button.
With no scored days yet, the screen says "Nothing recorded yet".
What you can do
Record yesterday's scores
Nothing records scores on a schedule. A day is scored when someone presses the button.
- Open Consistency.
- Press Score yesterday. It scores the day that has just ended, for everyone in the workspace.
The numbers start to mean something after a week or so of scored days. To fill in days that were missed, an agent can score up to 120 days back.
See the team
Ask an agent for the team list. It shows everyone's score worked out now, with each part, their streak, and how the score has moved against a week ago where that day was scored. The lowest scores come first. The screen does not show this list.
Change how people are scored
An agent can change the four weights (whole numbers from 0 to 100, not all zero), the window (1 to 120 days), the working days (at least one day) and when a task counts as stale (1 to 120 days). The screen has no settings form.
Change or switch off nudges
A nudge is a notification to the person themselves: "Your consistency score is …", saying which day it was below the threshold. Nudges start switched on, with a threshold of 60 and at least 3 days between nudges to the same person. They can be turned off, or the threshold (0 to 100) or the gap (1 to 60 days) changed, through an agent.
Who can do what
| Permission | Label | Lets you |
|---|---|---|
consistency:read | View consistency | See your own record, the team list and the scoring settings. |
consistency:write | Manage consistency | Score yesterday, fill in missed days, change the scoring and the nudges, and run a nudge now. |
Anyone with consistency:read can see the team list, so give it to people who should see colleagues' scores. See People, roles and permissions.
What runs on its own
| Job | When | What it does |
|---|---|---|
nudge-slipping-scores | Every day at 09:00 UTC (0 9 * * *) | Looks at each person's latest score from the last two days. Everyone below the threshold gets a nudge, unless they had one within the gap. It sends nothing when nudges are off. |
The nudge only judges scores that were recorded. If nobody has pressed Score yesterday recently, there is nothing to judge and nobody is nudged. Nudges arrive like any other notification: see Notifications and alerts.
For agents
An agent can read scores and settings, record scores, change the scoring and nudges, and nudge people. Changing the scoring and recording scores are writes. Changing the nudges and running a nudge count as acts outside the workspace, because they message colleagues, possibly in their chat as well as the bell. By default each one waits for a person to approve it. See Agents and approvals.
Read (read-only): consistency.mine, consistency.team, consistency.config
Change: consistency.updateConfig, consistency.recompute (scores up to 120 days back)
Nudges (ask a person first by default): consistency.setNudges, consistency.nudge
consistency.nudge can judge a chosen day. The gap between nudges is always measured from the real time, whatever day is chosen.
Over MCP the same tools are named consistency__mine, consistency__nudge and so on. See API keys and MCP access.