Approval chains are available through the icon
under the "Common stuff" section of the project dashboard.
An approval chain represents a sequence of steps that lead to the approval, or rejection, of a deliverable/entity.
The page is structured with 5 tabs:
- Open: all approval chains across the project that have started but not completed (approved or rejected)
- Closed: all the other past approval chains, both approved and rejected
- Deliverables stats: statistics on approval timing Vs. deliverable type, to find which deliverable take longer and address bottlenecks in your organization
- HR stats: statistics on approval timing Vs. users, to find out who are the good and bad performers when it comes to approve deliverables
- Static workflows: available only during trial of under the "Jack your Portfolio" plan, allows the creation of pre-configured approval workflows, with conditions and multiple steps
Approval chains can be of two types: flexible and custom. Flexible means that no static workflow for approval has been defined. So anybody with the clearance to edit one entity can send it for approval (see approval process for more details). Custom means that a static workflow has been defined (see below).
The approver, in this table, is the approver that is currently "blocking" the approval process.
The warning and alert columns are available only for custom chains, and show when the warning was sent to the approver (and the other users in the same step), and the alert was sent to both the approver and the system admin. Details is a minimal representation of how long the process has been so far and how long is the overall process (if custom).
Closed tab provides similar information for rejected and approved entities.
It's easy to spot which are the real bottleneck in your organization by having a look at this graph. In the example above "project benefit" take from a minimum of 6 days to a maximum of 9.5 days (median 8).
A similar graph is the one related to users. John Smith performs pretty well in the example below. François Pascal on the other end reacts pretty slow when it comes to approve deliverables.
Static workflows are available only during trial or under the "Jack your Portfolio" plan.
Here you can find the list of entities for which you've decided to have a custom approval workflow.
By clicking on the plus button you can create a new workflow (for a different entity).
Choose the entity for which you want to create the workflow:
A workflow designer will appear. Once the design is over, the next time we'll approve this entity we won't be able to perform a flexible "approve and send" to whoever we want (with approve rights). The system will automatically go through the workflow. Note: while we are approving an entity that is linked to a static workflow, we cannot change that workflow. We'll have to either reject or approve all entities referring to that workflow before being able to edit the workflow.