---
title: "Revise It: A Moat Analysis · Harness Architecture"
description: "Revit’s moat is the work of keeping a drawing set coordinated through revisions. A walk through Revit 1.0 to 3.0 and the features behind it."
source: https://www.testfit.io/harness-architecture/revise-it-a-moat-analysis
last_updated: 2026-11-03T00:00:00Z
---

Essay · April 14, 2025

# Revise It: A Moat Analysis

- **Author**: Clifton Harness
- **Date**: April 14, 2025
- **Address**: /harness-architecture/revise-it-a-moat-analysis

Interactive study One model, many views

Revit’s moat is that the contract documents it generates are consistently generated for a project. It is stable at revision clouds. Its moat, in my opinion, is change control: it produces the same export again and again, even as the software underneath keeps changing. Here I have tried to unpack it using OpenAI Deep Research as my study partner.

Some terms, because the whole argument hangs on them. A _moat_ is the advantage a competitor can’t easily copy. _Contract documents_ are the drawings (and specs) that become part of the construction contract: the set the contractor bids and builds from. A _revision cloud_ is the scalloped outline drawn around whatever changed on a sheet, tagged with the revision number. And a set is never issued once. Permit comments come back, the owner changes the unit mix, the structural engineer moves a column line, and the set goes out again as Revision 1, Revision 2, Revision 7. Every reissue needs a check of what changed and a clear revision record; the clouds are part of that work. A door number that silently changes on a sheet nobody clouded gets built wrong.

So the question for this page: which parts of Revit built that moat, and how early?

To cross the moat, one must understand it better than those currently defending the moat. Let’s begin.

One distinction to carry through the release history. Some features make a better _model_: massing, rendering, content libraries. Others keep the _set_ consistent when the model changes: one change propagating through modeled relationships, views drawn from the same model, 2D detailing kept in the same project, many people editing it without forking it. The second kind is the moat. After each release below there’s a note on which kind it shipped.

A note on the record: the dates, prices and feature lists below come from that Deep Research session, not from a line-by-line reading of Revit Technology’s own release notes. Treat each date as approximate and each feature as “arrived around this release.”

I will skip the private releases and jump right into the 1.0 Feature Sets

## Revit 1.0 April 2000

Released 25 years ago the month I wrote this, April 2025.

