If you have ever spent hours manually dragging and aligning floor plans or details across dozens of sheets to ensure they sit in the exact same spot, you know how tedious that process can be. This new feature can automate that alignment.

In this post, you will learn:

• What View to Sheet Positioning is.
• How to configure and use the feature.
• Why Scope Boxes are critical for this workflow.

About View to Sheet Positioning

In previous Revit versions, we relied on Guide Grids or third-party add-ins to align views on different sheets. While Guide Grids help, they still require manual snapping for every single view.

The View to Sheet Positioning feature in Revit 2026 allows you to define a “Master View” position. Once established, you can instantly align other views on different sheets to that same coordinate. This ensures that when you flip through a PDF set, the building doesn’t “jump” around on the page.

Step-by-Step: Configuring and Using the Feature

The workflow is straightforward and integrated into the Sheet view properties. Here is how you can use it:

Place your Master View: Open a sheet and place your primary view (e.g., Level 1 Floor Plan). Position it exactly where you want it on the title block. Select the view then save the position by clicking the button on the Modify tab> Positioning & View panel.

Now when you need to align another view on a different sheet, you can refer the position with this saved position. With the view selected on the sheet, look at the Properties Palette. You will see a new parameter for Sheet Position. (Note: You can also access it on the ribbon> contextual tab.)

Select a Saved Position as the reference, and Revit will move the viewport to the matching coordinates automatically.

Pro Tip: You can select multiple viewports across different sheets in the Project Browser (1) and apply the positioning (2) settings in bulk to save even more time.

You can see how it works here

Importance of Scope Boxes

While you can align views using their centers, this is often unreliable if the view boundary varies between floors. This is where Scope Boxes become essential: by assigning a Scope Box to your views, you define a fixed boundary. If your Scope Box is correctly positioned, the View to Sheet Positioning tool will work perfectly every time, regardless of how much the building’s footprint variations between levels.

If you haven’t started using Scope Boxes for your project setup yet, this feature is the perfect reason to start.

Summary

The saved position in Revit 2026 is a small but powerful update for Revit users. It removes the guesswork and reduce time from sheet production. By combining this feature with a well-placed Scope Box, you can ensure your drawing sets are professional, consistent, and much faster to produce.

What do you think about this new feature? Will this replace the way you use Guide Grids, or do you prefer the old-school manual alignment? Share your thoughts in the comments!

Here is the breakdown of the new names:

It’s More Than Just a Name

At first glance, many comments saying this as “just another marketing rebrand.” But if you look back at the vision Autodesk shared years ago (and some great analysis by Martin Day in AEC Magazine), the goal has always been to create “one platform to rule them all.”

By bringing Construction Cloud under the Forma umbrella, Autodesk is signaling that the wall between their different solutions are coming down. They want a unified industry cloud where data flows from and to different solutions seamlessly. While this can be challenging, it is a good plan.

Autodesk has different platforms. Some software runs on top of AutoCAD, but Autodesk also has Revit, Navisworks, etc. Converting data between them can be tedious and time consuming. If Autodesk can’t make all of their solutions running on one platform, why not having a data platform to manage all the data? Like now we already can link topography from Civil 3D in Revit and open a saved view in BIM Collaborate from Navisworks. I expect we can see more software can consume data from Forma in the near future.

Is the Naming Getting Confusing?

While I understand the logic, grouping everything under one “Industry Cloud” brand, I can’t help but feel the naming is getting a bit confusing.

For years, we’ve spent time explaining to clients and teams BIM360 rebranding to Autodesk Construction Cloud. Now, we have to re-train everyone to use “Forma” as a prefix for everything. Autodesk Forma used to be the conceptual site designer, but now the whole Autodesk Construction Cloud is Autodesk Forma. When someone says, “Is it in Forma?” are they talking about the early-stage design tool, or the common data environment? And will the desktop software will have new names too?

We’ll likely be spending a lot of time clarifying which “Forma” we’re talking about in meetings.

The Concept is Not New

This concept isn’t actually new. If you look at the manufacturing industry, companies like Dassault Systèmes have been doing this for a long time with the 3DEXPERIENCE platform.

They successfully unified design, simulation, and manufacturing under one massive ecosystem. It looks like Autodesk is aiming for that same level of “single source of truth” for the AEC industry. It worked for manufacturing because it eliminated data silos; the question is whether the fragmented nature of AEC will allow for the same success.

The Transition: What’s Next?

Autodesk has confirmed that the core functionality and UI layout will remain the same for now. Your current projects and data aren’t moving; they’re just getting a new badge.

