Skip to content

See when a plan was last written to

All plansAnyone who can see the project

A plan nobody updates still shows dates, progress and a health score, and they look as trustworthy as anyone’s. The Last written to chip says how long it has been since a person last changed the plan, measured against how often the plan has work due, so you can tell a plan that is quiet this week from one that has been left behind.

This is a different measure from the data freshness score, which counts the share of live tasks touched in the last seven days.

  • The project header shows the chip after the status badge, for example “Last written to 9 days ago” with a clock icon. The full header shows it at every level; the folded header on the Gantt shows it only when the plan is quiet or stale.
  • The Projects page shows the chip on a project only when it is quiet or stale, so a current plan carries no chip.

The chip appears from seven days after a person last wrote to the plan. A plan written to in the last week, or created in the last week, carries no chip anywhere.

The chip is grey when the plan is current, amber when it is quiet and red when it is stale. It reads “Not written to in 9 days” when no person has written to the plan since it was created or imported.

Hover over the chip for the date of the last change and the plan’s cadence, for example “This plan usually has work due every 2 days.”

A plan with a task due every day is behind after a few silent days; a plan with one task due a fortnight is not. So Onplana compares the days since the last change with the plan’s cadence:

  1. Cadence: the work items due in the four weeks before and after today, as a number per week. Seven days divided by that number is the cadence in days, kept between 1 and 14 days. A plan with nothing due has a cadence of 14 days.
  2. Score: the days since a person last wrote to the plan, divided by the cadence.
  3. Level:
Level When
Current The score is under 1.5
Quiet The score is 1.5 or more
Stale The score is 3 or more, or no person has written to the plan for 14 days

So a plan with a task due every day goes stale after 3 silent days, and a plan with nothing due goes stale at 14 days. The days are counted from the later of the last change and the day the project was created or its last import finished, so a new or just-imported plan starts current. A plan with work due every day can therefore be stale before its chip appears at seven days; the digests below still treat it as stale.

A change counts when a person makes it, including through their own connected AI assistant or the Onplana Tasks apps. An agent’s changes do not count.

Counts: creating, editing or deleting a task (its status, assignee, dates, a Gantt drag, indenting, bulk updates), collaborators, comments, attachments, dependencies, issues, ideas, pages, change requests and their reviews, adding or removing members, and closeout.

Does not count: time entries, edits to the project’s own fields (its name, status or dates), milestones, risks, sprints, documents, libraries, lists, cost lines, reordering on the Gantt, moving a task to another project, and a change to a task’s priority alone.

  • The overdue digest lists a stale plan as one line instead of its overdue tasks: “This plan has not been written to in 12 days, so its 8 overdue tasks are not listed one by one.” A plan nobody updates would otherwise fill the email with tasks that are probably done.
  • The weekly risk digest adds a line for each stale plan after the risks: “this plan has not been written to in 12 days, so its risks may be out of date.”

The weekly summary and the project digest are unchanged.

The portfolio summary (GET /api/portfolios/:id/summary, and the portfolio_summary tool for AI assistants) carries each plan’s staleness: the date it was last written to, the days since, the tasks due per week, the cadence, the score and the level (CURRENT, QUIET or STALE). So an assistant asked “which plans are going stale?” can answer from it. A plan written to in the last seven days has staleness: null, the same as on the chip.

I updated the project’s end date. Why does the chip not move? Edits to the project’s own fields do not count. Update a task, comment or record progress, and the chip goes away until the plan has been silent for seven days again.

Does logging time keep a plan current? No. Time entries do not count, because they do not change the plan’s dates or progress.