Business Continuity Checklist -- Perth IT Care

Your server dies at 9am on Monday morning. Staff are standing around, customers can't access your systems, and you're scrambling to find out if last night's backup actually contains what you need. How long until you're back online?

Most Perth businesses assume their backups work until they need them. But disaster recovery isn't just about having backups — it's about having tested systems you can actually restore from when everything goes wrong. This business continuity checklist will help you identify gaps in your current setup before disaster strikes.

How Long Can Your Business Actually Survive Without Each System?

Before you can plan recovery, you need to know what "fast enough" means for your business. Every system has a different tolerance for downtime.

Your email going down for two hours might be annoying. Your point-of-sale system being offline for two hours during peak trading could cost you thousands. Your website being down for a day might barely register, or it might be catastrophic if you're an online retailer.

Document your Recovery Time Objectives (RTOs) for each critical system:

• Email and communication tools
• Customer management systems
• Financial software and payment processing
• File servers and shared documents
• Your website and online services
• Phone systems

Be realistic about what "critical" means. Not everything needs to be back online in 30 minutes. Some systems can wait until the next day if your staff can work around the outage.

Perth businesses often underestimate how NBN outages can cascade. When an entire suburb loses internet, your cloud backups become inaccessible, your Teams phones stop working, and your card payment terminal goes offline. Planning for local infrastructure failures means having offline alternatives ready.

Are Your Backups Actually Usable?

Having backups and having working backups are completely different things. Too many businesses discover their backup files are corrupted, incomplete, or missing critical components when they're desperately trying to restore.

For WordPress websites, most backup plugins create files that can't actually be restored without the exact same hosting environment. If your web hosting provider disappears overnight, that backup sitting in their system won't help. We've seen Perth businesses lose weeks of work because their backup strategy relied entirely on their hosting provider's infrastructure.

Test your backups monthly:

• Attempt to restore a file from last week's backup
• Check backup logs for errors or warnings
• Verify backup sizes make sense (massive changes in file size usually indicate problems)
• Ensure you can access backup files from a different location
• Document what's NOT included in your backups

For databases and email systems, regular restoration tests are critical. A backup that takes 12 hours to restore might meet your technical requirements but fail your business requirements if customers expect quick responses.

Can You Actually Access What You Need During an Emergency?

When systems are down, you need access to recovery information. But if your password manager is on the failed server, or your documentation is stored in the cloud system that's currently offline, you're stuck.

Create an offline emergency kit that includes:

• Contact details for your IT support team, hosting provider, and internet service provider
• Admin passwords for critical systems (stored securely, not in a text file)
• Network configuration details and IP addresses
• Backup locations and access credentials
• Emergency procedures checklist

Print this information and store it somewhere accessible. When your office systems are down, you don't want to be hunting through cloud storage on your phone trying to find login details.

Practical tip: Create a sealed envelope with critical recovery information and review it every six months. If passwords or procedures change, update the envelope.

Communication During Outages

Your customers and suppliers need to know what's happening. But if your email system is down and your website displays an error page, how do you communicate?

Prepare alternative communication channels:

• Personal mobile phones with key customer contacts
• Social media accounts with posting access from mobile devices
• A simple status page hosted separately from your main website
• Pre-written email templates for common outage scenarios

Perth businesses often rely too heavily on Microsoft 365 for all communication. When your Microsoft 365 tenant has issues, email, Teams, and phone systems can all fail simultaneously. Having a backup communication method that doesn't depend on your primary systems prevents complete communication blackout.

Consider setting up a simple status page through a different provider than your main website hosting. When your primary website is down, you can redirect visitors to the status page that explains the situation and provides alternative contact methods.

Testing Your Recovery Procedures

The best disaster recovery plan is worthless if nobody knows how to execute it. Regular testing reveals gaps between what you think will work and what actually works under pressure.

Schedule quarterly disaster recovery tests:

• Pick a non-critical system and simulate failure
• Time how long each step takes
• Document what went wrong or took longer than expected
• Update procedures based on what you learned
• Train staff on their roles during outages

Start with small tests. Simulate losing access to your file server for an hour. Can staff access the documents they need? Do they know who to contact? Can they continue working while systems are restored?

For larger systems, consider testing during planned maintenance windows when you can control the timing and reduce actual business impact.

Local vs Cloud Dependencies

Many Perth businesses have moved everything to the cloud, assuming this eliminates local infrastructure risks. But cloud services have their own failure modes, and internet outages can make perfectly functional cloud systems completely inaccessible.

Identify your internet dependencies:

• What systems become unusable without internet?
• Which processes can continue offline?
• How long can you operate with degraded connectivity?
• What happens if your internet is restored but cloud services are still down?

Keep some critical capabilities offline. Physical payment terminals, offline copies of essential documents, and phone systems that work during internet outages provide fallback options when cloud systems fail.

Evaluating your current technology setup helps identify single points of failure before they become business-stopping problems. If everything depends on one internet connection, one server, or one cloud service, you're one failure away from a complete shutdown.

Recovery Priority Matrix

Not everything needs to be restored in the same order. Create a recovery priority matrix that matches your business needs:

Priority 1 (restore within 1 hour):

• Customer-facing systems during business hours
• Payment processing
• Critical communication tools

Priority 2 (restore within 4 hours):

• Internal file access
• Email systems
• Productivity software

Priority 3 (restore within 24 hours):

• Reporting systems
• Non-critical websites
• Archive access

This matrix helps you focus recovery efforts where they'll have the biggest business impact. Spending four hours restoring your internal wiki while your payment system stays offline might not be the right choice.

Document dependencies between systems. Your customer management system might depend on the database server and the file server. Knowing these relationships prevents wasted effort trying to restore dependent systems before their foundations are working.

Regular testing and honest evaluation of your current setup will reveal gaps before they become expensive emergencies. The goal isn't perfect disaster recovery — it's recovery that's fast enough and reliable enough for your specific business needs.