Pending changes protection is a tool used to suppress vandalism and certain other recurrent nuisances on Wikipedia while allowing a good-faith user to submit an edit for review. Intended for infrequently edited articles that are experiencing high levels of such troublesome edits from new or unregistered users, pending changes protection can be used as an alternative to semi-protection and full protection to allow unregistered and new users to edit pages, while keeping the edits hidden to most readers until they are accepted by a reviewer. There are relatively few articles on Wikipedia with this type of protection.
When a page under pending changes protection is edited by an unregistered (also called IP) editor or a new user, the edit is not directly visible to the majority of Wikipedia readers, until it is reviewed and accepted by an editor with the reviewer right.
Pending changes are visible in the page history, where they are marked as pending review. The latest accepted revision is displayed to the general public, while logged-in users see the latest revision of the page, with all changes applied. When editors who are not reviewers make changes to an article with unreviewed pending changes, their edits are also marked as pending and are not visible to most readers.
Both logged-in users and unregistered users who click the "edit this page" tab edit the latest version as usual. If there are pending changes awaiting review, there will be a dropdown box next to the article title, pointing to the pending changes.
Pending changes may be used to protect articles against persistent vandalism, violations of the biographies of living persons policy, and copyright violations.
Applying pending changes protection
|For the policy on applying pending changes protection, see Wikipedia:Protection policy#Pending changes protection. This section is intended to supplement or clarify the policy. If they disagree, please defer to the policy or discuss the option of changing it.|
Administrators may apply pending changes protection to pages that are subject to heavy and persistent vandalism, violations of the biographies of living persons policy, or insertion of content that violates copyright. Pending changes protection should not be used as a preemptive measure against violations that have not yet occurred, nor should it be used to privilege registered users over unregistered users in content disputes. Pending changes protection should not be used on articles with a very high edit rate, even if they meet the aforementioned criteria. Instead semi-protection should be considered.
In addition, administrators may apply temporary pending changes protection on pages that are subject to significant but temporary vandalism or disruption (for example, due to media attention) when blocking individual users is not a feasible option. 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.
Like semi-protection, PC protection should never be used in genuine content disputes, where there is a risk of placing a particular group of editors at a disadvantage.
Editors without administrator privileges can request page protection if the above criteria are met. Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.
Reviewing pending edits
|For the guideline on reviewing edits, see Wikipedia:Reviewing pending changes. This section is intended to supplement or clarify the guideline. If they disagree, please defer to the guideline or discuss the option of changing it.|
The process of reviewing is intended as a quick check to ensure edits don't contain vandalism, violations of the policy on living people, copyright violations, or other obviously inappropriate content. Reviewers are sufficiently experienced users who are granted the ability to accept other users' edits. Reviewers have a similar level of trust to rollbackers; all administrators have the reviewer right. 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. Reading the reviewing guideline, where the reviewing process and expectations for a reviewer are detailed, is recommended.
Acceptance of an edit by a reviewer is not an endorsement of the correctness of the edit. It merely indicates that the edit has been checked for obvious problems as listed above.
Reviewer rights are granted upon request at Wikipedia:Requests for permissions. While any administrator has the technical ability to remove the reviewer permission, removal should occur only as the result of consensus from a discussion or when an editor requests the removal of their own permission. Discussion regarding removal of the reviewer permission should normally occur at the Administrators' noticeboard. Discussion with the involved editor and/or a request for a second opinion at the Pending changes talk page is recommended before formally requesting removal.
Reviewing of pending changes should be resolved within reasonable time limits (at most a few hours). Backlog management should be coordinated at a community level. The backlog can be viewed at Special:PendingChanges. As of January 2013, edits are rarely unreviewed for more than two to three hours and the backlog is frequently empty.
Pending changes adds highlighting that is lost when disabled
In the edit history, accepted revisions are highlighted, which improves readability. Additionally, visible tags are applied to indicate why particular edits were accepted ("automatically accepted"/"accepted by [Username]"). As of September 2018, this highlighting is still permanently lost for past changes on a given page whenever the pending changes setting is disabled.  When pending changes are enabled again, the highlighting will only be applied to newer changes. Therefore, it is a good choice to leave pending changes enabled when other protections are applied. 
Effect of various protection levels
|Unregistered or Newly registered||Auto-confirmed, Confirmed||Extended confirmed||Pending changes reviewer||Admin||Appropriate for|
(See also: Wikipedia:Protection policy)
|None||normal editing (can edit; changes go live immediately)
"Go live" means the changes become visible to readers who are not logged in to Wikipedia. In all cases throughout this table, changes are immediately visible to readers who are logged in.
|The vast majority of pages|
|Pending changes||can edit but changes don't go live until reviewer acceptance||normal editing but if there are previous pending changes, no changes go live until the pending changes have been reviewed||normal editing*
and can accept pending changes
|Infrequently edited articles with high levels of vandalism or BLP violations from unregistered and new users|
|Semi||cannot edit||normal editing||Articles with high levels of vandalism or edit warring from unregistered and new users; some highly visible templates & modules|
|Extended confirmed**||cannot edit||normal editing||Specific topic areas authorized by Arbcom; pages subject to persistent disruption that semi-protection has failed to stop|
|Template||cannot edit (unless Template editor, in which case normal editing)||normal editing||High-risk templates & modules|
|Full||cannot edit||Articles with persistent vandalism or edit warring from (auto)confirmed accounts; critical templates & modules|
|* When an Administrator or Pending Changes Reviewer edits an article that has pending changes awaiting review, they must review the pending changes before their own edit goes live.|
** This row assumes that a Pending changes reviewer is also Extended confirmed. (A Pending changes reviewer needs the separate Extended confirmed right to edit through Extended confirmed protection; in practice nearly all Pending changes reviewers will have the Extended confirmed right.)
Frequently asked questions
- If an established user edits an article with unreviewed pending changes, is the new version automatically accepted?
- No. If the user is a reviewer (that is, the user has been granted the "reviewer" permission), they will be prompted to review and accept any unreviewed pending changes. If the user is not a reviewer, the edit will also be marked as "pending review". (Reviewers can test this by unaccepting the current version of a page under pending changes and then trying to edit.) An exception to this is when a user reverts a pending edit to the latest accepted revision: in this case the revert is automatically accepted.
- What happens if several IP edits to an article under pending changes result in a null edit? (For example, an IP makes an edit, then another IP undoes it.)
- If they were all made by a single IP, the new version is automatically accepted. If different users edited, the new version is not accepted (to prevent potential abuse).
- On which kinds of pages can pending changes be used?
- At first, it was determined by consensus that pending changes could be used only on articles, subject to the protection policy, and on test pages in project space. A later request for comment found it permissible to use pending changes beyond articles; however, it is restricted by the software to the main and project namespaces, and no request to allow other namespaces was made. It is not technically possible for talk pages to be placed on pending changes.
- Wasn't pending changes protection dropped?
- Yes and no. Pending changes protection was deployed on a trial basis in 2010. In 2011, pending changes protection was dropped as a mechanism for protecting pages, until a consensus agreement on its deployment was reached. There have been a series of discussions on using the feature and it was put back into service on December 1, 2012. Since then only pending changes level 1, affecting the edits of new and unregistered users, is being used. As of January 2017 there has been consensus to drop pending changes level 2, and as a result only level 1 is now used.
- How can you tell if a page has pending changes protection?
- Protected pages are normally marked with a small white-colored padlock symbol in the top corner depending on its level of protection. Also, there will be a drop-down box next to the article title, pointing to the pending changes, if there are any.
Below is a list of past discussions and polls relating to the Pending Changes feature:
- March 2009: First poll 4 to 1 approving original trial
- May 2010: RFC on some pre-trial issues
- June 2010 – August 2010: Pending changes trial
- August 2010: Straw poll 2 to 1 in favor of continuing PC in some form
- September 2010: Straw poll on interim usage
- September 2010 – May 2011: Continuation of pending changes without clear mandate
- February 2011 – May 2011: PC RfC 2011 Ended the original PC trial.
- March 2012 – June 2012:
PC RfC 2012 established consensus to enable PC before the end of 2012.
- September 2012: WP:PC2012/RfC 1 discussed whether to use Level 2 pending changes.
- October 2012: WP:PC2012/RfC 2 discussed when to apply pending changes, the criteria for rejecting edits, and various ideas for reducing backlog.
- November 2012: WP:PC2012/RfC 3 discussed deployment and usage of the pending changes feature.
- December 2012 – : Pending changes re-enabled on a permanent basis
- May 2013: PC RfC 2013 is closed as requiring further discussion for implementation. It reopened the question of whether to use Level 2 pending changes.
- January 2014: PC RFC 2014 opened to determine if there is consensus on how to implement pending changes level 2. By the time it was closed in June, there was no longer a consensus to use pending changes level 2 at all, but if and when such a consensus does develop, there is some consensus on when to apply it.
- October 2016 DC RFC 2016 opened to determine if the edit filter, bots and ORES should be allowed to defer suspicious edits for review using deferred changes. The RfC passed in its entirety.
- November 2016 PC RFC 2016 #1 opened to propose lowering the auto-accept threshold for PC2 and establish usage criteria.
- November 2016 PC RFC 2016 #2 opened to propose several things, including implementing pending changes for all articles, implementing it for certain types of articles (including good articles, featured articles, vital articles, and biography of living persons articles), auto-granting the reviewer right for those meeting certain criteria, and creating a semi-automated tool for reviewing. The portion for creating a semi-automated review tool was withdrawn from the RfC as not needing consensus, and the RfC was later snow-closed with consensus against all remaining proposed changes.
- January 2017 RFC to remove pending changes level 2, after all RFCs on the subject failed to achieve consensus for using it.
- Wikipedia:Flagged protection and patrolled revisions, the original trial proposal.
- Wikipedia:Deferred changes, proposal to allow bots, the edit filter, and/or ORES to defer suspect edits for review (originally Wikipedia:Deferred revisions).
- Wikipedia:Patrolled revisions, a request for a passive reviewing system, part of the original proposal.
- Wikipedia:Pending changes blocks, proposal for a form of user specific editing restriction that is to a classic block what pending changes protection is to classic protection.
- Wikipedia:PC2012, an overview of the 2012 implementation of pending changes.
- Wikipedia:Pending changes caveats, an essay on why the use of pending changes was severely limited.
- Special:PendingChanges, pages with pending edits.
- Special:StablePages, pages under pending changes.
- Special:ValidationStatistics, various statistics pertaining to the Pending Changes feature.
- Template:Pending Changes backlog, a display of the current backlog, which can be added to user pages.
- Special:Log/stable, actions to enable or disable pending changes.
- Special:AdvancedReviewLog, actions to review edits.
- As of September 2018, there are no protections weaker than pending changes level 1 (PC1), therefore PC1 will not interfere when other protections are enabled.