Runbooks: Difference between revisions

Latest revision as of 19:46, 7 December 2025

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

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

Activation Phase

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

Recovery Phase

Complete all follow-up actions specified in applicable runbook
Document lessons learned and system performance during incident
Update procedures based on real-world effectiveness
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.

@@ Line 1: / Line 1: @@
-'''Runbooks''' are field-tested emergency procedures designed for independent journalists and field workers who operate alone, often in remote locations with limited connectivity.
+'''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.
-The system separates sensitive information storage (handled by password managers) from actionable procedures that can be executed under stress.
 == Core Emergency Runbooks ==
-=== Motorcycle/Vehicle Down ===
+=== [[Vehicle Failure Runbook]] ===
-'''If your primary transportation fails in the field:'''
+Complete procedures for handling transportation breakdowns during field operations, including safety assessment, damage evaluation, insurance procedures, alternative transportation, and work continuity planning.
-# '''Immediate Safety''': Move to safe location, assess injuries, activate hazard lights
-# '''Evidence Collection''': Photo damage from multiple angles, note exact location coordinates, document weather/road conditions
-# '''Damage Assessment''': Can vehicle be operated safely? Is towing required? Are key systems damaged?
-# '''Insurance Activation''': Contact insurance carrier, file claim, arrange towing if needed
-# '''Alternative Transport''': Activate backup transport plan, coordinate pickup, secure equipment
-# '''Story Continuity''': If on assignment, notify editor/client of situation and revised timeline
-=== Digital Security Breach ===
-'''If accounts are compromised or you're locked out of systems:'''
-# '''Immediate Isolation''': Disconnect compromised devices from network, activate airplane mode
-# '''Alternative Access''': Use pre-configured backup device or secure location to access accounts
-# '''Account Recovery''': Follow predetermined recovery sequences for critical accounts (email, cloud storage, publishing platforms)
-# '''Source Protection''': Secure sensitive communications using offline methods, warn sources if necessary
-# '''System Restoration''': Remote wipe compromised devices, restore from known-good backups
-# '''Communication Fallback''': Activate alternative communication channels with editors/contacts
-=== Medical Emergency While Solo ===
+=== [[Digital Security Incident Runbook]] ===
-'''If injured or seriously ill while working alone:'''
+Comprehensive response protocols for account compromises, device theft, and system access loss, covering immediate isolation, account recovery, source protection, and system restoration.
-# '''Self-Assessment''': Use predetermined criteria to evaluate severity and mobility
+=== [[Solo Medical Emergency Runbook]] ===
-# '''Location Broadcasting''': Send GPS coordinates to emergency contacts via multiple methods
+Emergency medical procedures for serious illness or injury when working alone, including self-assessment, emergency response, evacuation procedures, and work continuity measures.
-# '''Emergency Services''': Call 911 with precise location, nature of emergency, and equipment details
-# '''Remote Assistance''': Activate emergency contact cascade, including family and professional contacts
-# '''Equipment Security''': Secure sensitive materials and equipment if possible before evacuation
-# '''Work Handoff''': If conscious, brief emergency contacts on current story status and deadlines
-=== Equipment Theft/Loss ===
+=== Equipment Theft/Loss Runbook ===
-'''If primary work equipment is stolen or lost:'''
+''(Planned - procedures for securing systems after equipment theft, insurance claims, replacement workflows, and maintaining operational security)''
-# '''Immediate Security''': Remote wipe devices, change all passwords, notify banks of potential card theft
+=== Legal/Detention Runbook ===
-# '''Documentation''': File police report with serial numbers and detailed equipment list
+''(Planned - protocols for arrest situations, legal representation, communication restrictions, and professional obligations during detention)''
-# '''Insurance Claims''': Contact equipment insurance, provide required documentation and receipts
-# '''Minimum Viable Kit''': Activate backup equipment cache or emergency replacement procedure
-# '''Work Continuity''': Assess what work can continue with available equipment, notify clients of delays
-# '''Data Recovery''': Restore data from cloud backups, contact IT support for system rebuilds
-== Information Storage System ==
+== System Architecture ==
-Critical information is stored securely and separately from procedures:
+=== 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.
-=== Insurance Documentation ===
+=== Access Methods ===
-* Motorcycle/vehicle policy numbers and emergency claim lines
+* '''Digital copies''': Encrypted local storage and cloud backup
-* Equipment insurance coverage and claim procedures
+* '''Physical copies''': Laminated field guides stored in equipment kits
-* Health insurance cards and emergency medical information
+* '''Memory aids''': Key decision trees memorized for situations where written procedures aren't accessible
-* Rental insurance for temporary accommodations
-=== Medical Information ===
+== Implementation Guidelines ==
-* Blood type, allergies, and current medications
-* Emergency medical contacts and preferred hospitals
-* Medical power of attorney and advance directives
-* Vaccination records and medical history summaries
-=== Identity and Legal ===
+=== Preparation Phase ===
-* Driver's license, passport, and backup ID information
+# Study runbook procedures in non-emergency conditions
-* Legal contacts and emergency representation
+# Practice key decision trees and communication protocols
-* Press credentials and professional identification
+# Verify all emergency contact information and backup systems
-* Important document storage locations
+# Test equipment and communication methods specified in procedures
-=== Financial Access ===
+=== Activation Phase ===
-* Banking information and emergency access procedures
+# Quickly assess situation to identify applicable runbook
-* Credit card companies and fraud reporting lines
+# Follow step-by-step procedures without deviation during crisis
-* Emergency fund access and transfer procedures
+# Document actions taken for post-incident analysis
-* Payment processing and client billing continuity
+# Communicate status updates per runbook communication protocols
-=== Equipment Registry ===
+=== Recovery Phase ===
-* Serial numbers, purchase dates, and warranty information
+# Complete all follow-up actions specified in applicable runbook
-* Replacement cost estimates and preferred vendors
+# Document lessons learned and system performance during incident
-* Configuration backups and license keys
+# Update procedures based on real-world effectiveness
-* Insurance claim values and depreciation schedules
+# Brief trusted contacts on incident resolution and system improvements
 == System Maintenance ==
