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

Current Limitation: Currently, users can download markup PDFs individually in ACC. This manual process is time-consuming, particularly when multiple documents and review packages need to be processed. Proposed Enhancement: Introduce a Bulk Export Markup PDFs feature that allows users to select a specific review package and download all associated markup PDFs in a single operation. Ideally, the export should also support multiple review package selections and provide the option to download the files as a single ZIP archive possibly. Suggested Functionality: Select one or multiple review packages. Bulk-export all associated markup PDFs. Download the exported files as a ZIP archive, with folders organized by review package. Preserve original document names and relevant revision information. Show More

In Autodesk Forma, some standard Issue fields cannot currently be disabled for specific Issue Types, even when they are not relevant to that workflow. For example, in the Issue Type settings, the “Placement” field remains visible for all Issues and cannot be hidden for a specific type. We would like administrators to be able to disable or hide non-required standard fields on a per-Issue-Type basis, in the same way that other field visibility settings can be configured. This would allow each Issue Type to contain only the fields that are relevant to that process. For example, an internal ICT Issue Type may not require Placement, Location, or other construction-specific fields. Removing these unnecessary fields would make the Issue form clearer, reduce user confusion, and improve data quality by showing only the information that users actually need to complete. Show More

When users are already working inside the Schedule module in Autodesk Forma, the Schedule item in the main navigation menu is not clickable. This makes it less intuitive to return to the main Schedule landing page after navigating deeper into the module. We would like the Schedule item in the navigation menu to remain clickable at all times. When selected, it should bring the user back to the main Schedule page. This behavior would be consistent with other modules, where clicking the module name in the navigation returns the user to that module’s main page. This small navigation improvement would make Schedule easier to use and provide a more consistent experience across Autodesk Forma. Show More

Add a section to the homepage that displays all tasks created by the user, including their current status.   This would make it easier to keep track of created tasks, see when someone has completed a task, and avoid missing updates or having to check emails to stay informed. Show More

When creating a Transmittal in Autodesk Forma for Construction, recipients are currently managed through a single recipient selection area. In the Issues module, responsibilities are more clearly separated through distinct fields such as “Assigned To” and “Followers”. This makes it easier to distinguish between the person or group responsible for taking action and the users who only need to be informed or kept in the loop. We would like the Transmittal creation workflow to use a similar structure by separating recipients into two distinct fields: Assigned To: users or groups who are expected to take action or are primarily responsible for the transmittal. Followers: users or groups who should receive visibility or notifications but are not responsible for the action. This would make responsibilities clearer, reduce ambiguity in communication, and align the Transmittal workflow more closely with the behavior already available in Issues. Show More

When creating or configuring an Issue template in Autodesk Forma for Construction, the template title is currently populated with the same value as the template name. We would like it to be possible to leave the Issue title blank in the template. The template name is used to identify and select the template, while the Issue title should be entered by the user when creating the actual Issue. Automatically using the template name as the Issue title creates unnecessary duplicate information and requires users to overwrite it each time. Allowing the title field to remain blank would make templates more flexible and ensure that users enter a meaningful title specific to the Issue being created. Show More

When creating an Issue in Autodesk Forma for Construction, the template selection dropdown currently displays more rows than the number of actual templates available. For example, in our case there are only three templates available: 01_Hardware 02_Toepassingen test However, the dropdown displays additional non-selectable rows such as “Recently used” and issue category/grouping labels. This results in eight visible rows for only three actual templates and makes the list unnecessarily difficult to scan. We would like the template selector to focus primarily on the selectable templates and avoid displaying extra non-clickable rows as separate list entries. Ideally, if three templates are available, the user should see three clear selectable template entries. This would make template selection much clearer, especially in projects where a larger number of Issue templates are configured. Show More

Current Limitation: Currently, users are required to manually configure their preferred settings for PDF markup tools each time they review documents in Autodesk Construction Cloud (ACC). The absence of persistent, user-specific default settings results in repetitive adjustments, increased review time, and an inconsistent user experience.   Proposed Enhancement: Enhance the ACC PDF markup functionality to allow individual users to configure and save their preferred settings for markup tools. These preferences should be associated with the user's account or role and automatically applied whenever they open a document for review, eliminating the need to reconfigure the settings for every review session.   Examples of configurable preferences may include: Preferred markup colors, line weights, and text sizes. Preferred font styles and text formatting. Preferred settings for clouds, callouts, arrows, shapes, and other markup tools. Other supported markup tool properties and display preferences. Users should be able to modify their saved preferences at any time, with an option to restore the system defaults. Show More

