To create feature parity UNIFI, Content Catalog should allow users to select an existing Revit project as a source, discover reusable elements contained within the model, select individual elements or categories, and either insert them into the active project or promote selected elements into managed Content Catalog content. Show More

Currently when you publish forms from Hub library to projects the form templates sit within the Template space. However it would be assumed that most construction sites would have a H&S folder, Quality Folder, Environmental Folder etc. Would be nice to have some type of system where if you publish a H&S form checklist from the Hub library it will auto locate in the H&S folder at the project level. I know there will be difficulties with this as Folders will not always assign eg H&S Folder, Health and Safety Folder, Safety Folder etc.  Show More

Model based assets should have the function to apply "or" logic when filtering by multiple data fields.  Currently the only filter behavior is "AND" logic between fields. The only "OR" logic behavior is when there are choices within data fields.     Show More

Introduce an option to export detailed audit logs for Submittals, RFIs, and Issues in Autodesk Forma. Currently, project teams need better visibility into the complete activity history of these records for tracking, reporting, compliance, and audit purposes. The proposed enhancement should allow users to export audit logs in PDF, Excel or CSV format, capturing details such as: Record ID and title. Created by and originating organisation. Date and time of each activity. Status changes and transitions. Assigned users and organisations. Comments, responses, and actions performed. Users responsible for each action. Complete activity and revision history. Show More

Ideally, when a user signs a Form, the system should automatically capture and record their current GPS location, subject to the user's permission to access device location services. The captured information could include: GPS coordinates (latitude and longitude). Location details, where available. Date and time of signature. A location reference or map link for verification. Expected Benefits Improve the reliability and traceability of site inspection records. Provide additional verification that Forms were signed at the intended project location. Strengthen accountability for site personnel completing inspections and approvals. Reduce the need for separate manual geolocation records or third-party applications. Improve the overall digital inspection and approval workflow. Use Case For site inspections and Permit-to-Work (PTW) workflows, users are required to complete and sign Forms at specific locations. Capturing geolocation alongside the signature would provide additional evidence that the inspection or verification was carried out at the designated site location. We would appreciate Autodesk considering this enhancement for future ACC Forms development. Show More

We use naming conventions in Forma a lot. In this context, the selected separator should not affect the bridging of documents between different environments. Unfortunately, this is currently the case. The order of the attributes in the naming conventions should not be a limitation either. Additionally, it would be useful to be able to link attributes when setting up a bridge between different environments. Show More

Target Feature Camera markers in the File Viewer (indicating where photos were taken)   Purpose When construction photos are submitted and archived as part of project closeout documentation, it is important to retain clear evidence of where each photo was taken. Being able to output construction photos together with their corresponding locations on a floor plan would make closeout documentation much easier to understand while also reducing the time and effort required to prepare deliverables.   Current Challenges In the File Viewer, camera markers on floor plans make it very easy to identify where each photo was taken. This provides clear and useful visual context while working in Forma. However, when preparing final project documentation for submission to clients, we face several challenges: Camera markers must be manually made public, which can be time-consuming on projects with a large number of photo locations. Camera markers are not included when floor plans are printed or exported to PDF. As a result, the useful relationship between a photo and its exact location on the floor plan, which is clearly visible in Forma, cannot be directly included in the final documentation delivered to the client. Other construction systems already support workflows where camera markers are displayed on floor plans and included in printed deliverables. These outputs can then be used directly as client documentation, significantly reducing the effort required to prepare project closeout documents. If Forma supported a similar workflow, project teams would no longer need to create separate documents simply to indicate where each photo was taken. This would provide significant practical value for construction teams.   Requested Enhancements We would greatly appreciate the addition of the following capabilities: 1. Option to make camera markers public by default Allow projects to configure camera markers as Public by default, for example through a project-level setting. This would eliminate the need to manually change the visibility of large numbers of camera markers. 2. Include camera markers in Print and PDF output Allow camera markers displayed on a floor plan to be included when printing or exporting the plan to PDF. Ideally, users should be able to select Include Camera Markers / Exclude Camera Markers when generating the output, depending on its intended use. Expected Benefits With these enhancements, project teams could create floor plans that clearly connect construction photos with their actual shooting locations and use them directly as part of project closeout documentation. This would: Make closeout documents clearer and easier for clients to understand. Improve the traceability and evidential value of construction photos. Eliminate the need to create separate documents showing photo locations. Reduce the effort required to manually change the visibility settings of large numbers of camera markers. Streamline the workflow from documentation preparation through client submission. Make construction photos more useful after project completion for facility management, maintenance, and renovation work. On construction projects, the location where a photo was taken can be just as important as the photo itself. Forma already provides this valuable relationship between photos and their locations on screen. If that same information could be preserved in printed and PDF outputs, it would turn an already useful feature into a much more powerful tool for project closeout, handover, and long-term building documentation. We believe this enhancement would benefit many construction projects and would greatly improve the practical value of Forma for project delivery and handover. Show More

