# Status Legend

## Purpose

Use this legend to label every LinkUp feature the same way. The label should describe the current truth, not the future plan.

## Status labels

<table id="bkmrk-status-meaning-when-"><tbody><tr><th>Status</th><th>Meaning</th><th>When to use it</th></tr><tr><td>Implemented</td><td>The feature exists and matches the intended workflow.</td><td>Use after the feature has been checked in the app, admin panel, API, or mobile app.</td></tr><tr><td>Partial</td><td>Some pieces exist, but the full workflow is not complete.</td><td>Use when web, mobile, admin, or backend support is uneven.</td></tr><tr><td>Legacy Only</td><td>The feature exists only in the old system or old screen.</td><td>Use when the feature has not moved into the current LinkUp surface.</td></tr><tr><td>Missing</td><td>The feature does not exist yet.</td><td>Use when no route, screen, admin tool, or mobile flow can be found.</td></tr><tr><td>Planned</td><td>The feature is intended but not live.</td><td>Use for roadmap items, proposed workflows, or future policy.</td></tr><tr><td>Needs Verification</td><td>The docs or code suggest the feature exists, but it has not been tested.</td><td>Use when a human needs to check the real screen before publishing.</td></tr></tbody></table>

## Rule of thumb

If we are not sure, use **Needs Verification**. Do not turn uncertainty into a confident help article.

## Implementation check table

<table id="bkmrk-expected-behavior-st"><tbody><tr><th>Expected behavior</th><th>Status</th><th>Surface</th><th>Manual check</th></tr><tr><td>Every KB article uses one of the approved status labels.</td><td>Implemented</td><td>BookStack</td><td>Review each page before publishing.</td></tr><tr><td>Unverified workflows stay marked until tested.</td><td>Implemented</td><td>Authoring process</td><td>Search BookStack for `Needs Verification` and `[VERIFY:`.</td></tr></tbody></table>

## Gaps / notes

This page is an authoring control. It does not prove whether a product feature works.