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

# Review creator content

> How content review works in Rally: review policies, the review queue, verification and the measurement window.

## Choose a review policy

Each program sets how much review creators' posts need before they go live:

| Policy | What happens |
| - | - |
| **Required** | Every post must be approved by your team before it can go live. |
| **Optional** | Creators may ask for a review before publishing. They can also publish without one. |
| **None** | No review step. Posts go live on the creator's schedule. |

Set it in the program's terms. Changing it creates a new program version.

## Review submissions

Creators submit drafts from their portal with **Submit for review**. Submissions appear in **Review queue**. For each one, choose **Approve**, **Request changes** with a note, or **Reject**. When you request changes, the creator sees your note and can submit a new version.

> [!TIP]
>
> A per-content reward can be set to pay only for approved posts. See [Choose how creators earn](https://docs.runrally.io/help/programs/rewards.md).

## Verification and the measurement window

After a post goes live, Rally reads its numbers from the platform and verifies them. Rewards based on views or engagement wait until the program's **measurement window** has passed, so they're paid on settled numbers. Posts that need a manual check appear in **Verification**.

You can also require that a post stay public for a minimum number of days before it counts towards rewards.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.