Autodesk Construction Cloud: What It Does and What It Does Not Replace

Firms across New York City adopt Autodesk Forma, formerly Autodesk Forma (formerly Autodesk Construction Cloud), expecting it to become their entire project IT infrastructure, then discover critical gaps a few months into deployment. Architecture, engineering, design-build and construction teams find that while Autodesk Forma excels at document control and field coordination during active construction, it does not replace file servers, Revit central model hosting, AutoCAD drawing workflows or backup systems. This reality creates confusion for principals, operations managers and BIM managers who assumed one platform subscription would cover every piece of their technology stack.

Autodesk Forma is a connected set of modules built mainly for managing project documents, RFIs, submittals, issues and field data across the construction phase, not for replacing your firm's general file storage, Revit cloud worksharing plan or independent backup strategy. Understanding where the platform fits and where your existing systems still carry the load determines whether your rollout supports project teams or creates new friction. For firms working in and around New York City, this distinction matters every day your teams coordinate across consultants, subcontractors and job sites.

This post walks through what Forma actually does, how Docs and Build fit into daily work, what stays in Revit and AutoCAD, where Bluebeam and takeoff tools still own the workflow, how the platform compares to alternatives, what security and access responsibilities remain yours, what drives cost, and how to deploy the platform without breaking project habits your teams rely on.

Key Takeaways

• Autodesk Forma manages construction-phase documents and field coordination but does not replace your file server, Revit worksharing setup or backup plan.
• Cost scales with licensed modules, named users and storage, so pricing varies by firm size and which parts of the platform you adopt.
• Successful rollout requires mapping where Forma adds value and where your existing Revit, AutoCAD, Bluebeam and file storage workflows continue.

What Autodesk Construction Cloud Actually Is

Autodesk Forma, formerly Forma, is a connected set of cloud modules built to manage documents, coordinate models, track field issues, process submittals and RFIs, and handle cost and takeoff data across your construction projects. Each module addresses a specific project need, and you license the modules your firm uses rather than buying one monolithic application.

The Modules Inside the Platform: Docs, Build, Cost, Takeoff and Insight

Forma Data Management (formerly Forma Data Management (formerly Autodesk Docs)) holds your project files, including Revit models, AutoCAD drawings, PDFs, Navisworks files, point clouds, and consultant submissions. It acts as a shared document repository where your team and external consultants can access the current drawing set, upload new files, and review markups. Docs supports version control and organizes files by folder structure, discipline, or issue date.

Forma Build (formerly Forma Build (formerly Autodesk Build)) handles field execution and project administration. Your team uses Build to log RFIs, track submittals, manage issues from the jobsite, handle daily reports, and coordinate punch lists. Field superintendents and project managers rely on Build to move documents through review workflows, assign issues to subcontractors, and keep jobsite data tied to the project record.

Forma Takeoff (formerly Forma Takeoff (formerly Autodesk Takeoff)) lets estimators measure quantities directly from PDFs or 2D drawings. You can mark up plan sheets, count fixtures, measure linear runs, and calculate areas without printing or using physical scales. Takeoff exports your counts to spreadsheets or links to estimating tools.

Autodesk Cost manages budgets, change orders, and cost tracking during construction. Project executives use Cost to compare estimates against committed costs, track change order impacts, and forecast where your project stands financially.

Autodesk Insight aggregates data across your projects, giving operations managers dashboard views of RFI turnaround times, submittal backlogs, issue counts, and other metrics. Insight pulls from the other modules, so you see performance trends across your portfolio rather than opening each project individually.

From BIM 360 to Autodesk Construction Cloud: What the Rename Changed

BIM 360 was Autodesk's earlier construction platform, and in 2021 Autodesk renamed and reorganized it into Forma. The platform was renamed again in March 2026 to Autodesk Forma. Projects created under the BIM 360 name moved to the new branding, but the underlying infrastructure, logins, URLs, and integrations stayed the same.

Older projects or legacy documentation may still reference BIM 360 Docs, BIM 360 Build, or BIM 360 Field. If your firm has projects that started under the BIM 360 label, check Autodesk's product pages for current module names and whether migration or account updates are needed.

