First point: A person who creates an issue has a drop-down list with all the categories/types available in the project. It's not user-friendly and is confusing. We need the ability to filter issue types based on role, company, or user. For example : a quality manager can only create quality issue, no need to see all other types. Second point:  Depending on the category, it should be possible to configure different drop-down lists of statuses. Show More

When doing review, we are doing lot of markups. On the same documents, we can have markups assigned to different people/companies. To track it, it could be interesting to have data to assigned markup to a discipline / user ? and to have a status to manage each markup as other software as Bluebeam. Show More

Hi Autodesk, I have shared the idea previously to have the workflow template to ACC Forms, but i think it would be a great improvement if Issues and Assets in ACC also could have a workflow setup feature similar to the Submittals module.   Currently, these modules rely heavily on manual updates for statuses and responsible parties. While this works, it often requires constant follow-up or manual reassignment to ensure the process moves smoothly. A built-in step-based workflow would bring much more structure and automation to these areas.   Proposed idea: Allow admins to define workflow stages (e.g., Draft → Review → Action → Close) and assign users or roles to each step. When a user completes their part, they can simply click Submit or Move to Next Step, and the system will automatically transition the record to the next workflow stage and notify the responsible person or role. Benefits of this enhancement: Improved clarity: Everyone can clearly see who’s responsible for the current step and what comes next. Better accountability: Each participant has a defined action stage, minimizing confusion or missed updates. Workflow consistency: Aligns the process across different modules, creating a unified experience similar to Submittals. Reduced manual effort: Eliminates the need to manually reassign or update statuses. Stronger process control: Helps standardize review and approval processes, especially for larger teams and complex projects. Example use cases: In Forms, certain forms (like Inspection or Permit Requests) could flow automatically from “Created by Site Engineer” → “Reviewed by Safety Officer” → “Approved by Project Manager.” In Issues, the process could move from “Reported” → “Assigned to Trade Contractor” → “Verified/Closed by QAQC.” In Assets, the lifecycle could progress from “Received” → “Installed” → “Inspected” → “Handed Over,” with each step linked to responsible users. Adding workflow configurability would make these modules much more dynamic, structured, and user-friendly, reducing delays and improving project coordination.   It would be great if the team could consider this suggestion, as it truly supports the purpose of using a digital platform; to streamline and automate workflows rather than rely on manual processes. I strongly believe this enhancement would bring significant value to many ACC users/teams who manage multi-step processes on a daily basis. Show More

Currently, when filtering issues by role or company, only those issues directly assigned to that role or company are displayed, not those assigned to users belonging to that role or company. It would be very helpful, especially for analysis and reporting, if this could be changed so that all issues belonging to a role or company could be filtered, even if they are directly assigned to users within that role or company.   Show More

Situation Currently, a separate custom field must be created in the “Issues” module for each possible property in order to allow multiple selections. Example: For a project with seven disciplines (e.g. Electrical, HVAC, Architecture, Plumbing, Building Automation, Laboratory, Process), seven individual fields are currently required — each with the possible values Yes or No. If only four disciplines are relevant (e.g. Electrical, HVAC, Laboratory, Process), all seven fields still need to be created, with only four set to Yes. Concept Introducing a new field type — a multi-selection dropdown list — would significantly simplify this process. The new field “Discipline” would include all seven options (Electrical, HVAC, Architecture, Plumbing, Building Automation, Laboratory, Process). The relevant disciplines could be selected directly via checkboxes in the dropdown list, for example: ☑ Electrical ☑ HVAC ☑ Laboratory ☑ Process In the field “Discipline”, the combined value would then appear as: Electrical; HVAC; Laboratory; Process For better reporting and data analysis, the selected values should be separated by a semicolon (;). Added Value Significantly reduced number of fields (in the example: 1 instead of 7) Simpler and clearer input for users Improved reporting and filtering capabilities Time savings when creating and maintaining issue templates Easily extendable by adding options to the dropdown list Show More

Currently, in the Model Coordination, clashes are no longer displayed as clashes once a task has been created for them, even if the task is still marked as open. This is incorrect in practice and leads to confusion, because clashes remain clashes until the task is completed/closed. The clashes must remain visible until then.   Perhaps instead of directly "closing" the clashes, a clash status could be introduced: open, in progress (once a task is created), and completed/closed.   Show More

