How to fix the Revit central model error: what does the message mean?

The Revit central model error means your local model has lost its connection to the central model.

In a workshared Revit project, a central model sits on the network and everyone works in their own local model. The central model error appears as soon as Revit can no longer link the two: the central model has been moved, renamed, is unreachable, or has become internally damaged. You can no longer synchronise and your changes do not reach the master.

The message itself is not data loss. Your work is still in your local model. The problem is the relationship between local and central. Until you restore that relationship or create a new local model, synchronising remains impossible. How worksharing and that relationship work exactly is covered in the guide on setting up Revit worksharing and the central model.

Revit shows different variants of the message depending on the cause.

The exact wording varies. Once you recognise the message, you know immediately which direction to go:

The first three relate to a broken or moved link and are quick to fix. The last one, about corruption, requires an audit or a backup.

Most central model errors are caused by moved files, network dropouts or duplicate usernames.

Recurring causes at a glance:

• Central model moved or renamed. Your local model still points to the old path. This is by far the most common cause.
• Network connection dropped. The connection to the network drive fails during synchronisation, so the write fails.
• Working directly in the central model. Someone opened the central model without Create New Local and claimed elements.
• Duplicate username. Two people with the same Username can block each other's synchronisation.
• Damaged file. A crash or incomplete synchronisation left the model in a corrupt state.
• Local model copied between PCs. A local model is tied to a user and machine; manually copying it to another PC breaks the link.
• Central model on a synced cloud service. A network drive that syncs through a consumer service such as Dropbox or OneDrive can lock the file or write it twice. Do not keep a central model there.

First determine which one applies. If the file still exists and can be opened, it is almost always a link or naming problem. If you only get an error when opening the file itself, think of corruption.

Do not confuse the central model error with a normal message that an element is in use.

Two messages look similar but have different causes. The central model error is about the link between local and central: you cannot synchronise at all. The message Can't edit the element until (user) resaves the element to central and relinquishes it is a normal ownership conflict: a colleague has borrowed that element. That is not a fault but the intended behaviour of worksharing.

If you recognise an ownership conflict, the solution is simple. Ask your colleague to synchronise so they release the element, or use Place Request to send a request automatically. Only when synchronising itself is impossible and Revit complains about the central model are you dealing with the actual central model error from this guide.

Creating a new local model resolves most link errors at once.

If the central model is still healthy and in place, restore the relationship by creating a fresh local model. Do this as follows:

1. Make sure your current work is safe: save your local model under a separate name as a backup copy.
2. Go to the application menu, choose Open and browse to the central model on the network drive.
3. Tick Create New Local in the bottom right and click Open.
4. Revit asks whether you want to overwrite or replace the existing local model. Choose Overwrite the existing file (or Append timestamp to keep both).

Application menu > Open > (central model) > tick Create New Local > Open > Overwrite the existing file

If you are concerned that your edited work is in the old local model, use Append timestamp so you can compare the old model. Changes that have not been synchronised unfortunately cannot be carried over; that is why frequent synchronising is worthwhile.

If you want to check where your local model points before overwriting anything, look at the path in the recent files or open the local model and try to synchronise once; Revit mentions the expected path to the central model in the error message. If that path no longer matches the actual location, you can be sure the central model has been moved.

With Detach from Central you create a clean new central model.

If the link is structurally broken or you need to move the central model to a new location, build a clean central model. Do this by detaching:

1. Choose Open and select the central model.
2. Tick Detach from Central at the bottom of the Open window.
3. Revit asks you to choose: select Detach and preserve worksets so your workset structure remains intact.
4. The file now opens independently of any central model. Go to Save As > Project, choose the desired network location and click Options.
5. Tick Make this a Central Model after save and save.

Open > Detach from Central > Detach and preserve worksets > Save As > Project > Options: Make this a Central Model after save

Then ask all team members to discard their old local models and create a new local model from this fresh central model. That way everyone starts again from the same healthy baseline. This structured approach, detach first and then rebuild, is similar to working from a clean basis in other Autodesk software, such as creating a corridor in Civil 3D, where you also get your source data in order first.

In case of corruption, recover the model with Audit or use the backup folder.

If you see a message that the file is corrupt and must be recovered manually, try an audit first:

1. Choose Open and select the central model.
2. Tick both Audit and Detach from Central.
3. Click Open. The audit checks and repairs the internal data structure. This can take a long time on large models.
4. Save the repaired file as a new central model via Save As with Make this a Central Model after save.

If the audit does not work, use the backup folder. Next to the central model, Revit keeps a folder named <centralmodel>_backup. It contains earlier versions. Restore an older, healthy version using the Restore Backup button on the Collaborate tab, or open the backup folder and restore an earlier backup version. Copy the backup folder to a safe location before restoring anything.

If Revit crashed in the middle of a synchronisation, the central model may have been left half-written. In that case, do not let anyone synchronise again until you have checked the model. Open it with Audit, check that all latest changes are present, and save it again as a central model. This prevents local models from linking to a half-damaged master. To avoid corruption in the first place, it is worth periodically purging heavy models and packaging them with eTransmit, so old, unused data does not overload the file unnecessarily.

The official steps to recover a damaged workshared file are in the Autodesk documentation on recovering a workshared file. If you work with cloud worksharing (BIM 360 or Autodesk Docs) and Revit crashes, the local recovery file is a standalone central model that you publish again.

Stable file locations and unique usernames prevent most occurrences of the error.

The central model error is almost always avoidable with discipline:

• Never move or rename the central model while local models are linked to it. If you must, use Detach and have everyone create a new local model.
• Give each team member a unique Username via the application menu, Options, General.
• Synchronise often and save your local model regularly, so any non-synchronised work remains limited.
• Never work directly in the central model; always open with Create New Local.
• Keep the central model on a stable network drive, not on someone's personal PC.

For larger teams, the free add-in Worksharing Monitor helps you spot problems early. It shows who is signed in, who is synchronising and whether the central model is still reachable. If someone notices that the network connection is unstable, they can wait to synchronise until the connection is stable, instead of forcing a half-completed write that damages the file. A simple team rule, do not synchronise during network maintenance, avoids most corruption cases.

If you purchase or use Revit licences through a third party, check that every installation has a valid, unique activation; unclear installations increase the chance of synchronisation problems. If you want to build your 2D documentation further after recovery, you will find a similar, structured workflow in the explanation of deriving a 2D drawing from a 3D model in Inventor.