BIM Collaborate and Forma Design Collaboration (formerly BIM Collaborate Pro) handle Revit cloud worksharing, which lets multiple users edit a central model at the same time. Forma Design Collaboration became Forma Design Collaboration under the March 2026 rename. This capability is separate from the document and field modules, so licensing Forma Data Management or Forma Build does not automatically give you cloud-hosted central models. Your firm still needs a plan for where Revit central models live, whether that is on your own server, BIM 360 Team (now discontinued for new projects), or BIM Collaborate.

Who on a Project Team Touches Which Module

Principals and operations managers typically use Insight to review project health, Cost to monitor budgets and change orders, and Data Management to access final drawing sets or major submittal packages. You might not log into Build daily, but you pull reports and dashboards to track firm-wide performance.

BIM managers work in Data Management to organize model folders, set permissions for consultants, coordinate Navisworks clash detection files, and troubleshoot version control. If your firm uses BIM Collaborate for Revit worksharing, you also manage central model permissions and sync settings.

Project managers and architects rely on Build for RFIs, submittals, and issue tracking. You assign questions to consultants, review shop drawings, and move items through approval workflows. Data Management holds your current AutoCAD sheets, specifications, and contract documents, and you upload revised drawings as the set evolves.

Field superintendents and MEP coordinators use Build on tablets to log jobsite issues, photograph conditions, assign tasks to subcontractors, and update daily reports. Issues tagged in the field sync back to the office, so your project team sees what is happening onsite without waiting for email updates.

Estimators and cost managers work in Takeoff to measure quantities from bid sets and Cost to build budgets, then track actual spend as the project progresses. Takeoff connects to Data Management so you are measuring from the same PDFs your design team uploaded.

Subcontractors and consultants receive invite links to specific projects and access only the folders, submittals, or RFIs assigned to them. They upload shop drawings to Build, respond to RFIs, and download the latest drawing set from Data Management without needing full platform licenses.

How Project Teams Use Docs, Build and BIM Collaborate Day to Day

Teams use Autodesk Forma (formerly Forma) to route drawings and specifications between consultants, manage construction RFIs and submittals without email threads, and review coordinated models in a browser without needing Revit or Navisworks installed on every device.

Document Control and Transmittals Across Design and Field

Forma Data Management (formerly Forma Data Management) provides a central location for version-controlled drawings, specifications and project correspondence that field teams and external consultants can access from tablets or phones. You upload AutoCAD drawing sets, PDFs and Revit exports into structured folder templates, apply permission rules by discipline or role, and send formal transmittals that log who received which revision on what date.

The platform tracks every file revision and markup, so when a structural consultant publishes an updated foundation plan, your team sees the change notification and can compare the new sheet against the prior version side by side. Transmittals move out to subcontractors and owners with a full audit trail, reducing the risk that someone builds from an outdated drawing.

Many firms continue to use Bluebeam for detailed markup sessions and final QA before a transmittal goes out, then save the marked set back to Forma Data Management as the record copy. That workflow keeps the familiar markup tools your team already uses while giving the platform responsibility for distribution and version history.

RFIs, Submittals and Issues in One Place

Forma Build routes requests for information, submittal packages and field issues through structured workflows that assign responsibility, set due dates and attach the relevant drawing or model view. When a foreman finds a conflict between the architectural plan and the MEP coordination model, he creates an issue directly from his phone, pins it to the exact sheet location and assigns it to the project manager.

Common workflows you can route through Forma Build:

• RFIs with attachments, assignees and response deadlines
• Submittals for shop drawings, product data and samples, routed to the architect or engineer for review
• Issues tied to a sheet coordinate or model element, tracked until closed
• Field observations logged with photos and tagged by trade or location

The platform does not replace the informal coordination that still happens over text, in the trailer or through Bluebeam sessions. It handles the formal log, the approvals and the record that each request was answered and by whom.

Model Coordination and Viewing Without Native Design Software

