Status check-ins

"Are you at risk?" — the three answers, and why a person outranks the arithmetic.


When work falls behind pace, Noots doesn't guess. It asks the person doing it.

Asking

Anyone with edit rights sees a banner on the Timeline: "N tasks are behind pace against their next milestone", with Ask their owners. The task's first assignee gets a notification linking straight back. If a task has no assignee, the ask goes back to whoever raised it, so it is never dropped.

Answering

The person asked sees a card headed Is this at risk? with the task, the exact reason ("20% of this checklist is done with 87% of the time spent"), an optional note, and three buttons:

AnswerWhat happens
Still on trackNothing changes. Believing people is the point of asking.
At riskThe task's priority is raised and a risk is logged in the Noot's RAID register.
Already slippedThe task is re-dated — by the number of days your note actually names.

"Already slipped" reads explicit, quantified phrases from your note — "3 days behind", "about a week", "a couple of days", "end of the week" — up to 60 days. A vague note ("it's going badly") moves nothing rather than inventing a number, so it's worth being specific.

A human answer lasts 10 days

Your answer outranks the pace arithmetic for 10 days, then goes stale and automatic tracking takes over again. The one thing it never outranks is a deadline that has actually passed — say "still on track" on Tuesday about a date that passed on Monday and the task still reads Delayed, with your answer shown alongside.

  • There is only ever one open ask per task — the system doesn't nag.
  • You can volunteer a status without being asked: the row menu offers Report where this stands.
  • Whoever asked can cancel the check-in, and is notified when you answer.
  • If Autopilot is asking for status, the email nudge for that task is suppressed — you get asked in-app, not both.
Still stuck? Open a support ticket and we'll help you out — tracked right inside Noots.