Wikipedia:Pending changes/Provisional policy
Appearance

- Edits on articles protected by pending-changes protection will not be displayed to readers who are not logged in, until the edits are checked by reviewers. Pending-changes protection (PC protection) is useful for quashing inappropriate editing while allowing good faith users to submit their edits for review.
- Reviewers are users with a similar level of trust to rollbackers (including all administrators) and the right can be granted and removed by any administrator. Reviewer rights are granted upon request at Wikipedia:Requests for permissions. Potential reviewers should recognize vandalism, be familiar with basic content policies such as the policy on living people, and have a reasonable level of experience editing Wikipedia. It is recommended to read the reviewing guideline, where the reviewing process is detailed, as well as expectations for a reviewer.
- Pending changes should be used on pages where the disruption to good-faith editing caused by existing protection tools would be disproportionate to the problem the protection seeks to resolve. It can be set to hold back edits by IP/non-autoconfirmed users (level 1) or by all non-reviewers (level 2). Suitable issues for pending changes protection include persistent:
- Vandalism;
- Re-insertion of rumor, error, and NPOV/V/OR violations;
- Edit warring by large groups of unregistered users;
- Disruption by users on highly variable IPs.
- These standards are to be interpreted more liberally on biographies of living persons, or in any situation involving content related to living persons. As with other forms of protection, PC should not be used preemptively.

- As with other forms of protection, the time frame of the protection should be proportional to the problem. Indefinite PC protection should only be used in cases of severe long-term disruption.
- Pending-changes protection should only be restricted to reviewers in cases where full protection would usually be appropriate; for example on articles persistently targeted by sockpuppeteers with autoconfirmed accounts. Like semi-protection, it should never be used in genuine content disputes, where there is a risk of placing a particular group of editors at a disadvantage.