Scientific Department

This document outlines essential guidelines and regulations concerning in-game conduct, testing requirements, promotion requirements, and many more topics. Scientific personnel and aspiring Foundation personnel are expected to adhere to these directives diligently and consult this document whenever clarification is needed.

§1: Introduction

§1.1: Department Introductory Message

Welcome to the Scientific Department! This department consists of users dedicated to researching and understanding the unknown. These tests help improve our ever-growing databases and ensure the Foundation stays safe against all kinds of anomalies.

Here in the Scientific Department you are encouraged to test as much as your heart desires and begin your journey in the department today. This document explains and contains all the information you need to make the first steps in that journey.

If at any point you have a question you cannot find the answer to within this document, send a message in our Discord server, where you can contact a member of the command team with any inquiries.

§1.2: Department Structure

The Scientific Department is divided into three core positions: the Low ranks, Medium Command, and High Command. Within these positions lies a variety of ranks users can progress through.

Low Ranks

• Intern:new members, typically inexperienced with the department and SCPs. To begin testing they must attend and pass an Intern Orientation, after which they may request a promotion.
• Lab Assistant:members who have finished the intern requirements. They assist other researchers, may co-host tests, and may host tests on certain Safe Class SCPs.
• Junior Researcher:may host tests on Safe Class and certain Euclid Class SCPs, and are responsible for their own tests and research.
• Researcher:may conduct tests on most Safe and most Euclid Class SCPs, and may conduct cross-tests on Safe Class SCPs only.
• Senior Researcher:the final low rank, able to conduct the widest variety of tests on any SCP with very minimal restrictions.

Medium Command

• Scientist:ensures the department’s operational capacity by grading events, conducting events, and supervising scientific personnel. Granted Level-3 clearance. Capacity: 11 members.
• Lead Scientist:a senior Medium Command position handling the same administrative work at a higher capacity and with more expectations. Granted Level-3 clearance. Capacity: 4 members.

High Command

• Board of Research:appoints new Medium Command members and handles all departmental affairs, ensuring the department is operational at all times. Granted Level-4 clearance. Capacity: 3 members.
• Director:the de-facto leader of the department, responsible for keeping High Command, Medium Command, and the Low ranks active. Questions for the Director should first go through the Board of Research. Granted Level-5 clearance. Capacity: 1 member.

§2: Code of Conduct

§2.1: In-Game Expectations

While professionalism and grammar are not the department’s top priority, they should not be ignored either. The command team asks that, while in-game, you use a reasonable level of grammar and maturity when speaking outside of team chat or in a public space, as you represent the department and improper behavior degrades our overall outlook.

§2.2: Disciplinary System

Punishments may vary based on the severity of the incident or who is issuing the punishment; this serves as an outline for command personnel. Punishments may only be appealed after two (2) months with no additional punishments in that timeframe. Contact a Scientist or above for more information.

§2.3: Testing Regulations

Testing is the forefront of the department’s duties. The following regulations ensure testing is ethical and is not abused.

• Interns cannot test under any circumstance and are instead required to attend an Intern Orientation.
• Any test or scientific event conducted by departmental personnel should be deemed ethical at all times. Ethical is defined by all of the following being met:
  • No Foundation personnel are harmed during the scientific event.
  • The anomaly itself is not harmed during the scientific event.
  • All testing procedures and restrictions are abided by and adhered to.
• When writing a rationale, any form of plagiarism will not be tolerated and can be met with an extreme punishment if caught.
• While conducting a scientific event, researchers are never to enter the anomaly’s containment chamber (exempt if BOR+ on 3/12/2026).
  • Scientific personnel should never interact with or touch the anomaly unless speaking with a sentient being.
• Cross-testing is defined as a test utilizing two or more SCPs (view §5.2).
  • Senior Researchers may conduct cross-tests on Keter, Euclid, or Safe SCPs, and may conduct Keter x Keter cross-tests only with Lead Scientist or above permission.
  • Researchers may conduct cross-tests on Euclid and Safe Class SCPs.
  • Junior Researchers may conduct cross-tests on Safe Class SCPs with authorization from a Lead Scientist or above.
