> ## Documentation Index
> Fetch the complete documentation index at: https://help.suggix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap and Status

> Use post statuses and due dates to turn feedback into a clear product roadmap.

Suggix helps you turn feedback into a roadmap by keeping each post tied to a status, priority, owner, tags, and optional due date.

The goal is to give users enough visibility to trust the process while keeping internal planning flexible.

## Recommended status flow

Use a simple status model that your team can maintain consistently.

| Status       | Meaning                                                |
| ------------ | ------------------------------------------------------ |
| Open         | Feedback has been received but not reviewed yet        |
| Under Review | Your team is evaluating demand, scope, and fit         |
| Planned      | The request is accepted and expected to be built       |
| In Progress  | Work has started                                       |
| Completed    | The request has shipped                                |
| Closed       | The request will not be built or is no longer relevant |

<Tip>
  A smaller set of statuses is easier for users to understand and easier for your team to keep accurate.
</Tip>

## Build a roadmap from feedback

<Steps>
  <Step title="Review incoming posts">
    Read new feedback, merge duplicates when needed, and tag related themes.
  </Step>

  <Step title="Set priority">
    Use votes, comments, customer impact, and strategy to decide what deserves attention.
  </Step>

  <Step title="Assign ownership">
    Assign an internal owner so each planned item has a responsible team member.
  </Step>

  <Step title="Update status and dates">
    Move accepted work to `Planned` or `In Progress` and add a due date when you are ready to communicate timing.
  </Step>

  <Step title="Communicate changes">
    Add comments or changelog entries when important roadmap items move forward.
  </Step>
</Steps>

## Use due dates responsibly

Due dates help users understand when work may arrive, but they should be used only when your team has enough confidence.

Use due dates for:

* Committed roadmap work
* Beta launches
* Publicly announced releases
* Time-sensitive bug fixes

Avoid due dates for early ideas, exploratory work, or requests that still need product discovery.

## Public roadmap hygiene

Review roadmap items on a regular cadence.

* Keep `Planned` and `In Progress` items current.
* Remove or close stale work that no longer reflects your plan.
* Explain major changes in comments when dates or scope change.
* Publish a changelog entry when completed work ships.

## Next step

<Card title="Publish a changelog" icon="list-check" href="/guides/changelog">
  Use changelog updates to tell users what changed and close the feedback loop.
</Card>