However, how will Forma support customers who still rely on traditional, file-based methods? Not everyone is ready for a pure cloud-data environment, and the platform needs to remain accessible to those who aren’t living in a 100% “connected” world yet. Interesting to see how it goes.

What do you think about the shift to Forma? Does it make the ecosystem clearer for your team, or is it adding another layer of complexity? Let us know in the comments.

That icon belongs to Autodesk Desktop Connector. a feature that plays an important role in modern CAD/BIM workflows.

What Is Desktop Connector?

Autodesk Desktop Connector is an application that creates a virtual drive on your computer, connecting your local folder structure with Autodesk cloud storage such as Autodesk Docs, Autodesk Drive, and Fusion. In other words, it allows cloud data to appear and behave like regular folders in Windows Explorer.

It works in a similar way to Dropbox, Google Drive, or OneDrive, but specifically for Autodesk storage systems like Docs.

What Is Desktop Connector Used For?

Desktop Connector is designed to let you manage Autodesk cloud files as if you were working locally, without opening a web browser. You can open, save, copy, move, or delete files directly from Windows Explorer.

Desktop applications can also open files stored in Autodesk Docs as if they were located on a local hard drive, without manually downloading or uploading files through a browser.

Each time you save a file, a new version is created in Autodesk Docs. If versioning is critical in your project, you should be careful when working with files through Desktop Connector.

How Desktop Connector Works

In general, Desktop Connector works as follows:

Virtual Drive

After installation and signing in, Desktop Connector creates a virtual drive in Windows Explorer. This drive displays the folder structure from Autodesk Docs (or Drive/Fusion).

However, even though the folder hierarchy is visible, files are not fully downloaded to your local machine until you open them or mark them as “Always keep on this device.”

This means only the data you actually need will be stored on your local hard drive.

File and Folder Synchronization

Working with Autodesk Docs often means following a predefined folder structure and handling a large number of files. With Desktop Connector, you can download and upload files and folders in the background, without manual interaction through a web browser.

Advantages of Desktop Connector Compared to Working in a Browser

There are several situations where Desktop Connector is more beneficial than using Autodesk Docs through a web browser.

Integration with Windows Explorer and Desktop Applications

With Desktop Connector, files are visible and accessible directly from Windows Explorer, without navigating through a browser. This also allows files to be opened directly from applications such as AutoCAD or Revit.

One thing to keep in mind is that frequent saves can quickly increase the number of file versions. It is often a good idea to separate working folders from shared folders.

More Efficient for Uploading and Downloading Files

Regularly uploading and downloading files can be inefficient, especially when dealing with many folders and subfolders. Desktop Connector allows you to take advantage of Windows file management features, while synchronization happens automatically in the background.

To Sum Up

If you want to avoid workflows that rely on repeated manual downloads and uploads, Desktop Connector is worth considering, especially when working with large numbers of files and folders.

BIM in the 1990s

In the 1990s, BIM as a term was not yet widely used. The dominant idea was object-based 3D modeling for buildings. The focus was on replacing 2D CAD drafting with intelligent 3D objects that “knew” what they were: walls, doors, slabs, and columns, not just lines.

At this stage, BIM was primarily understood as: A 3D digital representation of a building using intelligent objects

The concept focused on geometric modeling with embedded properties, primarily to improve drawing consistency and reduce manual coordination errors. Information existed, but it was secondary to geometry. Collaboration was limited, typically confined within a single discipline or organization. If there’s any collaboration, usually still shared as drawings.

BIM in the 1990s was largely authoring-centric rather than process-centric.

Popular Terminologies in this era were:

• Object-based modeling
• Parametric objects
• Building model
• Virtual building
• 3D architectural modeling
• CAD with intelligence

BIM in the 2000s

In the 2000s, BIM began to mature and gain industry recognition. The term Building Information Modeling became more commonly used, emphasizing that the model contained not just geometry, but also information. The industry began to realize that we could leverage information in BIM models.

BIM was now generally defined as: A digital representation of the physical and functional characteristics of a facility

The concept expanded beyond design visualization. Models started to support:

• Quantity take-offs
• Clash detection
• Basic coordination between disciplines

However, BIM was still largely model-centric. The model itself was seen as the primary deliverable. Processes, roles, and responsibilities around information were often informal or undefined. Interoperability became a growing concern, leading to early discussions about open standards.

Popular Terminologies in this era:

• Building Information Modeling (BIM)
• Intelligent model
• Clash detection
• Interoperability
• IFC
• Model-based coordination

