On large projects, you'll often have several Revit models that need to stay identical — for example, a campus development with multiple building models that share the same details, families, legends, and schedules. When you correct or refine content in one building, you want that change to flow through to all the others without manually rebuilding it each time.

This article walks through the recommended workflow for syncing shared content across multiple building models, plus the edge cases that tend to trip people up.

Before anything else, it helps to understand how Pirros decides what's "the same."

Pirros does not match content by view name or family name. It matches by Pirros ID and version ID.

So if Building A has version 1 of a partition detail and you've since pushed it to version 3, Pirros knows Building A is two versions behind — by ID, not by name. This is why two items that look identical and have the same name can still end up duplicated: if they have different Pirros IDs, Pirros treats them as two separate pieces of content.

The practical takeaway: pull your shared content from a single source so the IDs line up across all your models.

Create one project on Pirros for the campus (e.g., Campus – Shared Content) and link all of your building models to it. When every model points to the same project, content stays connected by Pirros ID, and you can push from any model and pull into the rest.

Pick one building model to be your master. This is where you make changes to shared details and families. The master is the model you sync into Pirros; the other buildings only download from Pirros.

This is the cleanest approach because it removes ambiguity. If every model can both push and pull, you can technically still get them all to match — but you'll spend more time figuring out which versions are current than you'll save. One source of truth keeps it simple.

All of this happens from the Pirros tab inside Revit — you don't need to go to the Pirros website for routine sync work.

Repeat Download Latest in each building model to bring them all current.

Download Latest is more than a pull button — it's your audit tool. Before you submit or finalize a model, run it. It tells you whether anything has been updated elsewhere that this model doesn't have yet. If everything is current, nothing comes down. If something's behind, it pulls it in.

Getting in the habit of running Download Latest before any deadline submission is the single easiest way to keep all your buildings honest.

When content is updated in Pirros, the person who synced the change does not receive a notification — but anyone who needs to download it does. So if one person both syncs and downloads, they may rarely (or never) see the email. If one teammate syncs and another downloads, the downloader will reliably get notified.

Either way, you don't need to rely on the email. Download Latest surfaces every pending update regardless of notifications.

In practice it's not always possible to keep all edits in the master — different buildings often get detailed to different levels at different times, and you may need to push a refinement from whichever model you happen to be in.

That's fine, as long as all models are linked to the same Pirros project. You can sync from any building file, and the other models will still pick up the change via Download Latest. Two guardrails make this reliable:

If you download content and end up with a duplicate — often the same item with a number appended — it almost always means the two items have different or nonexistent Pirros IDs. This happens when the same-looking content was originally pulled from different sources (say, one person grabbed a family from the typical library and another grabbed it from a different project).

To resolve a duplicate:

Pirros couldn't overwrite the mismatched item because, by ID, it wasn't actually the same piece of content.

You can't merge two pieces of content together on the Pirros website. But inside Revit you can point everything at the correct one — re-link instances to the single correct item, then delete the extras. This comes up more often than you'd expect, especially when multiple people started building the same content independently early in a project.

If I sync from any model and the families have the same name, will they just update?

Not based on the name — Pirros matches on the Pirros ID, not the view or family name. If two same-named items have different Pirros IDs, Pirros treats them as separate content and you'll get a duplicate instead of an update. Pull your shared content from a single source so the IDs line up.

Why did I only get a change notification once?
The person who syncs a change doesn't get the notification — only people who need to download it do. If you're both syncing and downloading, you'll rarely see the email. Either way, you don't need it: Download Latest shows every pending update regardless of notifications.

I downloaded an item and ended up with a duplicate that had a number after it. What happened?
That means the two items have different Pirros IDs, so Pirros couldn't overwrite one with the other. Keep the item with the correct/shared Pirros ID and delete the duplicate with the mismatched ID.

Can I copy a Pirros ID from one item to another to force them to match?
No — don't try to reassign IDs manually; it will cause problems. The right fix is to re-link instances to the single correct item in Revit and delete the extras, or to re-pull the shared content from one source.

Can I merge duplicate content together?
Not on the Pirros website. Inside Revit, point everything at the correct item (re-link instances), then delete the duplicates.

We already have several models that have drifted apart. How do we get back on track?
Get one file to a state you're comfortable with, make it the master, and push it to Pirros. Then download those items into the other buildings, checking for duplicates as you go (keep the correct Pirros ID, delete the mismatches). It takes some cleanup up front, but once the IDs are aligned across models, ongoing sync becomes straightforward.

What if multiple people need to work across the models at the same time?
This becomes a workflow question more than a tool question — decide who owns which content so people aren't editing the same items in parallel. As long as all models are linked to the same project, anyone can sync and the others can pull via Download Latest. Running Download Latest before any submission keeps everyone's models current.