Since September 2026, CAD (DWG) layouts can be brought into Model Coordination. However, there is currently no way to set the layout’s coordinates or rotation once it is loaded. As a result, it often does not line up with the 3D models in the coordination space. Requested features: Manual X, Y, Z offset input for each CAD layout Rotation angle input (about the X, Y, Z axis) Option to save the alignment so it persists for all users and future versions of the same file (Nice to have) Two-point or three-point pick alignment, snapping layout points to model points (snap to grids is also a good method) Benefits: 2D layouts can be aligned quickly to 3D models without re-exporting from AutoCAD with modified coordinates Easier clash review and coordination against 2D references such as setting-out plans, grids, and site layouts Less back-and-forth between CAD and model teams over shared coordinates Current workaround: Move or rotate the drawing in AutoCAD to match the model’s origin and then re-upload. This is slow and has to be repeated on every revision. Show More

Current behavior In the new Photo Experience, albums and sub-albums can be created. However, a photo can only be uploaded to one specific album level, either the parent album (“Project Photos”) or one of its sub-albums. A parent album only shows the photos that were uploaded directly to it. It does not include the photos from its sub-albums. Expected behavior A parent album should work as an aggregated view of everything below it: Project Photos shows all photos in the project, including those in all sub-albums. 1.1 Sub-album 1 shows only the photos of this sub-album. 1.2 Sub-album 2 shows only the photos of this sub-album. 1.3 Sub-album 3 shows only the photos of this sub-album. Why this matters With the current logic, I have to decide whether to upload a photo to “Project Photos” or to a sub-album. Because of this, the hierarchical logic of sub-albums is lost. There is effectively no benefit to creating sub-albums, since I could just as well create an additional album at the same level. A true parent-child relationship, where the parent album includes the content of its children, is what makes a hierarchy useful for organizing and filtering photos. Suggested solution Parent albums automatically include all photos from their sub-albums (recursively, if there are multiple levels). Optionally, add a toggle such as “Include photos from sub-albums” to let users switch between the aggregated view and the direct-content-only view. Show More

Having the option to set a default project image in project templates would ensure a consistent visual identity across all projects, without the need to manually upload the logo every time a new project is created. Show More

Currently, there’s no way to distinguish between location and asset QR codes that have been placed on site and those that exist in the system. Provide the ability to flag QR codes as “On site”, giving project teams a reliable view of which locations and assets can be scanned in the field.   Proposed behaviour (web and mobile):   1. Allow users (controlled by permission) to set the “On site” status once a QR code has been placed, for example via a simple toggle. 2. Display the “On site” status on location and asset lists. 3. Enable filtering of locations and assets by this status. Show More

We are experiencing inconsistent behavior in how personal issue filters are retained across Autodesk Construction Cloud modules. In Data Management, an issue filter is saved and retained for each individual user. However, the same filter is not retained in Model Coordination. When the user refreshes the page or navigates to another page and returns, the filter is cleared. We would expect the filter behavior in Model Coordination to be consistent with Data Management, with each user’s selected filter being retained. Show More

