Our design team doesn't like using Autodesk because the comments when submitting/reviewing don't pull forward on the export cover sheet (attached for reference). This limits the ability for us to record documents properly.  Show More

Being able to import or update in bulk from a spreadsheet would significantly make the task lighter and faster rather than typing and/or copying & pasting individually. Show More

Automate tech submittal review using AI.  Show More

Currently, only the Submittal Manager role can select which review workflow is applied to a submittal. Since many projects operate without a dedicated manager role, we request an option to allow Contractors to select the appropriate review workflow directly during the Submittal creation process.   Why this is needed: Eliminates Bottlenecks: Smaller project teams without a dedicated Submittal Manager are forced to assign additional responsibility to lead consultant just to route documents, causing unnecessary delays. Reduces Admin Overhead: Contractors already know which discipline (e.g., Structural, MEP) needs to review their package; letting them select the workflow speeds up the entire routing process. Flexible Project Setup: It allows lean projects to run more efficiently by enabling direct routing from the Submitter to the Reviewer. Show More

Currently, Autodesk Build allows Submittal Managers to edit the Submittal Subject at any time. We request a feature that automatically locks the Subject field and makes it read-only once a contractor officially submits the submittal.   Why this is needed: Protects the Audit Trail: Preventing mid-workflow renaming ensures the digital record in ACC always matches official contractual correspondence and transmittals, reducing dispute risk. Maintains Document Alignment: It prevents accidental or unauthorized naming changes, keeping your project records consistent and organized. Show More

In Forma Submittals, when the Manager Sets the final response. If the Final response isn't selected and the Manager clicks Next, an error pops up that appears to be coding, not an error message for users. The error reads: finalResponse must be a `object` type, but the final value was: null`. If "null" is intended as an empty value be sure to mark the schema as .nullable().    There are no workflow problems, but this error appears to be backend code and not the way the error should read for users.  Show More

When I go to create a submittal report there are options to "Filter" and to "Sort". When I put in the parameters for each of these options and then run the report in Excel Format, it still includes all the available fields in the report. I then have to manually remove the information I don't need. Is there a way to add a feature that removes information from being put into the report? Or is there a way to improve the "filtering" option to show information more specifically to the parameters that I input. Show More

In Submittals, when a trade partner submits a submittal, on the Submit to Manager pop up, to have a check box next to a custom field that states whatever a company needs it to state, and make it a required check box, would be extremely helpful in removing submittal review cover pages.  Show More

I recently had an issue where I created a submittal, and while sending it out, the upload of the pdf attachment failed, though the submittal still was sent out despite the fact that the upload failed and I no longer had access to it.   My suggestion is this:  If an upload of a document fails while sending out/ creating a submittal, the submittal should not be sent out in order to prevent this issue from happening Show More

To introduce project member-customized notification distribution groups, eliminating manual tagging. The notification distribution group can be used when mentioning members in the activity log (e.g., Submittals, RFIs, Issues) or when selecting them as Watchers. Current Pain Points The Hub Admin Bottleneck (Lack Agility for External Parties): Currently, only the Hub Admin has the permission to create new roles. On large-scale projects, external parties (such as Consultants and Subcontractors) cannot quickly set up custom distribution lists. They must go through a slow IT request process just to get a new role created, stalling daily communication. Allowing project-level members to create custom groups address this administrative bottleneck, granting external teams the agility to establish instant communication channels as project needs evolve. Inflexible "Role/Company" Tagging Leading to Excessive Email Notifications: Notification needs are highly dynamic and depend entirely on the discipline (e.g., Structural, MEP, Facade) and the specific scenario. Tagging an entire "Company" or a broad "Role" is not specific enough. It triggers excessive, irrelevant email notifications to project members in that company who have no involvement in that specific item, causing severe email fatigue and leading users to ignore system alerts. Introducing targeted, discipline-specific notification groups ensures that only relevant individuals receive alerts, drastically reducing email noise and restoring trust in system notifications. Show More

To restructure the email notification subject lines, prioritizing critical information (such as the Submittal Title and Forma Project Code) at the very beginning of the subject line. Current Pain Points Missing Critical Information (Submittal Title): Only the submittal number is currently provided while the Submittal Title is missing; as a result, the receiver cannot identify what is being discussed without manually opening every single email. Including the submittal title directly in the subject line allows recipients to immediately identify critical items and quickly flag them, or swipe to archive those that do not directly impact them. This enhancement eliminating inbox fatigue and ensuring no critical deadlines are missed. Space Consumed with Long Project Names: Starting the subject line with the full project name consumes the limited character space visible on Outlook desktop lists. Project member only see the project name and generic system text, while the actual details are cut off. By replacing full project names with compact project number, users can instantly identify the project context within the first few characters of the subject line. Show More

