Define what the school needs to recover
List the records that keep the school operating: student profiles, fee transactions, attendance, academic setup and relevant documents. Then ask which of those records a particular export contains. A student spreadsheet can help with an office task without containing everything needed to rebuild the application. Give each copy a clear purpose and an owner.
Ask what happens to attachments, configuration and transaction relationships when data is restored. For example, a receipt total without its student reference is difficult to reconcile. Write a simple acceptance checklist for a recovered workspace. The accountant, administrator and academic coordinator should each recognise the records that need checking before normal work resumes.
Choose a schedule around the amount of work you can repeat
Imagine losing everything entered since the last usable backup. Could the office reconstruct one day of collections from approved source records, or would even a few hours create a serious problem? Use that discussion to choose a schedule. A daily job is useful only when someone notices failure and knows which successful copy is still available.
Keep the schedule understandable to staff. If a service displays a time in UTC, write down the corresponding school time and check the next run shown on screen. In SkoolMatic, the Data & Backups page includes automatic backup settings and a UTC schedule. Review the current service configuration, wallet requirement and available retention before relying on that schedule.
Keep recoverable copies separate from the original problem
A second folder on the same computer may be lost in the same hardware failure, theft or malicious incident as the original records. Decide where an additional recovery copy belongs and who is allowed to reach it. Consider both accidental deletion and a failure affecting the school premises. The plan should explain how the school obtains that copy when the usual operator is absent.
CISA’s ransomware guidance recommends keeping protected offline backups and regularly testing their availability and integrity. For a school, a practical starting point is to maintain an appropriately secured recovery copy outside the immediate failure path and rehearse its use. Ask your support team which backup destinations and encryption arrangements are supported by the deployment rather than assuming every export has those protections.
Check completion, contents and authorised access
A scheduled start time is not proof of a completed backup. Check the recorded outcome and identify the latest successful copy. If the job fails, assign a person to investigate and document whether a manual copy is needed. Avoid creating a long list of unreviewed failed jobs that appears reassuring simply because a schedule exists.
SkoolMatic provides manual backup creation and download controls for the primary administrator, with password confirmation for sensitive backup actions. Its cloud backup settings can also support a school-managed S3 destination when configured. An optional destination has its own storage and retention responsibilities. Test access with an authorised operator and keep credentials in the school’s approved secure process, outside shared staff notes.
Practise restoration away from the live workspace
Arrange a supervised recovery exercise with the provider or school IT owner. Use a safe separate environment so a practice restore does not overwrite current school work. Record which copy was used, how long the steps took and whether attachments and key relationships were available. Keep sample personal information limited to the authorised recovery team.
After restoration, check several records rather than only the home screen. Compare student counts, a few receipt references, an attendance date and a document sample against the source. Ask whether work entered after the backup must be reconstructed. Do not declare recovery complete until the school owners have checked the parts of the application they will use.
Write the first-hour response in plain language
The response sheet should name the school decision-maker, support contact, last successful backup location and authority required for recovery. Include the instruction to stop uncertain edits until the active workspace is confirmed. Keep a copy accessible during a computer failure. Staff should not have to search the unavailable system for the only instructions that explain how to recover it.
Review the plan after a staff change, storage change or major software update. Treat a move to another deployment as a separate project with reconciliation and a controlled handover. The school ERP data migration guide explains how to plan that transition. Bring one completed backup and your recovery checklist to a SkoolMatic review so the discussion produces evidence rather than a promise.
What schools should check
Scope
Confirm which records and attachments a backup includes.
Schedule
Check completed jobs and the last successful copy.
Separation
Keep recovery copies outside the original failure path.
Practice
Verify representative records in a supervised restore.
Related questions
Is a spreadsheet export a complete school backup?
Not necessarily. It may contain selected rows while omitting attachments, settings or relationships needed for restoration. Ask exactly what the export includes and what recovery process can use it.
How often should a school create backups?
Choose a schedule around how much recent work the school could reconstruct, the service capabilities and the time needed to check failures. Review actual successful jobs rather than relying only on the configured schedule.
Should the school restore a backup directly over live records to test it?
Use a separate supervised recovery environment. Overwriting live work can destroy changes made after the backup. The provider and school owners should agree a safe rehearsal and a reconciliation checklist.
Explore the school software behind these workflows
Review the product workflow with your school team, then bring your current records and questions to a live demo.
Explore SkoolMatic featuresBook a Demo