Being able to pull a custom attribute from Issues into RFIs, etc would be helpful - keep them linked and updated. For example, if I'm tracking a WBS (Work Breakdown Structure) that is different than my Spatial Structure, I cannot use Locations for both, so I make a custom attribute. That I then must recreate in other areas and update in multiple places. Show More

Having a setting to allow RFI creators to not be able to add co-reviewers or mention people outside of their company or those already involved with the RFI would be a big value in firewalling and locking down access. Currently, if you mention someone, you can see the entire list of people on the project. If an owner is in there, we do not want just anyone to be able to tag them. Show More

Adding a function to a permission level should be a toggle instead of a drop down. Currently, if I want someone to upload files, they can then download files. But if I'm collecting items from multiple companies, I do not want to have them download other items. To solve cases like this: NAME                                       VIEW         DOWNLOAD           MARKUP            UPLOAD         EDIT          MANAGE Person                                        Y                         N                          Y                        Y                 N                   N Company                                    Y                         N                          N                       N                 N                   N Role                                             Y                         Y                          Y                        Y                 Y                    N Show More

Currently, when initiating a workflow in Autodesk Construction Cloud, only approvers can be added to the process. However, many change orders require additional people from our organisation to be informed of change orders for visibility and awareness purposes, without requiring them to take any approval action. Introducing a “notify-only”  option within workflows would allow users to include these stakeholders and automatically notify them when a change order is initiated or updated, while keeping the approval chain unchanged. This enhancement would improve communication, reduce manual follow-ups outside the system, and ensure that relevant teams such as commercial, finance, or project controls have real-time visibility without impacting workflow efficiency Show More

When Payment Application is rejected during the approval workflow, we suggested that the status of Payment Application will be changed to ‘Submitted’ rather than ‘Revise and Resubmit’.    If the user click 'Submitted' button, the claimed Work Completed would take the Work Completed amount which is inaccurate. The Claimed Work Completed should remain as the supplier’s first submission. The submitted status should remain the Claimed Work Completed original amount and allow the user to edit the Work Completed amount instead. Show More

Currently, once a Potential Change Order (PCO) is executed, it can no longer be edited. This creates a limitation, as change orders often go through multiple rounds of review, clarification, and back-and-forth communication during the approval workflow. In many real project scenarios, additional cost items are identified after the PCO has already been accepted or executed. At present, if a new cost item is added after the PCO has progressed to the Subcontract Change Order (SCO) stage, that cost item does not carry forward to the SCO. This results in incomplete records, manual workarounds, and potential discrepancies between the PCO and SCO values. It would be highly beneficial to allow controlled editing of PCOs even after they are accepted or executed, such as adding or updating cost items, with proper version tracking or audit history. Any approved changes should automatically flow through to the corresponding SCO to ensure cost continuity, data accuracy, and alignment between commercial documentation across all stages of the change management process. Show More

Currently, under Cost Module, Autodesk Construction Cloud provides limited options for exporting contract information, and key commercial details are often spread across multiple views or reports. This makes it difficult to generate a complete, professional record of a contract for sharing, review, or archival purposes. It would be highly beneficial to have the ability to export contracts as a single, comprehensive PDF that includes all relevant information, such as contract line items, associated change orders, contract values, budget assignments, and custom attributes. Having all of this data consolidated into one structured PDF would significantly improve usability for internal reviews, client submissions, audits, and claims documentation. This enhancement would reduce reliance on screenshots, manual exports, or external spreadsheets, while ensuring data consistency and traceability. A configurable export option—allowing users to select which sections or attributes to include—would further enhance flexibility and make ACC contract management more efficient and aligned with real-world commercial and reporting requirements. Show More

Currently, Autodesk Construction Cloud provides a manual option to send reminder emails for change orders. However, this requires users to actively monitor due dates and trigger reminders themselves, which can be time-consuming and may lead to missed follow-ups on busy projects. It would be highly beneficial to have automated reminder notifications when a change order passes its due date. The system should automatically send reminder emails or in-app notifications to the respective responsible users (such as approvers or reviewers) when action is overdue. Ideally, these reminders could be configurable, allowing teams to define reminder frequency or escalation rules. Show More

When a PCO (Potential Change Order) advances to an RFQ (Request for Quotation) or an SCO (Subsequent Change Order), the system should automatically retain the same name as the related PCO. Rationale: Ensures traceability between the PCO and its corresponding RFQ or SCO. Reduces confusion when tracking multiple change orders. Maintains consistency in reporting and documentation. Show More