BIM in the 2010s

The 2010s marked a significant shift. BIM adoption accelerated globally, driven by large projects, government mandates, and more capable platforms. During this era, BIM was no longer just about models; it became about process and collaboration.

BIM was commonly defined as: A collaborative process for creating and managing information throughout the lifecycle of a built asset

The concept expanded across the project lifecycle:

• Design
• Construction
• Handover
• Operations

This era introduced the idea that multiple models and multiple information containers exist, each serving different purposes. BIM execution planning became formalized, and roles such as BIM Manager and Information Manager emerged. However, many implementations still measure BIM maturity with model complexity rather than information quality.

Popular Terminologies in the 2010s

• 4D BIM / 5D BIM
• BIM Execution Plan (BEP)
• Common Data Environment (CDE)
• Level of Detail (LOD)
• Model federation
• BIM maturity levels
• Digital construction

BIM as Defined in PAS 1192

PAS 1192 represented a benchmark. Instead of redefining BIM as a better model, it reframed BIM as a structured approach to information management.

Under PAS 1192, BIM can be summarized as: The process of managing production, distribution, and quality of information in a collaborative environment

The key conceptual shift was this:

The model is not the goal; information delivery is the goal

PAS 1192 formalized:

• Information workflows
• Statuses and approvals
• Naming conventions
• The Common Data Environment (CDE) as a process, not just a platform

This era clarified that BIM success depends less on software capability and more on defined responsibilities and agreed procedures.

Popular Terminologies Introduced or Formalized

• Common Data Environment (formalized)
• Information delivery
• WIP, Shared, Published, Archive
• Information Manager
• Plain Language Questions (PLQs), a fancy terminology for Layman’s terms
• Data-centric BIM

BIM as Defined in ISO 19650

ISO 19650 represents the most mature and authoritative definition of BIM to date. It builds upon PAS 1192. And as ISO is the international standard, it supersedes all previous definitions and concepts, providing a globally consistent framework.

Under ISO 19650, BIM is defined implicitly as: The use of a structured, collaborative process to manage information over the whole life cycle of a built asset

The core concept is clear:

• BIM is not a model
• BIM is not a software
• BIM is information management using digital technologies

ISO 19650 places information at the center, governed by:

• Clearly defined information requirements
• Standardized information containers
• Lifecycle-wide information planning

With ISO 19650, BIM becomes organization-agnostic and software-neutral. It unifies previous fragmented interpretations into a single, coherent framework that applies equally to design, construction, and operations.

Popular Terminologies in the ISO 19650 Era

• Information container
• Exchange Information Requirements (EIR)
• Asset Information Model (AIM)
• Project Information Model (PIM)
• Appointing Party / Appointed Party
• Information management process

Closing Thoughts

To sum up, the evolution of BIM is as follows:

• 1990s: BIM as intelligent 3D geometry
• 2000s: BIM as a data-rich model
• 2010s: BIM as a collaborative process
• PAS 1192: BIM as structured information management
• ISO 19650: BIM as a standardized, lifecycle-wide information management framework

Today, BIM is no longer about producing better drawings or more detailed models. With ISO 19650, BIM is fundamentally about managing the right information, at the right time, for the right purpose; and this definition supersedes all that came before it.

CAD and BIM are not competing tools

They serve different purposes and operate at different levels of responsibility in a project. Understanding this difference helps you make better decisions when planning and sets expectations to move to BIM.

CAD: Creating Pieces of Project Information

CAD software, recognizable by drawings, plans, and models, has one main job: creating design information.

Whether it is:

• A 2D drawing
• A 3D geometric model
• A technical detail or schematic

CAD produces pieces of information that describe what is being designed or built.

However, CAD files are usually:

• Stand-alone documents
• Managed by individuals or disciplines
• Dependent on people to interpret the meaning and maintain consistency

In simple terms, CAD is for producing part of the information but not for managing how it fits into the bigger picture.

BIM: Managing Information, Not Just Models

BIM, as defined in ISO 19650, is not primarily about 3D models or software. BIM is about how information is organized, controlled, and trusted across a project and over time.

Instead of asking: “How do we draw this?”

BIM asks: “What information do we need, who needs it, and when?”

BIM ensures that:

• Information is created for a clear purpose
• Everyone works from the same source of truth
• Information is reviewed, approved, and tracked
• Data remains useful beyond design, into construction and operation

This is why BIM is often described as information management rather than design automation.

How CAD Fits Inside a BIM Process

ISO 19650 does not eliminate CAD. Instead, it assumes that many different tools will be used to create information.