Feature Overview Introduce a Labour Difficulty Factor within ProEst that allows estimators to apply a multiplier to labour quantities or productivity rates to account for varying levels of job difficulty and site conditions. Current Challenge Labour estimates are typically calculated using standard productivity rates. However, actual labour requirements can vary depending on factors such as site accessibility, working conditions, complexity of installation, and project-specific constraints. Currently, estimators need to manually adjust labour quantities to account for these conditions. Proposed Functionality Allow users to enter a difficulty factor against labour resources, cost items, or assemblies. The difficulty factor would act as a multiplier against the calculated labour hours. For example: Standard productivity: 1 hour per unit Quantity of work: 100 units Standard labour requirement: 100 hours Difficulty factor: 1.5 Adjusted labour requirement: 150 hours A difficulty factor of 1.0 would represent standard productivity, while 1.5 would indicate that the work requires 50% more labour time than normal. Business Benefits Improve the accuracy of labour estimates by accounting for job-specific conditions. Reduce the need for manual adjustments to labour quantities. Provide greater visibility into how difficulty impacts labour costs. Assist with workforce planning by providing more realistic labour-hour requirements. Allow estimators to maintain standard productivity rates while applying project-specific adjustments. Desired Outcome Estimators should be able to apply a Labour Difficulty Factor that automatically adjusts labour hours and associated labour costs, without affecting material, equipment, or other non-labour resources. Show More

Users are requesting the ability to add the same user to multiple workflow roles within an estimate.   For example the user may be the estimator, but also part of the review team. The user needs to be able to added to the estimate team as both the estimator and review workflow roles. Show More

To the Autodesk Platform Services and Model Coordination Team,   I am contacting you on behalf of the development team at AltoQi, the company responsible for AltoQi Builder and Eberick, leading BIM MEP and structural design tools in Brazil.   Currently, when our users upload IFC files generated by AltoQi to Autodesk Forma, the platform categorizes them as "Not supported for clash detection." This prevents our models from participating in the automatic clash detection engine, limiting the OpenBIM workflow for our mutual clients.   We have reviewed your interoperability guidelines and confirmed that our software architecture fully supports persistent IFC GlobalIds. Any conduit, pipe, fitting, or structural element generated by our export engine maintains its exact GUID throughout the project lifecycle, across multiple IFC exports and revisions.   To help us move forward, we would appreciate your guidance on the official validation workflow for submitting our files for evaluation and subsequent inclusion as supported for clash detection.   We are available to provide test files, technical logs, or any additional details regarding our export framework. We look forward to the opportunity to work together to improve the integration between our platforms.   Sincerely, Letícia Carvalho - Product Analyst AltoQi Development Team Show More

As a Project Admin, when searching for members in ACC, the search appears to be limited to recent results (approximately 30 days). Is there a setting or administrative option to expand the search to include all historical account members regardless of activity date? If not, is there a recommended workaround or enhancement planned for future releases?  Show More

Possibility to track Grids and Levels using Watch Groups in Design Collaboration Another thing that might be useful is tracking the project base point and the survey point. Show More

Description When the North orientation is changed in Navisworks, the model displays correctly according to the updated North direction. However, when the same .NWD file is uploaded to Forma, the updated North orientation is not preserved. The North direction displayed in Forma Viewer does not match the orientation set in Navisworks. Why This Is Important Accurate North orientation is critical for site planning, construction coordination, logistics reviews, and communication with clients. When the orientation is different between Navisworks and Forma, it can cause confusion and make it more difficult to clearly review and communicate project information. Suggested Improvement It would be helpful if Forma could preserve the North orientation defined in the Navisworks file when the model is uploaded. Alternatively, Forma Viewer could include a feature that allows users to manually adjust or set the North orientation after uploading the model. Thank you for considering this improvement. Show More

Hi,   Using assemblies within ProEst gives us the ability to swap items out by clicking on the item code and replacing the item. For example changing an item from a 1,000L water cart to a 10,000L water cart.  The issue is when changing this item, the note attached to the item also disappears. Generally speaking this is an assembly specific note rather than an item note so it would be appreciated if the note was kept when changing items. We lose the 'Must be on site by 8AM' note even though its still relevant. Show More

"Land Surveyor" or "Land Surveying" should be added to the business type list. "Civil Engineer" doesn't adequately describe the services offered for a number of Civil firms and leaves out independent surveying firms completely. Show More

Currently, if a document exists in two different folders with the same file name, it is very difficult to consolidate the version history. For example: P01 of a document exists in Folder A. P02 of the same document exists in Folder B. When attempting to move P02 into Folder A, Autodesk Docs rejects the move because a file with the same name already exists. The only workaround is to copy the file rather than move it. However, this creates several issues: The original version history is split between two separate documents. The copied file does not retain a single continuous audit trail. If multiple revisions are copied into one folder, an administrator must manually set the latest revision as the current version. During this process, important information such as review status and workflow history is not clearly visible, making it difficult to determine which revision should be the current version. Managing document history becomes time-consuming and increases the risk of version control errors. Suggested Improvement: Introduce an option to merge files with the same name when moving documents between folders. This would: Retain the complete version history and audit trail. Automatically place revisions in the correct sequence. Preserve review and workflow status information. Remove the need for manual intervention when consolidating documents. Improve document control and reduce the risk of errors. This would be particularly beneficial for projects where documents are occasionally created or revised in different folder locations and later need to be consolidated while maintaining a complete record of the document lifecycle. Show More

In the "Hub Admin" section under "Hub members," selecting a member makes it easy to identify the projects associated with them. For the future, I suggest developing a similar feature that allows the same operation starting from "Hub companies," enabling you to find the projects associated with a specific company. Show More