Field Office Rapid Deployment

Field office rapid deployment establishes minimum viable IT infrastructure when emergency response requires new operational locations within 24 to 72 hours. This playbook prioritises speed over optimisation, accepting technical debt and reduced redundancy to achieve operational capability. Standard field office establishment procedures apply once the immediate emergency phase concludes.

Activation criteria

Invoke this playbook when all three conditions are met: an emergency response has been formally declared, a new field location is required for programme delivery, and standard establishment timelines (typically 2 to 4 weeks) cannot accommodate operational needs.

Roles

For single-person IT deployments, the deployment lead assumes all technical roles. Ensure backup contact at headquarters can provide remote support during non-working hours.

Pre-positioned equipment

Rapid deployment depends on pre-staged equipment kits maintained at regional hubs or headquarters. The minimum viable kit contains equipment sufficient for 10 to 15 users with basic connectivity and collaboration capability.

+------------------------------------------------------------------+
|                    MINIMUM VIABLE KIT CONTENTS                   |
+------------------------------------------------------------------+
|                                                                  |
|  CONNECTIVITY (select based on assessment)                       |
|  +------------------------+  +------------------------+          |
|  | VSAT Terminal          |  | Cellular Router        |          |
|  | - Portable 1.2m dish   |  | - Dual SIM LTE/5G      |          |
|  | - 5-10 Mbps service    |  | - External antenna kit |          |
|  | - Modem + WiFi router  |  | - 12V DC power         |          |
|  +------------------------+  +------------------------+          |
|                                                                  |
|  NETWORK                                                         |
|  +------------------------+  +------------------------+          |
|  | Access Point (x2)      |  | Switch (8-port PoE)    |          |
|  | - Outdoor rated        |  | - Gigabit              |          |
|  | - PoE powered          |  | - Unmanaged acceptable |          |
|  +------------------------+  +------------------------+          |
|                                                                  |
|  POWER                                                           |
|  +------------------------+  +------------------------+          |
|  | UPS (1500VA)           |  | Power Distribution     |          |
|  | - 30 min runtime       |  | - Surge protection     |          |
|  | - Pure sine wave       |  | - Universal sockets    |          |
|  +------------------------+  +------------------------+          |
|                                                                  |
|  ENDPOINTS                                                       |
|  +------------------------+  +------------------------+          |
|  | Laptops (x5)           |  | Tablets (x5)           |          |
|  | - Pre-configured       |  | - MDM enrolled         |          |
|  | - Local admin enabled  |  | - Data collection apps |          |
|  +------------------------+  +------------------------+          |
|                                                                  |
|  COMMUNICATIONS                                                  |
|  +------------------------+  +------------------------+          |
|  | Satellite Phone (x2)   |  | Two-Way Radios (x4)    |          |
|  | - Charged, tested      |  | - Programmed channels  |          |
|  | - Credit loaded        |  | - Chargers included    |          |
|  +------------------------+  +------------------------+          |
|                                                                  |
|  ACCESSORIES                                                     |
|  +----------+  +----------+  +----------+  +----------+          |
|  | Cables   |  | Adapters |  | Tools    |  | Spares   |          |
|  | Cat6 x10 |  | Power x5 |  | Basic IT |  | PSUs x2  |          |
|  | USB x10  |  | Video x3 |  | toolkit  |  | Cables   |          |
|  +----------+  +----------+  +----------+  +----------+          |
|                                                                  |
+------------------------------------------------------------------+

Figure 1: Minimum viable kit contents for 10 to 15 user deployment

Verify kit completeness against inventory checklist before departure. Missing items identified at destination cause delays measured in days when supply chains are disrupted.

Phase 1: Pre-deployment preparation

Objective: Confirm equipment, connectivity options, and remote support readiness before departure.

Timeframe: 2 to 8 hours before travel

1. Retrieve the pre-positioned kit from storage and verify contents against the inventory checklist. Power on each device to confirm functionality. Charge all batteries to 100%. Document any missing or faulty items and arrange replacements if departure timeline permits.

