Ask for a recovery demonstration, not just a backup tick
Check what can actually be restored and who is responsible when an application fails.
A backup report may say that files were copied successfully. That does not answer whether your business can restore the website, its customer records and its working connections.
Start by naming what would stop work if it disappeared. For a small Australian business, the list might include incoming enquiries, active jobs, uploaded documents and the product catalogue. Email and third-party booking records may sit outside the website backup entirely.
Define the recovery question
Ask the supplier what is backed up, how often, how long copies are kept and where restoration is tested. Decide how much recent work the business could tolerate losing and how long it could operate without the system. These are business decisions that guide technical choices.
The ACSC small-business handbook includes backup advice. Your own plan needs the details of your application, suppliers and records.
Restore somewhere safe
A test restoration should use an appropriate separate environment and protect personal information. It should not send old notifications to customers or create real charges. Confirm which background tasks must remain disabled during the exercise.
Have someone check a familiar record and complete a demonstration task. The presence of files is less useful than seeing that the restored application can read the expected information.
Know whom to contact
Document the account owners and support route. If a developer is unavailable, the business should still know where its hosting and domain are managed. Store recovery information securely and review it after staff or supplier changes.
Faith Forge Labs can include recovery work in a scoped care arrangement. Restoration capabilities and support hours are agreed for the specific project rather than assumed from a general maintenance label.