This would save a lot of time compared to manually recreating subfolders. Show More

Discipline-Based Color Coding for Issues in Autodesk Forma Currently, when an issue is pinned in Autodesk Forma, the pin color is automatically assigned based on the issue status (e.g., Draft, Open, In Progress, etc.).   Suggestion: Introduce an option to customize issue pin colors based on discipline (e.g., Architecture, Structural, MEP, Infrastructure, Landscape), in addition to or instead of status-based colors. This would make it easier to visually identify and differentiate issues by discipline, improving coordination, navigation, and overall issue management within the project. Show More

Allow Hub Administrators to deactivate specific unused tools, similar to the tools available in Autodesk Build. Show More

During our transition from ProCore to ACC, we have found an issue caused by a lack of functionality with the Budget Pay App Tool. ProCore allows us to generate configurable PDF's that can re-group certain line items (from new CO's, SOV breakouts, etc.) according to how the  funding sources are grouped on a single PO (e.g. Installation vs Demolition allocations within the PO). We are attempting to split a single budget code into two separate lines within one Prime Contract, however the system does not allow such to take place. You can create sub-items of a budget code to differentiate them, but for some reason I cannot assign those differentiated budget code sub-items individually. Is there something I am doing incorrectly or is this a fundamental deficiency that needs to be addressed via platform changes. Thanks Show More

We would like to propose several enhancements to Autodesk Forma Forms that would significantly improve form configuration, user experience, and data consistency across projects.   1. Firstly, it would be highly beneficial to have a Company Lookup field that automatically retrieves and displays companies configured within the project, eliminating manual data entry and ensuring standardized company names across all forms.   2. Additionally, form administrators should have the ability to duplicate sections within a template and copy fields between sections, reducing the time and effort required to build complex forms.   3.Support for formula and calculated fields is also essential, enabling automatic calculations such as totals, percentages, and scores directly within the Tabular section of forms.   4. The current limitation of 15 columns per table restricts the design of comprehensive inspection and checklist forms. Increasing this limit or making it configurable would provide greater flexibility.   5. Finally, enabling attachment uploads within table rows and also signature field would allow users to associate photos and supporting documents directly with specific observations or checklist items, improving traceability, accountability and audit readiness.   These enhancements would greatly improve efficiency, data quality, reporting capabilities, and overall adoption of Autodesk Forma Forms for quality, safety and inspection workflows. We believe these features would provide substantial value to organizations managing large-scale construction projects. Show More

Users have reported that the document review process involves too many configuration settings, making it time-consuming. There is a need to simplify the process to improve efficiency and make it easier for users to complete document reviews. Show More

Currently, you cannot view recent mark-up activity on Sheets in the Activity Log. All published mark-ups should be traceable in the activity log, so that teams can verify RFI postings or other drawing updates by date completed, instead of having to open each sheet to verify postings. Adding Markup Activity to the Project Activity log would take the process of auditing RFI postings from a very tedious and manual effort to a quick glance to see a week's worth of postings. Show More

Target Autodesk Forma (Photo Feature) Purpose Improve the efficiency of photo management and organization in the field. Current Challenge In our projects, field staff display stored drawings (PDF files) and take photos that are associated with those drawings for documentation and tracking purposes. To manage photos efficiently, we organize them into albums by floor. However, the current photo feature does not allow users to select the target album when taking a photo. As a result, every photo must be manually moved to the appropriate album after it has been captured. In addition, it is often difficult to determine which floor a photo belongs to when viewing newly captured photos in the photo list. This makes post-processing and sorting time-consuming and increases the risk of mistakes. For example, in a 10-story building where a separate album is maintained for each floor, all photos taken onsite must later be moved manually into the correct floor album. As the number of photos increases, the workload grows significantly. Request Please add the ability to select the target album when taking photos with the Photo feature. Expected Benefits Allowing users to specify the target album at the time of capture would provide several benefits: - Reduce the effort required for photo organization - Prevent photos from being filed in the wrong album or left unclassified - Reduce the administrative burden on field personnel - Improve photo management quality in projects with large volumes of photos This enhancement would be especially valuable for large projects involving multiple floors or areas, where thousands of photos may be managed throughout the project lifecycle. If you face similar challenges, please consider voting for this idea. Thank you for your consideration. Show More

Product Autodesk Forma (Mobile App - Issues)   Goal Enable users to identify the location of issues more quickly and accurately when using Forma on mobile devices.   Current Challenge In the web version, an issue thumbnail is displayed in the issue details view, allowing users to immediately understand where the issue is located. However, in the mobile app, issue thumbnails are not displayed.  As a result, field personnel must open the drawing and manually search for the affected location before they can fully understand the issue. This is particularly challenging on construction sites, where users often need to review a large number of issues in a short period of time.  When the affected location cannot be identified at a glance, the review process becomes slower and more prone to oversight or misunderstanding.   Requested Enhancement Please add issue thumbnails to the issue details view in the mobile app, similar to the web version. Providing the same visual context available in the web version would allow users to quickly identify the affected location and make issue review more efficient in the field.   Expected Benefits - Instantly identify the location associated with an issue - Reduce time spent reviewing issues on site - Minimize misunderstandings and missed issue checks - Provide a more consistent user experience between the web and mobile versions - Improve productivity on projects with a large number of issues Because the mobile app is frequently used in the field, we believe that displaying issue thumbnails would provide significant value to users. If you are experiencing the same challenge, please consider voting for this idea. Thank you for your consideration. Show More