2. Contact the regional ISP coordinator or telecommunications lead to confirm connectivity options at the destination. Determine which is available: existing terrestrial ISP service, cellular coverage with adequate signal strength, or satellite as fallback. Request service activation for any accounts that require lead time.

   Connectivity assessment checklist:
   [ ] Terrestrial ISP available? Provider: _______ Lead time: _______
   [ ] Cellular coverage confirmed? Carrier: _______ Signal: _______
   [ ] Satellite service activated? Provider: _______ Beam: _______
   [ ] SIM cards procured for destination country?
   [ ] Data packages activated with sufficient allowance?

3. Provision temporary accounts in the identity provider for expected field staff. Use a standardised naming convention that identifies emergency deployment accounts: emergency-[location]-[number]@example.org. Assign accounts to a security group with the emergency deployment baseline policy, which permits authentication from any location and reduces MFA requirements to single factor for the first 72 hours.

   # Example: Create emergency accounts in Entra ID via CLI
   for i in {01..15}; do
     az ad user create \
       --display-name "Emergency Goma $i" \
       --user-principal-name "emergency-goma-$i@example.org" \
       --password "TempPass$(openssl rand -hex 4)!" \
       --force-change-password-next-sign-in true
   done

4. Configure devices for offline-first operation. Ensure collaboration platform files are set to sync locally, email clients cache 30 days of messages, and data collection applications contain all required forms. Test that core applications function without network connectivity.

5. Establish remote support arrangements with headquarters. Confirm the on-call schedule, communication channels (satellite phone number, messaging platform), and escalation path. Document the support contact details in printed form for the deployment kit.

6. Brief the logistics liaison on equipment requirements: total weight and volume, power requirements at destination, customs documentation needed, and handling instructions for fragile items. Satellite terminals and UPS batteries require specific shipping declarations.

Decision point: If kit verification reveals critical missing items (connectivity equipment, power infrastructure) and replacements cannot be sourced within the departure window, escalate to deployment lead for timeline adjustment or alternative sourcing.

Checkpoint: Proceed to Phase 2 when kit is complete, connectivity options are confirmed, accounts are provisioned, and logistics coordination is complete.

Phase 2: Site arrival and assessment

Objective: Evaluate site conditions and determine installation locations within 2 hours of arrival.

Timeframe: 0 to 2 hours after site arrival

1. Conduct a physical walkthrough of the facility with the logistics liaison. Identify the following: primary work area where staff will operate, secure location for IT equipment (lockable room or cabinet preferred), power source locations and socket types, potential antenna mounting points with clear sky view, and physical entry points requiring access control consideration.

2. Assess power infrastructure. Test mains power with a multimeter to verify voltage stability (acceptable range: 210V to 250V for 230V nominal, 105V to 125V for 120V nominal). Observe for fluctuations over a 5-minute period. Document outage frequency if facility staff can provide historical information. Calculate total IT load:

   Power load calculation:

   VSAT terminal:        60W continuous
   Cellular router:      15W continuous
   Network switch:       30W continuous
   Access points (x2):   30W continuous (PoE from switch)
   Laptops charging (x5): 325W peak (65W each)
   UPS overhead:         50W

   Total continuous:     185W
   Peak with charging:   510W

   UPS sizing: 510W × 1.25 safety factor = 640W minimum
   1500VA UPS at 0.8 PF = 1200W capacity: ADEQUATE

3. Test cellular signal strength at multiple locations within the facility using a smartphone or dedicated signal meter. Record values in dBm at each potential router location. Signal strength above -85 dBm typically provides usable data service; below -100 dBm requires external antenna or alternative connectivity.

   Location	Signal (dBm)	Carrier	Technology
   Main office area	-78	Local carrier	4G LTE
   Rear building	-92	Local carrier	4G LTE
   Rooftop	-71	Local carrier	4G LTE

4. If satellite connectivity is the primary option, identify antenna mounting location. Requirements: unobstructed view of the sky in the direction of the satellite (varies by provider and location), stable mounting surface, cable run of less than 30 metres to indoor equipment, and protection from tampering or accidental damage.

5. Document the assessment findings with photographs. Create a simple site diagram showing equipment placement, cable runs, and power distribution. This documentation supports both immediate installation and future standard establishment.

Decision point: If site conditions are unsuitable (no stable power, no viable connectivity options, inadequate physical security), report to deployment lead immediately. Options include generator deployment, alternative premises, or accepting degraded capability.

Checkpoint: Proceed to Phase 3 when equipment locations are determined, power adequacy is confirmed, and connectivity approach is selected.

