Ideas

The system should save the display options such as enabling classification code for the whole project. This would remove the need to change display options every time users access the project.

Please provide an MCP server so AI assistants can securely access and query Plannerly data. This would enable to automate internal reporting, replace manual Excel export workflows, and retrieve project information in natural language, improving efficiency and reducing manual effort.

Currently only the "equals" and "not equals" operators are available for data/property linking to model elements. In order to provide more options and flexibility to this linking, please consider the addition of other standard data query operators commonly used in various programming languages and databases, such as: Equals (=): Matches records where the specified attribute is equal to a given value - Currently Available Not equals (!= or <>): Matches records where the specified attribute is not equal to a given value - Currently Available Contains: Matches records where the specified attribute contains a specific substring or value. Not contains: Matches records where the specified attribute does not contain a specific substring or value. In: Matches records where the specified attribute is included in a list of given values. Not in: Matches records where the specified attribute is not included in a list of given values. Between: Matches records where the specified attribute is within a range of values. Greater than (>): Matches records where the specified attribute is greater than a given value. Less than (<): Matches records where the specified attribute is less than a given value.

In order to avoid accidental data loss, before deleting tasks, first archive them. This function could be extended to archiving Scope folders, task groups, task rows and milestones too

Add a sticky/always-visible horizontal scrollbar to the Scope module so users can reliably navigate large scopes on Windows PCs without needing to scroll to the very bottom of the page. Problem Currently, the horizontal scrollbar is only visible at the bottom of the Scope view. In cases where the scope is very large or vertically long, users must scroll all the way down before they can access horizontal navigation.

It would be great to see only the information lines and the milestones where the current filter has assignments. More precisely, I'd suggest to use that setting as a default (most planners will be happy to quickly see only what they're interested in) and to add a toggle for BIM managers and such to get back the view as it currently works, which is useful when you need to update requirements.

Ability to schedule an export of Excel file. The document can be either an emailed link, or deposited into dropbox, google, doc, A360 cloud.

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.

Currently, SSO appears to be limited to Microsoft Entra ID. Our organization uses Okta as our primary identity provider, and support for Okta would significantly improve adoption and simplify user management. We would like to request support for Okta integration, either through direct/native integration or via industry-standard protocols such as SAML 2.0 or OpenID Connect (OIDC).

1) instead of just writing "IfcSlab", it would be excellent if the Verify -module and the IDS export could take into account listings written in the form of "IfcSlab,IfcWall" 2) to be able to restrict applicability, it could be interesting to precise the predefined type in the same form than used by IFC documentation, e.g. "IfcSlab/BASESLAB" in a workable way for Verify + IDS So by extension, you could define the entity for properties from Pset_SlabTypeTrackSlab ( https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3_0_0/lexical/Pset_SlabTypeTrackSlab.htm ) to be = "IfcSlab/TRACKSLAB,IfcSlabType/TRACKSLAB"