Situation
A task is done (or done enough), and the result needs to be recorded before the window closes and memory goes stale.
Outcome
The task shows its real state: measured, with its actual value against the source set in its contract, or honestly unmeasured.
Steps
- 1On the task card, mark the work done. A manually measured task stays un-dimmed while it awaits its number ("Task completed. Result still needed."): work that is done with its result still outstanding is a real state.
- 2When the measurement window is ready, open the "Log a task outcome" panel ("Choose a completed task to review or record its result.").
- 3For a manually measured task, press "Add Result" and enter the actual value for the task's metric over its window. Integration-backed tasks ("Task completed. Measurement pending.") report from the connected source; paste the exact published page or post URL if the card asks for one. Note the source and the date the number was read.
- 4Read the verdict honestly: Exceeded, Met, Partial, Missed, or Inconclusive. Pending is a state (still awaiting measurement), not a verdict. A completed task with no proof is unmeasured or pending. It never displays as met.
- 5Separate task-linked measurements (exact pageviews and exact post results, labeled as such) from workspace-wide measurements (GA4 sessions, GBP call clicks, follower movement), which are observed during the window and never claimed as task-caused.
- 6Read it back with guardrail language (based on, observed after, coincided with). Never say "caused" or "proved revenue" without the required evidence.