Event Log
| Action Plan for no service on website | Date & Time | Actioned by | Check | Comment |
| Start an event Log | ¨ | |||
| Identified (screen capture if possible) any error message when calling the website | ¨ | |||
| Check AWS to make sure it is not a scheduled maintenance outage, or if they aware of any hosting issues | ¨ | |||
| Notify Sm8rtHealth developers of website failure or inactivity | ¨ | |||
| Screen capture the error or problem | ¨ | |||
| Critical activities that may have been disrupted due to the outage | ¨ | |||
| Contact IT support Tier 2 (Steven). If these persons cannot be contacted, escalate to Developer (Clive) | ¨ | |||
| Contact Clients and establish what was the last data transferred to administration system. | ¨ | |||
| Determine and record what was the last transaction recorded by SM8 | ¨ | |||
| Establish channels of communication for progress updates with Client and SM8 staff | ¨ | |||
| Determine if any transactional data needs to be restored | ¨ | |||
| Keep stakeholders informed | ¨ | |||
| Update event log when web service resumed | ¨ |
Recovery Plan
| Recover Plan | Date & Time | Actioned by | Check | Comment |
| Establish cause of website failure | ¨ | |||
| Establish symptoms resulting from website failure | ¨ | |||
| Identified critical activities that may be disrupted | ¨ | |||
| Convene all stakeholders to implement a suitable patch or system upgrade | ¨ | |||
| Implement any update to or changes to hosting environment | ¨ | |||
| UAT upgrade | ¨ | |||
| Update any records | ¨ | |||
| Promote changes to production environment | ¨ | |||
| Convey to all stakeholder | ¨ |
Person completing this checklist: _____________________________