+-----------------------------------------------------------------------------+
|                      CONNECTIVITY PRIORITY DECISION                         |
+-----------------------------------------------------------------------------+
|                                                                             |
|                   Site assessment complete                                  |
|                              |                                              |
|                              v                                              |
|            +-----------------+-----------------+                            |
|            |    Terrestrial ISP available      |                            |
|            |    and can activate < 24 hrs?     |                            |
|            +-----------------+-----------------+                            |
|                              |                                              |
|                   +----------+----------+                                   |
|                   |                     |                                   |
|                  YES                    NO                                  |
|                   |                     |                                   |
|                   v                     v                                   |
|      +-----------------------+ +-----------------------+                    |
|      |    Use terrestrial    | |       Cellular        |                    |
|      |      as primary       | |     signal > -85      |                    |
|      |    (lowest cost,      | |     dBm indoor?       |                    |
|      |    best latency)      | +-----------+-----------+                    |
|      +-----------------------+             |                                |
|                                  +---------+---------+                      |
|                                  |                   |                      |
|                                 YES                  NO                     |
|                                  |                   |                      |
|                                  v                   v                      |
|                       +-------------------+ +-------------------+           |
|                       |   Use cellular    | |     External      |           |
|                       |    as primary     | |     antenna       |           |
|                       |     (rapid,       | |     improves      |           |
|                       |    portable)      | |     signal?       |           |
|                       +-------------------+ +---------+---------+           |
|                                                       |                     |
|                                             +---------+---------+           |
|                                             |                   |           |
|                                            YES                  NO          |
|                                             |                   |           |
|                                             v                   v           |
|                                   +-------------------+ +---------------+   |
|                                   |   Use cellular    | | Deploy        |   |
|                                   |   with antenna    | | satellite     |   |
|                                   +-------------------+ | (reliable but |   |
|                                                         | high latency) |   |
|                                                         +---------------+   |
|                                                                             |
|                                                                             |
+-----------------------------------------------------------------------------+

Figure 2: Connectivity selection decision tree prioritising speed and reliability

Phase 3: Connectivity establishment

Objective: Establish working internet connectivity for the site.

Timeframe: 2 to 6 hours depending on connectivity type

1. Install power infrastructure first. Position the UPS in the designated equipment area. Connect to mains power and verify battery is charging (indicator light or display). Attach the power distribution unit to the UPS output. Test by disconnecting mains briefly and confirming UPS transfers to battery without equipment interruption.

2. For cellular primary connectivity, mount the router in the location with strongest signal identified during assessment. If using an external antenna, mount it at height with clear line of sight toward the cell tower (typically visible or direction known from signal testing). Connect the antenna cable to the router’s external antenna port, ensuring the internal antenna is disabled in router configuration if applicable.

   Cellular router configuration checklist:
   [ ] SIM inserted and PIN disabled or entered
   [ ] APN configured for local carrier (obtain from carrier)
   [ ] External antenna selected in settings
   [ ] Band locking to strongest band (optional, improves stability)
   [ ] WiFi SSID set to standard naming: [ORG]-[LOCATION]-RAPID
   [ ] WiFi password set to deployment standard
   [ ] Admin password changed from default
   [ ] DHCP range configured: 192.168.1.100-200
   [ ] DNS set to reliable resolvers: 1.1.1.1, 8.8.8.8

3. For satellite primary connectivity, assemble the VSAT terminal per manufacturer instructions. Mount the dish securely on the identified location. Power on the modem and initiate the pointing procedure, which uses audible tones or signal strength display to guide alignment. Satellite pointing requires patience: small adjustments of 1 to 2 degrees in azimuth and elevation, waiting 3 to 5 seconds between adjustments for the modem to measure signal.

   Typical satellite pointing parameters (varies by provider and location):

   Parameter	Example value	Source
   Azimuth	237.5°	Provider portal or app
   Elevation	42.3°	Provider portal or app
   Polarisation	-18.7°	Provider portal or app (if applicable)

   Lock the mount hardware once signal acquisition is confirmed. A successful link shows connected status on the modem and passes the provider’s activation test.

4. Connect the network switch to the connectivity device (router or satellite modem) and power on. Connect access points to PoE ports on the switch. Position access points to provide coverage across the work area, typically one per 50 square metres for adequate density in an office environment.