Forma Design Collaboration (now Forma Design Collaboration) hosts federated models from multiple disciplines so your team can review coordination in a browser without opening Revit or Navisworks. You load architectural, structural, MEP and civil models into a shared view, run clash detection and assign coordination issues to the responsible party.

Field staff and subcontractors view the coordinated model from tablets on site, measure dimensions and check elevations without needing design software licenses. The viewer supports section cuts, measurements and element properties, so a mechanical contractor can verify a duct run against the steel framing before fabrication.

Forma Design Collaboration does not host your live Revit central models for worksharing. Your central models still sync to BIM 360 Design, Autodesk Drive or a local server depending on your license and network setup, and you publish coordinated exports to the platform for review and field use.

What Stays on Your File Server, SharePoint or Egnyte Instead

Autodesk Forma, formerly Forma, manages documents during the construction phase of a project, but it does not replace the systems that store your firm's administrative records, financial data, HR files, templates, standards libraries or non-project content. You still need a file server, SharePoint or Egnyte for those assets.

Project Files vs Firm Files: Where the Line Falls

Forma handles project-specific construction documents: RFIs, submittals, issues, markups, drawings shared with contractors and consultants, and other files that belong to one active job. Files that support the firm rather than a single project belong somewhere else.

Your firm-wide CAD standards, Revit family libraries, title block templates, specification masters and quality control checklists live on your file server, SharePoint or Egnyte. These assets get versioned, updated and used across all projects, and they need governance, access control and long-term retention beyond what a single project requires.

Marketing materials, proposals, contract templates and project pursuit files also stay outside the platform. So do employee handbooks, HR policies, insurance certificates and office operations documents. Forma does not organize content by department or firm function, so it is the wrong place for these records.

Why General Document Management Still Needs Its Own Home

You need a central location for internal documentation that supports the business, not just construction delivery. SharePoint and Egnyte offer folder hierarchies, permissions by department, retention policies and integrations with Microsoft 365 or your accounting system. Forma does not.

Egnyte provides global file locking for AutoCAD drawings and other non-Office file types, which SharePoint does not natively support. If your firm stores DWG files centrally and needs to prevent overwrite conflicts when two users open the same file, Egnyte or a file server with proper locking handles that workflow better than SharePoint or OneDrive.

Many firms use SharePoint for internal collaboration, project pursuit, client relationship records and proposal libraries while keeping Forma for construction-phase documents only. The two systems serve different stages and different audiences, and forcing firm-wide files into a project-centric platform creates confusion and governance problems.

Administrative, Financial and HR Records Stay Outside the Platform

Financial records, including invoices, contracts, insurance policies and tax documents, require retention periods and access controls that align with accounting rules and audit requirements. Your file server or a dedicated financial system handles that, not Forma.

HR records such as employee files, performance reviews, benefits documentation and payroll data belong in a secure, role-restricted location. The NY SHIELD Act may apply to your firm if you maintain personal data, so confirm retention and access requirements with your counsel. Forma does not provide the departmental structure or compliance controls these files require.

Client contracts, professional liability policies, certificates of insurance and firm registrations need long-term retention and fast retrieval during audits or claims. Store them where your administrative team controls access and where they remain available long after a project closes.

What Stays in Revit, AutoCAD and Your Modeling Workflow

Autodesk Forma (formerly Forma) hosts models for coordination and review, but your live Revit central models and AutoCAD drawing sets continue to sync and save through separate services. Point clouds and other large reference files also live outside the platform modules and feed into your design workflow from their own storage locations.

Revit Central Models and Cloud Worksharing Are a Separate Product

Revit cloud worksharing is a distinct capability from Forma's document and field management modules. When you work in a cloud workshared Revit model, your central file is hosted through BIM Collaborate or Forma Design Collaboration (now Forma Design Collaboration), not through Forma Data Management or Forma Build.

Your team syncs to the central model just as they would with a server-based workshared file. The central model does not live inside the project folder structure you see in Forma Data Management. Instead, it exists in its own cloud location tied to the worksharing service.

