Skip to content

Project overview and status

Every project has an Overview — the first tab in the project navigation. It answers what the project is, how healthy a person says it is, where it sits in the roadmap, what is planned, and what just happened.

The brief is the project’s own description. There is no second document to keep in sync: editing the brief here is the same field the project settings edit.

Write what the project is for, who it serves, and — most usefully — what it deliberately excludes. Owners and admins edit it; everyone in the workspace reads it.

A status update is health plus a note written by a person. Both are required: a health chip with no reason is status theatre.

Health What it means
On track Going as expected. No decision needed from anyone else.
At risk Something could derail this. Say what, and what would help.
Off track This has already slipped. Say what changes or what you need.
On hold Deliberately paused. Say what would restart it.

Health is not the project’s lifecycle. A project is active or archived independently of whether it is on track — the two answer different questions and never share a field.

Updates are append-only. Posting a new one supersedes the previous update; it never edits or erases it. Earlier updates stay readable under Earlier updates, so “we said at risk three weeks ago and nothing changed” is a question you can actually answer. There is no edit and no delete.

ScopeKite never writes, scores, or infers a status. The overview will tell you how many days old the current update is — that is a fact, not a judgement — and then leave the judgement to you.

Owners and admins post updates; members read them. That follows the existing project-edit permission rather than adding a new one.

  • Roadmap shows the initiative and objective this project rolls up to, when it is linked. If it is not linked, it says so.
  • Cycles shows what is running now and what is next, with dates and committed counts.
  • Recent activity is the project’s own slice of the append-only history — who did what, with a link to the work item it happened on.

ScopeKite has no separate project lead or owner. Rather than invent one, the Access panel reports what is actually true: when the project was created and who can see it (everyone in the workspace, in this phase). Per-project membership and guest access are still on the roadmap.