⚠️ [MINOR INCIDENT] / [SERVICE OUTAGE] (delete as appropriate)
We are currently experiencing a service issue. Our team is actively working to resolve this.
Last updated: [Time and Date — e.g. 10:00 AM GMT, 9 April 2026] Next update due: [Time — e.g. 12:00 PM GMT]
We will update this page every 120 minutes — even if there is no new technical information, we will confirm that work is continuing.
CURRENT STATUS
| Area | Status |
|---|---|
| Platform Access & Login | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| Risk Assessments | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| Procedures | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| Checksheets & Tasks | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| Reporting & Analytics | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| Notifications & Alerts | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
| User Management | ✅ Operational / ⚠️ Affected / 🔴 Unavailable |
We know your operation depends on OpsPal, and we're treating this as our top priority.
WHAT’S HAPPENING
Issue: [Plain English description — e.g. “Users are unable to log in to the OpsPal platform” or “Checksheet notification emails are not sending”]
Started: [Time and Date]
Impact: [e.g. “All users are affected” / “Checksheet module only — all other features working normally”]
Root Cause: [Only include if confirmed by your developer — e.g. “We have identified an issue with our database server.” If unknown, use: “We are actively investigating the cause.”]
YOUR DATA IS SAFE
We want to be clear: your data is fully secure and intact. All risk assessments, procedures, completed tasks, and compliance records are safe. This is a service availability issue — nothing has been lost or compromised.
WHAT WE’RE DOING
Our development team is working on this right now. [Add brief detail if available — e.g. “We have identified the root cause and are deploying a fix.” If not: “We are actively diagnosing the issue and will share more detail as soon as we have it.”]
WHAT TO DO IN THE MEANTIME
(Use this section for full outage only — remove for minor incidents where the rest of the platform works normally)
We know your team still has compliance checks and operational tasks to complete. Here’s what we recommend while OpsPal is unavailable:
- Revert to paper-based or local backup processes for any time-sensitive compliance checks
- Inform your team leads that OpsPal is temporarily unavailable
- Retain any manual records — these can be logged retrospectively once OpsPal is restored
- Do not delay safety-critical checks — complete them manually and keep a record
If you need guidance specific to your facility, contact Dawn Anne directly.
NEED TO SPEAK TO SOMEONE?
Don’t wait for the next update if this is causing an urgent operational or compliance problem.
Dawn Anne McAneney — Customer Support 📧 dawn-anne@opspal.com 📞 07725 985 317
UPDATE LOG
Use this section to log each update chronologically during the incident. Add the newest entries at the top.
[Time, Date] — [Brief update — e.g. “Root cause identified. Fix being deployed. Next update: 2:00 PM GMT.”]
[Time, Date] — [e.g. “We have no new technical information to share at this point. Our team continues to work on the issue. Next update: 12:00 PM GMT.”]
[Time, Date] — [e.g. “Incident identified. Platform unavailable for all users. Team alerted and investigating. Next update: 10:00 AM GMT.”]
Book a Call With Our Team
We’re on hand for any questions you may have. Simply book a meeting using our booking system and we will talk you through any questions.