Revit first launched in 2000, everyone was excited about the promise of 4D (time) and 5D (cost) capabilities. Yet after two and a half decades, progress in this area has been surprisingly limited.

The industry still largely treats cost estimation as an afterthought bolted onto the design process, rather than a natively integrated function of the BIM model itself.

Autodesk has published several cost-estimation-related articles and lessons on its website.

1. How to Estimate Costs Based on Revit Model Data – relies on third-party software such as CostX.
2. Revit and Cost Estimating: A Practical Approach – covers parametric schedules and formula parameters.
3. Construction Estimating – introduces Forma Quantity Takeoff software.
4. Using Autodesk Quantity Takeoff and Linked Models in Autodesk Revit to Estimate a Project as the Design Changes – describes exporting a DWF file to QTO and then into Sage Estimating.

Despite these resources, none of them position Revit as the primary estimating platform — they all lean on external software and exported, read-only formats.

In 2018, AIQS released the Australia and New Zealand BIM Practice Guidelines (AIQS & NZIQS, 2018). Eight years later, the guideline remains unrevised, and it too relies on a read-only model approach rather than a native one.

Cost estimation and BQ automation would be far simpler if the industry built directly on Revit as a platform, rather than treating it purely as a design tool. Different stakeholders bring different perceptions to the problem.

Revit modelers won’t model the way a quantity surveyor (QS) wants, because cost estimation isn’t part of their core scope of service. QS professionals, meanwhile, view Revit primarily as a design tool, and Autodesk has not provided clear guidance bridging the two disciplines. The general consensus is that Revit’s geometry and dimensions are merely “by-products” of the BIM model, not a deliberate estimating asset.

As a result, many QS professionals overlook Revit for cost estimation and BQ automation altogether, defaulting instead to on-screen measurement — a method closer to their traditional workflow. Where Revit access isn’t available, QS firms typically request read-only IFC, DWF, or DWFX exports from the design consultant.

There’s also a communication gap: a pure programmer won’t understand QS workflows, and a QS won’t understand programming logic. Compounding this, QS-prepared bills of quantities (BQ) are bound by the Standard Method of Measurement (SMM), and directing modelers to build to SMM standards creates unnecessary workload and pressure during submission deadlines. Even when a model is set up to meet these measurement rules, exported read-only files can’t reflect instant updates when the design changes.

Beyond the lack of auto-updates, there’s a further risk: element duplication. Every Revit element carries a unique Element ID, but exported files like IFC, DWF, and DWFX use a regenerated Globally Unique Identifier (GUID) instead. This is why third-party software such as RIB CostX, Bluebeam, and Buildsoft require duplication sanity checks — a problem native Revit files simply don’t have.

By shifting cost estimation and BQ automation onto the Revit platform itself, all the issues above become irrelevant. Universities, institutions of higher learning, and professional bodies should treat this as a core subject and CPD offering, rather than a peripheral topic left to third-party software vendors.