Currently, exported sheets from Build > Sheets, including issues and markups, visually display the issues, but it is not possible to identify which specific issue is being referenced. Although the exported PDF contains a hyperlink to the corresponding Forma issue, this is only useful for users and companies who have access to Forma. For documentation purposes, especially when sheets are printed, it is essential that the Issue ID is also displayed directly on the sheet. This allows users to correlate the issue shown on the drawing with the corresponding issue detail report (PDF). I am aware that the Issue Detail Report provides an option to include a sheet overview. However, the embedded sheet is only available as a reduced-size overview, and the created markups are not displayed. As a result, it is not suitable for accurately locating and identifying issues on the drawing. We require the ability to export sheets at their actual scale and size, including all visible markups and issues, with a clear display of the corresponding Issue IDs. This would ensure that users can easily locate and match issues within a PDF issue report and maintain a complete and usable project record, even without access to Forma. Below is an example of how we would like exported sheets to be displayed, including the Issue ID directly on the drawing for easy reference and documentation purposes: MichaelSaxl_0-1787116534800.png   Show More

Team, We are using Autodesk Construction Cloud (ACC) for project document management (Docs module) across our engagements. We understand that e-signature functionality is currently available natively within the Cost Management module (via DocuSign, Adobe Sign, Dropbox Sign, or SignNow integrations) for contracts, change orders, and payment applications. Our requirement is to enable e-signature capability for general project documents and PDFs (e.g., drawings, submittals, transmittals, approval sheets) stored in ACC Docs — not limited to Cost Management-generated documents. It would also be very helpful if e-signature capability could be extended to the Markups tool within ACC Files. Many of our reviewers and approvers add sign-off comments, stamps, and markups directly on drawings and PDFs during review cycles, and having native e-signature support at that stage would eliminate the need to export files to a third-party e-sign tool and re-upload them. This would streamline approval workflows for redlines, punch lists, and drawing sign-offs, keeping the entire review-and-approval process within a single platform and providing a clear audit trail alongside the markup history. Additionally, I am attaching an image with respect to the e-stamps/e-signature related ideas that were already posted in the Forma Community ideas forum for reference: Ability to Create and Manage Stamp Templates at the Project Template Level — Requests enabling stamp templates to be configured at the Project Template level so they're automatically available across all new projects, instead of being recreated manually for each one. Ability to Apply Signature/Stamp Across Multiple Pages in a Single PDF — Requests the option to apply a signature/stamp to all pages (or a selected page range) of a multi-page PDF in one action, instead of stamping each page individually.   Show More

Have a list view (drop down list) to search and select a drawing sheet by number or name to jump to from within the Drawing Sheet view. This is functionality that is available in the web version of sheets at least at the sheet number level, that is currently not available in the mobile version of sheets at all. See attached screenshot of this. Also, on both web and mobile, from within a sheet view, add the ability to be able to search by sheet name to select another sheet to go to. Show More

We have created a project template for our company to use for all new projects in Autodesk. There are a number of settings, permissions and templates that can only be setup after the new project has been created. This becomes a very time consuming process with the number of projects we are creating. The following updates would be great to see and edit at a project template level in Autodesk Build: Schedule adding roles to schedule permissions creating plan templates (currently this can only be done within each project, but you still have to manually build the plan each time first) Assets adding roles to permissions Enabling collections in sheets Correspondence creating correspondence types adding roles to permissions Show More

When you change a docusign template you have to delete the current template which removes all the default settings and signing order that existed previously.  See attached for reference.     It would be great to have a "replace template" option as well, which would leave the settings in place. Show More

Currently, Cost Management allows users to create custom attributes (such as dropdown fields) for individual change order tabs like PCO, COR, and OCO, but these attributes are isolated to the tab they were created in. For example, if I create a "CO Reason Code" dropdown attribute on the PCO tab, it does not appear on the COR or OCO tabs. While I can manually recreate the same attribute on each tab, the values are not linked; a selection made in one tab has no connection to the same attribute on another tab, meaning the data isn't actually shared or synced. This makes it difficult to maintain consistent categorization, filtering, and grouping across the full change order lifecycle, since a change order often moves through multiple tabs as it progresses. We'd like to request the ability to create a custom attribute once and apply it globally across all change order tabs, with selections carrying over automatically between tabs. This would allow teams to filter, group, and report on change orders using consistent criteria throughout the entire workflow, rather than having to manage disconnected, duplicate attributes on each tab. Show More

To be able to view the Gantt Chart on mobile. Show More

Some users need the ability to edit reviews in bulk in order to complete and update the required information. Show More

We have a custom attribute for the main contract but can't have that attribute be visible on a budget payment application template.  The only way to have that attribute visible on the application template is to create the same custom attribute under budget payment application.  Seems reductant. The main contract and application are associated with each other under the budget module.  The contract feeds the SOV structure each month when the application is created. It would be ideal to have custom attributes for main contract be used in a budget payment application. Show More

