What belongs in a construction disaster recovery plan? A construction disaster recovery plan should identify the company’s critical systems, recovery priorities, responsible people, backup locations, communication methods, and step-by-step recovery procedures. It should cover cyber incidents as well as equipment failure, internet outages, severe weather, theft, and cloud-service disruption.

The plan needs to answer a practical question: how will the company continue its most important work when normal systems are unavailable?

Identify the work that cannot wait

Begin with business functions, not servers. Leadership should identify which activities become urgent first:

• Payroll and time entry
• Payment and banking
• Project communication
• Plans, specifications, and field documentation
• Scheduling and dispatch
• Estimating and bidding
• Customer and subcontractor coordination
• Safety and compliance records

Then map each function to the people, devices, connections, and applications it depends on.

A payroll process might rely on Microsoft 365, Sage HCM, Vista Viewpoint, hh2, or another system. Field operations may rely on Procore, HCSS, ServiceTitan, Bluebeam, Trimble, or Autodesk services. Design work may depend on AutoCAD, Revit, or SketchUp files and suitably equipped workstations.

Set recovery priorities

Not every application needs to return at the same moment. Define:

• How long each business function can be unavailable
• How much recent data the company could tolerate losing
• Which systems must be restored first
• Which manual workarounds are acceptable
• Who decides when to use the workaround

These business decisions guide backup frequency and recovery investment. They should not be left for the first hour of an emergency.

Know what is actually backed up

Create a written list of protected systems and data. Include where the backups are stored, how long they are retained, and who monitors failures.

Do not assume every cloud application is covered by the same backup. Microsoft 365, Procore, Vista Viewpoint, BuildingConnected, ServiceTitan, HCSS, and other platforms have different data ownership, export, retention, and recovery options.

Review each vendor’s current documentation and contract. Decide whether the vendor’s built-in recovery is sufficient for the company’s needs or whether another copy or export is appropriate.

At least one protected backup should be separated from ordinary user access so a compromised account cannot easily delete it.

Document people and communication

The plan should name roles, not rely only on one individual’s memory. Identify:

• Incident lead
• Executive decision-maker
• IT recovery lead
• Finance and payroll contacts
• Legal counsel and insurance contacts
• Communications owner
• Key application vendors
• Internet and telecom providers

Keep an offline copy of essential contact information. A plan stored only in Microsoft 365 may be difficult to reach during a Microsoft 365 incident.

Include temporary ways to work

Recovery does not always mean restoring everything immediately. It can include a controlled temporary process.

Examples include:

• A verified phone tree when Teams or email is unavailable
• Cellular connectivity when the primary site connection fails
• A documented manual time-entry process
• Read-only copies of essential plans
• Alternate computers for critical employees
• A defined process for urgent payment approvals

Temporary methods should protect security and recordkeeping. An emergency should not become permission to send sensitive files through any available personal account.

Test the plan

A backup report is not a recovery test. Test whether the company can restore useful information and resume a real business function.

Run short exercises such as:

• Restore a deleted project folder
• Recover a sample Microsoft 365 mailbox or file
• Test cellular internet failover at a job site
• Practice responding to a compromised executive account
• Walk through payroll when the normal application is unavailable

Record what worked, what failed, and who owns each correction.

Frequently asked questions

Is disaster recovery the same as backup?

No. A backup is a protected copy of data. Disaster recovery is the broader process of restoring systems and operations after a disruption.

How often should the plan be tested?

Test critical recovery procedures on a schedule based on business risk and after major changes to systems, locations, vendors, or responsibilities. A full annual exercise is useful, but some restore and failover tests should occur more frequently.

Who owns disaster recovery?

Leadership owns the business priorities. IT owns much of the technical preparation and recovery work. Finance, operations, communications, legal, insurance, and application owners also have responsibilities.

Learn More

• What Is Proactive, Lifecycle-Based IT Management and How Is It Different From Break-Fix?
• How Should IT Support Field Crews and Job Sites in a Construction Company?
• What Cybersecurity Does a Construction Company Need?

SisAdmin helps construction companies identify critical systems, strengthen backups, document recovery responsibilities, and test whether recovery plans work. A useful plan should fit the way your company operates, not sit untouched in a binder.