Requests

This is an information page.

It documents a Bharatpedia process, convention, or practice. It is not one of Bharatpedia's policies or guidelines, and its contents are advisory rather than mandatory. Editors should use common sense when applying it.

Shortcuts: BP:REQ · BP:REQUESTS

This page in a nutshell: This page is a directory of Bharatpedia's request venues — pages where editors may formally ask for an administrative action, a procedural step, or a community decision. Each venue has its own scope and format; use the right one.

Bharatpedia:Requests is a directory of the venues where editors may make formal requests. A request differs from an ordinary discussion in that it asks for a specific action or decision — a page to be protected, a discussion to be closed, a user right to be granted — and usually has a defined format and a defined set of outcomes.

This page is a directory, not a venue. Do not post requests here. Follow the link to the appropriate venue and post there.

Requests for administrative action[edit source]

These venues are for asking administrators to take, or refrain from taking, an action that requires the administrator toolset.

Administrators' noticeboard — the main venue for matters requiring administrator attention.
Requests for page protection — to ask that a page be protected, unprotected, or its protection level changed.
Requests for revision deletion — to ask that a revision be hidden from public view.
Requests for oversight — to ask that material be suppressed from the public record entirely.
Requests for unblock — for a blocked editor to ask that the block be lifted.
Sockpuppet investigations — to report suspected use of multiple accounts.

Requests for permissions[edit source]

Requests for permissions — the parent venue for requests for user rights, including rollback, pending changes reviewer, autopatrolled, and file mover.
Requests for adminship — for editors to be considered for administrator rights.
Requests for bot approval — to seek approval to run an automated or semi-automated account.

Requests for community decisions[edit source]

These venues ask the community as a whole, rather than a single administrator, to decide a question.

Requests for comment — to solicit outside input on a content, policy, or conduct matter.
Requested moves — to propose that a page be renamed.
Requests for merger — to propose that two or more pages be merged.
Requests for splits — to propose that a page be divided.
Articles for deletion — to propose that a page be deleted.
Requests for undeletion — to ask that a deleted page be restored.
Deletion review — to challenge the outcome of a deletion discussion.

Requests for procedural steps[edit source]

Closure requests — to ask an uninvolved editor to formally close a mature discussion.
Requests for arbitration — to ask that a serious, intractable dispute be resolved by arbitration.
Requests for mediation — to ask for moderated assistance in resolving a dispute.

Requests for content review[edit source]

Peer review — to ask other editors for feedback on an article.
Good article nominations — to nominate an article for good article status.
Featured article candidates — to nominate an article for featured article status.

Choosing the right venue[edit source]

A request posted in the wrong place is likely to be declined or ignored. Before posting, ask:

Does this require the administrator toolset? If so, use an administrative venue.
Is this a procedural step with a defined format? If so, use that step's venue rather than a general noticeboard.
Has the matter already been discussed? Content disputes should normally go to the article talk page first, before any request venue.
Is this a request for a decision, or a request for discussion? Requests ask for an action; discussions belong at the village pump or on the relevant talk page.
Has a similar request already been made and declined? Do not re-post the same request at a different venue in the hope of a different outcome.

How requests are handled[edit source]

Most request venues follow a similar pattern:

A request is posted in the venue's specified format.
Editors may comment, support, or oppose, depending on the venue.
An uninvolved administrator or editor reviews the request.
The request is closed with an outcome — granted, declined, or referred elsewhere.
The outcome is recorded and, where the venue keeps an archive, logged.

Closures should state the reasoning behind the outcome, not merely the result, so that editors can understand how the decision was reached.

Request etiquette[edit source]

Be concise. State clearly what you are asking for, and why.
Provide evidence. Use diffs and links rather than unsupported assertions.
Notify interested parties. Many venues require that editors affected by a request be notified on their talk page.
Remain civil. Personal attacks and incivility in a request undermine the request itself.
Accept outcomes. A declined request is not an invitation to re-post it elsewhere. If circumstances change materially, a fresh request may be appropriate, but repeated re-posting is disruptive.

Bharatpedia:Requests

Contents