You can upload snapshots of your Revit model to Forma Data Management for viewing, markup and model coordination with consultants and trades. But those snapshots are not the live central model. Changes to the workshared model happen inside Revit, not through the platform's document viewer.

If your firm already uses Forma Design Collaboration for worksharing, that subscription now falls under the Forma Design Collaboration name. Your login and project access remain unchanged. You still need a clear plan for how central models are hosted, who has sync rights, and where backups are stored.

AutoCAD Drawings Still Live and Sync Outside the Platform

AutoCAD drawings saved to cloud storage through Autodesk's own AutoCAD web and mobile features do not automatically sync with Forma Data Management. You manage your DWG files separately from the document control workflows inside Forma.

Many firms continue to organize AutoCAD drawing sets on a file server, SharePoint or dedicated CAD management system. When you need to share a drawing set with consultants or a contractor, you upload a PDF or DWG snapshot to Forma Data Management. The live drawing file remains wherever your CAD workflow keeps it.

Common workflow:

• Edit and save AutoCAD drawings in their own storage location
• Publish PDF sets for distribution and markup
• Upload PDFs to Forma Data Management for review and approval
• Sync final approved PDFs back to the drawing set folder

This separation keeps your source files under version control in your existing CAD environment while still giving project teams access to current sheets through the platform.

Point Clouds and Other Large Reference Files

Point clouds captured from reality capture scans are typically too large to store efficiently inside Forma Data Management. Most firms host point cloud files on local storage or a dedicated cloud service and link them into Revit, AutoCAD or other modeling software as external references.

When you need to coordinate existing conditions with a contractor or consultant, you can use Forma's model coordination viewer to overlay design models against a lightweight reality mesh. But the full-resolution point cloud data stays outside the platform and feeds into your design workflow directly.

Large linked models from structural or MEP consultants often follow the same pattern. You coordinate through lightweight versions uploaded to Forma while the full federated model lives in your BIM coordination environment.

Where Bluebeam, Takeoff and Field Tools Still Do the Work

Autodesk Forma includes its own markup and quantity tools, but many firms continue running detailed PDF markup through Bluebeam, estimating through standalone takeoff software, and field reporting through purpose-built apps they have already deployed. These tools handle workflows that need deeper markup collaboration, faster PDF turnaround, or mobile field capture the platform does not fully replace.

Bluebeam Still Handles the Heavy Markup for Many Firms

Bluebeam markup remains the standard for drawing coordination, RFI preparation, and consultant review at firms where speed and PDF-focused collaboration matter most. Forma Data Management stores and versions PDFs, and Forma Build offers basic markup and annotation, but Bluebeam Studio Sessions deliver real-time collaborative markup across multiple team members working in the same drawing set simultaneously.

Firms working with consultants and subcontractors outside your organization often find that Bluebeam is already part of the workflow before drawings reach Forma. The ARKANCE connector lets you move PDFs from Forma Data Management or Forma Build into Bluebeam Studio, mark them up in a Session, then save the updated set back into Forma without breaking version control.

Your team still needs to decide where final, signed AutoCAD drawing sets live and how markups flow between the field, the design team, and the owner. Bluebeam handles that PDF-heavy coordination layer, while Forma manages the broader document log, RFI tracking, and issue resolution around those same files.

Takeoff and Estimating Tools Have Their Own Place

Takeoff tools built into Forma Takeoff work well for general contractors already licensing the full platform and working from Revit models or consistent 2D sheets. The module supports both model-based quantities and PDF-based linear and area takeoffs in a single cloud interface.

Estimating workflows at many firms, however, still depend on standalone software tied to cost databases, historical project records, and subcontractor pricing templates that sit outside Forma. Your estimators may pull quantity data from Forma Takeoff but complete the bid assembly, unit cost assignment, and subcontractor comparison in dedicated estimating software that your preconstruction team has used for years.

Forma Takeoff fits large firms running end-to-end Autodesk workflows where quantities feed directly into Forma Cost for budget tracking. Smaller firms or those prioritizing PDF markup speed and lower upfront cost often stick with Bluebeam for takeoffs because the tool is already licensed, faster for their team, and does not require learning a new cloud interface mid-bid cycle.

