Who can use this feature?
🔑 Needs an Administrator license to configure the approval workflows
Automated contract approval workflows enable you to streamline the approval process by automatically assigning approvers to various lifecycle stages based on the contract's type and other specific attributes.
This enhances both efficiency and compliance, ensuring that each contract is reviewed by the appropriate stakeholders at the right time.
In this article:
Create approval workflows
Organization Administrators create and manage contract approval workflows by going to Settings / Approval workflows / Contract approvals [V2]
Click on New Workflow and give it a name.
Create and name the first phase in the workflow.
Choose approvers from the menu on the right. You can choose one or more individuals and specify whether it's sufficient for anyone in the group to approve or if everyone in the group must approve the contract.
Decide whether the phase is required.
You can also set approval phases to be:
Required - This phase cannot be removed when on a contract
Locked - This phase cannot be removed or edited when on a contract. To lock the phase, click on the lock icon at the top of the phase.
If you need to reuse an phase, you can quickly duplicate it from the three dots. From here, you'll also find options to cut/copy and then paste it, or if needed, delete it completely.
Set up conditional rules for your workflows
These workflows can be customized for specific scenarios, such as when a field meets a certain condition (e.g., contracts exceeding a particular amount).
To begin, click the + Plus icon and choose either a Simple or Advanced condition. Advanced conditions allow you to create multiple paths based on defined rules.
Simple condition
If you choose to build a workflow using a Simple condition, you'll complete the builder that appears on the right-hand side. In this builder, you can specify the condition on which the workflow will be triggered, such as when a certain field matches a certain value.
Advanced condition
When using an Advanced condition, you can design more complex workflows by defining multiple paths based on specific rules. You can also add additional conditions as needed.
In the example below, I’ve set up multiple workflows: one that triggers when the department matches a specific value, and another for when the contract value exceeds a certain amount.
Supported Fields
The fields that can be used for conditional logic are:
All LawVu standard and custom fields of the type:
Checkbox (single, multi)
Dropdown
Lookup (single, multi)
Radio
Number
Slider
Remember to choose what happens when the field value doesn’t meet the specified condition, is missing from the contract, or is left blank. To do this, click the "+" sign next to "False" or "Else" to add a workflow step.
Good to know
Incorrect Rules: If there's an issue, like assigning duplicate values to a conditional field or conflicting paths, a red warning sign will appear, and you won't be able to save the workflow until the logic is corrected.
Undo Changes: Use the "Undo workflow changes" button (bottom left) to revert edits in the current session. Once you navigate away or save, the history is cleared.
Duplicating Condition Paths: Reusing condition paths can simplify your work when a certain setup is needed.
Copy/Cut & Paste Phases: You can copy or cut and paste phases anywhere in the workflow, even across different nesting levels, for added flexibility.
Applying the workflows to contract types
Now that your workflows have been created, you can apply them to your relevant contract types and contract stages.
There are two ways to do this:
Click on the 'Assign workflow' button, then select '+Add' to include the contract type stages you'd like to assign to this approval workflow
2. Click over to the 'Contract types' tab and choose the appropriate contract type from the menu on the left.
You will be presented with a map of the available lifecycle stages for the contract, and you can apply your workflow templates to any of the available stages.
Click on the +Select workflow button. A small pop-up will appear, and you can select any of your previously created workflow templates.
You can add the approval workflow to multiple stages of the contract or a different workflow for each stage.
NOTE: You cannot apply a workflow template directly to a contract record - it must be applied to a contract type; when a new contract of that type is created, the workflow will be applied accordingly.
You can edit or remove a workflow template at any time, but this will only take effect for any new contracts that are created - or for any contracts in progress that haven't yet reached the relevant lifecycle stage where the workflow template has been applied.
Existing contracts that have workflows that are in progress or completed will not be affected.
FAQs
Contract Workflows
Will my existing workflows be migrated?
Will my existing workflows be migrated?
Existing contract approval workflows have been migrated automatically for customers who weren't part of the Early Access program. They aren't affected by the new workflow builder and can still be viewed in Settings > Contract management > Approval workflows. When you have built out your new workflows and assigned these to your contract types, you will need to contact our support team via chat or your CSM to "switch over" to the new workflows. This will enable the new workflows and turn off your existing workflows.
Can I assign more than one workflow to a lifecycle stage of a contract type?
Can I assign more than one workflow to a lifecycle stage of a contract type?
Only one approval workflow can be assigned to each lifecycle stage.
When are workflows applied to a contract?
When are workflows applied to a contract?
Approval workflows are applied:
At creation based on the contract’s field values at that time.
On entering / re-entering a lifecycle stage based on the field values at that time.
What happens if I edit an approval workflow from Settings or if I change the value of a controlling field on a contract?
What happens if I edit an approval workflow from Settings or if I change the value of a controlling field on a contract?
Edits are forward looking for new and existing contracts. This means:
For new contracts, the updated approval workflow will apply.
For existing contracts:
Previous and current lifecycle stages: no effect, unless re-entered.
Future lifecycle stages: updated approval workflow will be assigned, and approvers added on entering those stages.
What if I remove or delete an approval workflow from a contract type?
What if I remove or delete an approval workflow from a contract type?
What happens depends on the lifecycle stage of the contract:
Previous and current lifecycle stages: no effect, unless stage re-entered.
Future lifecycle stage: removed.
What happens if I change the contract type?
What happens if I change the contract type?
If you change the contract type:
This has no effect on previous lifecycle stages.
Current lifecycle stage: reassign approvers.
Future lifecycle stages are updated so members can look ahead to who will be assigned on entering those stages.
Conditional Logic
What happens if no value is entered in the contract field for conditional approval routing?
What happens if no value is entered in the contract field for conditional approval routing?
If no value is entered in the contract field designated for conditional approval routing, the condition will be considered "not met" (No), adhering to the workflow configured for this scenario.