If your firm lives in Revit and AutoCAD, your project files are your inventory, your billable hours, and your reputation, all in one place. This post is for principals, office managers, and IT leads at architecture, engineering, and construction firms across Massachusetts and New Hampshire who want a straight answer: is one backup enough? It isn’t, and here is why, in plain English.

Why Revit Projects Are Different From Ordinary Files

A spreadsheet is a file. A Revit project is closer to a living ecosystem. Central models, linked models, consultant references, families, and CAD xrefs all depend on one another, and a dozen people may be working in them at once.

That complexity changes what “backed up” has to mean. Copying files somewhere is not the same as being able to restore a working project.

• Models are large and constantly changing. A project can be modified hundreds of times in a single week.
• Dependencies matter. Restoring one file without the links and references it relies on can leave you with a model that opens but is broken.
• Deadlines are unforgiving. Losing a day of work the night before a permit submission or a bid is not an inconvenience. It is a crisis.

Where a Single Backup Fails

Most firms we talk to believe they are covered because “there’s a backup.” Often there is. The trouble is that one backup has one way to fail, and design firms tend to discover the failure at the worst possible moment.

Here are the most common ways a lone backup lets a firm down:

• It faithfully copied the problem. If a model was corrupted on Tuesday and the backup ran Tuesday night, you now have a clean backup of a damaged project.
• It only keeps the latest copy. When the newest version is the bad one, there is nothing older to return to.
• It lives in the same place as the original. A fire, a flood, a theft, or a ransomware attack that reaches your network can reach the backup too.
• Nobody has ever tested a restore. A backup that has never been restored is a hope, not a plan.
• It was set up once and forgotten. Projects grow, staff change, and a job that quietly started failing months ago can go unnoticed.

A backup is only as good as the worst day you need it. If you have only one, it has to be perfect every single time.

What Corruption and Ransomware Look Like at a Design Firm

These two threats are different, but both are far more common than most firms expect, and both punish a single-backup approach.

Model corruption: the quiet problem

Corruption rarely announces itself. A central model starts behaving strangely, syncs slow down, or elements go missing or duplicate. Sometimes it is a bad sync, sometimes a failing drive, sometimes a crash mid-save.

The danger is timing. By the time someone notices, several days of backups may already contain the damage. The question then becomes: how far back can you go, and how much work do you lose by going there?

Ransomware: the loud problem

Ransomware locks your files and demands payment to release them. For a design firm, that means project folders, drawings, and models suddenly unreadable, with a note on the screen and a deadline attached.

Attackers know that backups are your way out, so modern attacks actively hunt for them. A backup that is reachable from your office network is a backup that can be encrypted or deleted along with everything else.

• Active projects stall. Every team member who touches the affected files is stopped.
• Client and consultant trust takes a hit. Missed submissions and delayed deliverables are visible to everyone you work with.
• Contracts raise the stakes. Clients in government, healthcare, and institutional work increasingly ask how project data is protected.

What Layered, Versioned, Offsite Protection Means

“Layered” sounds technical, but the idea is simple. You never rely on one safety net. You build several, so that whatever goes wrong, at least one of them still holds. We will keep this to outcomes, because what matters to you is what the protection delivers.

Versioned: you can go back in time

Versioning means you keep many past copies of your projects, not just the latest. If a model was damaged last Wednesday, you can return to the version from last Tuesday.

• Recover from corruption by stepping back to the last good state.
• Undo accidental deletions and overwrites, which happen more often than anyone admits.
• Lose hours of work at worst, not weeks.

Layered: more than one line of defense

Layering means your protection does not hinge on a single copy, location, or method. If one layer fails or is compromised, another is still standing.

• A problem with one copy does not become a problem with every copy.
• An attack that reaches your day-to-day files does not automatically reach your protected ones.
• You are covered against hardware failure, human error, and malicious attack, not just one of them.

Offsite: your recovery does not depend on your building

Offsite means a protected copy of your work exists away from your office. A fire, flood, burst pipe, break-in, or network-wide attack at your location does not take your recovery options with it.

For firms across Massachusetts and New Hampshire, where older buildings, winter storms, and aging infrastructure are real factors, this layer is not paranoia. It is basic resilience.

Tested: you know it works before you need it

The final ingredient is proof. Protection that is regularly verified, with real restores checked against real projects, turns “we think we’re covered” into “we know we’re covered.”

Questions Every Principal Should Ask

You do not need to be technical to evaluate your own protection. Ask your team or your IT provider these questions and listen closely to the answers:

• If a central model was corrupted last week, can we get back to a version from before it happened?
• How many past versions of our projects do we actually keep, and for how long?
• If ransomware hit our office tonight, would our backups survive it?
• Is there a copy of our project data that exists outside our building?
• When did we last restore a real project as a test, and what happened?
• How long would it take to get one active project back up and running? A whole office?
• Who is alerted if a backup fails, and how fast?

If the answers are vague, or the honest answer is “I’m not sure,” that is useful information. It is far better to find the gap during a calm conversation than during an emergency.

Next Step

Design firms across Massachusetts and New Hampshire trust LG Tech MSP as their managed IT partner because we understand that your projects are the business. If you would like a clear picture of how well your Revit and CAD work is protected today, we are glad to talk it through. You can also read more about how we support architecture, engineering, and construction firms through our managed IT services for AEC firms. We also work with small-to-mid-sized businesses across other industries.

Last updated: 2026