Policies/en/Office-Actions-Policy/Procedures
This is a draft version. Source: adapted notably from the Wikimedia Foundation Governance Wiki, https://foundation.wikimedia.org/wiki/Policy:Office_actions/procedures (CC BY-SA 4.0), with changes. Status: proposal, to be adopted. See the detailed disclaimer.
In simple words: this page shows, step by step, who would check what before an office action is taken. No single person could decide alone: each action would go through several levels of review. The tables below list the baseline steps for each type of action.
Office actions procedures
In order for an office action to be considered and enforced, the following baseline steps would be involved, as relevant to the requested office action. This list is not exhaustive; steps listed here may be expanded to include more steps or removed entirely depending on the type of office action requested. This baseline list of steps is published in the spirit of transparency.
The review roles named below (team member, manager, director, department chief, communications, legal, executive direction) are those of the source organization. They are kept as an indicative review chain: at adoption, they would be mapped to the actual structure of the Ynternet.org Foundation and of the future WikiDeal governance bodies. All requests would be received through info@wikideal.net and routed internally.
Primary and secondary actions
| Foundation global ban | Foundation event ban | Copyright takedown compliance | Child protection | Conduct warning | ||
|---|---|---|---|---|---|---|
| 1 | Request office action from the Foundation. | info@wikideal.net | info@wikideal.net | info@wikideal.net | info@wikideal.net | No |
| 2 | Request acknowledgement. | Yes | Yes | Yes | Yes | No |
| 3 | Request evaluation by relevant team member and suggestion of a course of action. | Yes | Yes | Yes | Yes | Yes |
| 4 | Review by the member's team and manager. | Yes | Yes | Yes | Yes | Yes |
| 5 | Review by the team's director or lead manager. | Yes | Yes | No | No | Yes |
| 6 | Review by the department's chief. | Yes | Yes | No | No | Yes |
| 7 | Review by the legal function. | Yes | Yes | Yes | Yes | Yes |
| 8 | Review by the communications function. | Yes | Yes | No | No | Maybe |
| 9 | Review by the executive direction. | Yes | Yes | No | No | Maybe |
| 10 | Enforcement of the office action and notice to the affected individual. | Yes | Yes | Yes | Yes | Yes |
| 11 | Notice to other affected parties. | Yes | No | No | Yes | Yes |
| 12 | Dissemination of information relevant to the office action to specific groups. | Maybe | Yes | No | No | Yes |
| 13 | Appeal option | Yes | Maybe | Yes | No | Maybe |
Actions involving advanced rights
| Interaction ban | CheckUser | Page protection | Advanced rights removal | Range blocks | ||
|---|---|---|---|---|---|---|
| 1 | Request office action from the Foundation. | No | No | No | No | No |
| 2 | Request acknowledgement. | No | No | No | No | No |
| 3 | Request evaluation by relevant team member and suggestion of a course of action. | Yes | Yes | Yes | Yes | Yes |
| 4 | Review by the member's team and manager. | Yes | No | Yes | Yes | Yes |
| 5 | Review by the team's director or lead manager. | Yes | No | Yes | Yes | Yes |
| 6 | Review by the department's chief. | Yes | No | No | Yes | No |
| 7 | Review by the legal function. | No | No | No | Yes | No |
| 8 | Review by the communications function. | Maybe | No | No | No | No |
| 9 | Review by the executive direction. | Maybe | No | No | No | No |
| 10 | Enforcement of the office action and notice to the affected individual. | Yes | Yes | Yes | Yes | Yes |
| 11 | Notice to other affected parties. | Yes | No | No | No | No |
| 12 | Dissemination of information relevant to the office action to specific groups. | No | No | No | Yes | No |
| 13 | Appeal option | Maybe | No | Yes | Yes | Yes |
Certain steps of the aforementioned process may be omitted and others may be added, subject to each specific office action and the relevant policy that prescribes it.