5. Test connectivity from a laptop. Verify the following sequence:

   • WiFi association: device connects to SSID and obtains IP via DHCP
   • Local network: can ping gateway (typically 192.168.1.1)
   • Internet: can ping external host (8.8.8.8)
   • DNS: can resolve domain names (ping example.org)
   • Services: can reach organisational cloud services (Microsoft 365, Google Workspace)

   # Connectivity verification sequence
   ping -c 4 192.168.1.1       # Gateway
   ping -c 4 8.8.8.8           # Internet (bypass DNS)
   ping -c 4 example.org       # DNS resolution
   curl -I https://login.microsoftonline.com  # Cloud services

6. Measure and document connection performance. Acceptable thresholds for emergency deployment:

   Metric	Acceptable	Degraded	Unacceptable
   Download speed	> 2 Mbps	0.5 - 2 Mbps	< 0.5 Mbps
   Upload speed	> 0.5 Mbps	0.25 - 0.5 Mbps	< 0.25 Mbps
   Latency	< 200 ms	200 - 600 ms	> 600 ms
   Packet loss	< 1%	1 - 5%	> 5%

   Satellite connections typically show 600 to 800 ms latency; this is expected for geostationary satellite and acceptable for emergency operations.

Decision point: If primary connectivity fails to establish after 2 hours of troubleshooting, activate the backup option immediately rather than continuing to debug. Operational capability takes priority over optimal connectivity.

Checkpoint: Proceed to Phase 4 when devices on the local network can reach organisational cloud services. Voice and video quality assessment can wait until core services are active.

Phase 4: Core services activation

Objective: Enable access to organisational systems for field staff.

Timeframe: 1 to 3 hours

1. Verify identity provider connectivity. Attempt authentication to the identity provider from a field device using a test account. For federated identity, the authentication flow traverses multiple services, each of which must be reachable:

   Authentication flow verification:

   User device
       |
       v
   [Initial app/portal] --> reachable? Y/N
       |
       v
   [Identity provider login page] --> reachable? Y/N
       |
       v
   [MFA service if required] --> reachable? Y/N
       |
       v
   [Token issuance] --> completes? Y/N
       |
       v
   [Application access] --> granted? Y/N

2. Test access to core productivity services. Each service requires explicit verification because firewall rules, proxy configurations, or network restrictions at the deployment location may block specific domains:

   • Email: send and receive test message
   • Calendar: view and create test appointment
   • File storage: upload and download test file
   • Messaging: send and receive test message in team channel
   • Video: initiate test call (even if quality is poor, verify connection)

3. Configure backup authentication methods for bandwidth-constrained conditions. If the connection is satellite or degraded cellular, standard MFA flows involving push notifications or authenticator apps may timeout. Configure fallback options:

   • Pre-generated one-time codes (print before travel for users without reliable phone signal)
   • SMS to local number if cellular is available
   • Hardware security keys (FIDO2) which work offline after initial registration

4. Activate data collection platforms. For humanitarian response, mobile data collection is often the primary operational requirement. Verify:

   • Data collection app connects to server and downloads latest form definitions
   • Offline mode functions correctly (submit while disconnected, sync when connected)
   • GPS functions for location capture
   • Photo and media capture works and uploads successfully

   Test the complete workflow: create a test submission offline, reconnect, sync, and verify the submission appears in the server dashboard.

5. Configure printing if equipment is available. Emergency deployments often include a portable printer for registration cards, distribution lists, or referral documentation. Install drivers, test print, and position consumables (paper, ink/toner) accessibly.

6. Establish satellite phone or alternative communication as backup channel. Program headquarters contact numbers. Test both voice and SMS capability. Brief the logistics liaison on usage procedures since satellite phones often serve shared purposes beyond IT.

Decision point: If critical services (identity, email, data collection) cannot be accessed despite working internet connectivity, engage headquarters support immediately. The issue may require firewall exceptions, DNS configuration, or service-side enablement.

Checkpoint: Proceed to Phase 5 when test accounts can access email, file storage, and the primary operational application (typically data collection for emergency response).

Phase 5: User enablement

Objective: Equip arriving staff to work productively.

Timeframe: Concurrent with staff arrival, typically 2 to 8 hours total