• Scientific personnel are to abide by the Site Zulu Code of Ethics at all times.
• Mass tests are defined as a test with ten (10) or more Class-D.
  • Senior Researchers may conduct mass tests on Euclid and Keter Class SCPs with authorization from a Scientist or above.
  • Researchers may conduct mass tests on Safe and Euclid Class SCPs with authorization from a Scientist or above.
• Any orders given by the Mobile Task Forces are to be adhered to at all times; refusing their orders can result in the event being shut down.
• Race or skin color must not be used as a factor in any testing procedures. If you are caught doing this, there will be serious consequences.

§2.4: Tool Usage

This section will be finished upon site release.

Additional tools are listed as TBD in the source document.

§3: Promotions & Quota

§3.1: Promotion Requirements

• Intern → Lab Assistant
  • Attend and pass one (1) Intern Orientation.
  • Hold Level-1 clearance within the main group.
• Lab Assistant → Junior Researcher
  • Conduct three (3) tests with a grading of C or higher.
  • Pass the Junior Researcher Exam.
• Junior Researcher → Researcher
  • Conduct three (3) anomaly tests graded C or higher and two (2) tests graded B or higher.
• Researcher → Senior Researcher
  • Conduct four (4) anomaly tests graded B or higher and two (2) tests graded A.
  • No punishments within the last two (2) months.
  • Hold Level-2 clearance within the main group.
  • Show high levels of maturity and be hand-selected by departmental Medium Command.
• Senior Researcher → Scientist
  • Complete and pass your Scientist trial; must be recommended by a Lead Scientist and approved by the Board of Research.
• Scientist → Lead Scientist:selected by the Board of Research.
• Lead Scientist → Board of Research:hand-selected by the Director.
• Board of Research → Director:hand-selected by the Overseer.

§3.2: Testing Credits

Rewards program; will be finalized in the future.

§3.3: Co-Hosting Events

Co-hosting scientific events is a way for multiple researchers to work on one event; upon completion, everyone involved receives the same credit. When starting an event, Junior Researchers and above may announce they are taking co-hosts, and Lab Assistants may request permission to join (acceptance is up to the hosting researcher). Co-hosts are expected to be on their best behavior and can be dismissed at any time if deemed no longer fit to co-host.

§3.4: Anomaly Seminars & Lectures (Not In Effect)

Anomaly seminars and lectures are informative events where Scientists teach Foundation personnel and other scientific personnel about a topic of their choice pertaining to the anomalous.

Seminars teach personnel about a location and the anomalies within, and are more generalized to keep them short. Lectures are specific to an SCP and go more in-depth to give attendees a deeper understanding of the SCP at hand.

§3.5: Specialization Program

Some researchers may be more inclined to research a certain SCP or topic. The Specialization Program rewards these users so their work does not fall on deaf ears. Specializations are issued to researchers who have displayed a formidable understanding of a certain SCP, shown through their tests and research efforts.

Those who receive an SCP specialization gain access to the respective database page, receive a special mention inside the document pertaining to that SCP, and receive a medallion within the ScD Discord. Currently the only way to gain a specialization is through an SCP specialization. All HCZ SCPs are unique and have their own requirements.

Once eligible for an SCP specialization, go to the #tickets channel within the Scientific Department Discord, press the “Contact Medium Command” button, and submit proof of the tests and gradings. (Defunct until the release of anomaly actors.)

§4: Testing

§4.1: Event Types

• Intern Orientations are the first step in the department, serving to teach new members the ropes and ensure they are competent and knowledgeable in basic rules and requirements before testing.
• Tests are the most common event, used to research the unknown. Tests may only be hosted if the researcher is eligible or has the correct authorization.
  • Researchers first draft a rationale and procedure, then request permission to conduct it. Only request permission if the SCP requires an authorized rationale (view the SCP database).
  • Upon acceptance, the researcher joins Site Zulu and requests their amount of Class-D and the required combative support.
  • They bring the Class-D and combative to the SCP(s) and conduct the procedure and rationale.
  • Once finished, they open the terminal and log the test with a report of its contents.
• Seminars and Lectures provide insight on an anomalous object and its properties, for Foundation personnel or fellow ScD members. They are often hosted on a stage.
• Interviews on sentient or communicative anomalous entities help gain knowledge of behavioral and anomalous properties. Such interviews can be hosted by a Researcher.
• Anomaly Expeditions are authorized field operations hosted by a Researcher, tasked with researching or accessing an anomalous area outside the main facility.

