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

# The Document Review Workflow

> Confidence scores, health flags, and the approve/deprecate review queue

Every new Document starts out as a **draft** and isn't visible to general
search until a reviewer approves it. This keeps unfinished or unvetted
content out of search results while still letting the right people see and
work on it early. This page covers how that review process works.

## Health flags

Each Document can carry one or more health flags, shown as badges wherever
Documents are listed:

| Flag         | Meaning                                                                                                       |
| ------------ | ------------------------------------------------------------------------------------------------------------- |
| `thin`       | The content is short enough that it may not be substantive yet.                                               |
| `unreviewed` | No one has marked this Document as reviewed.                                                                  |
| `orphan`     | This Document isn't connected to any domain or linked from any other Document, so it may be hard to discover. |
| `stale`      | The content hasn't been reviewed in a long time and may be out of date.                                       |
| `drifted`    | The content may no longer match its original source.                                                          |
| `derived`    | This content was derived from another source document.                                                        |

These flags are meant as pointers for reviewers — a quick way to spot
content that needs a second look, not a judgment on whether it's wrong.

## Confidence

Every Document has a **confidence** score, shown as a percentage, that
reflects how much a reader should trust it at a glance — based on things
like age, whether it's been reviewed, and how substantial the content is. A
reviewer can override this score when approving a Document, if they have
reason to trust it more or less than the automatic score suggests. Wherever
confidence is shown — in the review queue or in search results — the
reviewer's override takes precedence when one has been set.

## The review queue

The **Review Queue** page lists draft Documents in the domains you're a
reviewer for. If you're an org admin but haven't been individually assigned
as a reviewer for any domain, this list will look empty — you can still act
on any Document directly (see below), just not browse them here. For a
full, org-wide view of the backlog across every domain, see
[Queue Health Monitoring](/knowledge-base-queue-health).

You can filter the queue by health flag, using the same filter available on
the search page.

### Previewing a Document

Clicking **Preview** on a queue row opens the full Document content. You'll
only be able to preview Documents you're actually authorized to see — the
same rule applies whether you reach a Document through the queue or through
a direct link. If you're not authorized, or the Document doesn't exist,
you'll see a generic "unable to load" message rather than any part of its
content.

### Approving a Document

The **Approve & Publish** button moves a Document from draft to published,
making it visible to general search. You can optionally set a confidence
override at the same time, if you want reviewers and readers to trust this
content more or less than its automatic score suggests.

### Deprecating a Document

The **Deprecate** button retires a Document — typically one that's become
outdated — without deleting it. Deprecated Documents stop showing up in
general search but remain visible to reviewers and admins.

## Summary: who can do what

| Action               | Who can do it                                        |
| -------------------- | ---------------------------------------------------- |
| List review queue    | Reviewers, scoped to their assigned domains          |
| Preview a Document   | Reviewers (their domains) or org admins (any domain) |
| Approve a Document   | Reviewers (their domains) or org admins (any domain) |
| Deprecate a Document | Reviewers (their domains) or org admins (any domain) |

For the full picture of reviewer and admin access, see
[Permissions & Roles Explained](/permissions-explained).