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
Version control for Revit
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
Ask around until someone remembers which project touched the building last.
Delete the last job's sheets, revisions, and demo by hand before the real work starts.
Field fixes stay in one project file. The next team measures the same wall again.
Seven model files with conflicting names collapse into one current master for Building 12.
How it works
Start a project from the building's master. Your template comes in. The last job's sheets, revisions, and demo don't.
Work in Revit like always. When another team merges, you see what changed and whether it's on your floors.
When record drawings land, merge your project back. The next team starts from v15, field corrections and all.
The product
Start a project
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
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
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
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
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
No new modeling rules. Heartwood reads what your team already does in Revit and keeps the record in a file you can open.
{
"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" }
] }
]
}
Heartwood is in development with A/E teams who work in the same buildings again and again. The waitlist decides who gets in next.