Title: Allow Cost Management Budget Structures to Be Saved in Project Templates Idea / Enhancement Request: Autodesk should allow a Cost Management budget structure to be saved as part of a project template. During an owner-side Cost Management implementation, we configured a standard project template with the correct Cost Management settings, budget code structure, permissions, tools, and project setup. However, the actual budget structure could not be stored inside the project template. Each new project still requires the team to manually import the standard master budget template after the project is created. Current workflow: Create a new project from the Autodesk project template. Open Cost Management. Go to the Budget tab. Import the standard master budget template. Group the budget view by the budget code structure. Save the desired view for that project. Requested workflow: Allow a project template to include a preloaded Cost Management budget shell so that when a new project is created from the template, the Budget tab is already populated with the standard structure. The template does not need to carry live project values. At minimum, it would be helpful if the project template could carry forward: Standard budget rows Budget code assignments Parent and child budget hierarchy Default units Default descriptions Saved budget views and grouping Standard empty budget shells for owner or internal tracking workflows Why this matters: For owners and repeat project teams, the budget structure is often standardized across projects. In this case, the team wants each new project to start with the same cost categories and custom budget fields. Project managers would then rename custom fields, enter values, and remove lines that do not apply. Without this capability, each new project requires a manual import step. That adds setup time, increases the chance of inconsistent budget structures, and makes it harder to standardize reporting across projects. Business value: This enhancement would help teams: Standardize Cost Management setup across projects Reduce project startup steps Improve consistency in budget tracking Support better cross-project reporting and dashboards Reduce user error during budget setup Make project templates more complete for owner-side project controls workflows Suggested feature: Add an option in Project Templates called "Include Budget Structure in Template" or "Save Budget Shell to Project Template." When selected, new projects created from that template would automatically include the predefined budget structure, with values left blank or optionally carried forward based on user preference. This would be especially valuable for owner organizations, healthcare systems, public agencies, and repeat project teams that use Cost Management for internal budget tracking and standardized project reporting. Show More

During our time using BuildingConnected we have found the database of subcontractors to be incredibly useful. However, even if a subcontractor has a BuildingConnected account, they sometimes do not prefer or outright refuse to use the platform, or the invitations are sent to their spam folder. As such, we have had to email them separately, which takes a significant amount of time to click through their contact card and copy their email. Additionally, we would like to be able to place the contacts in an internal spreadsheet for record keeping.   To make this process smoother, a function to export the bidders or invitee emails/contact cards on a given project as a CSV or, better yet, an excel sheet would greatly help. Show More

Once sent back, the workflow can't be edited without voiding and restarting the entire review. Allow mid-cycle workflow adjustments. Show More

When a file referenced in a transmittal is moved, the transmittal shows it as deleted instead of tracking the new path. Show both original and new path, and/or offer a "void transmittal" option. Show More

Review markup is currently limited to viewable file types (PDF/models). Add markup/comment support directly on Excel files within a review, without converting to PDF first. Show More

Revision/transmittal numbers currently must be added manually via attributes, which is time-consuming and error-prone. Automatically include the current review ID and current transmittal ID as file metadata/filename info, similar to how file versions display, so reviewers can see status directly from the Files module. Show More

A recent update in the Review Workflow Settings allows users to assign Key Reviewers within the review interface. However, the "Minimum Number of Key Reviewers Should Review" option is currently available even when the workflow is configured as "Every Key Reviewer Must Review". This behavior appears to be a bug or configuration error because the minimum reviewer count is not applicable when all key reviewers are required to complete the review. Having this option available creates a workflow inconsistency and may lead to incorrect review completion behavior. Expected Behavior: The "Minimum Number of Key Reviewers Should Review" option should only be available when the corresponding workflow condition supports minimum reviewer selection. "Every Key Reviewer Must Review" is selected, the "Minimum Number of Key Reviewers Should Review" option is still available. If the system is designed to support this option in this workflow type, then the configured minimum number of reviewers should be respected and function correctly when reviewers are added through the review interface. Please investigate this issue and implement a fix to ensure the workflow settings are aligned with the intended review logic. Show More

Presently only Issue Reports support template-based scheduled exports. Extend the same scheduling capability to Review, Files Log, and Transmittal reports so recurring status updates go out automatically. At present, the functionality is limited to the Data Connector. For project-specific requirements, direct integration with Forma would add significant value by automatically fetching relevant project data. This would not only save time but also improve data accuracy, enhance workflow efficiency, and reduce dependency on manual update. Show More

Extend functionality of assigning Meeting items to Non-Members to Issue management. This would increase the ability to assign items to non project members for reporting. (Ideally they are all on the project, though when a license restriction or member does not sign-in to platform there is no way to assign items (Issues) to these members. Extending the same function already built into Meetings would greatly improve this without additional costs. Please consider this simple yet powerful feature extension. Show More

The default “Coordination” issue category cannot currently be set to inactive. The status is locked to Active, even when this category is not needed in a project. Project administrators should be able to deactivate the Coordination category in the same way as other issue categories. In our case, we use our own issue structure and issue types, so keeping the default Coordination category permanently active creates unnecessary clutter and can cause confusion for users. Requested improvement: Please allow project administrators to change the status of the Coordination issue category from Active to Inactive when it is not required. Show More