Problem Description: When merging IFC and Revit files into a single leading coordination model, I use the Model Coordination feature. From this environment, I save the combined model to Docs so that all project members can view it. However, I’m missing two key functionalities: Linking Sheets: It’s currently not possible to link sheets (floor plans, details, etc.) to the combined coordination model. This limits context and makes it difficult to navigate directly from the combined model to relevant drawings. Mini-map / Reference: There is no mini-map visible in the combined model, which means the reference to the floor plan or room is missing. This makes it harder to quickly orient yourself within the model and understand the location of elements. Why is this important? Linking sheets to the combined model would significantly improve workflow, allowing users to jump directly from the coordination model to relevant drawings. A mini-map or reference overlay would enhance navigation and spatial context, especially for large and complex projects. Proposed Solution: Add an option to link sheets to combined models in Model Coordination. Implement a mini-map or reference overlay in the viewer so users always know where they are in the model. Impact: These improvements would greatly enhance collaboration and coordination within projects and create a more integrated experience between 3D models and 2D documentation. Show More

When adding an issue on an iPad, it used to be the case that to add a photo a user would need to scroll down to the References section, select '+Add' and then the user could select 'Use Camera' and add a photo to the issue. This photo could then be used by all project members. However, a few months ago the interface was updated and this 'Attachments New' section showed up with big, obvious button that says 'Use camera'. Attachments are not available anywhere else in the project.  Despite multiple trainings and emphasis on the unwanted change to the interface, my field forces continue to take the path of least resistance and keep selecting the first 'Use Camera' option they see. This causes a number of problem for other project members who need to see these photos, but can't because they are attached, not referenced.  While this sounds like an internal training issue, I argue that this is really a user interface issue. The user interface practically screams to the user to use the Attachments section rather than the references section. I am requesting that this interface be updated. For example, the big, obvious 'Use camera' button could be removed and the interface updated to match the References section. Another idea would be to add an 'Add Photo' section with a menu pop-up asking the user to choose to add the photo as a reference or as an attachment. Or anything in between. But can we please agree that this interface is misleading and confusing and that an update is needed? Show More

  ACC Submittals support only one consolidated status per submittal When multiple files are submitted under a single submittal, it is not possible to track individual file statuses (Approved / Rejected / Revise & Resubmit) Review stamps and comments are available at file level, but these are not reportable or structured data. Suggestion - Allow each file inside a submittal to have its own status Example: File A → Approved File B → Revise & Resubmit File C → Approved   Show More

Problem Description: When a user is mentioned in the comments section of an issue, they are not automatically added as a follower of that issue. As a result, they only receive a single email notification and cannot easily filter or track the issue afterward. This often leads to missed action points because the mentioned user is not actively subscribed to updates. Why is this important? Users who are mentioned are usually relevant to the discussion or action, so they should stay informed about any updates. Without automatic following, important tasks can be overlooked, reducing accountability and slowing down workflows. Proposed Solution: When a user is mentioned in an issue comment, automatically add them as a follower of that issue. Alternatively, provide an option to enable this behavior as a project setting. Impact: This improvement would ensure that mentioned users remain engaged and informed, reducing the risk of missed actions and improving collaboration and issue resolution. Show More

Hello,   Using a naming convention is highly effective. When a file does not comply with this convention, it is placed in a Holding Area. Request: Currently, no notifications are sent when a file is moved to the Holding Area. It would be beneficial to introduce a notification process so that relevant users are informed as soon as a file enters this area, enabling faster review and resolution.       Show More

