Scientific Duties
This document outlines all guidelines, procedures, and templates regarding most test submission types.
Embedded Files
Table of Contents
🚨Want to know what you can test on?
Look at the Testing Resctions!
SECTION 1 — INTRODUCTION
The Scientific Duties lays out the regulations and procedures for how to conduct different varieties of research. Regulations within this handbook is enforceable Scientific Command and any violations will result in departmental punishment.
SECTION 2 — AUTOMATIC FAILURES
Automatic failures are factors in which a submission is automatically failed. These failures are not given for a lack of detail or formatting issues, but rather extreme cases such as disrespect, plagiarism, and other harmful content is present. An automatic failure may negatively impact your reputation in the Scientific Department.
Non-Disciplinary Failure
Failure to provide an image showing proof that the host gave credits to any Class-Ds involved; and
Turning in a test submission with too many incomplete sections.
Disciplinary Failure
Turning in a test submission where the individual's rank was lower than the required rank for that test type;
Turning in a submission that has been plagiarized or AI-generated; and
Turning in a submission that contains explicit language.
Explicit language being quoted should be censored.
SECTION 4 — PRE-TEST PREPARATION
Before beginning a test, there are several components of an effective test:
Topic: Topics are the first step toward scientific research; test hosts must have a topic on an anomaly they want to research.
Topics need to be ethical and follow the Code of Ethics; however, you may request for an exemption by going to the #special-test-requests channel in the ScD Discord Server.
Example: I want to research SCP-4966s and their interactions with SCP-1200-46.
Hypothesis: Hypotheses are assumption statements that define the cause-effect relationship between two or more variables.
Example: The consumption of SCP-1200-46 affects the transparency of SCP-4966.
Methods: Methods are the design of tests and how the test host got the results that they got.
Example: SCP-4966 will consume SCP-1200-46 and be observed by the test host(s).
Results: Results are the final component of tests and either prove or disprove the hypothesis.
Example: The researcher wants to observe the relationship between SCP-4966 and SCP-1200-46, so they let SCP-4966 consume SCP-1200-46. In conducting the research, the researcher found that their hypothesis was proven.
SECTION 5 — SUBMISSION TYPES
ScD has several types of submissions, each with distinct requirements and purposes. Below is a basic graphic that shows what duties can be done at each rank.
BASIC TESTS
Total Points: 20 (Up to 40 with 20 bonus points available)
Rank Restriction: Research Student+
Basic tests are short, Discord message-based submissions meant to help new researchers practice the fundamentals of testing.
Steps to perform a Basic Test:
Request Class-Ds and combative escorts via the "Requests" radio channel.
Escort ratio: 1 combative per 2 Class-D's
Have the escort brief the Class-Ds, then head to the SCP's containment zone.
At the containment zone, brief the Class-Ds/SCP(s) on their assigned tasks.
After the test, reward Class-Ds via the Terminal (Test Participation rating 1-0; 100 - 1300 credits).
Submit the research log with results and proof via #basic-submissions.
INTERVIEWS
Total Points: 35 (Up to 65 with 30 bonus points)
Rank Restriction: Assistant Researcher+
Interviews allow researchers to learn more about sentient anomalies and lore characters. They must always be conducted with professionalism and respect.
Containment chamber interviews require the anomaly's responsible combative unit present.
Free-roaming anomalies do not require escorts.
Proper clearance is mandatory before interviewing.
Steps to perform an Interview:
Introduce yourself and explain the interview.
Ask questions about your research topic (background, abilities, relationships, etc.)
Log the transcript and responses via #interview-submissions. Recording is recommended.
ADVANCED TESTS
Total Points: 24 (Up to 44 with 20 bonus points)
Rank Restriction: Assistant Researcher+
Advanced tests are for more experienced researchers who aim to be more creative with their presentations, earn medals, or featured in #exemplary-submissions.
Steps to perform an Advanced Test:
Request Class-Ds and combative escorts via the "Requests" radio channel.
Escort ratio: 2 combative per 1 Class-D
Have the escort brief the Class-Ds, then head to the SCP's containment zone.
At the containment zone, brief the Class-Ds/SCP(s) on their assigned tasks.
After the test, reward Class-Ds via the Terminal (Test Participation rating 1-0; 100 - 1300 credits).
Submit the research log with results and proof via #advanced-submissions.
RESEARCH PROJECTS
Total Points: 72 - 144
Each test conducted will use the Advanced Test grading rubric.
Rank Restriction: Junior Researcher+
Research projects are long-term assignments that require multiple tests to complete.
Research projects will use the project lead's testing clearance.
Research project leads may choose for their project to be private or public.
Research projects must be ethical unless an ethical waiver is received.
If a project is left inactive for more than two weeks, it will be removed.
LECTURES
Total Points: 75
Rank Restriction: Researcher+
Lectures are for public showcases on findings, anomalies, or lore.
Steps to perform a Lecture:
Announce the activity over the radio. Rally the attendees in a designated area.
Perform the theoretical section (the topic, how it works, what it does, etc.)
[IF ANOMALY TOPIC] Proceed with your attendees to the anomaly's chamber, show them the area, and give them an optional showcase.
A combative escort will be needed for this portion.
Host a brief questionnaire about the topic.
MASS TESTS
Total Points: 50 (Up to 75 with 25 bonus points)
Rank Restriction: Researcher+
Mass tests are tests of multiple Class-Ds to determine research results that require more than the minimum of used Class-Ds.
All mass tests must be approved by a Board of Research+ in the #special-test-requests channel.
Command does not require High Command approval for mass tests.
Mass tests must be ethical unless an ethical waiver is received.
SECTION 6 — ADDITIONAL RESEARCH METHODS
The Scientific Department has other methods of research other than testing. These are usually requested in the #special_test_requests forum. Check out the pinned post for additional information on the groups required for certain testing methods.
Collaborative Tests
Collaborative tests are when a maximum of three researchers, who equally work alongside each other, make a test report together. Collaborative tests give five extra research points and can count towards promotion requirements.
Collaborative tests will use the highest ranking researcher's testing clearance;
Collaborative tests must be ethical unless an ethical waiver is obtained;
All members of the collaborative test must equally contribute to the test report; and
The sections must be highlighted in a separate color and mentioned on who did what.
All members of the collaborative test will be rewarded research points for the report.
Ethical Waivers
Ethical waivers are used for when department members want to conduct an unethical test; Waiver requests are submitted in the #special-test-requests channel and the following regulations must be followed:
Assistant Researcher+ can request for ethical waivers; and
Scientific Department members may request for any ethical waivers to any anomaly that they have access to.
Ethical Waivers have to be approved by any member of the Ethics Committee.
Termination Attempts
Termination Attempts are high-risk tests on an anomaly that could lead to the endangerment or potential termination of an SCP. Termination testing is limited to Senior Researchers. The requirements are as follows:
The purchase of the "Termination Attempt" reward from the reward shop.
Making a corresponding post in the #special_test_request forum.
A detailed plan for the process of the termination attempt - Show us the thoughts you put into the test!
Explanation of the scientific data you plan to gather from this test: What are you trying to find out? How do you plan to find out?
For object anomalies, the termination waiver has to be approved by the Research Director.
For sentient anomalies, the termination waiver has to be approved by the AA Director and Research Director.
The Research Director may set additional requirements depending on the nature of the test.
Lastly, a member from ScD Command will be required to supervise the experiment to ensure the outlined process for the attempt is being followed.
Less regulated termination attempts may be conducted as a reward for different awards. These are approved on a case-by-case basis by the Research Director and other involved parties.
Field Tests / Dangerous Experiments
Field Tests and Dangerous Experiments are forms of testing that are done in close collaboration with Mobile Task Forces - Eta-9 Wardens. These may range from proposed re-containment methods that Eta-9 may trial for you to tests that are inherently dangerous or are likely to go wrong.
Both versions are requested in the Eta-9 server in the #special_requests forum.
Dangerous Experiments are conducted as normal, with possible requirements being set by Eta-9.
Field Tests will be completed over time by any Eta-9 member, with results being logged in #field_reports.
Both may be requested for any SCPs within your testing clearance.
Controlled Breaches
Controlled breaches are tests that require the SCP to be in a breached state to be properly conducted. This may include new forms of re-containing the anomaly or for other reasons.
These may be requested in the #special_test_requests forum.
Controlled breaches are reserved for special cases that can not be done or would be unreliable in the form of a field test.
Controlled breaches may be requested by any Senior Researcher.
Controlled breaches require approval from Eta-9 Central Command.
SECTION 7 — 173 CLEANINGS
This guide outlines the proper procedures for conducting SCP-173 containment cleanings.
Eligibility
Only Junior Researcher+ are authorized to conduct SCP-173 containment cleanings. Authorized participants include:
Scientific Department: Junior Researcher+
Security: Security Guard+ (required combative escort; Eta-9 will take over if on-site)
Class-D: A minimum of two Class-Ds are required
Radio Notification
Containment cleanings for SCP-173 may only occur after an official radio notification indicates the chamber requires cleaning (approximately ~30 minutes).
Cleaning Preparation
Before starting:
Confirm radio notification that the cleaning is required.
Request Class-D participants through the radio's request channel (other ScD can spectate; however, they cannot co-host).
Gather cleaning equipment (e.g., mops and buckets).
Brief all Class-D participants on the procedures.
After the cleaning:
Complete the log and post it in the #cleaning-logs channel.
Rewards
Cleanings reward both the host and the participants for their contribution:
Class-D: Earn credits from the host via the Terminal (Test Participation rating 1-10; 100 - 1300 credits).
Host: Earn 10 research points for hosting the cleaning.
SECTION 8 — DISCOVERIES
The Discovery Program rewards creative, original, and meaningful research that contributes to the Foundation's understanding of anomalies, chemicals, or lore. Researchers who make verified discoveries can earn bonus research points and have their findings permanently recorded in department archives.
Submission Process
Submissions are reviewed by the Command team to check if:
It's a valid discovery
It's already known
Or just a bug/not valid
Verification (if needed) requires a simple repeat test. No full test report is required.
Verification is usually handled by the Command team.
Type of Discoveries
Anomaly Discoveries - Added to an anomaly's record
Chemical Discoveries - Added to the chemical records
Lore Discoveries - Added to the lore records
SECTION 9 — SPECIALIST PROGRAM (ON HOLD)
On hold until further notice.
Safe Specialist
Euclid Specialist
Keter Specialist
Chemical Specialist
This documentation was created and approved by Central Command.
Page updated
Google Sites
Report abuse