In a BIM-based project:

• CAD drawings are still created
• Those drawings become managed project information
• Their status (draft, shared, approved) is clearly defined
• Their use is controlled through a shared system

In other words, CAD creates information, and BIM manages it.

When BIM Software Is Used Like CAD

An important point we need to understand is that using BIM software does not automatically mean you are “doing BIM.”

If BIM-capable software is used only to:

• Draw geometry
• Produce drawings
• Ignore data quality, responsibility, and collaboration

Then it is no different from CAD. The value of BIM lies in managing information, not in producing more detailed models.

The Role of a Common Data Environment (CDE)

ISO 19650 introduces the concept of a Common Data Environment, a shared system where all project information is stored, reviewed, and approved.

Think of it as:

• A single, trusted place for project information
• Clear rules about what can be used and when
• Full traceability of decisions and changes

Both CAD files and BIM models live in this environment. What matters is not the file type, but whether the information is controlled and reliable.

The Real Change Is How You Work, Not a Technical Upgrade

BIM adoption is often mistaken for a software upgrade. In reality, it is a change in how organizations treat information.

The shift is:

• From drawings to information assets
• From individual files to shared responsibility
• From personal judgment to defined processes

CAD remains a critical production tool. BIM introduces the structure that allows information to be reused, trusted, and leveraged across the asset lifecycle.

To Sum Up

A Simple Way to Remember the Difference

• CAD creates information
• BIM manages information
• BIM software without information management is still CAD
• BIM benefits comes from control, clarity, and trust in data

BIM does not replace CAD. It replaces unmanaged information with governed, reliable information, enabling you to make better decisions throughout the project lifecycle.

This behavior is related to how Revit handles drafting pattern orientation. For drafting patterns, Revit allows you to control whether the pattern is oriented to the view or aligned with the element. This flexibility helps keep drawings readable and visually consistent across different views.

However, this option is not available for model patterns. And that actually makes sense. Model patterns represent the real-world pattern of a physical element (such as brick or tile), not just an annotation on a drawing. Because of that, their orientation is tied to the model itself rather than the view.

Where to find the pattern orientation settings

To review or change drafting pattern behavior:

• Go to the Manage tab.
• In the Settings panel, click Additional Settings.
• Select Fill Patterns.

Note: You can also access and edit fill patterns directly from the Material Editor, which is often more convenient when working with material definitions.

From the Fill Patterns dialog, select the pattern you want to modify. If you need multiple versions of the same pattern with different behaviors, it’s a good idea to duplicate the pattern first.

Then:

• Click the Duplicate icon to create a copy, or
• Click the pencil icon to edit an existing pattern.

Understanding “Orientation in Host Layers”

In the Edit Pattern Properties dialog, look at the bottom of the window. You’ll find the option called Orientation in Host Layers.

This setting controls how the drafting pattern behaves relative to the element and the view.

The available options are (see the image below):

1. Orient to View: The pattern aligns with the view direction. This keeps the pattern visually consistent regardless of how the element is rotated.
2. Align with Element: The pattern follows the orientation of the host element, such as a wall. Rotating the wall will rotate the pattern.
3. Keep Readable: This option behaves similarly to Align with Element, but with an additional benefit: it maintains readability by showing wall joins and related linework more clearly.

Understanding these options can help you avoid confusing pattern behavior in drawings—especially when working with rotated elements—and make your documentation cleaner and more predictable.

For example, BIM 4D is commonly understood as a model linked to a construction schedule. In practice, however, there is no clear or consistent definition of how that linkage should be. A similar issue exists with BIM 5D, which is typically associated with cost, yet the scope, level of detail, and expected outputs can vary significantly from one project to another.

BIM dimensions also tend to create misleading expectations. When a project is described as implementing BIM 7D, there is often an assumption that it must automatically include 3D, 4D, 5D, and 6D as well, even if those uses are not actually required.

As a result, BIM dimensions function more as labels than as practical tools for technical communication. In a collaborative project environment, this ambiguity can lead to misaligned expectations between owners, consultants, and contractors. Ultimately, projects may become burdened with unnecessary detail simply because the BIM implementation was never clearly defined.

Defining BIM Uses in a Project

A clearer and more structured approach is to define BIM Uses. BIM Use explicitly describes how the BIM model will be used to support business and technical processes within a project.

Common examples of BIM Uses include:

• Design coordination and clash detection
• Quantity take-off and cost estimation
• Construction sequencing and method planning
• Shop drawings and fabrication support
• Asset information for handover and operations

