The status timeline

Every idea has a timeline that shows every status change, newest at the top. The timeline is the source of truth for "what happened to my idea".

The status stepper

At the top of every idea's detail page, below the title and status badge, a stepper shows the full pipeline in order:

Submitted - In review - Scored - Approved - In implementation - Implemented

The current step is highlighted. If the idea has been rejected or withdrawn, the stepper forks to show that outcome instead.

The stepper gives every reader, including submitters, an immediate read on where the idea stands without having to parse the activity feed. It does not replace the feed — it summarises it.

What you'll see

Each timeline entry has the same shape:

• Status pill, the new status the idea moved into, in the workspace's status colour.
• Actor, the user who triggered the change. System for auto-decisions and reviewer-completion transitions.
• Timestamp, when the change happened, rendered in mono so it's easy to scan.
• Note, the comment or feedback attached to the change, when present.

A typical sequence on an approved idea reads:

1. In review, System, the moment the idea was submitted.
2. Scored, System, when the last reviewer (or the AI) finished.
3. Approved, System, auto-decision, with the score and threshold note.
4. In implementation, Admin or primary reviewer name, when someone moved the idea from the Shortlist into execution.
5. Implemented, Admin name, when the work shipped, with the wrap-up note.

The shortlist: between approved and in implementation

When an idea reaches Approved it does not automatically move to In implementation. Instead it joins the Shortlist, a ranked list of all approved ideas waiting to be started.

The Shortlist is accessible to every workspace member via Shortlist in the sidebar.

What a newly approved idea looks like

A freshly approved idea lands on the Shortlist with no priority and no due date. The admin or the category's primary reviewer sets both after approval. Until both are set, the idea appears in the Needs attention column on the right side of the Shortlist page.

Priority and due date

Each idea on the Shortlist has:

• A priority band, High, Medium, or Low. Admins and the category's primary reviewer assign the band from the Shortlist row or from the idea's detail page.
• A due date, empty until set. A one-click suggestion of today plus the workspace's Accepted-idea SLA days is available as a starting point when setting the date. The suggestion is a convenience, not an automatic assignment.
• An overdue state, shown as a red chip, when today is past the due date. Overdue ideas also increment the badge count on the Shortlist sidebar item. Overdue state is computed on read; no automatic notification fires when an idea becomes overdue.

Setting priority and due date from the idea page

The Priority and due date card appears on the idea's detail page once it is approved. It shows the priority selector, the due-date picker, and a Start execution button. Once an execution exists, the same card switches to showing the execution status: progress, target date, a link to the board, and a completed indicator when the work is done. There is no separate execution card; the pre-execution editor and the execution status both live in this single card.

Triage column

The Shortlist page is split into two columns. The left side groups ideas by priority band (High, Medium, Low) once both fields are set. The right side, Needs attention, lists ideas that are still missing a priority or a due date.

An idea moves from Needs attention into its priority band as soon as both fields are filled in.

Moving to execution

When work is ready to start, click Move to execution on the idea's Shortlist row. This opens the execution start modal and transitions the idea to In implementation. The action is available to admins and the category's primary reviewer; all other roles see the Shortlist in read-only mode.

The Executions page also has an Up next tab that shows the same Shortlist, giving execution managers a single place to see what is queued.

Expanding a row

Each Shortlist row has a chevron that reveals the idea's description, who submitted it, and the category's responsible person inline. The idea title is still a link to the full idea page.

Append-only

Timeline entries are not editable and are not removed. If feedback is overridden later, the new override appends a new entry; the old entry stays.

This means:

• You can audit any decision. Every override, every auto-decision, every reviewer completion is recorded.
• You can't tidy up. A wrong override stays on the timeline; the only way to "fix" it is another override that supersedes it.

What submitters learn from the timeline

Submitters can read their own idea's timeline. They can see:

• When their idea reached scored and which reviewers contributed.
• The auto-decision and the score that drove it.
• Any admin overrides, with the admin's name and the new feedback.

They cannot see other reviewers' individual scores from the timeline; that view is on the scorecard surface.

Withdraw and archive

Withdraw and archive are also transitions and appear on the timeline.

• Withdraw, initiated by the submitter, allowed before a decision is made. The timeline shows the submitter's name as the actor.
• Archive, initiated by an admin from any status. The action is idempotent; archiving an already-archived idea has no effect.

Note

The timeline doesn't capture comments or clarification threads. Those live on the idea page itself, alongside the description.

What's next

From approved to done

From approved to done covers the implementation transitions.

The feedback loop

The feedback loop explains how feedback lands and where it shows up.

Three outcomes

The three outcomes is the upstream stage.