Field Reporting Tools Contractors Already Run

Field reporting apps your superintendents and foremen carry on tablets often predate your adoption of Forma and connect to subcontractor management, daily logs, and safety documentation workflows the platform does not cover. Forma Build tracks issues, punch lists, and photos from the job site, but it does not replace purpose-built apps for time tracking, equipment logs, or detailed safety checklists required by your insurer or your own internal procedures.

Your field teams need reliable offline access when connectivity drops on a job site, and many standalone field apps sync locally then push updates when the tablet reconnects. Forma Build requires a live connection for most functions, so firms working in basements, remote sites, or areas with intermittent service continue running separate field tools alongside the platform.

Integration between Forma Build and your existing field app depends on whether the vendor offers a connector or API access. You should confirm current integration status with both Autodesk and your field software vendor before assuming data will flow automatically between systems.

Autodesk Construction Cloud Compared to Procore and Other Platforms

Autodesk Forma, formerly Forma, and Procore both manage construction phase workflows, but they handle design integration and project execution differently. Many firms license both because their strengths sit in different parts of the construction timeline.

Where the Two Platforms Overlap

Both platforms manage RFIs, submittals, issues, daily logs and drawings during construction. You coordinate field teams, track punch lists and maintain a single source of truth for project data. Both connect general contractors, subcontractors and consultants outside your firm.

The overlap is real enough that you will route similar workflows through either platform. An issue raised by a field team on a job site in Long Island City or a submittal from a subcontractor moves through similar approval chains. Both platforms store PDFs of drawing sets and markups.

The difference appears when Revit central models and live design data enter the picture. Forma Build pulls directly from Forma Design Collaboration and hosts live model references, so your BIM manager can trace an RFI back to the model geometry that triggered it. Procore handles design files as uploaded references rather than as connected models, which is fine when your workflow ends at PDF drawing sets but limiting when you need to keep model data and field data in sync.

Why Some Firms End Up Running Both

Design teams already on Revit and the AEC Collection often license Forma because the integration with their existing Autodesk tools is direct. Your Revit central models sync through Forma Design Collaboration, point clouds and Navisworks clash reports flow into Forma Docs, and the model viewer inside Forma Build shows current geometry without re-exporting.

Meanwhile, your project executives and field teams may prefer Procore because it leads in project execution workflows. Procore's scheduling integration, cost tracking and subcontractor onboarding are built for general contractors running multiple trades on tight timelines. If your firm already trains subcontractors on Procore for daily reports and timecards, switching platforms mid-project creates friction.

So you license both. Forma manages design coordination and model-based submittals during preconstruction, and Procore takes over once boots are on the ground. The handoff is manual, usually a one-time export of drawings and RFI history, but it keeps each team in the tool they know.

Maintaining two platforms doubles training, complicates reporting and splits your single source of truth. But for firms where design and construction sit in separate departments with different tools already in place, the cost of forcing one platform onto the other team often exceeds the cost of running both.

Choosing Without Rebuilding Your Whole Stack

Your existing software licenses shape the decision more than feature lists do. If you already subscribe to the AEC Collection, you have access to Forma Design Collaboration, and adding Forma Build or Forma Docs extends what you already own rather than introducing a new vendor relationship.

If your general contractor partners or your field teams already use Procore across every project, joining them on the same platform reduces coordination overhead. Subcontractors submit daily logs in one place, and your project managers do not translate data between systems.

Neither platform replaces Bluebeam for markup-heavy coordination. You still run detailed PDF markups and Studio Sessions in Bluebeam, then upload the final marked set to Forma Docs or Procore as the record copy. Neither platform replaces your file server or SharePoint for firm-wide administrative and HR records, so budget for both project management software and general storage.

Most mid-sized firms settle on one platform as the primary system of record and connect the other tools through integrations or manual uploads. Your BIM manager and operations team should map the actual handoffs in your current projects before committing to either platform.