-=== Monthly Checks ===
+=== Regular Testing ===
-* Verify emergency contact information remains current
+* '''Monthly''': Review contact information and verify system access
-* Test backup communication methods and devices
+* '''Quarterly''': Full walkthrough of one randomly selected runbook
-* Update equipment inventory and serial numbers
+* '''Semi-annually''': Test all backup communication and access methods
-* Review and update insurance coverage
+* '''Annually''': Complete system review and update all procedures
-=== Quarterly Reviews ===
+=== Documentation Updates ===
-* Full runbook procedure walkthrough
+* Update procedures after any real-world activation
-* Test emergency access to all critical systems
+* Incorporate lessons learned from training exercises
-* Update backup equipment and supply caches
+* Revise based on changes to insurance, equipment, or operating procedures
-* Review lessons learned from any incidents
+* Version control all changes with dates and rationale
-=== Annual Updates ===
+== Usage Philosophy ==
-* Complete system review with trusted contacts
-* Update all insurance policies and coverage limits
-* Refresh physical document copies and storage locations
-* Conduct full emergency response exercise
-== Field Implementation ==
+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
-These procedures are designed to be:
+The goal is not perfection but rapid, effective response that protects life, maintains operational security, and preserves professional obligations even under adverse conditions.
-* '''Executable under stress''' - Simple steps that don't require complex decision-making
-* '''Equipment-independent''' - Can be followed with whatever communication tools are available
-* '''Scalable''' - Procedures work for minor incidents and major emergencies
-* '''Tested''' - Regular practice ensures procedures work when needed
-The runbooks assume you may be operating with limited connectivity, damaged equipment, or while injured, and provide multiple pathways for each critical function.
 == Categories ==
@@ Line 115: / Line 78: @@
 [[Category:Risk Management]]
 [[Category:Solo Operations]]
+{{Navbox Runbooks}}

📋 Runbooks
Setup	Runbooks · New Computer Runbook
Emergency	Medical Emergency · Vehicle Failure · Security Incident
Comms	Emergency Communications · PGP Communication Guide
Reference	Technical · Field Operations