A major red flag for SharePoint users considering a migration to Forma Data Management is the limited dropdown (lookup) list functionality. Search: The dropdown list only has two columns: Value and Description. The description CANNOT be used for SEARCH. Dropdown lists are created to store company standards. They contain multiple columns that SharePoint uses as projected fields. Linking a lookup item makes all columns in the view available and searchable. Naming standard: If a company uses the dropdown lists for a naming standard, we are forced to use the value code from the dropdown list. The complete description is not available for search, and users can only use the code. Show More

Bridge is currently limited to Files, Folders, and RFIs. All other key project management modules — Submittals, Meetings (minutes/agenda), Specifications, Sheets, and others — cannot be bridged between projects or accounts. Meeting series often start early in precon. Meeting series often carry over and/or evolve from early phases to construction. During this phase, meeting series may move from a client hub to the contractors hub, while the structure/attendees largely stay the same. When this happens, meeting history is lost or requires heavy data entry work to replicate. It would be very helpful if the Meetings module (and others) could be added to Bridge functionality.  Show More

Give users ability to remove the Project Files folder or get rid of it all together. This folder does not provide any additional value and unnecessarily extends the file path through Desktop Connector. Removing it would help reduce path lengths and make it easier for users to manage the Windows 260-character limit. Show More

Introduce the ability to create and configure custom attributes within Forms in Autodesk Forma, allowing project teams to tailor forms to their specific project requirements and information management standards. The proposed enhancement should allow users to: Create custom attributes with configurable field names and descriptions. Support different field types, such as text, numbers, dates, dropdown lists, checkboxes, and multi-select options. Make fields mandatory or optional based on project requirements. Configure custom attributes at the form template level. Include custom attributes in form views, registers, filters, and reports. Support exporting custom attribute data to Excel/CSV. Retain custom attribute values throughout the form lifecycle, including submissions, reviews, and revisions. Show More

On large projects, multiple departments may act as Submittal Managers (e.g., Civil, Architectural, MEP, QA/QC, Procurement). We request the ability to assign multiple Submittal Managers while restricting their visibility only to: Submittals they create Submittals assigned to their department or discipline Submittals explicitly shared with them Project Administrators should continue to have full visibility across all Submittals. This enhancement would improve information governance, reduce unnecessary access to unrelated documents, and better support large enterprise projects with multiple teams. Show More

As a long-time user of Autodesk document management solutions, I would like to request enhanced markup management capabilities in Autodesk Forma Data Management, similar to what was available in BIM 360 Docs. Today, projects can contain hundreds of markups from multiple review cycles, disciplines, and stakeholders. While the current markup tools are useful for creating and publishing markups, there is no efficient way to organize them into logical groups, making large-scale reviews difficult to manage. [autodesk.com], [help.autodesk.com] Requested functionality: Create custom markup groups (e.g., Architectural, Structural, MEP, Client Review, IFC Review, Revision A, Revision B). Show/hide markup groups independently. Filter markups by group, author, date, status, or discipline. Bulk edit, publish, archive, or delete markups within a group. Save markup views for different review teams. Support grouping across file versions while maintaining markup history. Business value: Many organizations use markups as part of formal design and review workflows. On large projects, hundreds or thousands of markups can accumulate, creating significant visual clutter and making it difficult to focus on specific review activities. Grouping functionality would improve usability, productivity, and traceability while reducing the need to convert markups into Issues solely for organizational purposes. This capability was highly valuable in BIM 360 workflows and would greatly improve the user experience for teams transitioning to Forma and Autodesk Construction Cloud. Show More

Problem statement: In the Deleted Items view, the Description attribute isn’t visible. Without it, users may not be able to tell what a deleted file contains before restoring it, especially when several files have similar names.   Desired outcome: Display each deleted file’s Description attribute in the Deleted Items view, so users can identify the right file before restoring it. Show More