The Security, Backup and Access Gaps the Platform Leaves to You

Autodesk Forma, formerly Forma, handles data security and encryption through Amazon Web Services and earns SOC 2 and ISO certifications for the infrastructure it operates. Those controls do not extend to making an independent backup of your central models, marking former employees as inactive when they leave, or proving to a cyber insurer that you can recover a Revit file set from last week.

Backup Still Needs to Be Your Own Plan

Forma replicates data across multiple AWS availability zones to keep the platform running if a server fails. That infrastructure resilience is not the same as versioned backups you control or can restore without opening a support ticket.

If a project manager accidentally deletes an entire folder of AutoCAD sheets from Forma Data Management, or a consultant overwrites a Bluebeam markup set during a live session, your ability to recover that file depends on whether Forma's own versioning preserved it and whether you can locate the right version in the folder history. There is no guarantee that every action is reversible through the platform interface.

Most cyber insurers ask whether you back up project data independently and how often. Relying entirely on the SaaS platform's own availability means you cannot answer that question the way the policy expects. A complete backup plan includes regular snapshots of central models from Forma Design Collaboration, drawing sets from Forma Data Management, and any critical takeoff or cost data from Forma Takeoff, stored in a location you control and can restore from without contacting Autodesk support.

Access Control and Offboarding Stay a Firm Responsibility

Forma includes role-based permissions that let you assign view, edit or admin rights to each user on a project. The platform does not automatically revoke access when someone leaves your firm, notify you of stale accounts, or audit who still has admin rights to a project folder six months after substantial completion.

Your firm owns these steps:

• Marking departing employees inactive in your Autodesk account
• Removing former staff from Forma projects where they hold admin or contributor roles
• Reviewing consultant and subcontractor access at project milestones or when contracts end
• Auditing who retains links to shared Revit models or shared folder URLs after their role concludes

A BIM manager leaving with admin access to every central model or a former project engineer still holding contributor rights to a live submittal log creates exposure that Forma's platform security cannot close. Access control is a repeatable internal process, not a feature you license.

What Cyber Insurers Expect Beyond the Platform Itself

Cyber insurance applications commonly ask how you back up data, how often you test restores, and what happens when an employee leaves. Answering "we use Forma" addresses where files live during a project, not whether you can prove a recovery point from last Tuesday or demonstrate that offboarding follows a checklist.

Insurers want evidence of independent backup schedules, documented offboarding workflows, and regular confirmation that both still work. Many carriers now require multi-factor authentication across all systems that store client or project data, and they expect you to enforce that requirement rather than assume the platform does it by default.

Forma supports multi-factor authentication, but turning it on and requiring it for every user in your account is an admin decision you make in the Autodesk Account portal. If your policy requires MFA and you have not enabled it, the gap is yours to close.

What Autodesk Forma Costs and What Drives the Price

Forma pricing moves based on how many named users you license, which modules your team needs, and how much storage and connected products your projects require. These variables combine differently for every firm, which is why the platform is sold as a quote rather than a fixed shelf price.

License Types and How Seats Are Counted

Forma uses named user licenses, meaning each person who logs in needs their own seat. You cannot share a single login across multiple people or rotate credentials between shifts. This matters when you need to give field staff, subcontractors or external consultants access to Forma Build or Docs.

If your field superintendent pulls up a punch list on an iPad, that person counts as a user. If your mechanical engineer at a consulting firm needs to review a coordinated model or download a drawing set, that firm needs its own seat or you need to provision one under your account. The count adds up quickly when you include everyone who touches project data, not just internal staff at desks.

Some modules, including Forma Data Management, are sold per user per year. Others, like certain preconstruction or cost modules, may be priced per project or bundled at the account level, but the named user model still applies to anyone logging in to access documents, issues or RFIs.

Storage, Modules and Add-ons That Change the Bill

Storage pricing scales with the volume of files you host in Forma. Point clouds from a job site survey, large Revit models pushed up as reference files, and years of archived drawings all count toward your total. Autodesk offers a base storage allocation with most plans, and additional storage is purchased separately when you exceed that threshold.