指摘事項のステータスを変更した際、ステータスに対応した色が反映されません。即時に変更後のステータスに対応した色が反映されるように改善してほしいです。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ When I change the status of a issues items , the color corresponding to the status is not reflected. I would like this to be improved so that the color corresponding to the changed status is reflected immediately. Show More

ステータス名称の変更および追加をユーザーが自由に設定できるようにしてほしいです。これにより、活用方法とステータス名称の不一致を防止し、利用者が直感的に使用できる環境を目指したいです。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ I would like to be able to freely change and add status names to the system. This will prevent discrepancies between usage and status names, and create an environment that users can use intuitively. Show More

現状ではシート上に配置されている指摘事項の全体数しか表示されていません。ステータスやタイプでフィルタをかけた場合に、該当する指摘事項の数を表示することで、詳細の理解をしやすくしてほしいです。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ At present, the sheet only displays the total number of identified issues. To improve clarity and understanding, I would appreciate it if the number of issues matching the applied filters—such as status or type—could also be displayed. Show More

ユーザーが必要と思う項目のみ表示できるよう、柔軟に設定できるようにしてほしいです。現状ではデフォルトで非表示にできない項目があり、利用したくない項目も表示されてしまうため、利用者が困惑する原因となっています。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ I would like to see more flexibility in the settings so that users can display only the items they need. Currently, there are items that cannot be hidden by default, and items that users do not want to use are displayed, which causes confusion for users. Show More

It would be nice to split out and have independent controls on issues permissions based on visibility and assignment. For my use case, I want a specific role to be able to see all issues (help prevent duplicates) but only be able to assign to their company. Current state to see all issues you then have rights to assign to anyone. Short term it could be solved by adding an entire company as a watcher, but unless you use templates (and depend on the user to select the template), there isn't a way to set a default watcher. Having view only full visibility and assign only to own company would resolve this.   An additional option would be where you can set a role to only be able to assign to a set list of roles.  Show More

Specifications is a great way to mark parts of files. However, they're not visible in the issues in the app version. Specifications connected to an issue are very handy for the people on the construction site. That way they don't have to scroll through dozens of pages and only get to see the relevant information. Show More

Even though we have Watcher's field in the Issue detail, when we extract the report, it's not appearing. Even in the template field list watcher field is not available  Show More

I am a Project Manager, and when I create an issue, I place it on a large overall drawing sheet in Collections (Sheets) so we can view all issues in one consolidated drawing. However, the General Foreman typically places issues on a shop drawing sheet, which is smaller in scale and contains more detailed information. I’d like the ability to place an existing issue (already created and located elsewhere) onto another drawing without having to create a new issue. This would allow us to view the same issue across different scales of drawings. Show More

Images frequently becoming corrupted when completing forms using the app. These cannot be retaken for subsurface works so entire ITC forms are invalidated. This means we incur waste of time and resource and that we are unable to submit a full record of inspections to the client : g.allaouis@equans.fr Show More

Hello, A lot of customers use MS Teams (more and more) to manage some project. It will be great to better integrate ACC to MS Steams. For instance, instead of sending emails when something changes or issues arise, prefer sending messages via Microsoft Teams. The benefit is faster visibility, better collaboration, and reduced inbox clutter. Voila Olivier Show More

Currently photos uploaded as attachments to Issues and Forms are associated only with that form, and no not appear in the project Photo Library. It would be helpful if these photos did appear in the library, as it would allow forms/issues to be used to effectively group photos, as well as ensuring that all photos captured by the site team are visible. In the current system many photos will not be available to project members unless they know they need to go looking for them. Show More

When you are on a sheet you have to individually click on each issue - this would be good to have a number in the issue pin (instead of the type of pin) and utilize the issue list on the side view to link the number of the pin to the number on the list.  Show More

We’ve been working with the “Assigned Item by Company” report template, and while it’s a great fit for projects with clearly defined company structures, we’ve run into a few challenges.   In many of our projects, subcontractors can change midstream. When that happens, it becomes tricky to track which items still need attention—especially if they were originally assigned to a company that’s no longer involved. We also have cases where multiple subcontractors operate under the same company, and in those situations, it would be much more helpful to slice reports by role rather than by company.   It would be incredibly useful to have the flexibility to switch between assigning items by company or by role, depending on the project setup. This would allow us to generate more accurate and automated reports tailored to how our teams actually work. Show More