Skip to main content
Automated Contract approval workflows
Alina avatar
Written by Alina
Updated over a week ago

Who can use this feature?

👤 Clients who are part of the Early Access program

🔑 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.

This feature is currently only available to those clients who are part of the Automated contract approval workflows - Early Access Program . If you'd like to be part of this program, reach out to your Customer Success Manager (CSM).

If you're already enrolled in the Early Access Program, explore this article to learn how to share your feedback: Everything you need to know about the automated contract approval workflows early access program

In this article:


Create approval workflows

Organization Administrators create and manage contract approval workflows by going to Settings / Approval workflows / Contract approvals

  • 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.

  • Add other phases to the workflow if needed by selecting the 'Add next step' icon.

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 approval phase, you can quickly duplicate it from the three dots:


Set up conditional rules for your workflows

These workflows can be tailored to specific scenarios, such as when a field is of a certain value ( for example contracts exceeding a certain amount )

Setting up conditional rules for your workflows involves a three-step process: first, define the primary condition that will trigger the workflow; second, determine who will approve the contract when the condition is met ("Yes"); and third, specify who will approve the contract when the condition is not met ("No").

Click on the flag icon and select a condition from the list of available fields:

The LawVu fields that can be used for conditional logic are:

  • Contract value

  • Region

  • Department

  • 3rd party contract?

  • Urgent

  • Restricted

  • Potential liability

Choose what happens when the condition is not found (when the field is not on the contract or the field was left blank). You can choose to skip to the next phase of the workflow or send the contracts to one or more allocated approvers:

Click on the "+" sign next to "No" to create a workflow for cases where the primary condition is not met.

Watch this animation to see how approvers can be automatically assigned based on whether the contract value exceeds a specific amount:


Applying the workflows to contract types

Prerequisite: If you haven't created any contract types, you'll need to do that first, then return here once that is complete. Learn more about contract types

Now that your workflows have been created, you can apply them to your relevant contract types and contract stages.

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?

Yes

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?

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?

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 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?

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?

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.

What if the field is completely removed from contract details?

If the field is removed from the contract details, the workflow will follow the flow set in the "If this condition is not found" section:

To learn more about this Early Access program and how you can provide feedback, check out our comprehensive guide: Everything You Need to Know About the Automated Contract Approval Workflows Early Access Program.

Did this answer your question?