Add a customizable .xlsx Procurement Log report that can be generated directly from the Submittals tool, similar to the existing PDF report customization options. Users could select and arrange the fields they need, save the configuration as a template, and reuse it throughout the project lifecycle without having to reformat each downloaded report. Including calculated comparisons between approval or closeout dates and key procurement milestones, such as required dates, lead times, and dates required on-site, would provide better visibility into procurement status, help teams identify schedule risks earlier, and significantly reduce the manual effort currently required to produce recurring procurement reports that is already being provided in the platform.   Currently the .xlsx report is not customizable, provides an unnecessary amount of information, doesn't mirror the columns/information we have selected to be viewed in the main submittal log, etc.  Show More

Inside the Reports tool, there is a Submittal Items Summary report template that is customizable (and schedulable!).  Good job Autodesk.  But..... As I was adjusting my particular desired fields, I saw it gives the ability to show the Due Date field beside each submittal item, but NOT the date it was sent to the architect/engineer (Sent to Reviewer field).   It would be very helpful to show this since it documents how long the submittal has been in the hands of the reviewer.  Sure, you can go back into the Submittals tool and see this, but that takes a while.  This report needs to be a quick global view.  Having this added information will help reviewers prioritize their reviews. Show More

We should have the ability to create issues directly from markups during a Submittal Review. Show More

There currently is not an option to edit the text when creating a submittal or an RFI. It would be helpful to bold, underline, and add other similar elements to the text to help bring something to the attention of the reviewer/users.  Show More

It's great that custom fields were added to submittals, but when you search for a term in a text formatted custom field, it doesn't show the submittal. To me, this defeats the purpose of the custom field. Please make data from text formatted custom fields something that a search in the search bar would pick up and display Show More

1) Keep the same template and nomenclature for the data shown when extracting summaries of RFIs, Submittals and Issues in excel format. Currently, submittals will show Ball in court under a certain name, but RFIs summary will present it differently which makes it difficult to follow up with the concerned parties about all their due tasks.    2) A master summary of all Submittals, RFIs and Issues that can be extracted as a PDF or Excel would be really beneficial. Show More

Currently, saved Submittals are paginated in the view, requiring users to click through multiple pages to review content. This disrupts navigation and makes it harder for users who prefer continuous scrolling, especially when reviewing large sets of Submittals or PDFs. Proposed Solution Add an option to toggle between paginated view and continuous scrolling for saved Submittals. Ensure smooth scrolling for PDFs and Submittal content.   Show More

Currently, users must manually specify a number for each Submittal, which can be confusing and prone to errors. While some customers prefer manual control, others would benefit from automatic sequential numbering. The lack of flexibility creates inefficiency and inconsistency across projects.   Proposed Solution Add a settings option to choose between: Manual numbering – users specify the submittal number. Automatic sequential numbering – the system assigns the next available number. Show More

Currently, attachments are sorted alphabetically by default. This rigid sorting method does not reflect the contextual importance or logical order of information, which can confuse users reviewing attachments.   Proposed Solution Introduce the ability to customize attachment order within Issues, Assets, Forms, and other modules. Show More

Currently, the submittal output includes a cover sheet and summary page that often contain blank or non‑pertinent information. The second page of the output is almost entirely unused, reducing the value of the report. Without customization, teams cannot tailor submittal outputs to their specific workflows or project requirements.   Proposed Solution Allow users to customize submittal cover sheets and output templates. Show More

I'd like to create a step in a submittal workflow where multiple individuals are assigned a submittal and only one of their responses satisfies that workflow step. These individuals are internal employees of my company, so assigning the submittal to my entire company, meaning all engineers would be assigned this submittal, does not work for me.  Show More

It's great that we can now add Custom Fields in Submittals, but we need the option to set the custom field as Required, like in the Issues tool.  We also need the ability to choose which Submittal Type a custom field is added to. Show More

Currently, correspondence IDs are automatically generated with the GCOR prefix and sequential numbering when uploading responses EX from Outlook. This makes it difficult to group related items such as RFIs, PCOs, or Submittals under a consistent ID scheme. Users cannot change or customise the ID to align with project workflows.   Proposed Solution Allow users to change or customise the correspondence ID after creation. Enable creation of different ID types/prefixes, e.g., RFI, PCO, SUB. When sending or sharing correspondence, the chosen prefix (e.g., RFI ID) should appear in the email subject and tracking. Show More

Allow users to attach the files included in a Submittal directly to the email notification. This would allow recipients to view the submitted documents from the email without needing to click a link and access Autodesk Forma Show More

Using specifications for the first time and we are a subcontract.  High level we don't use all the specifications for submission long term. We use it for tracking purposes on submittals that are required sub-tiers below our company.    The main issue that I have is that when generating the submittals from the specifications,  you can't read the specifications description without editing it or hovering over the description.  I believe that this should be a wrap text portion or expand.  Something to allow us to read the description when generating.  Like selecting certain submittal portions only.  It takes alot longer to sort.  If there was a way that you can see the physical spec like the page when you select a generated submittal.    Show More

Currently, submittal items marked as Void are hidden from the register list by default. The only way to view them is to manually apply a filter to include voided items. This creates visibility issues and makes it harder to track the full history of submittals.   Proposed Solution Update the register list to display voided submittals by default, with a clear status indicator: Eg, Voided. Alternatively, provide a toggle option so users can easily switch between Show All and Hide Voided views without applying complex filters. Show More

Currently, once a submittal is marked as Void, there is no way to change it back to an active status. This creates issues when a submittal is mistakenly voided, as the item becomes permanently inactive even though it retains its number. Without a reversal option, users must create duplicate submittals or rely on manual workarounds, which can cause confusion and inefficiency.   Proposed Solution Introduce a Reverse Void option that allows authorised users with the correct permissions to reactivate a voided submittal. Show More

In the AutoSpecs module, users can currently select a spec section eg 265000, 1.03A, check the box, and publish it to the Submittals module. However, each spec section can only be published once. This limitation prevents users from publishing the same spec section multiple times when required, creating inefficiencies and gaps in documentation.   Proposed Solution Enhance the AutoSpecs module to allow multiple publications of the same spec section into Submittals. Show More

Currently, the system only allows one final response option to be selected for a submittal. This creates challenges in scenarios where multiple outcomes apply. For example: A submittal may be returned as Approved as Noted and Resubmit Required. If only Approved as Noted is selected, the resubmit requirement may be overlooked. If only Resubmit is selected, the team may incorrectly assume the submittal is on hold and cannot be released. This limitation leads to confusion, miscommunication, and potential delays in project workflows. Proposed Solution Enhance the system to allow multiple final response options to be selected simultaneously. Provide a clear UI with checkboxes or a multi‑select dropdown so users can choose more than one applicable response. Show More