The 90-Day Multi-Site Uptime Blueprint (Prompt Pack)

What This Delivers

• Multi-Site Failover Policy Template
• Device-Level Resilience Map
• Pooled Data Plan Config
• Outage Escalation Matrix

Input Requirements

To use this framework, users should gather the core operational and connectivity details across their sites and device types. The prompts work best when you provide real-world network, device, and billing information.

Users should provide:

• Number of sites and site types
• Site criticality tiers
• Primary and backup connectivity methods at each site
• Device inventory by type and role
• SIM counts and carrier assignments
• Current pooled or non-pooled data structure
• Monthly data usage by device group or site tier
• Soft cap thresholds and alert preferences
• Known outage patterns and failover triggers
• Escalation contacts and response timelines
• Current pain points such as downtime, data overages, inconsistent failover, or unclear ownership
• Rollout constraints such as budget, staffing, vendor limitations, or deployment deadlines

Example input set:

• 45 locations across retail, field offices, and mobile units
• Tier 1 sites require always-on POS and VPN uptime
• Primary circuits include fiber, cable, LTE, and 5G
• Backup varies by site and is not standardized
• 220 active SIMs across routers, gateways, kiosks, and IoT devices
• Current issue: overages on LTE failover usage
• Current issue: no consistent trigger policy for failover events
• Current issue: outage escalation differs by region

Methodology

1. Define site tiers and operational priorities
   Group locations by business importance, traffic profile, and outage sensitivity so failover design matches real business risk.
2. Map device roles and resilience requirements
   Identify which devices need primary and backup connectivity, which traffic should fail over, and which traffic should be blocked or restricted during backup events.
3. Build the pooled-data structure
   Organize SIMs into logical groups, estimate pool requirements, apply soft caps and alert rules, and model likely billing outcomes under normal and failover conditions.
4. Standardize failover and outage response
   Create a repeatable policy for triggers, recovery actions, escalation timelines, and ownership across sites and teams.
5. Turn the framework into a 90-day rollout plan
   Prioritize rollout by risk and operational value, define KPIs, and set a test cadence so the framework moves from planning to deployment.

Prompts

Prompt 1:
Act as a multi-site connectivity architect. Using the site, device, and carrier information below, create a standardized failover policy framework that defines site tiers, primary and backup roles, failover triggers, blocked traffic during backup operation, and escalation actions. Keep the output practical and ready for operations teams to review and adopt.

Inputs:
- Number of sites:
- Site types:
- Site criticality tiers:
- Primary connectivity by site:
- Backup connectivity by site:
- Device types by location:
- Critical applications and traffic classes:
- Known outage patterns:
- Existing failover issues:
- Escalation contacts and owners:

Prompt 2:
Act as an IoT and edge operations strategist. Based on the network and device details below, produce a pooled-data plan, device resilience map, outage escalation matrix, and 90-day rollout plan. Include pool math, SIM grouping, alert thresholds, soft caps, overage controls, failover MTTR goals, uptime goals, and a phased deployment timeline.

Inputs:
- SIM count:
- Device inventory:
- Monthly usage by site or device group:
- Current carrier plans:
- Current overage issues:
- Failover triggers:
- Data cap policies:
- Recovery expectations:
- Team structure:
- Rollout constraints:

Output

Users will receive a compact framework bundle designed for executive review and operational rollout.

1) Executive Summary

Length: 1 page
Highlights:

• Site tiers
• Device roles
• Risk hotspots
• High-level failover exposure
• Key opportunities to standardize

2) Pooled Data Plan

Length: 2 pages
Includes:

• Pool math
• SIM grouping
• Soft caps
• Alert thresholds
• Billing scenarios
• Cost-control recommendations

Example outputs:

• Tier 1 sites assigned premium failover pool
• Mobile assets grouped into capped backup pool
• Soft cap alerts at 70 percent, 85 percent, and 95 percent of pool usage

3) Device Resilience Map

Length: 1 to 2 pages
Presented as a matrix listing:

• Device type
• Primary connection
• Backup connection
• Failover triggers
• Data caps
• Blocked or restricted traffic
• Recovery priorities

Example:

• POS router: fiber primary, LTE backup, fail over at packet loss threshold, block software updates on backup
• Security camera gateway: cable primary, 5G backup, cap non-critical upload traffic during failover

4) Multi-Site Failover Policy

Length: 6 to 8 pages
A ready-to-adopt document covering:

• Site tier definitions
• Connectivity standards
• Failover conditions
• Traffic handling rules
• Device-specific policies
• Testing procedures
• Ownership and governance

5) Outage Escalation Matrix

Length: 1 page
Includes:

• Incident severity levels
• Timeline targets
• Team actions
• Vendor engagement steps
• Escalation ownership

Example:

• Tier 1 outage unresolved at 15 minutes escalates to network lead
• Carrier ticket required by 30 minutes
• Business stakeholder notification triggered by 45 minutes

6) 90-Day Rollout Plan

Length: 1 page
Includes:

• Deployment milestones
• Site rollout phases
• Success metrics
• Testing cadence
• Review checkpoints

Key KPIs:

• Uptime percentage
• Failover MTTR
• Data overage rate
• Policy adoption rate
• Test completion rate

Summary

This matters because leaders need a fast, standardized way to keep many sites and devices online without exploding data bills. When failover rules differ by site, device, or carrier, downtime risk increases and costs become harder to control.

This prompt pack turns your real operating data into a plug-in framework you can deploy in 90 days. It helps you reduce downtime, control pooled-data usage, standardize outage response, and create a cleaner operating model for IoT, edge connectivity, and multi-site operations.

The strategic value is simple. Instead of treating every outage, SIM pool, and device type as a one-off issue, you create a repeatable framework your team can scale across locations. That means faster decisions, better uptime, lower overage exposure, and a more disciplined foundation for growth.