Jump to content

Runbooks: Difference between revisions

From Archive
Creating Runbooks documentation from contingency planning notes
 
Rewriting with concrete, actionable emergency procedures instead of abstract concepts
Line 1: Line 1:
'''Runbooks''' are systematic procedure guides designed for handling specific crisis scenarios and emergency situations. The concept emphasizes actionable protocols over information storage, providing step-by-step procedures that can be executed under stress.
'''Runbooks''' are field-tested emergency procedures designed for independent journalists and field workers who operate alone, often in remote locations with limited connectivity.


== Philosophy ==
The system separates sensitive information storage (handled by password managers) from actionable procedures that can be executed under stress.


Runbooks operate on the principle of separating sensitive information storage from procedural guidance. This approach ensures that procedures remain accessible and executable even when primary systems are compromised, while keeping sensitive data secured separately.
== Core Emergency Runbooks ==


The system is designed to be simple enough to use during a crisis but comprehensive enough to handle complex situations.
=== Motorcycle/Vehicle Down ===
'''If your primary transportation fails in the field:'''


== System Architecture ==
# '''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


=== Dual-Component Design ===
=== Digital Security Breach ===
'''If accounts are compromised or you're locked out of systems:'''


The runbook system consists of two complementary parts:
# '''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


# '''Information Repository''': Secure storage of critical data (credentials, contact information, serial numbers)
=== Medical Emergency While Solo ===
# '''Procedure Guides''': Step-by-step protocols for specific scenarios
'''If injured or seriously ill while working alone:'''


=== Storage and Access ===
# '''Self-Assessment''': Use predetermined criteria to evaluate severity and mobility
# '''Location Broadcasting''': Send GPS coordinates to emergency contacts via multiple methods
# '''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


Runbooks are maintained in multiple formats and locations:
=== Equipment Theft/Loss ===
'''If primary work equipment is stolen or lost:'''


* Encrypted local storage
# '''Immediate Security''': Remote wipe devices, change all passwords, notify banks of potential card theft
* Printed copies for field operations
# '''Documentation''': File police report with serial numbers and detailed equipment list
* Cloud backup (encrypted)
# '''Insurance Claims''': Contact equipment insurance, provide required documentation and receipts
* Physical copies at secure locations
# '''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


== Core Runbook Categories ==
== Information Storage System ==


=== Field Operations ===
Critical information is stored securely and separately from procedures:
* '''Equipment failure protocols''': Procedures for handling technical breakdowns in remote locations
* '''Transportation contingencies''': Alternative transport activation and incident management
* '''Communication fallbacks''': Maintaining connectivity when primary systems fail


=== Digital Security ===
=== Insurance Documentation ===
* '''Access restoration procedures''': Recovery from account lockouts and security breaches
* Motorcycle/vehicle policy numbers and emergency claim lines
* '''Remote system management''': Controlling and securing systems from alternative locations
* Equipment insurance coverage and claim procedures
* '''Data protection protocols''': Securing sensitive information during compromises
* Health insurance cards and emergency medical information
* Rental insurance for temporary accommodations


=== Medical and Personal Safety ===
=== Medical Information ===
* '''Solo emergency procedures''': Self-assessment and evacuation protocols
* Blood type, allergies, and current medications
* '''Emergency contact cascades''': Systematic notification procedures
* Emergency medical contacts and preferred hospitals
* '''Location broadcasting methods''': Ensuring help can locate you in crisis
* Medical power of attorney and advance directives
* Vaccination records and medical history summaries


=== Asset Protection ===
=== Identity and Legal ===
* '''Theft response procedures''': Immediate security measures and recovery steps
* Driver's license, passport, and backup ID information
* '''Insurance claim protocols''': Documentation and filing procedures
* Legal contacts and emergency representation
* '''Replacement workflows''': Minimum viable kit deployment
* Press credentials and professional identification
* Important document storage locations


== Implementation Guidelines ==
=== Financial Access ===
* Banking information and emergency access procedures
* Credit card companies and fraud reporting lines
* Emergency fund access and transfer procedures
* Payment processing and client billing continuity


=== System Maintenance ===
=== Equipment Registry ===
* Serial numbers, purchase dates, and warranty information
* Replacement cost estimates and preferred vendors
* Configuration backups and license keys
* Insurance claim values and depreciation schedules


'''Quarterly Tasks:'''
== System Maintenance ==
* Verify all stored information remains current
* Test emergency access procedures
* Update contact information
* Check physical copy integrity


'''Annual Tasks:'''
=== Monthly Checks ===
* Complete system review and testing
* Verify emergency contact information remains current
* Refresh all physical copies
* Test backup communication methods and devices
* Update insurance and policy information
* Update equipment inventory and serial numbers
* Review and revise procedures based on experience
* Review and update insurance coverage


=== Usage Protocol ===
=== Quarterly Reviews ===
* Full runbook procedure walkthrough
* Test emergency access to all critical systems
* Update backup equipment and supply caches
* Review lessons learned from any incidents