During the Subcontract Change Order (SCO) review process, Autodesk Construction Cloud displays a review timeline at the top of the record, showing the workflow steps, reviewers, and approval progress. This timeline is very useful for tracking the review status and understanding where the SCO is within the workflow. However, once the SCO workflow is completed, this review timeline is no longer visible. As a result, users lose access to important historical information, such as who reviewed or approved the SCO, the sequence of approvals, and the overall workflow progression. This information is often required for audits, claims support, internal reviews, and future reference. We do have an option to see in the activity section but it does not provide the information at a glance, whereas the review timeline does. Activity history has too much text and includes non-review related history. Show More

Currently, when a workflow in Autodesk Construction Cloud is rejected, it typically returns to the initiator or restarts from the beginning. This limits flexibility, especially for complex approval workflows that involve multiple stakeholders and review stages. In many real-world project scenarios, a workflow may only require corrections or clarification at a specific step rather than a full restart. For example, a reviewer may need revisions from a particular approver or department while the earlier approvals remain valid. The inability to send a workflow back to a specific step results in unnecessary re-approvals, increased administrative effort, and longer cycle times. Show More

RFIs have an option to send reminder email but Submittals do not.  Show More

I am so tired of constantly deleting Cookies and browsing history, and restarting my computer in the vain hopes that autodesk will not run like a Frame-y, Mess in Chrome or Microsoft Edge.    Or Waiting 3-4 Minutes on a page in order to try and get it to smooth out.   The Mobile App works and runs 100 times better than the Browser based version, and it really affects productivity when your doing mark ups or location marking, and the screen is moving at 5 frames a second.   Yes I have tried all the Tech support ideas, and Yes all the ports are open, and Yes my computer meets the requirements   thanks again for your time, Frustrated In Vancouver   Show More

Edit Assets in table format, similar to exporting out to excel - having both options would benefit. At the moment the team have to individually click on each Asset and update where sometimes the team prefer Excel like features.  Show More

We’re using Design Collab to share and consume folders. The issue we’re seeing is that when roles are assigned in Teams (Design Collab), everyone with a role gains view access to all subfolders under the shared folder. Our intent is to assign roles at the subfolder level so access aligns with the specific discipline/folder. In Docs, those roles had view and create permissions limited to their folders. After setting up Design Collab, they now have view access across all subfolders within the shared folder. This is a concern for clients who are particular about access controls. For example, if we share an architectural model in the Arch folder, we may not want power engineers to view it. This need for granular, discipline‑specific permissions is especially important on large projects with multiple clients, disciplines, and roles. We’d like to ensure Design Collab enforces true role‑based, subfolder‑level permissions (i.e., view access only to the folders tied to each role), rather than granting blanket view access across the shared hierarchy. Show More

It would be nice to link a view point of Modell Coordination direct in meeting notes. That would help the users to improve the meeting speed (and handling) and skip the discussion on drawings.  Show More

Please enable the ability to configure Section Assignees in Autodesk Build Form Templates at both the Account Library level and within Project Templates. Today, Section Assignees can only be set inside an active project, after the form has already been deployed AND copied, which prevents standardized, centralized setup.   Current Limitation Section Assignees are not available when creating or editing a form in the Account Library Section Assignees do not carry through Project Templates Project Admins must manually turn on Section Assignees in every project This results in inconsistent forms across teams and an added administrative burden   Why This Matters Organizations managing multiple projects expect form templates to deploy with a consistent structure and consistent role-based responsibilities. Without Section Assignees in Library or Project Template mode, form template behavior varies from project to project, increasing setup time and the risk of missed reviews or incomplete workflows.   Requested Enhancement Add support for: Assigning roles, companies, or members to each form template section directly in the Account Library Saving those assignments as part of the form template Deploying form templates into projects with Section Assignees already in place Optionally updating Section Assignees across existing projects when a form templates are updated Impact Ensures consistent review and handoff workflows across all projects Reduces repetitive manual configuration Allows true centralization of form template management Improves compliance and quality control for enterprise customers Show More

With the Manage permission in Assets you should be able to also import assets from models. Now, as of 11th December 2025, it is only the project admins who can do it. This is not good because you preferably want the persons (f.ex. 3rd party) handling Assets not be able to control the whole project. This is especially critical when working with multiple stakeholders. Show More

At the moment every user has to select the accurancy settings for the measurements every time again when open the coordination view. In infrastructure projects we work with Millimeter accurancy. The setting should be stored. Ohterwise the user has to do many clicks before the information is usefull.  Show More