BIM collaboration without BIM 360

BIM 360 is the default platform for sharing models, but many firms need something simpler and more affordable.

The BIM 360 problem

Autodesk's BIM 360, now rebranded as Autodesk Construction Cloud, has become the assumed standard for BIM collaboration. It offers cloud-hosted model editing, clash detection, document management, and project-wide coordination tools. For large firms running complex projects with dozens of disciplines, it can justify its cost and complexity.

For a significant number of architecture practices, though, BIM 360 is more platform than they need. A ten-person firm working on residential and mid-scale commercial projects does not require cloud-hosted model editing with granular permission systems and enterprise-grade clash detection workflows. What they need is much simpler: a reliable way to share BIM files, keep everyone working from the same version, and let team members and consultants review models without requiring a full Autodesk licence.

The cost of BIM 360 is a real barrier. Per-seat pricing adds up quickly, especially when you include external consultants, structural engineers, and MEP teams who need access. Many of these collaborators only need to view and comment on models, not edit them. Paying for full BIM 360 seats so that a landscape architect can look at the site plan once a fortnight is difficult to justify.

The setup complexity is another friction point. Configuring BIM 360 properly requires dedicated administration: setting up projects, managing permissions, configuring folder structures, and training team members on the platform's workflows. Smaller firms rarely have a dedicated BIM manager, and the principal or senior architect who ends up administering the system has better things to do with their time.

What smaller firms need from BIM collaboration

When you strip away the enterprise features, the core collaboration needs for most BIM workflows are relatively modest. Teams need to store large BIM files in a central location that everyone can access. They need version control so that people are working from the current model, not a copy from last Tuesday. They need a way for people to review and mark up models without opening them in Revit or ArchiCAD. And they need to share files with external consultants without requiring everyone to be on the same software platform.

These are file management and communication problems, not BIM authoring problems. The modelling itself happens in Revit, ArchiCAD, Vectorworks, or whichever authoring tool the firm uses. The collaboration challenge is everything that happens around the model: storing it, sharing it, discussing it, and keeping everyone aligned.

This distinction matters because it opens up a much wider range of solutions. You do not need a BIM-specific platform to solve file management and sharing problems. You need good cloud storage, sensible version handling, and tools for review and markup.

Using Fabric as a BIM collaboration layer

Fabric provides the infrastructure that makes BIM collaboration practical without the overhead of BIM 360. It is important to be clear about what Fabric is and what it is not. Fabric is not a BIM authoring tool. It does not open .rvt files for editing, it does not perform clash detection, and it does not replace Revit, ArchiCAD, or any other modelling application. It is a file management, storage, and sharing platform that solves the access and collaboration problems surrounding BIM files.

With that distinction established, here is how Fabric fits into a BIM collaboration workflow.

Fabric's cloud drive (https://fabric.so/features/your-cloud) provides centralised storage for BIM files without consuming local disk space. BIM models are large, often running into hundreds of megabytes or several gigabytes, and storing multiple project models locally strains laptops and workstations. Fabric streams files on demand, so team members access what they need without downloading entire project archives. The model files live in the cloud, backed up and synced, with one canonical copy that the whole team references.

When a project architect updates the Revit model, the new version is synced to Fabric's cloud drive. Team members who need the file pull the current version. There is no ambiguity about which version is the latest, no emailing of ZIP files, and no "final_FINAL_v3" naming problems. The cloud drive serves as the single source of truth for the project's BIM files.

For review and markup, Fabric's annotations feature (https://fabric.so/features/annotations) allows team members to mark up exported views, screenshots, and documents derived from the BIM model. While you cannot annotate a live .rvt file directly within Fabric, the common review workflow in most firms involves exporting views to PDF or image formats for discussion. Annotations in Fabric support drawing on images and timestamped comments on video and audio, which covers design review meetings, site walk recordings, and exported model views.

Fabric's publish feature (https://fabric.so/features/publish) creates polished, shareable pages that can include project files, images, and documents. When a structural engineer needs to review the architectural model's exported drawings, you publish a page with the relevant files and share the link. The engineer does not need a Fabric account to view the page, and link analytics tell you whether they have looked at it. This replaces the cycle of emailing large attachments, chasing read receipts, and wondering whether the consultant has seen the latest issue.

Working with external consultants

One of the most persistent pain points in BIM collaboration is working with external teams. Structural engineers, MEP consultants, landscape architects, and cost estimators all need access to parts of the model or its outputs, but they rarely use the same software or platforms as the lead architect.