§4.2: Testing Restrictions

Certain restrictions ensure the safety of personnel and prevent unnecessary breaches during site events. Testing may not occur on-site in the following scenarios:

• During a confirmed breach where Protocol Red has been initiated, all tests are canceled and ongoing events are terminated immediately and postponed until the breach is finished.
• During a confirmed raid where Protocol Superblue has been initiated, all tests are canceled; ongoing events may continue but should not last longer than 10 minutes.
• The Class-D Containment Zone is considered staffed if there is at least one (1) Security Department member for every two (2) Class-D present. Before requesting a test, ask on the radio “CDCZ Staffed?” and await a response.
• All tests within the Lower Containment Zone require 1 SD per 3 CD.
  • Any mass-test within LCZ requires three (3) SD members.
• All tests within the Medium Containment Zone require 1 SD per 2 CD and 1 MTF.
  • Any mass-test within MCZ requires four (4) SD members and two (2) additional MTF.
• All tests within the Heavy Containment Zone require one (1) Mobile Task Force operative.
  • Any mass-test within HCZ requires 1 SD per 1 CD and two (2) MTF operatives.
• All tests within the Biological Containment Zone require one (1) Beta-7 operative.
  • Any mass-test within BCZ requires three (3) Beta-7 operatives.

§4.3: Testing Requirements

Some anomalies are more dangerous than others and carry specific requirements to test on them. These requirements ensure scientists are adequately prepared, appropriate resources and staff are deployed, and proper precautions against accidents, containment failure, or breaches are in place.

More precautions are required for high-risk SCP testing, involving increased Mobile Task Force presence and approval from higher-ranking personnel. Failing these requirements can result in compromised safety, containment failure, or a loss of important research data.

• For Keter Class anomalies, the hardest to contain, requirements are more extensive: a number of MTF operatives, special containment chambers, and high-level personnel clearance (Level-3 and higher). Cross-testing of Keter anomalies is only authorized with approval from Scientists and above for specific cases.
• Engineering will address containment integrity, Medical will be attentive to staff health, and Ethics will ensure tests stay within Foundation regulations.

§4.4: Anomaly Expeditions

Anomaly expeditions can be hosted by anyone who is a Researcher or higher and are meant for research of an anomalous area. Currently there is only one anomalous area, Labyrinth.

• An anomaly expedition must have an objective.
• It can be hosted with or without Class-D.
• 1 SD is required per every Foundation Personnel (ScD, civil spectators).
• 2 SD per 1 CD is required.
• If the CD is under the effects of a different SCP or carrying an SCP, then 3 SD per 1 CD is required.
• At least 1 MTF is required, plus an additional MTF per every 5 members (FP, ScD, SD, CD) of the expedition.
• Test and record all important information.
• The expedition is to be halted if a riot occurs.
• After completion, the expedition is to be recorded in the #expedition_logs channel following the provided format.

§4.5: Grading Rubric

§5: Addendum

§5.1: Spectating Regulations

Spectating tests is a privilege given to faculty staff and can be revoked just as easily, to prevent abuse of the system or unnecessary risks.

• Scientific members at any rank may have spectators: up to three for LCZ tests, four for MCZ tests, and two for HCZ tests.
• These numbers are flexible; you may request more spectators with approval from a Scientist or above.
• Engineering and Logistics department members have exclusive permissions for spectating and are on reserve in case something goes wrong. They still count toward your spectator limit.
• Members of the Ethics Committee, Foundation Executives, and Internal Security Department do not count toward the spectator limit and may spectate at their own discretion.
• If questioned by a member of the Ethics Committee or Internal Security Department regarding your test, you are obligated to answer.
• Scientific members may remove or refuse spectators at any time, except for the aforementioned departments and users.
• When accepting spectators, consider the location the personnel is allowed within and the clearance level required to access the SCP (view the SCP database).
• Departments marked with (*) have the special spectating privilege noted above.
• Department of External Affairs members conducting tours may spectate tests with their tour up to MCZ tests; during this event they do not count toward the spectator limit.

The general rule of thumb for accepting spectators by clearance:

§5.2: Cross-Testing Extended

Cross-tests combine two or more SCPs to see how they interact, which often results in unpredictable or dangerous effects. To account for potential risk, strict protocols exist to maintain safety, containment, and validity.