Summary Currently, Autodesk Construction Cloud (ACC) allows metadata and attributes to be applied primarily at the file level, while folders do not support structured custom attributes. For teams managing large volumes of documents, we strongly request the ability to assign custom, typed attributes to folders and use them for search and filtering, similar to enterprise document management systems. Background & Use Case Many project teams are transitioning from other document management platforms to ACC Docs while maintaining parallel operations during migration. In these environments: Folders represent meaningful project groupings (e.g., project units, delivery stages, organizational structures) Users need to search and filter folders based on structured information, not free text Folder-level attributes are essential to replicate existing, well-established document management rules Current Limitation At present, folders can only store unstructured information (e.g., notes or annotations), which creates several issues: No ability to define data types (date, dropdown, text, etc.) High risk of: Inconsistent input Typos Users ignoring input rules Difficult to enforce governance and standardized operations Workarounds such as encoding information into folder names or annotations are possible, but they are not scalable, error-prone, and hard to maintain. Required Attribute Examples (Illustrative) Typical folder-level attributes required include: Organizational category (dropdown) Completion or milestone date (date field) Department or functional group (dropdown or text field) These attributes need: Controlled input (data type enforcement) Consistent values Searchability across the folder structure Business Impact Without structured folder attributes, teams are forced to: Overcomplicate folder hierarchies Rely on naming conventions instead of data Accept reduced search accuracy compared to existing enterprise platforms This creates friction during platform adoption and limits ACC’s effectiveness as a centralized document management solution for large projects. Requested Enhancement Enable custom attributes on folders in ACC Docs Support typed fields (date, dropdown, text, etc.) Allow folders to be searchable and filterable based on these attributes Apply governance rules similar to file-level metadata Expected Benefits Improves document discoverability at scale Reduces operational errors caused by free-text input Eases migration from existing document management systems Strengthens ACC Docs as an enterprise-ready platform This enhancement would significantly improve usability for teams managing complex document structures and align ACC Docs with real-world enterprise document management needs. Thank you for your consideration. 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

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

ACC does not allow administrators to define the project’s exact geographic location. Since the address is entered manually, the system displays only an approximate location rather than an accurate one. 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

As ACC becomes the default repository for the files inside a project, its folder structure grows and can be quite large during project development. This frequently makes us spend a considerable time navigating through folders or finding a specific one.  We should be able to bookmark folders in a project, and then display them in a "favorites" section in the browser inside the Files area.  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

Following the ISO 19650 folder structure for large civil and infrastructure projects, correctly assigning folder permissions is essential. Currently, this process is challenging because there is no way to link the assigned user’s company with their role. Creating ISO 19650-based roles is not desirable, as it would result in an excessive number of roles, reducing clarity. In the worst case, permissions would need to be assigned individually to users. To address this, it would be highly beneficial to enable a relationship between companies and roles when assigning folder permissions (and/or rules). This would: Simplify the setup of large-scale projects and streamline permission management during execution. Eliminate the need for user-based permissions, improving overall data access security. Reduce role clutter at both the project and hub levels, maintaining readability and manageability. New users automatically inherit correct permissions based on their company-role relationship, minimizing manual setup. Resulting in faster onboarding Easier to track and verify access rights for compliance with ISO 19650 and internal governance. Supports growth and complexity in large projects without exponentially increasing role management complexity.     Show More

We would like the RFI Detail Report to be able to in Excel format. We need the "Suggested Answer" to show up on our report (and we need this in Ecxel format), but the Detail Report does not allow this - only .pdf.  The Summary Report can be downloaded as an excel file, but does not show the Suggested Answer. 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

It would be nice to have a status of reopened or have some data point that reflects this that you can use in Insight or as a filter. Think workflow of subcontractor marks an issue complete, the Project Manager verifies that the work was not done and changes it back to open. Being able to view those that were marked as complete but were validated that they were in fact not complete would be useful.  Show More

Autodesk Construction Cloud (ACC) currently limits Custom Field (Text) inputs to 250 characters. This restriction creates challenges for large and complex projects where detailed, structured information is required. Custom Text Fields are commonly used to capture contractual references, technical notes, compliance remarks, and operational instructions. In many cases, these details cannot be adequately conveyed within the existing character limit, forcing users to abbreviate critical information or split content across multiple fields. As a result, teams rely on workarounds such as creating additional Custom Fields, using external documents, or storing important information in comments or descriptions. This reduces data consistency, impacts reporting quality, and undermines ACC’s effectiveness as a centralized source of truth. Requested Enhancement Increase the Custom Field (Text) character limit beyond 250 characters, while maintaining existing functionality such as searchability, reporting, and cross-module usage. Expected Benefits More complete and accurate data capture Reduced reliance on external tools and manual processes Improved usability for large-scale and compliance-driven projects This enhancement would significantly improve ACC’s ability to support real-world enterprise construction workflows. Thank you for your consideration.         Show More

At the moment it would be very helpful to show point clouds in the model coordination view together with models and other information's. That would save a lot of time to create models from existing condition. It would enable the project team to discuss fast in 3D in meetings to find solutions. A mesh is not a solution because of details and the accuracy. See example pictures of other CDE types for inspiration. Show More