Objective: To learn the different kinds of approval types you can utilize within Change Orders.
Difficulty: Easy
In this article:
There are three different kinds of approval types to choose from when assigning approvers to Change Orders. Knowing the requirements of each one will deepen your understanding of the Change Order process, helping you to optimize your experience with Duro.
Unanimous
The unanimous approval type feature requires everyone to unanimously vote for a Change Order to be approved. All approvers must approve a Change Order for it to pass. If not all approvers assigned to a Change Order do not agree that it should be approved, it will be rejected.
There are a few different advantages to choosing this approval type. Change Orders that do end up getting approved are strongly supported since all members voted for it to be approved. Users with different perspectives come together and agree on a single outcome, which can strengthen the momentum behind a Change Order. Each user's opinion matters since it only takes one vote to change the course of action. A disadvantage to that, however, is that if just one member dissents, they have the power to completely veto a Change Order. If not everyone agrees on the outcome, it could be time-consuming to have to spend resources of time and energy unifying the team around what's getting changed and why.
Majority
A majority approval type specifies that the most votes towards approval or rejection is followed. Majority rules, so two out of three team members would have to approve a Change Order for it to go through. Obtaining approval with a majority approval type feature is much easier than getting it approved with a unanimous setting.
One or two individuals voting to reject a Change Order would not necessarily turn the tide on its approval. However, it is more likely that there will be individuals who disagree with a Change Order's ruling. Additionally, it takes the power away from the minority group and places it in the hands of the majority.
First-In
The first-in approval type dictates that the first person to vote on a Change Order gets to decide its course of action. This is the fastest route for getting a Change Order approved, and it caters to a shorter timeline, thus eliminating the need for all votes and reactions to be submitted. If the first person to see it approves it, the Change Order will get approved.
Conversely, if the first person to see it rejects it, the Change Order will get rejected. The obvious disadvantage is that a great Change Order with needed improvements may still get rejected, even if only one person dislikes it, simply because they responded first to the Change Order notification they received. The first-in approval type should be used with shorter approver lists of one or two members where the users included have been kept up to date with all progress and are likely to approve the defined changes.
Pro Tips
If you'd like to change the default approval type feature, simply submit a ticket request.
Comments
0 comments
Please sign in to leave a comment.