---
# System prepended metadata

title: SoP - Alert Levels / Emergencies
tags: [SoP]

---

###### tags: `SoP`
# SoP - Alert Levels / Emergencies

## Alert Levels

Alert levels are set by command staff, or acting command staff, to indicate the status of the installation.

### Code Green - All Clear

Standard operating level. No suspected, or immediate threat to the installation.
All departments may carry out work as normal.

- Suit sensors are not required.
- Security must have weapons holstered.
- Security may not wear specialized body armor.
- Security staff require permits to freely carry non-standard weaponry.
- Crew members may freely walk in hallways and maintenance areas.
- Secure areas should not be pre-emptively bolted down, except for the Vault and the AI Core.
- All searches must have valid reasoning; Privacy laws are fully in effect.

### Code Blue - Suspected Threat

Elevated alert level. There are reports or other evidence available to indicate that there is a possible threat to the installation.

- Suit sensors are recommended to be set to vitals, but are not required.
- Security must have weapons holstered.
- Security may not wear specialized body armor.
- Security staff require permits to freely carry additional weaponry.
- Privacy laws are relaxed. Searches require probable cause, rather than a warrant or charge.
- Secure areas may be bolted down as necessary.

### Code Yellow / Orange / Violet - Emergency

Raised alert level. Confirmed security threat to the facility.

The alert level picked should match the **highest** severity threat. Often times, conditions are met for more than one code activation.

- Suit sensors must be set to vitals or higher. Security may detain in cases of non-compliance.
- Security staff may be outfitted with armaments and armor necessary to contain the threat.
- High security areas may be locked down as necessary
- Maintenance access may be restricted by command orders.

#### Code Yellow - Security Alert

Security threat on the facility, or intruder alert.
The Head of Security and Facility Director hold primary authority during Code Yellw.

- Security staff may search anyone with probable cause.
- Security staff may freely search departments with probable cause.
- Security may mandate tracker-level sensors for any person, group of people, or the entire facility.

#### Code Orange - Engineering Emergency

A major engineering emergency, such as multiple active breaches, engine delamination, or life support failure.
The Chief Engineer and Facility Director hold primary authority during Code Orange.

- Crew are to avoid afected or damaged areas of the station outside of necessity. Violators may be detained for rubbernecking / failure to obey safety protocol.
- Engineering staff may lock down areas of the installation as necessary.
- Engineering staff have free access to departments as necessary to contain the situation.
- In extreme cases, tracker-level sensors may be mandated by command.

#### Code Violet - Medical Emergency

A major medical, biological, chemical, radiological, or anomalous threat, or a large number of injured personnel.
The Chief Medical Officer and Facility Director hold primary authority during Code Violet.
The Research Director holds primary authority as well if the threat may require the intervention of the Science Division, or is anomalous in nature.

- Tracker-level sensors may be mandated by the Medical department.
- Crew are to avoid interfering with Medical personnel, including blocking of entryways or rubbernecking. Violators may be detained by security.
- Medical staff have free access to departments to perform their duties.
- Quarantine may be mandated during a suspected outbreak of a contagion, and enforced by security.

### Code Red - Immediate Threat

There is an immediate, and severe threat to the installation, or multiple severe emergencies.

- All liberties extended to departments under Code Yellow, Orange, and Violet remain.
- Suit sensors **must** be set to tracking. Violators may be detained by Security.
- Security may search any person or department for any reason.
- Anyone deemed a threat may be detained by security until the emergency is over.
- Maintenance access may be restricted by command orders.
- External access may be restricted by command orders.
- High security areas areas **and** exterior access may be locked down as necessary.
- Security should be outfitted with any armaments or armor necessary.
- All orders from Comamnd must be followed with priority to Chain of Command, even without a head of staff having immediate authority.

### Code Delta - Imminent Destruction

The installation's self destruct mechanism has been engaged. Martial law is in effect.

- All crew members are to seek out the nearest evacuation option.
- Security may use any force necessary to ensure a successful evacuation.

### Unable to set Alert Level

During extreme emergencies, it may become impossible to activate the right alert level.

- If there is a threat justifying a given alert level, verbal permission from active members of command is enough to enact these policies, even without the alert level being set.
- This should be a rare occurence.

## Emergency Protocols

### When to Evacuate

The installation is equipped with state of the art equipment to ensure the survival of the mission. While rare, it is sometimes necessary to evacuate, or even scuttle the installation.

Here are some examples of when it is valid to perform an emergency evacuation:

- Loss of life that cannot be triaged by the Medical team (often above 33%-50%)
- Loss of installation integrity that cannot be triaged by the Engineering team (often above 15-20% of available **mass**, or above 75% in total volume being breached)
- Uncontrolled reactions, including fires, and the aftermath of such, rendering more than half of the installation unsurvivable without industrial equipment
- Active, uncontained singularity or tesla orbs, or an active and contained singularity on a planet
- Uncontrolled outbreak of a contagion;
    - ~50% of the crew being infected if there **is** 'effective' containment
    - The lack of effective containment; the contagion bypasses all defensive measures, *and* separation of crew is not feasible / effective
    - Lethal symptoms overtaking ~30% or more of the crew
    - A non-negligible (~10% or above) portion of the crew being infected, if the contagion causes loss of control of motor function, or altered mental state.
- Boarders or intruders, or the imminent arrival of hostile elements with estimated force above what can be repelled by the crew.
    - Evasion should be attempted first, if at all possible. Scuttling the ship is a last resort.