• Senior Researchers may conduct cross-tests with Keter, Euclid, or Safe Class SCPs at a Scientist+ clearance level. They can become cleared for more hazardous tests based on experience, with increased supervision of Keter-class tests as a risk-reduction measure.
• Researchers can cross-test Safe and Euclid Class SCPs. Although less dangerous than Keter class, these are not to be taken lightly as they are unstable.
• Junior Researchers may use Safe Class SCPs alone, unless cleared by a Scientist+. This protects them as they gain experience before working with more complex anomalies.
• Only cleared staff may co-host tests with anomalies within their clearance level. A Lab Assistant, for example, will never help with Keter-class SCPs.

After cross-tests, a researcher (preferably the host) must record the results to maintain consistent and accurate records.

§5.3: Documentation Standards

Accurate and professional documentation is critical to the department’s operations. Test logs and event reports are permanent records within the Foundation database and may be referenced by senior staff, Ethics Committee personnel, or other departments.

Required formatting of a Research Log:

• SCP Name: SCP designation (e.g. SCP-173, SCP-049), object class (Safe, Euclid, Keter, etc.), Foundation clearance level (1–5), and test date (MM/DD/YYYY).
• SD/MTF Present: security detail / MTF present (e.g. 4 Security, 2 MTF), test subjects (e.g. D-283, D-134), and assigned researcher(s) (host, co-host(s), rank).
• Theory / Objective: describe the reason for the test and state the hypothesis: what is being tested and what outcome is predicted.
• Process / Procedure: step-by-step description of how the test was conducted, including preparations, containment precautions, special equipment, researcher-SCP interactions, and Class-D instructions.
• Results: record observable outcomes, including SCP activity, Class-D condition, anomalous effects, and any unexpected events.
• Conclusion / Analysis: summarize findings and their relevance, indicate whether the hypothesis was confirmed, disproven, or inconclusive, and suggest follow-up tests if applicable.
• Notes / After-Action Report: additional comments such as breach risks, psychological effects, or ethical considerations, and any unusual aftermath requiring further containment action.
• Signature: researcher name / username and departmental rank.

Standards:

• All logs must be written in complete sentences with proper spelling and grammar.
• Logs must remain objective; avoid jokes, unnecessary commentary, or exaggeration.
• Plagiarism of another member’s test logs, such as copying their whole test and submitting it as your own, is strictly prohibited and will result in disciplinary action.
• Logs must be submitted promptly after event completion.

§5.4: Research Ethics & Safety Protocols

Purpose: to uphold the integrity of the Scientific Department and ensure all research is conducted consistently with Foundation ethics and safety. This section provides clear rules for acceptable and unacceptable testing behavior.

Core Ethical Principles:

• Respect for Life: no unnecessary harm to Class-D personnel. Experiments must be justified by legitimate scientific objectives.
• Anomaly Welfare: SCP objects must not be deliberately provoked, damaged, or exploited unless explicitly required by the test rationale.
• Foundation Integrity: experiments must never compromise containment, site security, or broader Foundation goals.

Safety Requirements:

1. Pre-Test Safety Check: researchers must confirm that proper Security Department and/or MTF staff are present before beginning their test.
2. Evacuation Readiness: researchers must always have an emergency protocol prepared in case of breach or unexpected SCP behavior. Terminate the test immediately if a breach or raid is occurring.
3. Command Oversight: tests involving Keter-class anomalies require written rationale approval from a Scientist+ and must be logged before commencement.
4. Emergency Termination: researchers may request immediate test termination if containment integrity, staff safety, or SCP stability is compromised.

Unethical Testing Examples (Prohibited):

• Conducting tests with no scientific purpose (e.g. “seeing what happens” without a valid rationale).
• Excessive or repeated harm to Class-D personnel without necessity.
• Ignoring SCP containment rules for personal amusement.
• Initiating a test during site-wide emergencies (breach, raid).

Consequences of Violations:

• First offense: Verbal Warning / Formal Warning.
• Repeated offenses: Strikes or demotion.
• Severe offenses (e.g. causing breaches intentionally): Removal from the department.

§6: Conclusion

This concludes the Scientific Department handbook. All members who join are expected to read and adhere to all regulations within this document. Any questions or concerns can be directed to members of the Medium Command or High Command.