Version control for Revit

Start every project from the right model.

Heartwood keeps one current master model for every building. Projects branch from it, built work merges back, and the next team starts where the last one finished.

Without Heartwood

Every repeat job starts with the same hunt.

  • Which model is current?

    Ask around until someone remembers which project touched the building last.

  • Save As, then strip it.

    Delete the last job's sheets, revisions, and demo by hand before the real work starts.

  • Corrections go nowhere.

    Field fixes stay in one project file. The next team measures the same wall again.

Building 12 / Models

Seven model files with conflicting names collapse into one current master for Building 12.

How it works

Branch. Build. Merge.

01

Branch

Start a project from the building's master. Your template comes in. The last job's sheets, revisions, and demo don't.

  • v13 base
  • 0 old sheets
02

Build

Work in Revit like always. When another team merges, you see what changed and whether it's on your floors.

  • 1 behind
  • 2 changes on Level 3
03

Merge

When record drawings land, merge your project back. The next team starts from v15, field corrections and all.

  • +212 added
  • −48 demolished
  • 9 converged
Building 12
v13 v14 v15 Roof replacement Construction Merged into v14 Level 3 clinic In design · from v13 Construction · 1 behind Merged into v15

The product

Made for BIM managers. Easy for everyone else.

Start a project

A clean start, every time.

Branch from the building's current master. Your firm's template comes in. The last job's sheets, revisions, and demo don't.

Worksets, phases, levels, and hosting stay intact.

Stay current

Know when the master moves.

When another team merges, every open project sees it. Heartwood shows what changed and whether it touches your floors.

A pane inside Revit, and the same view in your browser.

Merge

See every change before it merges.

Heartwood compares where you started, what you built, and the master as it stands today. Changes both sides already made sort themselves out. Real conflicts are a short list.

New construction adds. Demolished removes. Your phasing already says what changed.

Where this came from

Every element has a history.

Select a wall and see which project put it there, which version moved it, and why.

Elements keep their history through every Save As, copy, and project.

Every building

Your whole campus, current.

One master per building, whether you look after two or two hundred. See what's open, what's behind, and what merged last.

Under the hood

Built the way your models already work.

No new modeling rules. Heartwood reads what your team already does in Revit and keeps the record in a file you can open.

building-12.registry.jsonPlain JSON
{
  "schema": 1,
  "building": { "id": "b12", "name": "Building 12" },
  "versions": [
    …
    { "v": 14, "kind": "merge", "branch": "roof" },
    { "v": 15, "kind": "merge", "branch": "l3-clinic" }
  ],
  "branches": [
    { "id": "lab", "name": "Lab fit-out",
      "base_version": 13,
      "history": [
        { "status": "in_design", "date": "2026-03-02" },
        { "status": "in_construction", "date": "2026-09-14" }
      ] }
  ]
}
Tracking
Every element, every copy. Heartwood follows each element from the master into every project and back, so nothing loses its history.
Compare
Three-way. Base, project, and current master, so another team's merged work never reads as your deletion.
Changes
From your phasing. New construction adds. Demolished removes. Your team already marked it up by doing the job.
Branch
A true copy. Worksets, phases, levels, and hosting come along. Then your template goes in.
Safety
Dry run first. Every change to a model starts as a report you can read.
Data
Stays in your hub. Element data stays in your hub or file share. The service sees names, statuses, and counts.
Record
One file per building. Plain JSON. Readable, portable, and yours to keep.
Runs in
Revit 2025 and later. A pane inside Revit, plus the same app in your browser.

Be one of the first firms on Heartwood.

Heartwood is in development with A/E teams who work in the same buildings again and again. The waitlist decides who gets in next.