Support Central
Both Workflows and Document Processes are available to use for document reviews on your project. They are independently integrated with the Document Register, but not with each other.
With Document Processes, reviewers open each document in the viewer and pin review issues to add their comments and markups. Comments raised by multiple reviewers are centrally managed, tracked, and resolved in a dedicated issues register. Workflows provides the option to markup documents using external tools and upload them as replacement files in bulk.
If you are unsure which one to use, our Professional Services consultants can help you with process discovery and mapping.
The below table explains the key differences between Document Processes and Workflows.
| Function / Feature | How does this work in Workflows? | How does this work in Document Processes? |
|---|---|---|
| Managing documents in a review | Documents are grouped together into a workflow review. | Documents are reviewed as separate deliverables that can be repeatedly reviewed to collect comments. |
| Issues and Comments | Comments tracked within the workflow itself. They need to be manually managed in a separate comment resolution sheet. |
Comments are pinned to the document as issues. They are tracked and managed in a separate register. Issues are visible across all reviews of a deliverable until it is closed. |
| Markups | Markups are added into a new version the document. | Markups are added to pinned issues as a separate layer to the actual document. They are visible from the deliverable and tracked in a separate issues register. |
| Defining a review process | Each organization creates its own workflow templates that can be shared. | The project-owning organization configures review processes in the Review Matrix. They can also allow an additional organization to configure the Review Matrix. This provides greater control over the project's review processes. |
| Starting a review | Selecting multiple documents and starting a workflow results in a single workflow based on the selected template. | Selecting multiple documents and starting document processes results in multiple deliverables created and routed to different reviewers based on each documents metadata and the rules in the Review Matrix. |
| Lead Reviewer | The Lead Reviewer is the last step of a workflow template. They consolidate markups and provide the final outcome for the review. This is typically the outcome recorded in the Document Register. |
Every step in a review must have at least one Lead Reviewer. The Lead Reviewer provides a review outcome to complete the step and move the review onto the next step. Similarly to workflows, the last stage of a document process review will also have a Lead Reviewer who provides the final outcome. |
| Tracking reviews | There are limited fields available to add as columns when searching and tracking workflows. | All document fields and project fields are available in Document Processes. There are separate registers to view and track deliverables, steps and issues/comments. |
| File replacement | Reviewers can externally markup a document and replace the review file. This is often done in bulk. | There is no file replacement option. The document opens in the viewer where reviewers pin issues to add comments and markups. |
| Sub workflows | Reviewers can initiate a subworkflow during a review. | If additional reviewers are required during a review, the process owner can add them to current or future steps. |
