Please update app to allow linking "Issue" to a mark up. This is possible on the website but not on the app.   Show More

I would like to request a feature in the cost module that allows us to create a daily contract progress entry (similar to a form linked to SOV items — with an approval workflow). This way, at the end of the month, we can have a consolidated report of the work completed and then process the payment for that period. Show More

We need the ability for a single correspondence thread to contain multiple correspondence types as the discussion evolves.   In real project workflows, a conversation often starts as general correspondence, then progresses into a change request, and may ultimately result in a contract variation. At the moment, these stages can require separate records, which breaks the context and makes it harder to follow the full decision trail.   Example workflow within the same thread: Correspondence 1 - General Correspondence - asking question to contractor Correspondence 2 - General Correspondence - response from contractor Correspondence 3 - Change Request - requesting formal confirmation of contract variation Correspondence 4 - Contract Variation - confirmation of contract variation   Ideally, each item in a thread could have its own correspondence type, while still remaining part of the same conversation history. Show More

  Request enhanced conditional logic functionality within Autodesk contract templates that would allow images, exhibits, or entire sections to dynamically display or remain hidden based on selected dropdown values within the contract properties/custom attributes. Current Challenge At this time, if different contract scenarios require different exhibits, bond forms, insurance attachments, or images, the only practical workaround is to create and maintain multiple separate contract templates. Requested Enhancement Allow contract templates to conditionally show or suppress: Images Exhibits Attachments/placeholders Sections/tables Entire clauses or paragraphs based on: Dropdown selections Yes/No responses Custom attribute values Contract type selections Example Use Case A contract contains a custom dropdown field: "COI or Bond Statement” Options: Required Not Required Desired behavior: If “Required” is selected → Automatically include bond exhibit pages/images. If “Not Required” is selected → Automatically suppress those pages/images. This functionality would eliminate the need for separate contract templates solely to manage optional exhibits. Adding this capability would: Significantly improve template efficiency Reduce template duplication Improve user accuracy Streamline contract generation Allow more advanced and scalable document automation Better align Autodesk Forma with modern document generation platforms This enhancement would be especially valuable for construction teams managing multiple contract variations, insurance requirements, bond requirements, and jurisdiction-specific exhibits. Show More

When issuing contracts, the Scope of Work field is too limited in: 1. It's outline capability.  We need more than just 1, 2, 3, etc.  We often push out in the outline to subcategories. 2. It's format capability.  If we cut and paste from a trade partner quote, the font on the contract is HUGE.  A format painter option would be gold.     As much as I love the cost management feature, this has made our contracts look somewhat jenky.  Currently, you have to open the doc, click EDIT, make the changes, close, wait for the document to update, then re-merge the Document Package to correct something that Microsoft has done for decades.  The only other option is to re-type the whole thing so the native formatting looks correct.   Show More

When using the e-sign feature, where can I grab the sub-status that displays "Out for Signature"? The Forma status of "Sent" is the same for items that have been sent for e-signature and items that HAVE NOT been sent for e-signature. Likewise, there is not a property/column in ACC to bring in the status of e-signature. Show More

We noticed that if project members are located in a different time zone than the Forma project itself, when they fill in the date custom attributes in Cost Management, whether it's for contract or for change order or for payment application, the value that show up in the generated template can be different (+ or - 1 day) from the value that we entered in Forma Cost Management. I've already discussed this matter with technical support team and they have understood and realized the problem, but have no roadmap on fixing it yet. Having this bug, is a major downside when it comes to international companies who operate and work in multiple regions. Even within one country we could have multiple time zones, and not everyone exactly work on the same area as the project is located at. So I would like to ask you to please fix this bug. Many thanks. Show More

I would like to visualize more Qual information in a contractor's building connected account "at a glance" that will ease the award process. In general, it would be helpful to be able to customize/add areas to the view. Specifically, I would like to visualize the if an MSA has been uploaded from the BC side.  Additionally, and a separate issue is the fact that MSA often have riders which are additional documents and I would like to be able to upload more than one document to the MSA area in TT. Show More

I would like to be able to customize the contract status term. For example, I would like to customize the executed status. Or add another step. This is very important because the existing statuses are not sufficient for the level of status we work with in projects. 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

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

@ian_turner  Can you create a link between contract templates in the cost tab of the project settings and Cost-> Subcontract Type. SO that when one subcontract type is shown then only certain templates are allowed to be used. Similar to the idea of custom attributes being linked to the subcontract type. This would help limit people using the wrong templates when generating. Show More

