Gridcheck, LLC
Document Owner: Gridcheck Executive Leadership
Effective: August 2026
Review Frequency: Annual
Last Reviewed: August 2026
Next Scheduled Review: August 2027
Business Continuity Philosophy
Our company operates on a lean, decentralized architecture with redundancy and fallback strategies embedded in how we work. Given our small team size and the nature of our SaaS product (Gridcheck), our risk profile is low, and most disruptions result in minor inconvenience, not critical failure.
Systems Resilience
- Gridcheck SaaS Platform is hosted on AWS in the US East region. In the event of a regional outage or critical failure, we are prepared to restore from recent backups to a different AWS region or instance. These backups are automated and regularly verified.
- Email and Communication Trails are independent of Gridcheck and are maintained through third-party services (e.g., Google Workspace, Outlook). Every transaction and appointment confirmation leaves a redundant trail, enabling continuity of communication even if the platform is down.
- Appointment Schedules and Class Rosters are often replicated in separate platforms by clients (e.g., Outlook calendars, Apple calendars, paper backups, or institutional scheduling software). As such, no single point of failure exists for time-sensitive coordination.
- Fallback Operations: In the event of Gridcheck downtime, users can rely on emailed confirmations or export backups (spreadsheets) for temporary tracking. Most of our work can continue in a “reduced horsepower” mode without true interruption of service delivery.
Disaster Scenarios
| Scenario | Impact | Recovery Plan |
|---|---|---|
| AWS Outage | Low-Med | Restore from backup to alternate instance/region |
| Gridcheck Platform Bug | Low | Manual coordination via email & spreadsheets |
| Total Internet Blackout (U.S.) | Existential | Not a recoverable business-level event; fallback to personal coordination and memory if needed |
| Loss of a Key Staff Member | Medium | Roles are interchangeable; documentation and email history provide continuity |
Conclusion
Our business model does not rely on a tightly coupled, monolithic system. Instead, we embrace distributed tools and resilience through redundancy and transparency. We recognize that some level of risk comes with the territory—but our systems are designed to absorb those risks without breaking stride.
Who to Contact
For urgent continuity related issues:
Cliff Hanks – 505-303-0562 x709 – cliff@gridcheck.com
Angela Jones – 505-303-0562 x703 – angela@gridcheck.com
or email support@gridcheck.com