We need the option when pulling in documents into the OCO to be able to pull in the Merged PCO documents instead of all the individual documents from the PCO.  Pro's: Pulling in the Merged PCO.pdf is a cleaner when reviewing the PCO to make sure all the PCO's backup has been attached Easier to follow Ensures we are using the same document that was used as backup in the PCO approval process in the OCO. that the Owner. Con's: Existing process pulls in all the individual documents Makes it harder to understand what document belongs to what PCO Difficult to ensure all the documents are in the correct order. Allows users to delete out documents that the owner has already seen in the PCO approval process.    There is a work around but it is time consuming.  You have to "attach from Autodesk Docs" go find the folder the merged document is saved on and click on it to attach it.        Show More

I (try to) manage all projects across the board. For example, when a new colleague joins, they sometimes have to be added to 3,000 active projects. Or when role permissions change (due to a change of function), those permissions have to be adjusted across all (more than 5,000) active projects.   Can a tool be created to manage active projects and in particular users, roles, folder rights for account admins? Show More

Current Limitation: In Autodesk Construction Cloud (ACC) Submittals, reviewer-related date information (such as review start date, response date, or reviewer action dates) is correctly captured within the platform and is also available when exporting submittal data to PDF format. However, when exporting the same submittal data to Excel, these reviewer date fields are not included in the Excel output. Business Impact: This limitation makes it difficult for project teams to perform reporting, tracking, and analysis using Excel, especially for audit purposes, schedule tracking, and management reporting where reviewer timelines are required. Expected Enhancement: The Excel export for Submittals should include the same reviewer date fields that are currently available within the platform and reflected in the PDF export. Benefit: Providing consistent data across PDF and Excel exports will improve reporting accuracy, reduce manual workarounds, and enhance overall usability for project controls and documentation teams. Show More

Creating a Data Exchange file from a published Revit model initially seemed like a great idea. In fact, the entire concept of Data Exchange, even when used within its native software, appears very promising. However, it currently does not extract all parameters or properties from the model.   I raised a case with Autodesk Support regarding this issue, but was redirected to this Idea Board. These missing parameters are, at present, by design. It seems the development team is aware of the limitation and plans to address it in the future.   As I understand it, the Data Exchange format currently focuses primarily on geometry rather than parameters, as it cannot guarantee the inclusion of properties. But isn’t that the core purpose of having data-rich Data Exchange files?   My formal request: Please enable the extraction of all parameters into the Data Exchange, both when created via the ACC viewer and when generated within the native software. This would make Data Exchange files reliable for any use. At present, Data Exchange is not practical because the missing parameters are unpredictable, making it impossible to know which data will be excluded. Show More

Ability for ACC Build Minutes of Meeting to be generated automatically by connecting MS Copilot/MS Teams Transcript or by Autodesk AI taking the minutes. Show More

After writing minutes of a meeting you need to notify and share with invitees. You can do this but it comes with a generic notification with no option to customize it. The request is, when sharing meetings, to have the option to send out a notification with a customized subject and message. An example of this can be seen in Cost Management when sending out contracts, you can customize the subject and the message (see screenshot attached). Show More

When creating a new template->"Build a new form"->"Select a starting template" the user is presented with a list of templates to start a template creation from. This list must be editable in some way, at least to project admins who would be able to add or remove starting templates suggestions from this list. These starting templates are key when developing large sets of templates that have commonalities such as project details pages, signature pages, table pages and such which would be common over a range of templates (and forms).   These are the current list of templates (as of Jan 2026): Blank Template Daily Report Incident report Safety Checklist Covid-19 Safety Checklist Covid-19 Screening Checklist for jobsite visitors Show More

We use our phone list generated from ACC to place in our O&M manuals at the the end of the project, we also throughout the project will create a phone list for site to reference, it would be extremely helpful if we could input the members title so we know who to call for certain situations. Please, pretty please, make this happen!!!!??? Show More

Using Autodesk AI Assistant to generate BIM Execution Plan from the Customer requirements which are also uploaded into ACC Show More

Simpler upload functionality to upload 000's of specifications allowing to skip version sets etc and shortening the upload process Show More