It would be very helpful if the cost module had a mobile version, especially for approvals. Do you have any idea when this might be implemented? Show More

Currently there are two ways to enter PCO's. If you enter a Change Order Transfer, if forces the PCO balance to $0.  The issue we are running into is after the PCO is entered and we need to make a change to the PCO.  Whether that is getting a quote from a sub, the scope changes and the PM needs to add additional cost items, there is no validation to ensure the PCO balances to $0 prior to submitting the PCO.  The PM can press the add button, change the "Type" to Budget Transfer and add as many cost items as they want to the PCO, but there is no validation to ensure the PCO has a $0 balance if the Type = Budget Transfer     I am requesting a setting to be added for a $0 Validation in the Change Order Types.  If it is flagged for the Change Order type it will not allow you to submit a PCO if the balance is anything but $0.  Below is a potential solution to the flag that could be created.     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

Significant Added Value Through Automated and Structured Document Distribution in Construction Projects  1)Problem Statement In construction projects, the timely, organized, and traceable distribution of drawings and documents to subcontractors and project participants is a critical success factor. Drawings typically go through several revision cycles. It must be ensured that subcontractors always work based on the latest approved version, without having to spend time searching for it on the project platform. Proactive and accurate delivery of the relevant documents is essential for maintaining quality and efficiency in project executionCurrent 2)Situation (As-Is Analysis) The current workflow in the Autodesk Construction Cloud (ACC) is as follows: Drawing Approval: After completion of the review workflows, drawings are marked as “approved” using specific attributes. In our setup, the custom attributes “Document released for execution” and “Milestone 4 achieved” are used for this purpose. Trade Assignment: Each relevant document or drawing is linked to the corresponding trades or subcontractors via the attribute “Package ID” (Vergabepaket). This means that one drawing or document may contain several package numbers. Manual Distribution Process: After approval, the drawing files must be manually copied into the corresponding subcontractor folders (e.g., into a directory named “Drawings released for execution”). 3)Weaknesses of this process include: High manual effort: Copying files manually is time-consuming and consumes significant resources. Error-prone: Manual steps increase the risk of mistakes (e.g., copying the wrong version, missing a trade, etc.). Redundant data storage: The same file is stored multiple times on the platform, leading to clutter and increased storage use. Markup process inefficiency: The markup (redline) process no longer occurs on a single shared document, since each subcontractor performs markups on their own copy. Lack of transparency: The distribution process cannot be automatically tracked or verified. The alternative approach—having subcontractors “subscribe” to drawings themselves—is insufficient, as it does not ensure proactive notification of entirely new drawings and shifts the responsibility for obtaining up-to-date information onto the subcontractors   4)Proposed Solution: Implementation of Search Folders To automate and optimize the distribution of drawings, it is proposed to use dynamic search folders (also known as “Saved Searches”) within the ACC. Functionality: No physical copies: Search folders do not contain duplicated files but only links (hyperlinks) to the centrally stored original files. This preserves the “Single Source of Truth” principle. Filter-based display: The contents of each search folder are dynamically generated based on predefined filter criteria. A document will only appear in a folder if it meets the specified attribute conditions. It is also defined in which area (which directories) the search folder should filter documents. Implementation: A dedicated search folder is created for each package (i.e., for each subcontractor). Each folder is configured with an individual filter rule. A drawing link will automatically appear in a subcontractor’s search folder when, for example, the following three criteria are met: Approval status: The attribute “Document released for execution” is set. Workflow status: The attribute “Milestone completed” is set. Assignment: The Package ID attribute contains the subcontractor’s specific package number. The subcontractor accesses only the search folder designated for them and automatically sees, in real time, all drawings relevant to their scope that have been released for execution — always in the latest approved version. Benefits of the Solution Full automation: Manual distribution steps are completely eliminated. Guaranteed up-to-date content: Subcontractors have immediate access to the latest approved drawing versions. Construction companies can currently access execution documents in one central location for their work package, without having to search extensively and without the need for a central distribution point.Increased efficiency: Significant time savings for planning and project management teams. Process reliability: Human errors in document distribution are eliminated. No data redundancy: Prevents multiple data copies and related inconsistencies. Maximum transparency: The distribution status is always clear and traceable.   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

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

Make fields within Contracts required base on the Type that is listed.  For example: we have purchase orders and subcontracts within the cost module. If the type is subcontracts then all the custom attributes we created for subcontracts would be required.  Show More