Web dashboard

Track a client goal from a task

Link a goal to a task the client already has, record one completion, and read the workings behind the count.

Sound is off

A task-counted goal keeps score of how often a client's task is actually done. You never type the progress in — it comes from the work being recorded.

This example counts completions of the client's daily Morning routine task towards a target of five. The task has to exist already; setting up its schedule is a different job.

Counting starts when the goal is created. Work recorded before that does not count towards it, which is worth knowing before anyone wonders why a long-running routine shows zero.

There are four ways to count: a number of times in total (counts up, never resets), every week or fortnight (starts again each period, no finish line), most days (re-worked each day, nothing resets sharply), and days in a row (one missed day resets the run). Pick the one that matches what you actually want to know — they answer different questions about the same task.

The workings under each goal are the part worth reading. They separate three different things: days that counted, days where something was recorded but did not count, and days where nothing was recorded at all. A stalled goal is usually one of the last two, and they need opposite responses — one is a care question, the other is a recording question.

The count reflects what has been recorded. It is not a judgement about how the person is doing.

Step 1
Open the client's Goals tab
Goals live on the client's own page, alongside their other tabs. This walkthrough starts with a client who already has a daily Morning routine task recorded against them — the goal links to that task rather than creating anything new.
Step 2
Name it for the outcome
Not for the task. "Settled mornings" says what you are trying to achieve; "Do morning routine" just restates the task that already exists.
Step 3
Link the task
Counted from is what makes the goal move — pick the task whose completions should add up. Without it the goal has nothing to count.
Step 4
Set the target and the window
How many, and over what. The four windows behave differently the moment a day gets missed: a number of times in total counts up and never resets; every week or fortnight starts again each period with no finish line; most days is worked out again each day, so nothing resets sharply; days in a row is a streak that one missed day ends. This example is five times in any seven days, worked out again each day.
Step 5
Do the work as normal
Complete today's routine the way you would anyway. The goal is not something anyone updates by hand.
Step 6
The progress comes from the record
Completing the task is what moves the goal. That is the whole point of linking it: the count cannot drift away from what happened.
Step 7
Notes stay on the completion
What you write when completing the task is kept on that completion record, with who completed it and when. It is not copied into the goal: the workings show the date, whether the day counted, the recorded value and who recorded it — not your words. So the note is the place to explain a day, and the goal is the place to count it.
Step 8
Check the goal moved
Back on Goals, the count has moved on its own — one of five. Nobody typed it in.
Step 9
Open the workings
Underneath the goal, day by day.
Step 10
Three different rows
A green tick is a day that counted, carrying who recorded it and the value if the task records one. A grey question mark is a day where nothing was recorded at all. A red minus is the third state: something was recorded and did not meet the goal.

You will not see a red minus on the goal in this walkthrough, and that is not a gap in the recording. A goal counted from a straightforward task hits on any completion, so a recorded day always counts. The red minus belongs to goals with a condition on the answer — at least this many, at most that many, or equal to a particular value — where a recorded number can miss.
Step 11
Which kind of stall is it
"Nothing recorded" means no evidence either way: the work may have happened and gone unrecorded. A recorded day that did not count means it happened and did not meet the goal. Those need different conversations, which is why the workings keep them apart rather than showing one flat bar.
Step 12
Where it lands
Today's routine is recorded, and the goal reads one of five across the last seven days — counted from the completion, not typed in by anybody.
Step 13
Changing a goal does not rewrite history
The workings are built from the completions as they were recorded. Adjusting a target changes what "done" means from here; it does not retroactively make past days count, and counting still starts from when the goal was created.