Policy status and phases

Category policy
Copyright policy
Deletion policy
Speedy deletion
AI Policy
DNP policy
NDA policy
Editing policy
Disruptive editing policy
External links
Neutrality policy

Images policy
Naming policy
Personal articles
Stub policy
User naming
Vandalism policy
Writing policy

See also: guidelines, administrators
Icon-shortcutShortcut: SP:PSP

The life of a Sasukepedia policy

These are the statuses and phases that policies at Sasukepedia will go through before being adopted (implemented and followed by Sasukepedia users) or otherwise:

Policy status and phases

Policy pages should have a status at the top that indicates whether the policy is still a proposal, ratified, or adopted. A policy can also be recalled by users or vetoed by the Admins.

  • Policy/Proposal – The policy proposal is open for voting.
  • Ratified – The policy is in effect, but there are changes that need to be carried out or implementation details to solve before it can be fully adopted.
  • Adopted – This policy is officially accepted by the Sasukepedia community insofar as those who voted represent the community. It has been fully implemented.
  • Recalled – If an adopted policy gets more no votes than yes votes at some time in the future, it becomes recalled back to a status similar to proposal status, except that if the no votes exceed yes votes for some period of time (recall time), the policy becomes a candidate for deletion.
  • Vetoed – The admins can always veto a policy outright. Their rule is law, but the users can of course comment on vetoed policies to try to persuade the admins.

Vote ratios and time

  • Ratification minimum – the winning side must have a minimum of 5 votes.
  • Ratification ratio – if the ratification minimum has been met and the yes votes exceed the no votes by 3 to 1, then the policy is has met the ratification ratio. Examples: 5:1, 6:2, 9:3, etc..
  • Ratification time – the winning side must remain winner for 1 week (7 days). However, if the ratification ratio is high (4 to 1 in favor) and the number of yes votes is high (15), 3 days is enough.
  • Recall time – also 1 week (7 days). However, if the recall ratio is high (4 to 1 against) and the number of recall votes is high (10), 3 days is enough.

The standard for a quick recall votes is lower than for adoption, since a policy that people mostly don't like is likely to cause more trouble than a policy that people do like, but some disagree with.

Decreed policies

Some policies will be established by admin via decree without voting, unlike normal policies.

Community input is still valued in cases where an admin doesn't seem to have good reasons, so maybe another admin will revert it. Like with any other policy, you can start a vote to recall it. Or a new policy proposal to change it. But be aware that if you're e.g. proposing that Sasukepedia should contain exploit information, any administrator is likely to Veto it outright.

Grandfathered policies

A grandfathered policy is a something that had been in effect and actively enforced by admins as well as the vast majority of the contributors for a long time without it having been a documented policy. This kind of de-facto standard can be documented after the fact as a grandfathered policy; usually by administrators.

Like with any other policy, you can start a vote to recall it. Or a new policy proposal to change it.


The following banners will appear on policy pages (proposal or otherwise) to indicate their status (and phase):


The following templates can be used for setting up votes in discussion area of policy article:

These templates will appear, but don't need to be added manually:

Note that unlike "Vote" and "Delete" templates, there are no "/Closing" subtemplates for policies. The reasoning is that if no-one cares enough to go check up on his policy without having a list of closing policy votes, perhaps it did not deserve to be a policy in the first place?


See Also

Community content is available under CC-BY-SA unless otherwise noted.