The modules you activate drive the largest cost variation. Forma Data Management handles document control and may be enough for firms that only need a central repository and basic markups. Forma Build adds RFIs, submittals, daily logs, quality and safety tracking. Forma Takeoff and Forma Estimate add preconstruction functions, while Forma Design Collaboration replaces older Forma Design Collaboration functionality for coordinated Revit workflows.

If you need only document management for a small project, your cost stays lower. If you run full project management, cost tracking, takeoff and model coordination across multiple active jobs, you license more modules and the subscription cost rises. Firms often start with a core set and add modules as project types or client requirements expand.

Where Licensing Mistakes Add Up

The most common mistake is licensing too many users at the outset or too few as the project grows. If you provision seats for everyone who might someday need access, you pay for unused licenses. If you provision too few, field staff and trade partners lose access when they need to close out punch items or upload photos, and you scramble to add seats mid-project.

Another frequent issue is mixing up what Forma includes versus what still requires a separate Autodesk subscription. Forma does not include Revit, AutoCAD or Navisworks licenses. You still need those seats separately, typically through the AEC Collection. Firms that assume Forma replaces the Collection end up with access to the platform but no way to author the models or drawings being coordinated.

Storage overruns catch firms by surprise when large datasets accumulate across projects. A single laser scan can exceed several gigabytes, and firms running multiple scans per month hit storage caps faster than expected. Monitor usage regularly and adjust your storage allocation before Autodesk automatically adds capacity and bills for it, so you control when the increase happens rather than reacting to an invoice.

Rolling Out the Platform Without Breaking Existing Project Habits

Introducing Autodesk Forma, formerly Forma, means changing how your firm shares files, tracks issues and manages submittals while active jobs are still running on email attachments and network drives. The most successful rollouts migrate existing project history intact, train teams on workflows that mirror what they already do, and lock down folder structure and permissions before the first drawing goes live.

Migrating From BIM 360 or a File Server Without Losing History

If your firm used BIM 360, project data can move into Forma without losing version history, metadata or permission assignments. Autodesk provides migration paths that preserve folder structure and file relationships, which matters when a consultant needs to reference a submittal chain or a change order links back to a specific RFI. The process works best when you consolidate scattered BIM 360 projects into a single Forma environment rather than replicating the same fragmented setup.

For firms moving from a file server or SharePoint, the transition requires more planning. Forma Docs accepts bulk uploads, but it does not carry over Windows file permissions or nested folder logic automatically. You need to map your current structure to Forma's project-level permissions and decide which historical projects warrant full migration versus archived reference storage. Most firms move active jobs and recent completed work first, leaving older archives on the file server with read-only access until they close out.

Email attachments and shared drive links do not transfer into Forma as trackable references, so plan for a cutover date per project where all new files go into the platform and all requests for current drawings point there.

Training Project Teams Used to Email and Shared Drives

Your project managers and coordinators are used to emailing PDFs, saving AutoCAD files to a folder and opening Revit models from a mapped drive. Forma training needs to show them the equivalent workflow, not a feature tour. Start with document uploads, folder navigation and external sharing links, because those replace the habits they use daily.

Run a live pilot project through Forma Build's RFI and submittal modules before rolling out firmwide. Pick a job with cooperative team members and enough activity to surface real questions. Let the project team test issue tracking, markup review and mobile field access on actual work rather than sample data.

Consultants and subcontractors outside your firm do not need Forma licenses to view shared files or respond to RFIs, but they do need clear instructions on how to access links and upload responses. Prepare a one-page guide with screenshots for external collaborators, because they are working on ten other projects and will not sit through your internal training session.

Setting Up Project Structure Before the First Job Goes In

Forma organizes work by project, and each project needs a folder structure and permission matrix defined before anyone uploads files. Most firms start with a template that mirrors CSI divisions for submittals and a drawing set structure that separates disciplines, because project teams already know where to look. Lock this template down at the account level so new projects inherit consistent organization rather than each PM inventing their own.

