Scenario: Currently, sub-items cannot be added to SOV items once they have been partially claimed. One of our project teams often needs to introduce additional sub-items or further breakdowns even after partial claims have been submitted. As a workaround, we attempted to use Change Order to manage these new sub-items. However, sub-item hierarchies created through Change Order are not reflected or displayed in the Budget Payment Application, which limits their usability during the claim process, unlike Cost Payment Application where the hierarchies of Change Order are reflected.   Proposed Enhancement / Workaround Requirement: For this workflow to function effectively, Change Order breakdown details should be visible and usable within the Budget Payment Application. Ideally, the Change Order sub-header name should be able to match an existing SOV sub-header name, allowing relevant breakdowns to populate automatically under the corresponding SOV item. In Change Order, there should be an option to choose whether: the Change Order items remain separate from the SOV, or the Change Order items align with existing SOV item names and populate beneath them. Please refer to Appendix A in the attached document for a visual reference. Show More

It would be helpful to have the ability to add a new budget code to contract via change order. For example, if an item is purchased using a contract, and the vendor adds a freight charge upon shipment of said item, it would be good to be able to add a freight budget code to that contract with a CO. Show More

It would be helpful if: When you save a custom view to replace the "Default View", the view name reflects the custom description. For example, if the view that needs to automatically show when opening Cost>Budget is "Company Standard View", the default view name would update to reflect "Company Standard View". Otherwise, that view is in two different places and any updates would have to be made in both views. This creates duplicate work and more risk for human error. Company created standard views for any tools were lockable so that members do not inadvertently save changes over the set, company standard template. Updates to a set view could be pushed to all projects instead of having to go into each project and manually edit each view that needs to be updated. Item number 1 above means work is doubled as edits would have to be made in both the "Default View" and custom view. Show More

Create a program like Clearstory where users can create potential change orders with a simple narrative and ability to add photos. Assign a responsible contractor and then allow a performing contractor to be added to that issue. Allow fields to add total man hours and labor rates.  Show More

When a PCO (Potential Change Order) advances to an RFQ (Request for Quotation) or an SCO (Subsequent Change Order), the system should automatically retain the same name as the related PCO. Rationale: Ensures traceability between the PCO and its corresponding RFQ or SCO. Reduces confusion when tracking multiple change orders. Maintains consistency in reporting and documentation. Show More

During the Subcontract Change Order (SCO) review process, Autodesk Construction Cloud displays a review timeline at the top of the record, showing the workflow steps, reviewers, and approval progress. This timeline is very useful for tracking the review status and understanding where the SCO is within the workflow. However, once the SCO workflow is completed, this review timeline is no longer visible. As a result, users lose access to important historical information, such as who reviewed or approved the SCO, the sequence of approvals, and the overall workflow progression. This information is often required for audits, claims support, internal reviews, and future reference. We do have an option to see in the activity section but it does not provide the information at a glance, whereas the review timeline does. Activity history has too much text and includes non-review related history. 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

Currently, when a workflow in Autodesk Construction Cloud is rejected, it typically returns to the initiator or restarts from the beginning. This limits flexibility, especially for complex approval workflows that involve multiple stakeholders and review stages. In many real-world project scenarios, a workflow may only require corrections or clarification at a specific step rather than a full restart. For example, a reviewer may need revisions from a particular approver or department while the earlier approvals remain valid. The inability to send a workflow back to a specific step results in unnecessary re-approvals, increased administrative effort, and longer cycle times. Show More

Currently, once a Potential Change Order (PCO) is executed, it can no longer be edited. This creates a limitation, as change orders often go through multiple rounds of review, clarification, and back-and-forth communication during the approval workflow. In many real project scenarios, additional cost items are identified after the PCO has already been accepted or executed. At present, if a new cost item is added after the PCO has progressed to the Subcontract Change Order (SCO) stage, that cost item does not carry forward to the SCO. This results in incomplete records, manual workarounds, and potential discrepancies between the PCO and SCO values. It would be highly beneficial to allow controlled editing of PCOs even after they are accepted or executed, such as adding or updating cost items, with proper version tracking or audit history. Any approved changes should automatically flow through to the corresponding SCO to ensure cost continuity, data accuracy, and alignment between commercial documentation across all stages of the change management process. 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

Users (especially the consultants) would like the ability to flag each submittal item with indicators for Cost Implication and Time Implication. Currently, ACC Submittals does not provide dedicated fields for capturing these impacts, making it difficult for project teams to assess potential variations or schedule risks early. This feature request proposes adding two optional columns—Cost Implication and Time Implication—as configurable Boolean or dropdown fields at the submittal item level. This enhancement would help stakeholders quickly identify submittals that may affect project cost or schedule and support more efficient decision-making, reporting, and risk tracking. Show More

Descargar Forsaken AR APK Forsaken AR es un título que reinventa los juegos de terror en realidad aumentada, llevando al jugador a un mundo donde las criaturas, los espíritus y los fenómenos paranormales aparecen directamente en tu entorno real. Show More

Our old system would list all previously approved change orders for OCO & SCO's when created and in cost management there is no way for this to happen with out creating a work around. Would like the option to have this added to the forms.  Show More

Currently, change orders are managed through Cost Management and are heavily focused on budget and timeline implications. Our team uses change orders during our design stage, before they have budget implications, to track requirement or design basis changes. Our company has multiple subteams that act as stakeholders for projects in other teams, meaning that before we create a budget or schedule, we are locking down requirements from all the stakeholders. Sometimes these have to change either because of new information gathered or conflicts between 2 requirements. We currently track this work using forms to submit an "official" request for the change. Having something similar to how Vault handles change orders would be amazing for the management of change when there are no timeline or budget implications. Show More

Link - Hollow Knight Silksong Hollow Knight Silksong es un juego metroidvania centrado en Hornet, uno de los personajes más icónicos del primer título. En esta secuela, Hornet es capturada y llevada a un nuevo reino lleno de criaturas extrañas, trampas mortales y secretos ocultos. A diferencia del protagonista anterior, Hornet posee un estilo de combate más acrobático, rápido y basado en movimientos ascendentes, lo que convierte la experiencia en algo totalmente fresco y dinámico. Show More

A setting needs to be added that will prevent Subcontractors from being able to bill for unexecuted SCOs.  Currently, if a SCO is in a "Sent" status it will automatically be added to the Sub Pay Application or they can select it and add it in.  Subs should not be allowed to bill for an SCO unless it has an executed status.  If that SCO has to be changed and it is already in a sub billing then it becomes tedious to have to revert back to detach it especially if integrated with the ERP. 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

I am developing a Power BI dashboard for change orders. We need the “Type” field available as a chart legend, but it is currently not included in the ACC Data Connector extraction. Show More

Cost items in the Changer order workflow have their own number systems, which makes sense if the cost items are created first then linked to a PCO. The problem with that is if the log gets heavy, it can be difficult to track specific cost items to their associated Changer order. Can there be a way to give the Cost items a prefix (or suffix) that coincides with the Changer or number (or name) to make it easier to view, sort or filter list?  Show More