The Promotions Team on the SCP Wiki is concerned with ensuring promotions occur — be they from average user to Junior Staff or Operational Staff to Moderator — we keep staff team's bloodflow going.
To further explain, Promotions Team makes Team Sub/Captains aware of potential Junior Staff applicants in their respective threads. Additionally, we communicate with Team Sub/Captains to verify the questions they have on their threads are up to date at triannualy. We also manage the triannual staff promotions cycles. And of course, we also deal in mod tools promotions.
LINK TO STAFF RECRUITMENT QUESTIONS: Here.
Teams Using Promotions Team Services
- Community Outreach
- Internet Outreach
- Site News
- Data Analysis
- Art Committee
- Critique Team
- Curation Team
- Collaboration Pages Team
- Adult Pages/Content Warning Team
- Guide Updating Team
- Rewrite Team
- Licensing Team
- MAST
- 05 Updating Tea
- Sandbox Cleaning Team
- Tagging Team
- Deletions Team
- Promotions Team
- Internal Communications
- Internal Promotions
- External Recruitment
- Tech Team
INTERNAL COMMUNICATIONS
Internal communications, as the name implies, communicates with the Sub/Captains of all teams we help recruit. We make sure the questions the Sub/Captains want potential Junior Staff to answer are up to date on a trianual basis, same time as promotions. We also update the questions if the Sub/Captains want to update them before our triyearly check-in.
INTERNAL PROMOTIONS
Internal promotions very closely follows the schedule set out on 05 Command, particularly in regards to scheduling. The schedule is updated once per year on January 1st to ensure it stays within given guidelines and intentions (namely the scheduled voting period as laid out at the top of the page).
The first step is simply informing captains, vice captains, and admins that promotions will begin in a week's time, allowing them to begin discussing and considering who to place up for promotions. After a week, an official notice for the submission of promotion candidates will be posted. Alongside this notice is posted Junior Staff members that have been on staff for a year or more as stated by the Junior Staff promotions reform policy so captains may evaluate whether they are to be promoted or retained for another cycle. Junior Staff who have already been retained for an additional cycle are to be put up or removed from their position. Additionally, if this is the Winter Promotions cycle, any candidates for mod tools as well as any individuals whose mod tools are to be retained is to be created alongside promotions.
This submission period lasts two weeks, during which captains, vice captains, and admins will be reminded of the deadline. If teams do not have any promotions, they are to notify the Promotions Team of such. If a week has passed and candidates (or lack thereof) are still missing from teams, captains are to be individually notified regarding the upcoming deadline.
Once all promotion candidates are acquired and the deadline is met, a discussion thread regarding the nominees will be made on both the mainsite forum and 05 Command promotions forum. After two weeks have passed of discussion has passed, an official voting thread will be posted containing a required quorum and rules regarding promotion. Staff have a week to vote, during which any staff currently subject to the Inactivity Policy are to be individually notified. If it is the Winter Cycle, a thread for mod tools renewal is also created.
After a week has passed, voting will be closed and results tallied, with successful promotions being announced on the SCP Official Staff Server. Following promotion, results of each candidate are to be tallied up (yays, nays, abstentions, and total votes) and posted in the thread, alongside a list of active staff who did not vote this cycle. If an individual has not voted in the past two cycles, in accordance with the Inactivity Policy they are to be retired unless they are chosen to be retained via admin fiat.
EXTERNAL RECRUITMENT
External recruitment is responsible for assisting teams with the actual process of recruiting new staff from among the community. To do this the subteam has several aims which drive our internal processes.
Aim 1: Help individual staff teams set up recruitment threads in the site forums. Coordinate with individual staff teams to regularly check these threads, notify team captains of new potential recruits, and make sure there is followup.
Aim 2: Aim 2 is a somewhat more involved process and responsibility than the other two. It will include:
- Identifying potential candidates within the community for recruitment. This should largely occur by monitoring user activity and behavior in community spaces, both official and where applicable, non-official. A nonexhaustive list may include skipIRC, the official Foundation Discord (including SCP-General, Wiki Talk, Deer College/Critique Channels), onsite forums/discussion threads, edits from users who are applying tags or otherwise making small SPaG or formatting corrections to existing work.
- Identification of these candidates will largely be based on several different factors.
- Interest in policy work which meshes with staff goals and/or introduces new practical approaches to existing problems.
- Interest in contributing to normal staff functions (maintenance, licensing, community and internet outreach, curatorial responsibilities, image replacement, etc.).
- Effective communication and maturity.
- Obviously doesn’t need to be said that team members must be aware of user history with the community, including interactions with existing staff members.
- Evaluating which team a candidate might be the best fit for, and then contacting the teams captains/vice captains to suggest they should reach out.
- Making sure that team captains follow up on such efforts.
- Reminder, Junior Staff must have been Site Members for 100 days.
Aim 3: Onboarding new junior staff in Staff Cord. Individual teams may have more specific onboarding processes, and if they don’t, then its probably our responsibility to encourage team captains to put them in place. In terms of staffcord, we will be responsible for introducing what each channel is for, the relative opsec for each channel and their general use cases, as well as walking new junior staff through acceptable behavior as a staff member in these spaces.