Permissions control who sees cost data, who can approve submittals and who has access to field reports. Define roles by discipline and responsibility: project executives see everything, field staff see only their trade's issues and models, and external consultants see only folders shared explicitly with them. Forma lets you assign permissions at the project and folder level, but simpler is better for adoption.

Plan where Revit central models will live separately from Forma, because Forma Docs stores published files and PDFs but does not host live worksharing models. BIM Collaborate handles cloud worksharing if your firm licenses it, or you continue hosting central models on a local server and publishing coordination sets into Forma for distribution.

Getting the Platform and Your IT Working Together

Forma deployment touches your network, your devices and the way project data flows between field teams and your office, which means platform administration belongs in the same hands that manage the rest of your firm's infrastructure. Treating it as a BIM task alone leaves critical gaps in access control, device policy and integration with the tools your accounting and operations teams rely on.

Why Platform Administration Is an IT Responsibility, Not Just a BIM Manager Task

Your BIM manager understands project structure, model coordination and who needs access to which drawings. That expertise does not extend to Active Directory synchronization, firewall rules for cloud traffic or enforcing device compliance across iPads issued to field teams. Forma administration requires both sides.

User provisioning is a clear example. When someone joins or leaves the firm, IT already manages their email, file server permissions and application licenses. Adding Forma to that workflow keeps the process consistent and reduces the chance that a departed employee retains access to live projects.

Network segmentation and device management also fall outside typical BIM workflows. If your field teams use tablets running Forma Build on job sites, IT needs to confirm those devices meet your security baseline, can connect through your VPN when required, and sync properly with models and documents stored in Forma Data Management. A BIM manager can set folder permissions inside the platform but cannot configure the network policy that governs how those devices reach it.

Shared responsibility works best: BIM sets project templates, folder structures and permissions within Forma, while IT handles authentication, device enrollment, integration with your file server or ERP, and monitoring platform performance as part of your broader operations technology stack.

Connecting the Platform to Your Network and Devices

Forma runs in the cloud, but your team still accesses it from your office network, job site trailers and personal devices in the field. IT needs to confirm that your firewall allows outbound traffic to Autodesk endpoints, that your VPN supports the bandwidth consultants and subcontractors need when they pull Revit models or large PDF sets from Forma Docs, and that mobile device management policies cover tablets used for daily logs and issue tracking.

Integration points add another layer. If your accounting team pulls cost data from Forma into an ERP or your project managers push schedules from Procore into Forma Build, IT configures those connections using APIs or middleware platforms. Forma supports integrations with common construction accounting and SaaS tools, but someone still needs to authenticate each connection, map data fields and monitor sync errors.

Device policy matters on job sites. Superintendents and foremen access Forma Build on iPads and Android tablets in the field, often over cellular connections. IT should enforce passcode requirements, remote wipe capability and app whitelisting so a lost device does not expose project data or allow unauthorized changes to submittals and RFIs.

Signs Your Firm Needs Outside Help Managing It

If your internal IT staff consists of one person who also handles help desk tickets, printer repairs and vendor renewals, adding Forma administration to that workload often creates a bottleneck. Projects stall when new users wait days for access, integrations break without anyone noticing, or field teams cannot connect because a firewall rule was never updated.

Another warning sign is when your BIM manager spends more time troubleshooting login issues, device sync problems and integration errors than coordinating models. That work belongs with someone who manages infrastructure daily, not as a side task squeezed between clash detection and consultant coordination.

Firms working on Department of Defense projects face an additional layer. DFARS applies to defense contractors, and CMMC sets cybersecurity standards for those firms. If either applies to your work, confirm your platform administration aligns with those requirements, which typically means engaging IT support with experience in that area.

If you lack in-house capacity to manage authentication, device policy, API integrations and network configuration for Forma alongside your other systems, outside IT support focused on operations technology for AEC firms fills that gap without requiring a new hire.

Autodesk renamed the platform to Autodesk Forma in March 2026, and pricing depends on which modules you license and how many users need access. The platform serves all disciplines across the construction phase, not just general contractors.