I want everyone to receive the submittal on the same day (consultant, client, subs) so they all have to be in the same review step. I then want to modify the due dates for individual people in the same review step (consultant has 10 days, client has 15 days, so that the client gets to see our response before they have to submit). Is there a way to make the due dates individualized for each reviewer, and not a global change for everyone in that review step.   Thank you!! Show More

When you add an attachment to submittals it doesn't bring the STAMPS that were created on that file in FILES. Now i have to export then redownload and override that files. There should be an option that says do you wish to bring stamps with the file you are about to attach. Show More

1. The comment responses should be visible throughout the review process. Person 1 leaves a response (make corrections noted) and comment response text. Person 2 leaves a response and can see the Person 1 response and comment response. The close and distribute can see all of the previous comments to set the final response and response comments. Making comments is a critical part of this process. It doesnt make sense that the only place you can see the comments are in the table (hard to see/hard to copy) or the activity log (hard to scroll through). Every reviewer needs to see all of the comment responses easily when making their review.  2. The export of a final submittal response should be customizable. There is some info that the contractor/vendor does not need to see on that title cover page, but it is unique to each user/project.    Thanks! Show More

Forma Build Submittals should include a dedicated Submittal Deviation field that allows contractors and subcontractors to clearly identify any differences between the submitted item and the contract documents. A deviation may include: A different manufacturer or model than specified Changes to materials, finishes, dimensions, or performance requirements A proposed substitution A different installation method Changes caused by product availability or lead-time constraints The field should require the submitter to document: What was originally specified What is being submitted instead The reason for the deviation Any known impact on cost, schedule, performance, warranty, coordination, or other trades It would also be helpful to include a required selection such as: No deviations Deviations identified Substitution proposed When a deviation is identified, the system could require additional comments or supporting attachments before the submittal can be submitted. This feature would make deviations more visible to reviewers and reduce the risk of important changes being hidden within shop drawings, product data, or attachments. It would also create a clearer record showing that the contractor disclosed the deviation and that the design team reviewed it. Adding a dedicated deviation field would improve transparency, accountability, and consistency throughout the submittal review process. Currently, a customer is using a Custom Field to manage this process. Show More

Problem Organizations often configure multiple review templates for different disciplines or workflows. Once a review template is assigned to a submittal, its name is not visible on the item, making it difficult to verify whether the correct workflow was selected. This can result in Document Controllers inadvertently selecting the wrong review template without realizing the mistake until the workflow is already in progress. Suggested Enhancement Display the assigned Review Template Name on the Submittal Item details and optionally as a column in the Submittals list. Business Value Improves transparency of workflow configuration. Helps Document Controllers verify template selection before submission. Reduces workflow errors and rework. Simplifies troubleshooting and auditing. Show More

Problem The Specifications tool currently allows the creation of specification sections but does not support the creation of sub-specification sections. Many projects require a hierarchical specification structure to organize discipline-specific or trade-specific requirements. Suggested Enhancement Allow administrators to create and manage Sub-Specification Sections within the Specifications settings. Example: Division 03 – Concrete 03 30 00 – Cast-in-Place Concrete 03 30 00.01 – Foundations 03 30 00.02 – Columns   Business Value Supports industry-standard specification structures. Improves document organization and navigation. Reduces the need to create multiple independent specification sections. Better accommodates large and complex construction projects. Show More

Problem The Specifications tool currently allows the creation of specification sections but does not support the creation of sub-specification sections. Many projects require a hierarchical specification structure to organize discipline-specific or trade-specific requirements.   Suggested Enhancement Allow administrators to create and manage Sub-Specification Sections within the Specifications settings. Example: Division 03 – Concrete 03 30 00 – Cast-in-Place Concrete 03 30 00.01 – Foundations 03 30 00.02 – Columns   Business Value Supports industry-standard specification structures. Improves document organization and navigation. Reduces the need to create multiple independent specification sections. Better accommodates large and complex construction projects. Show More

Problem A single submittal often contains multiple documents. Currently, the review response applies only to the overall submittal, making it difficult to identify which individual files have been approved, rejected, or require revision.   Suggested Enhancement Allow each attached file to receive its own review status while maintaining an overall submittal status. Example: Drawing A – Approved Specification B – Revise and Resubmit Datasheet C – Approved as Noted The overall submittal can then summarize the individual responses.   Business Value Improves clarity for complex submittals. Eliminates ambiguity when only certain documents require revision. Reduces unnecessary resubmissions. Aligns the workflow with common engineering and consultant review practices. Show More