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

We need the ability to configure conditional custom attributes within the following Cost Management areas: Payment Applications Contracts Variations / Change Orders For example, when a user selects a specific value in one custom attribute, a second related custom attribute should automatically appear. Example: If Custom Attribute 1 = “Yes”, then Custom Attribute 2 becomes visible and required. If Custom Attribute 1 = “No”, then Custom Attribute 2 remains hidden. This conditional logic would help simplify the user interface, avoid displaying unnecessary fields, and ensure users only provide information that is relevant to their selected option. It would also be beneficial if the conditional logic could support rules such as: Show / Hide field, Make field Required / Optional, and potentially Enable / Disable field based on the value selected in another custom attribute. This functionality would provide much greater flexibility when configuring Cost Management workflows and would better support different business and contractual requirements. Show More

Please add the option to download or export a pdf version of the compared view. Currently you can only view the comparison view of two sheets. This would assist with providing detailed descriptions or back up for contractors providing pricing. Currently we need to download each sheet version and use Bluebeam to overlay the two sheets. Completing all this at one point would be extremely useful.  Show More

In the PCO tab of the change management module, if the user hard types a dollar amount into the estimated column of the grid for a cost item that has a unit cost, the default is to add the line as 1 unit at a unit rate of the hard typed value. The ideal function would be for the units to auto calculate backwards from the hard typed value and the unit cost of that cost item from the budget module. Example below.    Parameters: Project manager's rate is $100/hr per the budget module.   Current function:  $10,000 typed into estimated column field for a project manager cost item.  Flyout window shows 1hr at a rate of $10,000/hr for a total of $10,000 Ideal function: $10,000 typed into estimated column field for a project manager cost item.  Flyout window shows 100hrs at a rate of $100/hr for a total of $10,000 (the unite rate was pulled from that specific cost item in the budget module).  Would be good to be able to still override the Quantity, rate, and total fields in the flyout window in case a different rate needed to be added. ex: 80hrs at $125/hr for $10,000.  The current function can remain as is for lump sum and similar functioning units.    @ian_turner  Show More

Markup lines in the Change Management tool default to being Budget Only lines. There are many kinds of markups that would not be Budget only, like insurance or bonds. There is no way to change this default. There should be a setting associated with the Budget Code or with the Markup Template that allows for customization of this setting.   In my mind, it would be best for the Markup lines of a Change Event would be able to match the Scope of the Change Event itself.  Show More

We are currently using Docusign and would like some additional setting that can be setup in Autodesk.  This goes for any e-signature company as well.   We want to be able to set the "Repeat reminder" for an envelope.  The other option what would be nice to send an alert for is the "Expiration" alert.   Show More

My team and I would really appreciate if it would be possible to select the SCO number instead of auto numbering. The reason why this is important is that, for our subcontractors, is confusing to see SCO's#1, #3 and #4 under their list since the SCO #2 was assigned to other subcontractor. So, they end up thinking that one SCO is missing and we need to clarify things for all them.   Imagine a work where we need to set up tens of subcontractors, it'd be madness to coordinate things with SCO numbers being assigned randomly. Show More

Currently, the only PCO's are able to be pulled into a pending change order column in the budget, which includes SCO's that are being processed, and unapproved PCO's.  The issue with this is that pending PCO's is they are not real costs yet, just estimates for things that are optional, and are not required to be done if the owner does not want to spend the extra money.   Ideally, we can separate the SCO's that have been issued for signature or pending, since once we create the SCO, we are basically committing to the cost, so this is not a committed cost.    PCO's are not committed, and again are optional, so these items should be separated, or more importanly SCO's should have their own column. 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

In certain projects, we execute a single contract with the owner; however, project funding is distributed through multiple owner-issued Purchase Orders. Per the owner’s accounting requirements, each Purchase Order must be tracked independently and requires its own Owner Change Order (OCO). To comply with this requirement, we have configured multiple Main Contracts within Autodesk for a single project.   While this structure addresses owner-side accounting needs, it creates inefficiencies on the subcontracting side. In practice, we typically issue a single subcontract (commitment) to a supplier that may span multiple owner Purchase Orders. Creating separate commitments for each Purchase Order is duplicative, time-consuming, and does not reflect standard contracting practices for us.    Currently, the system does not allow a single commitment to be associated with multiple Main Contracts, which forces workarounds or additional administrative effort.   We request an enhancement that would allow commitments to span and allocate values across multiple Main Contracts within the same project. This could be enabled through a configurable setting or relationship that allows a single commitment to reference multiple Main Contracts while maintaining accurate financial tracking. Show More