1. Prepare the workspace for user onboarding. Set up workstations with devices powered on and connected to WiFi. Print the WiFi credentials and post visibly. Prepare a brief orientation document (one page maximum) covering:

   • WiFi network name and password
   • How to access email and files
   • Who to contact for IT issues (name, location, backup channel)
   • Security essentials: lock screen when stepping away, report lost devices immediately

2. Onboard users as they arrive. The abbreviated emergency onboarding process:

   • Provide device (laptop or tablet) and accessories
   • User signs into device with emergency account credentials
   • User completes forced password change
   • Verify email access, file access, and data collection app
   • Brief on backup communication procedures (satellite phone location, radio channels)
   • Document: user name, device serial number, account assigned

   Target 15 minutes per user for technical onboarding. Detailed system training happens after the immediate emergency phase.

3. Maintain an equipment allocation register. In emergency deployments, asset tracking happens manually on paper or spreadsheet:

   User name	Device type	Serial number	Account	Date issued	Signature
   Jane Doe	Laptop Dell	ABC123	emergency-goma-01	2024-11-16	[signed]
   John Smith	Tablet Samsung	XYZ789	emergency-goma-02	2024-11-16	[signed]

4. Configure shared devices if the user-to-device ratio requires sharing. Enable shared device mode where the platform supports it (Windows shared PC mode, Android shared device mode). Without platform support, create a local account per user or establish a sign-out protocol where users sign out of all applications when handing over the device.

5. Establish a local IT presence point. Even if the deployment lead departs, users need to know where to seek help. Options:

   • Designated local IT focal point (train a non-IT staff member on basics)
   • Clear escalation path to regional or headquarters IT
   • Self-service documentation for common issues (password reset, reconnecting WiFi)

6. Capture feedback from initial users. The first users identify issues that subsequent users will also encounter. Common early issues:

   • WiFi password entry errors (capitalisation, special characters)
   • Timeout during first authentication (retry usually succeeds)
   • Application not syncing (force sync from settings)
   • Printing not working (driver not installed on user device)

Decision point: If user volume exceeds deployment capacity (more than 15 users for a minimum viable kit), coordinate with headquarters to expedite additional equipment shipment or adjust operational expectations.

Checkpoint: Phase 5 is complete when all arriving staff have working devices and can access core services. Connectivity may be slow or intermittent, but users can perform basic functions.

Phase 6: Handover to standard operations

Objective: Transition from emergency deployment to sustainable operations.

Timeframe: 48 to 168 hours after initial deployment (2 to 7 days)

1. Document the deployment configuration comprehensively. Create a site documentation package containing:

   • Network diagram showing all equipment, IP addresses, and connections
   • Equipment inventory with serial numbers and locations
   • Account list mapping users to emergency accounts
   • Configuration backups from router, access points
   • Connectivity contract details (provider, account number, data allowance)
   • Power infrastructure notes (voltage, socket types, generator location)
   • Known issues and workarounds

2. Assess what remains non-standard. Emergency deployments accumulate technical debt deliberately accepted for speed. Typical items requiring remediation:

   Emergency state	Standard state	Effort to remediate
   Emergency accounts	Named personal accounts	2 hours per 10 users
   Temporary WiFi password	Certificate-based authentication	4 hours plus endpoint config
   Single connectivity path	Primary plus backup	Days to weeks
   Minimal security baseline	Full security policy	1 to 2 days
   Paper asset register	Asset management system entry	1 hour per 10 assets

3. Schedule the transition activities with the incoming IT support. If a dedicated field IT officer will assume responsibility, conduct in-person handover. If remote support continues, schedule video calls to walk through the documentation and demonstrate current configuration.

4. Migrate users from emergency accounts to personal accounts. The emergency accounts exist to enable rapid provisioning; they lack proper naming, may have elevated permissions, and are not suitable for long-term use. For each user:

   • Create personal account following standard naming convention
   • Migrate data from emergency account (email, files)
   • Assign personal account to appropriate security groups
   • Verify access to required applications
   • Disable emergency account (do not delete until data migration is confirmed)

5. Implement standard security baseline. Emergency deployments reduce security controls for speed. Restore:

   • Standard MFA requirements (disable first-72-hour relaxation)
   • Conditional access policies for the new location
   • Device compliance policies
   • Full disk encryption verification
   • Endpoint protection verification