A project may adopt one or multiple BIM Uses, depending on its objectives.

By defining BIM Uses from the outset:

• The purpose of BIM becomes explicit
• The BIM scope can be derived more accurately
• The risk of miscommunication between stakeholders is reduced
• BIM delivery becomes more efficient, avoiding both over-modeling and under-modeling

Within the ISO 19650 framework, BIM Use is closely linked to the definition of Exchange Information Requirements (EIR). EIR does not ask whether a project requires “BIM 4D or 5D.” Instead, it focuses on what information is required, when it is required, and for what purpose. In this sense, BIM Use becomes the foundation for defining project information requirements.

Applying the Right LOIN for Each BIM Use

Once BIM Uses are clearly defined, the next step is determining the appropriate Level of Information Need (LOIN). ISO 19650 emphasizes that information should be fit for purpose, not excessive.

LOIN consists of three main components:

• Level of Geometry: the required geometric detail of model elements
• Level of Information: non-geometric attributes and data
• Level of Documentation: supporting deliverables such as drawings or schedules

Each BIM Use requires a different LOIN. For example:

• Design coordination requires geometry that is accurate enough for clash detection, but not fabrication-level detail
• Quantity take-off requires consistent classification and quantity-related properties, but not necessarily highly detailed geometry
• Construction planning requires elements to be linked to zones, phases, or construction activities

This approach aligns directly with ISO 19650 principles, ensuring that information is produced at an appropriate level for its intended use. LOIN, therefore, becomes a key mechanism for both quality control and efficiency in the production of BIM information.

BIM Dimensions Are No Longer Sufficient

The use of BIM dimension terms such as 3D, 4D, and 5D is no longer sufficient to describe BIM requirements in increasingly complex construction projects. These terms are inherently ambiguous and do not clearly represent actual information needs. While they may still be acceptable at a conceptual level, they must be accompanied by precise definitions and scope.

A more effective and ISO 19650-aligned approach is to:

• Clearly define BIM Uses based on project objectives
• Specify appropriate LOIN for each BIM Use
• Link both to EIR and structured information management within the CDE

This approach ultimately improves collaboration quality, clarity of expectations, and, most importantly, the overall success of BIM implementation across the project lifecycle.

Internal Collaboration Before Publication

Autodesk Construction Cloud (ACC) allows each stakeholder to work within their own account, enabling internal coordination, design iteration, and quality control without immediately exposing data to the owner. This approach aligns with ISO 19650 principles, where information remains in the Work In Progress (WIP) state until it is formally approved for sharing.

Folder Structure and Data Access

Under ISO 19650, folder access restrictions are not just technical settings. They are part of an information management strategy designed to protect data integrity and reliability. Each folder -such as Work In Progress (WIP), Shared, and Published- serves a specific purpose and has a different access level. The WIP folder is restricted to each organization’s internal team, allowing development, coordination, and revisions to take place without the risk of unvalidated data being used prematurely.

Access is only extended to external parties once the information has passed a formal review and approval process. Data moved to the Published folder is considered to have met the required information standards and is ready to be consumed by others, including the project owner. By controlling access based on information status, ISO 19650 ensures that each stakeholder accesses the right information at the right time, reducing errors caused by the use of unapproved data.

Document Review and Publishing in Autodesk Docs

Autodesk Docs provides a structured document review and approval workflow. Once a file has gone through the review process and is approved, the system automatically:

• Assigns an Approved status to the file (or Rejected if revisions are required)
• Duplicates the approved file into a designated folder – Published, in this case

The Published folder then acts as a single source of approved information, ready to be shared with external parties or the project owner.

Bridge: Automating Data Sharing Across Accounts

This is where Bridge plays a key role. Bridge enables automatic synchronization between folders in one ACC account and folders in another ACC account.

With Bridge configured, approved files in the designer’s Published folder are automatically shared and kept up to date in the target folder within the owner’s account – without any manual uploads or duplicate workflows. This significantly reduces human error and prevents unauthorized data modification.

Bridge ensures that the project owner always receives the latest validated information, while unapproved or work-in-progress data remains protected and isolated.

To Sum Up

By combining the review workflow in Autodesk Docs with Bridge in Autodesk Construction Cloud, collaboration between stakeholders becomes more controlled, efficient, and transparent. Each party can work independently within their internal environment, while the project owner consistently receives accurate, verified, and up-to-date information.

Ultimately, Bridge is more than just a file-sharing feature – it is a critical mechanism for enabling secure, multi-account collaboration in line with BIM best practices.