Ideas

It would be huge to have a notification screen that tells the users with assigned tasks are pass due, also a notification screen (Similar to Bluebeam) to tell what/who has been working in the project.

Problem description: Currently, when adding information content types, separate parameterization must be performed for each possible value, which results in repetitive work and can lead to redundancy if I want to assign the same property (e.g., A01 Field) to multiple items, but with different values. Suggested improvement: I would like to suggest introducing a “Template / Predefined List” feature in the Scope module, where the user would create an information content type once (e.g., “A01 Discipline”), for which all possible values would be predefined in a drop-down menu (e.g., Architecture, Structural Engineering, Mechanical Engineering, etc.). When assigning values, it should be possible to specify that one value is correct, or possibly more than one. Advantages: Time savings: The time spent on data entry is significantly reduced by eliminating repetitive tasks. Data integrity: The risk of manual entry errors is minimized, as users can only select from a fixed list. Standardization: Parameterization within projects becomes much more transparent and structured.

Description: Currently, entity types and subtitles are visible in the Scope Grid view, providing helpful context and quick identification of items. However, this information is not available in the Scope Timeline view, which creates an inconsistency between views and makes it harder for users to quickly understand and differentiate entities when working in the timeline. Requested Improvement: Extend the Scope Timeline view to also display entity types and subtitles, similar to how they are presented in the Scope Grid view. Consider maintaining the same visual styling and placement used in the Grid View to ensure a cohesive user experience across both views.

Currently, timeline bars inherit Team colors. Adding the option to reflect status colors could make the schedule more intelligent and in some use cases more informative.

Allow users to move the automatic page numbers to different positions (e.g. bottom middle, top left, top right, bottom left, bottom right) in the headers and footers on exported PDFs. Currently the page number position is fixed, and users need the flexibility to reposition it to suit their document formatting requirements. Requested by Balfour Beatty.

Currently, the Quick Assign and Quick Delete modes are available for Tasks Items only. To improve efficiency and consistency, we propose extending this functionality to Information Requirements and their associated Information Requirement Rows. Users can quickly assign or remove multiple information requirements without navigating each row, streamlining workflows for large projects and reducing manual effort and errors. *The feature potentially should allow to delete any task field values, when applicable returning back to the default value.

Currently, when working with the Information Requirements palette, the Scope grid can only be scrolled when at least one information requirement is selected. If no information requirements are selected, the blue overlay blocks interaction, preventing scrolling. This behavior limits the ability to properly review assignments and increases the risk of user errors, as users cannot inspect or verify the underlying grid without first selecting an information requirement. Proposed Improvement: Allow the grid to be scrollable in the background behind the blue overlay even when no information requirements are selected. This would enable users to review assignments freely, improve usability, and reduce potential mistakes.

It would be usefule to have button for this function.

Add two new SmartField data types that both allow multiple either Short Text or Formatted Content options to be added. These will both appear as a dropdown selection in the Docs Section.

Add the ability to filter the scope grid by information requirements. Specifically, when viewing an information requirement, the counter that shows how many times it has been applied to scope items should be clickable. Clicking this number would automatically filter the scope grid to display only the scope items that have that specific information requirement assigned. This would significantly improve traceability, navigation, and usability when working with large scope grids and complex information requirement mappings.