6. Initiate procurement for permanent infrastructure. The minimum viable kit is borrowed from emergency stocks and must be returned or replaced. Work with logistics to procure:

   • Permanent connectivity (terrestrial ISP if available, dedicated VSAT)
   • Additional endpoints for full staffing
   • Proper network infrastructure (managed switches, enterprise access points)
   • Office infrastructure (cabling, racks, dedicated power circuits)

7. Complete deployment report. Document:

   • Timeline from activation to operational capability
   • Equipment deployed and current status
   • Issues encountered and resolutions
   • Costs incurred (connectivity, travel, consumables)
   • Recommendations for future rapid deployments
   • Outstanding items requiring follow-up

Decision point: Handover timing depends on emergency phase duration and staff rotation. If the deployment lead must depart before full handover, prioritise documentation and remote support arrangements over in-person transition.

Checkpoint: Phase 6 is complete when documentation is handed over, transition plan is agreed, and the deployment lead can depart without critical knowledge leaving with them.

Communications

Initial assessment template

Use within 2 hours of site arrival:

Subject: [RAPID DEPLOY] [Location] - Initial assessment

Location: [City, Country]
Assessment time: [Date, Time UTC]

Site conditions:
- Facility status: [Suitable / Needs work / Unsuitable]
- Power: [Stable / Unstable / Unavailable]
- Connectivity assessment: [Terrestrial / Cellular / Satellite required]

Timeline estimate:
- Connectivity operational: [T + X hours]
- Core services available: [T + X hours]
- User onboarding ready: [T + X hours]

Blockers or escalations:
- [List any issues requiring headquarters action]

Next update: [Time]

[Name]
Deployment Lead

Operational status template

Use when connectivity and core services are operational:

Subject: [RAPID DEPLOY] [Location] - Operational

Location: [City, Country]
Status time: [Date, Time UTC]

Operational status: OPERATIONAL / LIMITED / DEGRADED

Connectivity:
- Type: [Terrestrial / Cellular / Satellite]
- Speed: [X Mbps down / X Mbps up]
- Latency: [X ms]
- Stability: [Stable / Intermittent / Unstable]

Services available:
- Email: [Yes / No / Limited]
- File storage: [Yes / No / Limited]
- Data collection: [Yes / No / Limited]
- Voice/video: [Yes / No / Limited]

Users onboarded: [X] of [Y] expected
Equipment deployed: [List key items]

Outstanding issues:
- [List any ongoing issues]

Support requirements:
- [List any HQ support needed]

Next update: [Time or milestone]

[Name]
Deployment Lead

Documentation requirements

Maintain the following records during deployment for audit trail and lessons learned:

Decision log: Record significant decisions with rationale and outcome. Format:

[Date Time] [Decision] [Options considered] [Rationale] [Outcome]

2024-11-16 14:30 Connectivity selection: Cellular chosen over satellite
  Options: Wait for terrestrial (3 days), cellular (available), satellite (available)
  Rationale: Cellular signal adequate (-76 dBm), lower latency than satellite,
             faster setup than waiting for terrestrial
  Outcome: Operational within 2 hours, 4 Mbps achieved

Issue log: Track problems encountered and resolutions:

[Date Time] [Issue] [Impact] [Resolution] [Duration]

2024-11-16 16:45 MFA timeout during first login
  Impact: Users unable to complete authentication
  Resolution: Extended timeout in conditional access policy, users retry
  Duration: 45 minutes to identify and resolve

Handover checklist:

[ ] Network diagram created and accurate
[ ] Equipment inventory complete with serial numbers
[ ] User-to-account mapping documented
[ ] Configuration backups saved
[ ] Connectivity contract details recorded
[ ] Power infrastructure documented
[ ] Known issues listed with workarounds
[ ] Transition plan agreed with incoming support
[ ] Emergency kit items accounted for (return or replace)
[ ] Deployment report submitted

See also

• Field Site IT Establishment for standard field office setup when time permits
• Emergency IT Activation for surge capacity procedures that precede rapid deployment
• Emergency Communications Setup for communication channel establishment
• Satellite Deployment for detailed VSAT procedures
• Emergency Staff Deployment for rapid user provisioning
• Field Hardware Selection for equipment specifications