The project setting to calculate the change order's markups by percent would remain but in some case scenarios, the markups for one change order need to be edited manually. This may be due to an agreement with the owner on the markup values for that particular change order. The system should allow the ability to click on the markup value and edit it in the same way it allows changes to the values of the other lines.  Show More

Currently, when sending documents for e-signature, we utilize predefined templates; however, dynamic variables are not supported within the email subject or message of these templates. This limitation prevents us from automatically including key information such as the Project Name, SCO or OCO number, Main Contractor, and other relevant details.   This would save my project setup team time on each project we setup as well as our Project Managers from having to go into the message and manually change it each time.     Show More

Cost Management Product In the contract settings, we can currently fully lock a flyout after integration (thereby removing the ability to change anything) -or- we can lock the amount only - see snip.  My company opts to lock the amount only, as we sometimes need to change items in the flyout after sending (i.e. the contact name for the vendor, the work scope, etc.).  This allows us the flexibility we need to work with our vendors and get contracts executed.   This same setting is not currently available in the Change Management module for subcontract change orders (SCO) and I would like to request that it be implemented ASAP to allow for more flexibility than is currently available.  When an SCO is sent, it is frozen and we have no ability to change any aspect after integration.   Show More

Each time we send a contract we have to manually CC people and remember to do that. We want to be able to set default people for the CC line so we only have to set this up once. If we forget to CC someone on a contract, we don’t get the information we need to people that need it and it slows workflows. We are manually copying people. Show More

Currently, when initiating a workflow in Autodesk Construction Cloud, only approvers can be added to the process. However, many change orders require additional people from our organisation to be informed of change orders for visibility and awareness purposes, without requiring them to take any approval action. Introducing a “notify-only”  option within workflows would allow users to include these stakeholders and automatically notify them when a change order is initiated or updated, while keeping the approval chain unchanged. This enhancement would improve communication, reduce manual follow-ups outside the system, and ensure that relevant teams such as commercial, finance, or project controls have real-time visibility without impacting workflow efficiency Show More

Currently, Autodesk Construction Cloud provides a manual option to send reminder emails for change orders. However, this requires users to actively monitor due dates and trigger reminders themselves, which can be time-consuming and may lead to missed follow-ups on busy projects. It would be highly beneficial to have automated reminder notifications when a change order passes its due date. The system should automatically send reminder emails or in-app notifications to the respective responsible users (such as approvers or reviewers) when action is overdue. Ideally, these reminders could be configurable, allowing teams to define reminder frequency or escalation rules. Show More

We would like to request to add calculation column functionality for custom attributes in change orders to automate calculations.     Custom calculation columns are currently not available for change orders. While custom attributes can be used with manual input, there is no way to create calculated fields that automatically compute values based on these custom attributes.     Therefore, we would like to add the ability to create calculation columns in change orders that can reference and perform mathematical operations on custom attributes, similar to how calculation columns work in other ACC modules (Budget Overview Columns)    This additional feature will eliminate manual calculation errors, reduce spent on repetitive calculations, improve data consistency across change orders and enable real-time updates when attributes value change.    Example:  Based on the screenshot above,    Custom Attribute 1: RAOV (Add) S$  Custom Attribute 2: RAOV (Omit) S$  Desired Calculation Column: "RAOV (Nett)" = [RAOV (Add) S$] + [RAOV (Omit) S$]     Current workaround issue of now is manual calculations in custom attributes which is prone to human error, inconsistent updates when source values change, time-intensive data entry and difficulty in maintaining accuracy across multiple change orders. So, it will be better if formula builder interface similar to the "Budget Overview Columns" is applicable to Change Orders as well. Thus, it will allow real-time calculation updates when referenced attributes change.   It is also good to have a support for basic mathematical operations (+,-,/,x) and to format results in currency, percentage or decimal places).    This new feature would significantly improve change order management efficiency and data accuracy for our project team.    Thank you.   Show More

We would like the ability to delete a drafted cost item even if phase code is attached to PCO cost item.  Currently, if we allocate from the budget, but need to delete that allocated line and the code is attached to a separate PCO, we are prevented from doing so.   Show More

We need the option when pulling in documents into the OCO to be able to pull in the Merged PCO documents instead of all the individual documents from the PCO.  Pro's: Pulling in the Merged PCO.pdf is a cleaner when reviewing the PCO to make sure all the PCO's backup has been attached Easier to follow Ensures we are using the same document that was used as backup in the PCO approval process in the OCO. that the Owner. Con's: Existing process pulls in all the individual documents Makes it harder to understand what document belongs to what PCO Difficult to ensure all the documents are in the correct order. Allows users to delete out documents that the owner has already seen in the PCO approval process.    There is a work around but it is time consuming.  You have to "attach from Autodesk Docs" go find the folder the merged document is saved on and click on it to attach it.        Show More