Workflow Feature Feedback

We are providing this feedback based on active use of ProjectSight on healthcare and government construction projects, as well as direct comparison to Autodesk Construction Cloud (ACC) and Procore.

At this time, we have chosen not to use the ProjectSight workflow feature due to several structural limitations that prevent it from functioning predictably in real-world submittal workflows.

Key issues:

1. Workflow Completion Time Model
   ProjectSight requires a total workflow completion time that is then divided evenly across all steps. In practice, users do not manage submittals based on total workflow duration. Review time must be defined per step, and different reviewers (AE, owner, government, internal QC) require different review durations. ACC and Procore do not require a total workflow duration—each step has its own independently defined review time.

2. Schedule-Driven Submission Due Dates
   Because step durations are derived from a fixed total workflow duration, it is not possible to set submission due dates based on the project schedule without causing step review times to vary wildly from submittal to submittal. In ACC and Procore, submission deadlines are decoupled from review durations, allowing consistent reviewer expectations.

3. Reviewer Response Visibility
   Reviewer responses that drive workflow paths are not clearly visible to subsequent reviewers unless they are manually duplicated in the comment field. If a reviewer selects “Revise and Resubmit” without comments, that decision is effectively hidden unless the history tab is opened. ACC and Procore clearly display each reviewer’s response at every workflow step, regardless of comments.

Because ACC and Procore use nearly identical step-based, template-driven workflow logic, they have established industry expectations. Architects and owners routinely ask whether ProjectSight has a “workflow” or “ball-in-court” capability similar to those platforms, and currently we have to say it is still in development.

Until the workflow feature:

• Removes the requirement for a total workflow completion time

• Allows independently defined step durations

• Supports schedule-driven submission deadlines

• Clearly displays reviewer responses at each step

we will continue managing submittals outside of the workflow feature.

This feedback is offered constructively, and we would welcome the opportunity to provide additional input as the feature evolves.