- Parametric Change Engine – Changes to one element can propagate through its modeled relationships. Moving a wall can update attached floors and roofs and the flipping dimstrings associated with the wall. This feature alone is nearly impossible to build. (_Parametric_ means elements are defined by rules and relationships rather than fixed coordinates; _dimstrings_ are the chained dimension strings measured off that wall.)
- Graphical Family Editor – A graphical interface for designers to create parametric objects – making parametrics easy to access for designers for the first time. Dynamic blocks only came to AutoCAD in 2006. (A _family_ is Revit’s parametric object: a door, a window, a casework type, with its sizes and rules. Dynamic blocks are AutoCAD’s comparable feature; “2006” is the AutoCAD 2006 release.)
- Automatic Coordination – Changes to shared model elements propagate to the model views and schedules that represent them through [parametric relationships](https://help.autodesk.com/cloudhelp/2024/ENU/Revit-GetStarted/files/GUID-71F2C8EE-2A90-4076-A6C7-702082566DDF.htm).

**What it did for the set:** almost everything. The change engine plus automatic coordination is the moat in its first form. A plan, a section and a schedule can draw from one model, reducing the manual coordination that separately drafted CAD sheets require. That does not make the whole set incapable of disagreement: [drafting views are not associated with the model](https://help.autodesk.com/cloudhelp/2024/ENU/Revit-DocumentPresent/files/GUID-7B76A2EA-F1F4-484B-AA96-2E2E53B56E49.htm), and manually drawn details still need review.

## Revit 2.0 August 2000

At the time shipping a new version FOUR months after the first one was seen as lunacy. Are these guys nuts? Check out their velocity:

- Massing Study Tools – Simple 3D form modelling
- Building-Scale Detailing – Wall section editing and the ability to do larger scale drawings (DETAILS)
- Family Editor Improvements – custom doors, windows, edit in place
- AccuRender Integration – Raytracing & basic photo-real rendering
- Content Libraries and Catalogs – Predefined components (Doors and Windows) and gearing up for manufacturer catalogs. This enabled architects to place common elements without needing to model them from scratch
- Version 1 was impressive but very buggy. V2 Had a whole lot more stability
- Speed and Model Regeneration, even for larger models
- Revit 2.0 File type (non-backwards compatible); this was a free upgrade to everyone that bought in the first year
- UI: everything was edited in a dialog box, there was no parameters panel with immediate canvas updates yet

All the hallmarks of moving the Technology “Parametric Propagation Engine” towards product market fit are apparent here. They billed $200/ Mo & with no options for annual or perpetual licenses. The early “BIM” took a much larger mindshare from the AEC industry–and there was nothing known as BIM at this time. (BIM, Building Information Modeling, is the coordinated 3D model with data attached to every element; the name came later.)

**What it did for the set:** mostly model features (massing, rendering, content), plus two that matter more than they look. Stability and regeneration speed are what let a team trust the set: a set you can’t regenerate on a large model, or that crashes mid-issue, isn’t change control. And building-scale detailing is the first step toward the big-scale drawings a CD (construction document) set needs.

## Revit 2.1 October 2000

- Bugfixes and Performance Improvements

**What it did for the set:** more of the same trust. Unexciting, and exactly the kind of release a document tool needs.

## Revit 3.0 February 2001

The multi-role demands upon the software that AEC has? The need to allow more than one editor into the machine. (AEC: architecture, engineering and construction.)

- Multi-User Collaboration **in Parallel** (Worksets) – Users could check out a subset of the model to edit it, while others could only view it. Once checking the subset back in, it would engage the parametric propagation engine and get everyone up to speed on changes.
- 4D Construction Phasing (Phases) – Setting existing, demolition, new construction started here. Keeping all phases in one model was unheard of at the time
- Compound Walls, Floor, Roofs – Using multiple materials for how these elements are comprised of physical materials. (So a wall knows it is stud, sheathing and gypsum board, not just two lines.)
- Detail views and Drafting views – 2D specific detailed linework attached to named views–used for call out views and section blowups. This enabled construction documents on par with CAD
- Rendering – added radiosity for more natural lights within spaces. They also leveraged Accurender procedural plants to create geometry without needing to create geometry
- Expanded Library – drag and drop placement of doors, windows, fixtures from family libraries

**What it did for the set:** this is the release where, by this record, the moat closes. Worksets let a whole team edit one model without forking it into copies that drift apart. Phases put existing, demolition and new work in the same model, so the demo plan and the new plan come from one source. Detail and drafting views let the hand-drawn part of a CD set (the details) live in the same file as the model and get referenced from it. Compound assemblies make the wall tags and sections tell the truth. Only rendering is purely a model feature.

Count the dates as recorded here: 1.0 in April 2000, 2.0 in August, 2.1 in October, 3.0 in February 2001. Four releases in ten months, and by the fourth the whole loop was in place: one model, many views, many editors, every phase, details attached, and tools for keeping reissues coordinated.

I will leave this analysis here for now. It shows what is accomplishable by a startup in the early 2000s, and we should all learn from it and respect its velocity. It derailed CAD and moved us towards parametric modeling.

Derailed, not replaced: plenty of the industry still runs on CAD and PDFs (that’s the argument of [BIMposter Syndrome](https://www.testfit.io/harness-architecture/bimposter-syndrome.md)). What Revit moved was the drawing set, from something drafted to something generated. That’s the judgment this history points to: the moat isn’t the model, it’s the reissue. Anyone trying to cross it has to beat Revit at the boring job: propagate modeled changes, review the affected sheets, and document revisions. Revit supports that workflow; it does not guarantee that every change has been clouded. Its [revision workflow](https://help.autodesk.com/cloudhelp/2024/ENU/Revit-GetStarted/files/GUID-C9215297-DAF2-4317-9F14-D9CD75EC9BE6.htm) includes drawing clouds around revised areas and assigning their revision sequence. A tool that generates better buildings but can’t support that work ends up upstream of Revit, not instead of it, which is where TestFit sits today: it fits the building to the site, and the geometry goes through Dynamo (Autodesk’s visual-scripting tool for Revit) into Revit, where the set gets made and reissued.

### Revision history

- **November 3, 2026**: Distinguished parametric coordination from manual detailing and revision review.

End of essay · Clifton Harness · April 14, 2025