Currently, Autodesk Construction Cloud (ACC) limits the number of assignees per Submittal to a maximum of 10 users. For large-scale construction projects, this limitation creates significant workflow challenges. We strongly request increasing this limit to at least 30 individual assignees.         Background & Problem Statement     ACC Submittals are designed to track review status per individual assignee, which is a very valuable capability for accountability and auditability.   However, the current limitation causes issues because:   Submittals often require review by many individual stakeholders, not just roles or companies Role-based or Company-based assignees do not fit workflows where: Individual approval status must be visible Review history needs to be tracked per person   Individual-based assignment is essential for: Compliance Accountability Long-term record keeping of who reviewed what and when             Business Impact     Due to the 10-user assignee limit, teams managing large projects are forced to:   Create multiple duplicate Submittals for the same document Partially revert to manual or paper-based workflows Use additional tools outside ACC to complete reviews     This significantly reduces efficiency and undermines ACC’s value as a centralized platform for large projects.   Additionally, Submittals templates often reach the maximum limit (250 templates) more quickly due to duplicated workflows created solely to bypass the assignee restriction.         Requested Enhancement     Increase the maximum number of individual Submittals assignees to at least 30 users Maintain the current functionality of: Individual review status visibility Per-user approval history tracking             Expected Benefits     Enables ACC to fully support large and complex project workflows Eliminates the need for duplicate Submittals and manual processes Improves adoption of ACC as a true enterprise-level construction management platform         This enhancement would significantly improve usability for teams managing large-scale projects and better align ACC Submittals with real-world industry requirements.   Thank you for your consideration. Show More

The Build Home page keeps improving with the inclusion of the Insight Builder dashboards. But it still has a lot of wasted space.   The first thing to note as a recent improvement is that when changing to an Insight Builder tab (dashboard), it is displayed in full width. That is, the 'white space' on the left and right are greatly reduced. This doesn't happen on the Overview tab, but I'm glad it does on the IB dashboards.   So that then leaves that very large waste of space above the dashboard tabs that contains the "welcome" message and the project's address in the top-right.   Referring to the below screenshot, I would like to see those data elements (green) be moved into the Overview tab, allowing that vertical space (purple) to be reallocated to the dashboards. That way we can get the full benefits of the screen space for the IB dashboards.      Show More

References on packages, photos, schedules tasks, assets (possibly others) are not apparent whether a reference has been included or not as part of using that tool.  There is only a link/button/heading that the user can click on and see if something has been added there or not.  Would be nice to have some sort of flag, or numerical indication when those tools have a "Reference".  Issues, Forms, RFI's as an example do a decent job at visually seeing whether something is there based on those being right in the user interface, or a box with things "attached" so to speak. Show More

Currently when Documents are uploaded to the attachments of a PCO and we "Batch Request for Quotes" the document is copied from the PCO to generate RFQ's there is no automatic synchronization between them.  When we get a revised document pertaining to the PCO/RFQ and upload the new document to the attachments of the PCO there is no way for the new document to be pushed to the RFQ's that are tied to the PCO or in other words any document changes made on the PCO do not automatically update across the RFQ's.    This is a problem when we are sending RFQ's to 30+ Suppliers and we get a revised document.  We need for a way to be able to upload the new document at the PCO and have it sync to the 30+ RFQ's that are tied to the PCO.    The current work around is to go into each of the 30+ RFQ's and delete out the original and upload the revised document, which takes hours when we are sending these out to all Suppliers.   Show More

We've had instances where, for example, 2 Sheets collections were created but they should've been under one, but there is currently no way to merge them together without having to delete and re-upload. In some cases, it wasn't discovered till too late, and comments were already made on some sheets, so deleting and re-uploading is not an option. Please make this merge possible. We are not able to use the Compare function otherwise. Show More

IFCSpaces are helpful model objects for calculating quantities, such as surface areas. Currently, IFCSpace items are not treated as physical objects within the Autodesk Construction Cloud viewer which means that they cannot be used. It would be helpful to close this gap so that every model object, including IFCSpaces, can be used for quantity takeoff. Show More

Something that I have found to be problematic on several projects is that clashes understandably leave the clash pool upon being assigned to an issue. This behaviour is fine and logical until a project member goes full tilt creating issues from clashes, or you realise just after creating the issue that something was incorrectly included/excluded. In these cases depending on how widespread the impact is the only real workaround is to set up a whole new coordination space or reuploading the affected models-both being unideal solutions.   What would be greatly helpful is to basically have an option where by in these situations the issue can be deleted/deactivated and all those clashes return back to the clash pool for future review. As it stands, when clashes are marked as 'not an issue' we have the option to restore the clashes to the pool. It seems logical to have this exact same functionality for clashes that incorrectly or prematurely get assigned to an issue. Show More

  It would be helpful to add Project Admin Locations as Docs attributes. In this way all files in Docs will be aligned to project standard locations in a consistent way. Show More

It would be so helpful to have an option to pin or favourite a file, and be able to have all the favourites in one place with quick links. In the sea of documents, some can easily escape you if they have a document number or title that doesn't quite reveal what's within them. Show More