### Evacuation / Emergency Jump Procedure

- ((OOC: Not implemented yet)) For vessels: An emergency jump may be the only way to safely evacuate all crew without losing the ship. Prioritize an emergency FTL jump to the nearest command post. Evacuation should be a last resort.
- All personnel are to evacuate with the emergency shuttle, or, failing that, the nearest shuttle or pod.
- If escaping via shuttle, ensure the surrounding airspace is safe. 
- If the installation is on a planet, escaping to nearby buildings *may* be possible. Weigh the risk of doing so versus attempting an orbital evacuation.
- Prisoners are to be brought to the secure area of the shuttle, or otherwise kept secure during evacuation.
    - See: Immediate Threat to the Prisoner; for non-severe cases, simply release the prisoner.
    - For prisoners posing a severe threat, leaving them behind is acceptable if it is impractical to bring them with. Make a best faith effort to ensure they can last 24-48 hours while a recovery team is en route.
    - If no crew are being let behind, letting them go to fend for themselves (marooning) is highly recommended, instead of abandoning them in the brig.
- Casualties are to be brought back with the evacuation for processing. **Ensure the survival and recovery of mirrors, or, lacking that, an individual's intact biological brain or a synthetic's positronic core.**
- Cyborgs / AIs are to be brought with for processing if at all possible. They contain valuable blackbox data.
- Authorizing early departures of an emergency shuttle is **not** allowed unless there is an immediate threat to the shuttle.

### Exterior Evacuation

In some extreme cases (e.g. fires, viral outbreaks spread by air, similar), it may be safer to escape to the outside of the installation than to stay inside. Follow these guidelines:

- **Do not go outside during or before a FTL transition. This will *kill* you.**
- **Do not go outside while the ship is maneuvering, or if you are on a ship at all. This will potentially strand you in space. Evacuate to available shuttlecraft, or, failing that, available fighters.**
- Stick close to the installation. Planetary bodies often have potentially hostile wildlife - exterior defenses can only hold them off from close distances.
- Know your surroundings - if there is an active threat outside of the installation, weigh the risk of staying indoors with moving outdoors.
- Re-enter the installation at first opportunity to assist with repairs and recovery.

### Intruder Alert / Unexpected Visitors

- All crew should avoid maintenance areas until resolved / clear.
- Crew should use a buddy system; Avoid being alone outside of view of others.
- The Security team should locate and ascertain the intruder's intentions, and alignment.
- Hand the visitor off to the Head of Personnel for a temporary visitor pass, if cleared, or detain if deemed a danger.
- The incident should be reported to Central Command for further instructions.

### Radiation Storm

- Move all crew to maintenance tunnels, or otherwise shielded areas.
- Ensure the storm passes before declaring an all clear.
- Set up triage for casualties as necessary.

### Engine Delamination

- Perform [[SoP: Engineering|Repair Triage]] to prolong the survival of the crew.
- Pass out all available survival gear to unequipped crew.
- Determine if it is necessary to evacuate / perform an emergency jump.

### Gas Leaks / Fire

Applicable if the gas is toxic, flammable, or in some cases like Phoron, both.

- Call a Code Orange if there are no somehow more pressing problems.
- Allow emergency services to resolve the situation. Do not involve yourself without training - a single spark can result in mass casualties.
- **All crew** should avoid having any open flames, including cigarettes, lighters, blowtorches, bonfires.
- Pass out emergency equipment to unprotected crew.
- If caught in, or near such a scenario, follow these guidelines:
    0. **Put out all sources of open flame. Do not under any circumstances cause any sparks.**
    1. Put on internals. Some gases are lethal within **seconds.**
    2. Put on goggles to protect your eyes from reactive agents.
    3. Put on a heavy coat, or if possible, a firesuit or emergency spacesuit.
    4. Do not panic. Call for help, let everyone know where you are. Intercomms should be used during comms outages.
    5. Slowly, and carefully, make your way out of the leak. 
- Anyone uninvolved should avoid opening firelocks unless they have inflatables, and know what is on the other side.
- Activate all fire shutters near affected areas.
- Any crewmembers who are not part of Engineering or Medical are strictly prohibited from being in the area.

### Inbound Meteors / Debris / Objects

If an object is detected moving towards the installation at high speeds, follow the below steps to ensure your safety:

- Move to an interior area. Avoid exterior areas. Do not be caught outside.
- Do not enter impacted rooms.
- Locate the nearest emergency closet.
- Allow emergency services to handle the situation.

#### Unidentified Kinetic Insertion

If lifesigns or activity are detected by proximity sensors prior to impact, follow these guidelines:

- **Elevate alert to Code Yellow.**
- Do not enter the affected area until cleared.
- Map out escape routes from affected area.
- Security staff should arm up with lethal-capable weaponry and sweep the area.
- **All crew are to avoid maintenance until threat is identified, or cleared.**

### Viral Outbreak / Loose Contagion

((OOC: Virology is under rework. This is the only segment that mandates quarantines due to how obnoxious it is right now, but in the future, expect things to change.))

- Set alert to Code Violet.
- **Shelter in place** until Medical / Science can determine the cause and sources of spread. 
    - Walking from place to place is allowed if wearing masks and maintaining physical distance from others.
    - Full voidsuits are recommended.
    - Avoid large congregations.
- When cause is determined, enact most efficient means of halting spread and curing the affliction.
- Quarantining infected individuals may be necessary to resolve the crisis.

