Runbooks

Runbooks are field-tested emergency procedures designed for independent journalists, field workers, and anyone operating alone in remote locations. Each runbook provides step-by-step protocols that can be executed under stress.

Core Emergency Runbooks

Vehicle Failure Runbook

Complete procedures for handling transportation breakdowns during field operations, including safety assessment, damage evaluation, insurance procedures, alternative transportation, and work continuity planning.

Digital Security Incident Runbook

Comprehensive response protocols for account compromises, device theft, and system access loss, covering immediate isolation, account recovery, source protection, and system restoration.

Solo Medical Emergency Runbook

Emergency medical procedures for serious illness or injury when working alone, including self-assessment, emergency response, evacuation procedures, and work continuity measures.

Equipment Theft/Loss Runbook

(Planned - procedures for securing systems after equipment theft, insurance claims, replacement workflows, and maintaining operational security)

Legal/Detention Runbook

(Planned - protocols for arrest situations, legal representation, communication restrictions, and professional obligations during detention)

System Architecture

Information Separation

Runbooks contain only procedural guidance. Sensitive information (account numbers, contact details, medical information) is stored separately in encrypted password managers and secure document storage.

Access Methods

• Digital copies: Encrypted local storage and cloud backup
• Physical copies: Laminated field guides stored in equipment kits
• Memory aids: Key decision trees memorized for situations where written procedures aren't accessible

Implementation Guidelines

Preparation Phase

1. Study runbook procedures in non-emergency conditions
2. Practice key decision trees and communication protocols
3. Verify all emergency contact information and backup systems
4. Test equipment and communication methods specified in procedures

Activation Phase

1. Quickly assess situation to identify applicable runbook
2. Follow step-by-step procedures without deviation during crisis
3. Document actions taken for post-incident analysis
4. Communicate status updates per runbook communication protocols

Recovery Phase

1. Complete all follow-up actions specified in applicable runbook
2. Document lessons learned and system performance during incident
3. Update procedures based on real-world effectiveness
4. Brief trusted contacts on incident resolution and system improvements

System Maintenance

Regular Testing

• Monthly: Review contact information and verify system access
• Quarterly: Full walkthrough of one randomly selected runbook
• Semi-annually: Test all backup communication and access methods
• Annually: Complete system review and update all procedures

Documentation Updates

• Update procedures after any real-world activation
• Incorporate lessons learned from training exercises
• Revise based on changes to insurance, equipment, or operating procedures
• Version control all changes with dates and rationale

Usage Philosophy

These runbooks assume:

• Limited cognitive capacity during crisis - procedures must be simple and clear
• Degraded communication - multiple backup methods and clear priorities
• Equipment failure - procedures work with minimal tools and technology
• Time pressure - critical actions prioritized in first 15 minutes of each scenario

The goal is not perfection but rapid, effective response that protects life, maintains operational security, and preserves professional obligations even under adverse conditions.