Some users have expressed concerns about the limitations with the current review workflow process. In multi-step approval workflows, only the final approval step supports a formal approval decision, while intermediate reviewers can only provide comments. They would like every review step to be able to issue a formal approval or rejection decision, not just comments. Show More

Enable a dedicated Timesheets tool that could be integrated into the Forma Build platform. It could become an essential tool that would provide the ability for site team to track hours worked within a form workflow, have the hours signed off daily by the site manager, and could then be submitted to their Line Manager or payroll through the Submittal tool.  There’s multiple options for how this could be utilised by referencing the Timesheet with different tools on Build such as Meetings, Assets, Submittals, Schedule Workplans etc.   Adding the option for Timesheets is badly needed. Show More

We need a function to be able to export our messages sent and received - currently we can only export a good faith report that shows a message was sent but not the contents. Add the messaging to the good faith report and please provide and export option for all messaging sent and received. Thank you! Show More

Many projects have roles such as Information Managers, Document Controllers and Project Leads who need visibility of all reviews for governance, reporting and oversight purposes, but do not need to participate in the review workflow. Could Autodesk introduce a dedicated "Review Viewer" permission that allows nominated users to view all project reviews and associated comments without being added to each workflow or requiring Project Administrator rights? Benefits: Improves project oversight and reporting. Reduces the need for elevated admin permissions. Maintains governance and segregation of duties. Allows key project roles to monitor review progress and bottlenecks more effectively. Minimises administration associated with managing review distribution lists. Show More

It appears that recently Data Exchange models are now appearing in the Model Coordination space.   While I appreciated that there are instances where this could be useful, it is now producing many duplicate models in my coordination spaces across all discipline folders. The Revit model and the Data Exchange model. And since Data Exchange models are filename-less, I can't exclude them from the Formats selection in the Coordination Space Content settings.   The impact this causes is having two models for each discipline that may end up being used inconsistently across Views, and the risk of them getting out of sync.   We urgently need a means to disable Data Exchanges from Model Coordination, or add them to the Formats list in the content settings. Show More

We have received consistent feedback from users regarding the visibility of RFI question or answer text within Autodesk Forma. Currently, when an RFI question or answer exceeds the initial display area, users must click the "See More" link at the bottom of the question or answer to view the remaining content. This behavior can create confusion because users may not realize additional information is available, resulting in incomplete understanding of the RFI requirements. In many cases, critical context and details are hidden below the fold, and the current "See More" control is not sufficiently prominent to draw attention. We would like to request consideration for one of the following improvements: Display the full RFI question by default without requiring users to expand the text. If full display is not feasible, increase the visibility and prominence of the "See More" control by: Using a larger font size or button style. Adding a visual indicator that content is truncated. Applying a contrasting color or highlighting the control. Displaying a message such as "Additional question details below - click See More." Improving the visibility of complete RFI content would help reduce missed information, improve user experience, and minimize the risk of responses being submitted without reviewing the full question. Show More

It would be useful to be able select/deselect form sections that are exported when exporting a form. It could use a toggle feature to select which sections are exported.    Some forms have multiple sections that are not relevant to all stakeholders, so it would be useful to configure the view for different parties.  Show More

For the use of custom fields, it would be very beneficial if the additional field types Date and Person Selection were available when creating custom fields within the Issues functionality. This would make it possible to directly add and manage important time- and daterelated information within Issues. For example: -Validity periods (from/to) -Application date -Creation date -Received on -Approval date -Review deadlines -Project- and processspecific milestones A dedicated date field type would significantly increase the flexibility of Issue management, improve data quality, and provide additional possibilities for filtering, evaluations and reporting. This would allow time-related information to be recorded in a structured and consistent way without having to use freetext fields or workarounds. In addition it would also be beneficial to have a custom field type for Person or Person Selection. This would make it possible to assign additional project- and processspecific roles to individual persons within an Issue, independently from the general Issue assignment. For example: -Applicant -Creator -Reviewer -Approver -Responsible person -Contact person -Other project- or processspecific roles Especially for Issues that go through several processing, review or approval steps, this would allow the involved persons and their respective roles to be clearly and structurally assigned. Adding the field types Date and Person Selection to custom fields would therefore significantly increase the flexibility of Issue management and provide more possibilities to represent project- and processspecific workflows in a structured way. Show More

I love having Clash Checks. But the problem is so does everyone else. And when everyone else decides to make their Clash Checks public, it means the list grows rapidly. To the point that it becomes unusable.   We really need some kind of Clash Test filtering so we can block out the noise. Or allow each View to select which Clash Checks from all public ones to show in this list. This needs to be addressed sooner than later.   Show More

If and when the required forms & subtasks are completed, it would be great if the status to automatically show "complete" and for that to trigger the next handoff task to move from "backlog" to "open." Additionally: - When assignees start filling out required forms, "open" automatically switches to "in progress."  - These tasks should show up on the home page of the assignees so they are aware of their immediate tasks (I know assignees are already getting email notifications , which is good.)  - Parent Task status should be updated to reflect the sub-task status. i.e. if a sub task is "in progress" the parent automatically should switch from "open" to "in progress."  Show More