# '''Situation Assessment''': Identify which runbook applies to current crisis
=== Annual Updates ===
# '''Information Access''': Retrieve necessary data from secure storage
* Complete system review with trusted contacts
# '''Procedure Execution''': Follow step-by-step protocols
* Update all insurance policies and coverage limits
# '''Documentation''': Record actions taken during incident
* Refresh physical document copies and storage locations
# '''System Update''': Incorporate lessons learned post-incident
* Conduct full emergency response exercise


== Security Considerations ==
== Field Implementation ==


* Runbooks contain no sensitive data, only procedures
These procedures are designed to be:
* All digital copies are encrypted
* '''Executable under stress''' - Simple steps that don't require complex decision-making
* Physical access is controlled and monitored
* '''Equipment-independent''' - Can be followed with whatever communication tools are available
* Regular security reviews of access methods
* '''Scalable''' - Procedures work for minor incidents and major emergencies
* Redundant recovery methods prevent single points of failure
* '''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 ==
== Categories ==


[[Category:Operations]]
[[Category:Emergency Procedures]]
[[Category:Emergency Procedures]]
[[Category:Documentation]]
[[Category:Field Operations]]
[[Category:Risk Management]]
[[Category:Solo Operations]]

Revision as of 22:03, 31 August 2025

Runbooks are field-tested emergency procedures designed for independent journalists and field workers who operate alone, often in remote locations with limited connectivity.

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

If your primary transportation fails in the field:

  1. Immediate Safety: Move to safe location, assess injuries, activate hazard lights
  2. Evidence Collection: Photo damage from multiple angles, note exact location coordinates, document weather/road conditions
  3. Damage Assessment: Can vehicle be operated safely? Is towing required? Are key systems damaged?
  4. Insurance Activation: Contact insurance carrier, file claim, arrange towing if needed
  5. Alternative Transport: Activate backup transport plan, coordinate pickup, secure equipment
  6. 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:

  1. Immediate Isolation: Disconnect compromised devices from network, activate airplane mode
  2. Alternative Access: Use pre-configured backup device or secure location to access accounts
  3. Account Recovery: Follow predetermined recovery sequences for critical accounts (email, cloud storage, publishing platforms)
  4. Source Protection: Secure sensitive communications using offline methods, warn sources if necessary
  5. System Restoration: Remote wipe compromised devices, restore from known-good backups
  6. Communication Fallback: Activate alternative communication channels with editors/contacts

Medical Emergency While Solo

If injured or seriously ill while working alone:

  1. Self-Assessment: Use predetermined criteria to evaluate severity and mobility
  2. Location Broadcasting: Send GPS coordinates to emergency contacts via multiple methods
  3. Emergency Services: Call 911 with precise location, nature of emergency, and equipment details
  4. Remote Assistance: Activate emergency contact cascade, including family and professional contacts
  5. Equipment Security: Secure sensitive materials and equipment if possible before evacuation
  6. Work Handoff: If conscious, brief emergency contacts on current story status and deadlines

Equipment Theft/Loss

If primary work equipment is stolen or lost:

  1. Immediate Security: Remote wipe devices, change all passwords, notify banks of potential card theft
  2. Documentation: File police report with serial numbers and detailed equipment list
  3. Insurance Claims: Contact equipment insurance, provide required documentation and receipts
  4. Minimum Viable Kit: Activate backup equipment cache or emergency replacement procedure
  5. Work Continuity: Assess what work can continue with available equipment, notify clients of delays
  6. Data Recovery: Restore data from cloud backups, contact IT support for system rebuilds

Information Storage System

Critical information is stored securely and separately from procedures:

Insurance Documentation

  • Motorcycle/vehicle policy numbers and emergency claim lines
  • Equipment insurance coverage and claim procedures
  • Health insurance cards and emergency medical information
  • Rental insurance for temporary accommodations

Medical Information

  • 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

  • Driver's license, passport, and backup ID information
  • Legal contacts and emergency representation
  • Press credentials and professional identification
  • Important document storage locations

Financial Access

  • Banking information and emergency access procedures
  • Credit card companies and fraud reporting lines
  • Emergency fund access and transfer procedures
  • Payment processing and client billing continuity

Equipment Registry

  • Serial numbers, purchase dates, and warranty information
  • Replacement cost estimates and preferred vendors
  • Configuration backups and license keys
  • Insurance claim values and depreciation schedules

System Maintenance

Monthly Checks

  • Verify emergency contact information remains current
  • Test backup communication methods and devices
  • Update equipment inventory and serial numbers
  • Review and update insurance coverage

Quarterly Reviews

  • Full runbook procedure walkthrough
  • Test emergency access to all critical systems
  • Update backup equipment and supply caches
  • Review lessons learned from any incidents

Annual Updates

  • 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 procedures are designed to be:

  • 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