On March 30, 2026, Autodesk Construction Cloud stopped existing. Not the platform — the name.
Everything moved under Autodesk Forma. Autodesk Build became Forma Build. Autodesk Docs became Forma Data Management. Autodesk Takeoff became Forma Takeoff. BIM Collaborate Pro became Forma Design Collaboration. Autodesk Estimate became Forma Estimate. The product that used to be called Forma — the early-stage site design tool Autodesk built out of the Spacemaker acquisition — is now Forma Site Design.
Autodesk's own framing is that this is "a brand and experience evolution, not a platform replacement." That is accurate and worth taking at face value. No data migration. Same URLs. Same logins. Same APIs. Same licensing. If you had a Power BI report pulling from the Data Connector on a Friday, it still worked on the Monday.
So if nothing broke, why does this matter?
Because your paperwork is now wrong
Go open your BIM Execution Plan. Search it for "Autodesk Construction Cloud." Then search your subcontract templates, your CDE clauses, your division 01 spec sections, your ITPs, and the technology exhibit you attach to every trade agreement.
Every one of those hits is now a reference to a product that Autodesk does not sell under that name.
In practice, nobody is going to void a subcontract over a retired brand name. But contract documents get read by people who weren't in the room, sometimes years later, sometimes by a claims consultant. A specification that mandates "the Contractor shall maintain all project documentation in Autodesk Construction Cloud (ACC)" is a specification that names a thing you cannot go buy. When a sub asks which platform they are contractually required to use, "the one that used to be called that" is a worse answer than it sounds.
This is the same category of problem as a spec that still calls for a discontinued product line. It doesn't break anything on day one. It creates ambiguity that costs somebody an RFI, or an argument, later.
What to actually do about it
There is a right way and a wrong way to fix this, and the wrong way is a global find-and-replace.
Name both, for a while. In contract documents, write it as "Autodesk Forma (formerly Autodesk Construction Cloud)" on first use, then Forma thereafter. Everyone in the field has said ACC for years and will keep saying it through at least the next project cycle. Your documents need to be findable by people searching either term.
Fix the module names carefully. This is where people are going to get it wrong. Autodesk renamed the products. It did not rename every module inside them. Cost Management is still Cost Management. Model Coordination is still Model Coordination. Insights is still Insights. Assets is still Assets. If your BEP says "Model Coordination," leave it alone.
Know what isn't a product. "Forma Construction Cloud" is not a thing. Neither is "Autodesk Forma Build Cloud." I have already seen both in the wild, in documentation written since March. If you invent a hybrid name in a contract document, you have made the ambiguity worse, not better.
Update the admin vocabulary too. Accounts are now Hubs. Account admins are Hub Admins. If you have written onboarding procedures, permission matrices, or training material that walks someone through "Account Admin," the person following it in the UI will not find that word.
The part worth paying attention to
The rename tells you something about Autodesk's direction that the press release does not say outright.
Before March, Autodesk had two things called different names that did different jobs: Forma, an early-design tool, and Construction Cloud, a construction delivery platform. Now both sit under one noun. Autodesk has also put Forma Building Design into general availability for AEC Collection subscribers, and has a Revit "Connected Client" in tech preview that moves data from Forma into Revit without manual file exchange.
Read together, that is a company organizing its entire product line around one continuous data spine from site design through construction operations. Whether it delivers is a separate question — the Revit Connected Client is a tech preview, not a deployment plan, and tech preview is where a lot of promising Autodesk features go to sit for a couple of years.
But the naming is a statement of intent, and intent is worth knowing when you're deciding what to standardize on for the next five years.
One more thing, for the smaller contractors
Alongside the rebrand, Autodesk introduced Essentials tiers — Forma Build Essentials with punch lists, photo markup and daily logs, and Forma Data Management Essentials now bundled into AutoCAD, Revit and Civil 3D subscriptions.
If you looked at Build two years ago, decided it was priced for a general contractor three times your size, and walked away, the arithmetic has changed. That is worth a fresh look before your next renewal.
The honest summary: nothing broke, and you have time. But "we'll update the templates eventually" is how a document ends up going out to bid in 2028 mandating a platform nobody sells. Put an hour on the calendar, run the search, and fix the language while it's a housekeeping task instead of a question in a claim.
If you want a hand auditing your BEP and contract exhibits against current Autodesk naming, that's a short conversation and I'm happy to have it.
Need a hand with this?
Campbell CTS does Autodesk Forma implementation, BIM coordination, reality capture and training for contractors. Free technology assessment — no pitch, no pressure.
Start a Conversation