BIM 360 addresses this by bringing everyone onto one platform, but that approach has an obvious scaling problem: every external collaborator needs a licence or an account, the lead firm often bears the cost, and someone has to manage the permissions. For a project with six or seven consultant disciplines, the administrative burden is considerable.

Fabric's approach is lighter. The lead firm stores BIM files and exported documents in the cloud drive. When a consultant needs something, the firm shares it through a published page or a direct link. The consultant can view, download, and comment without needing any particular software beyond a web browser. Annotations let them mark up drawings and images with their feedback, which the design team can review in context.

Connections (https://fabric.so/connections) add another dimension. If consultants work in Google Drive or Dropbox, Fabric can connect to those services, bringing external files into the same searchable space as the firm's own project files. Rather than maintaining separate file ecosystems for each collaborator, everything becomes accessible from one place.

This model works particularly well for the many consultants who only need periodic access. A fire engineer who reviews the project at two or three key stages does not need a permanent seat on a collaboration platform. A shareable link with the relevant documents, plus the ability to annotate and comment, covers their needs with no setup, no training, and no ongoing cost.

The version control question

Version control is central to BIM collaboration, and it is worth addressing how Fabric handles it compared to BIM 360. In BIM 360, version control is deeply integrated with the modelling environment. Multiple users can work on the same central model simultaneously through Revit's worksharing, with BIM 360 managing the central file in the cloud.

Fabric does not replicate this. If your firm relies on Revit worksharing with multiple people modelling simultaneously, you will still need a solution for the central model hosting, whether that is a local Revit Server, BIM 360, or another Revit-compatible cloud hosting service. Fabric is not a replacement for that specific workflow.

Where Fabric helps with version control is at the file level. When the project architect saves a new version of the model to the cloud drive, it replaces the previous version as the current file. Team members who need the exported drawings, schedules, or 3D views can always find the latest versions through Fabric's cloud storage. Semantic search (https://fabric.so/features/search) makes it easy to locate specific deliverables: searching "latest structural coordination drawings" returns the relevant files based on their content, regardless of file names or folder locations.

For many firms, especially smaller ones that do not use Revit worksharing extensively, this file-level version management is sufficient. A single architect working on a model, saving it to the cloud drive, and sharing exported views with the team and consultants covers the majority of collaboration needs without the complexity of a full BIM coordination platform.

What Fabric does not do

Clarity about limitations is important when considering any tool for BIM workflows. Fabric does not open or edit BIM files. You cannot load a .rvt, .ifc, or .pln file into Fabric and make changes to the model. All modelling happens in the authoring tool of your choice.

Fabric does not perform clash detection, model checking, or automated coordination between disciplines. If your workflow requires automated interference checks between architectural and structural models, you will need a dedicated tool for that.

Fabric does not provide real-time co-authoring of BIM models. Multiple people cannot work on the same model simultaneously through Fabric the way they can through BIM 360's integration with Revit.

Fabric does not have offline support. You need an internet connection to access files stored in the cloud drive.

These are meaningful limitations for firms that depend on these specific capabilities. For firms that do not, Fabric covers the collaboration essentials at a fraction of the cost and complexity of BIM 360.

When this approach makes sense

The firms most likely to benefit from using Fabric instead of BIM 360 share some common characteristics. They are typically small to mid-sized, with fewer than fifty people. They use BIM authoring tools but do not rely heavily on cloud-hosted worksharing. Their collaboration needs centre on sharing files, reviewing drawings, and coordinating with external consultants rather than on real-time multi-user modelling.

Sole practitioners and small partnerships find this approach particularly useful. A two-person firm does not need enterprise document management. They need their files backed up, accessible from any device, and easy to share with clients and consultants. Fabric's cloud drive and publish features cover those needs cleanly.

Firms that work with many external consultants also benefit. Rather than negotiating BIM 360 licences and onboarding each consultant onto the platform, they can share work through published pages and annotated documents. The friction of collaboration drops significantly when the consultant's only requirement is a web browser.

Project types matter too. Residential projects, small commercial fit-outs, and renovation work often involve BIM modelling by a single architect or a small team, with consultants contributing through traditional drawing exchange rather than model federation. For these projects, the full BIM 360 stack is unnecessary overhead.

A practical middle ground

The conversation about BIM collaboration tends to polarise between the full-platform approach, represented by BIM 360 and its competitors, and the informal approach of emailing files and using shared network drives. Fabric occupies a practical middle ground.

Your modelling workflow stays the same. You use Revit, ArchiCAD, or whatever authoring tool suits your practice. Your BIM files live in Fabric's cloud drive, backed up and synced, accessible to your team without filling up local storage. When you need to share work with consultants or clients, you publish pages with the relevant documents. When someone needs to mark up a drawing or comment on a design, they use annotations. When you need to find a specific file, semantic search locates it by meaning rather than by file name.

The AI assistant (https://fabric.so/features/ai-assistant) adds a further layer of usefulness. You can ask questions across your project documents in natural language: "What were the structural engineer's comments on the roof design?" or "Find the latest energy modelling report." The assistant searches your files and returns answers with references, saving time that would otherwise go to opening and scanning multiple documents.

Smart organisation (https://fabric.so/features/smart-organization) keeps your project files categorised even when your team's filing discipline lapses. Files are understood by their content, not just their folder placement, so the inevitable drift from your folder template does not result in lost documents.

This is a simpler, less expensive, less administratively demanding way to handle BIM collaboration. It does not cover every use case that BIM 360 addresses, and it does not try to. For the many firms whose needs are more modest than what enterprise platforms assume, it is a workable and welcome alternative.

Frequently asked questions

Is Fabric a replacement for BIM 360?

Fabric replaces the file management, sharing, and review aspects of BIM 360 for firms that do not need cloud-hosted model editing or automated clash detection. It handles storage, version management at the file level, document sharing, and markup. It does not replace BIM 360's integration with Revit for real-time co-authoring or model coordination workflows.

Can Fabric open or edit Revit (.rvt) files?

No. Fabric is not a BIM authoring or editing tool. It stores, organises, and shares BIM files, but all modelling and editing happens in your BIM authoring software. You cannot open a .rvt file within Fabric and make changes to the model.

How does Fabric handle large BIM files?

Fabric's cloud drive (https://fabric.so/features/your-cloud) streams files on demand, so large BIM models do not need to be downloaded in full to local storage. Files are stored centrally in the cloud, backed up and synced, and team members access them as needed. This is particularly useful for firms whose team members work on laptops with limited storage.

Can external consultants access files shared through Fabric?

Yes. Fabric's publish feature (https://fabric.so/features/publish) creates shareable pages that consultants can view in a web browser without needing a Fabric account or any specific software. You can share exported drawings, specifications, and project documents through a link, and link analytics show whether the recipient has viewed the materials.

Does Fabric support IFC file sharing?

Fabric can store and share IFC files through its cloud drive, just as it handles any other file type. Consultants can download IFC files from shared links and open them in their preferred viewer. Fabric does not open or render IFC models within its interface, but it serves as a reliable distribution and storage layer for these files.

How does Fabric compare to BIM 360 on cost?

BIM 360 (Autodesk Construction Cloud) uses per-seat pricing that increases with each team member and external collaborator who needs access. Fabric's pricing model is simpler and typically more affordable for smaller teams, especially when many collaborators only need to view and comment on files rather than edit them. The savings are most significant for firms that would otherwise purchase BIM 360 seats for consultants who only need periodic access.

Can Fabric integrate with Google Drive or Dropbox where consultants store their files?

Yes. Fabric's connections feature (https://fabric.so/connections) integrates with Google Drive, Dropbox, and other cloud storage services. Files stored in these platforms become searchable within Fabric, so you can find consultant deliverables alongside your own project files without requiring everyone to move to a single storage platform.

Does Fabric work offline?

No. Fabric requires an internet connection to access files stored in the cloud drive. If your workflow involves working in locations without reliable internet access, you will need to download files locally before going offline. This is a consideration for site visits or remote project locations.

What file types can Fabric store and share?

Fabric's cloud drive handles any file type, including .rvt, .ifc, .pln, .dwg, .pdf, and all common document and image formats. While Fabric does not open or edit BIM-specific file types, it stores, syncs, and shares them reliably. Semantic search and smart organisation work across supported document types to help you find files by content and meaning.

How does Fabric's semantic search help with BIM project files?

Semantic search (https://fabric.so/features/search) lets you find files by describing what you need in plain language rather than remembering exact file names or folder locations. For BIM projects, this means you can search for "MEP coordination drawings for level 3" or "structural engineer's response to RFI 42" and find relevant documents even if they were filed inconsistently or named differently from what you expected.

Related pages

• https://fabric.so/features/your-cloud

• https://fabric.so/features/search

• https://fabric.so/features/annotations

• https://fabric.so/features/publish

• https://fabric.so/features/ai-assistant

• https://fabric.so/features/smart-organization

• https://fabric.so/connections