Skip to main content
Statements of Work (SOW)

Learn how to use SOWs effectively within LawVu

Alina avatar
Written by Alina
Updated over 9 months ago

In this article:


What are SOWs (Statements of Work)?

A Statement of Work (sometimes called a Scope of Work) defines project-specific activities for a contractor providing services to their client. An SOW is often an important accompaniment to an MSA or Request for Proposal (RFP).

They are usually created before the project begins and help define its essential parts. Depending on the project's complexity, you may have several SOWs nested within one contract β€” one SOW for each Legal Service Provider or subcontractor.

A statement of work usually defines:

  • Purpose

  • Scope of work

  • Term of the contract

  • Milestone/Deliverables schedule

  • The acceptance criteria for the finished work

  • Cost and payment schedule


How to use Statements of Work in LawVu

Enable the Statement of Work tab for the contract type

Statements of Work need to be enabled at the Contract Type level.

Admins can switch the SOW tab on by going to Settings / Contract Management / Contract types / Settings tab of the particular contract type where they can switch on 'Allow association of Statement of Work child records':

Once switched on, the Statements of Work tab is displayed as the last tab within the contract:

If at a later point you chose to disable the Statements of Work tab on a contract type you previously enabled it for, this will not unlink any existing SOWs.

Three ways to create SOWs

The first option is to navigate to the Statements of Work tab within a contract and click the + Add statement of work button. You'll be able to create a new SOW or link to an existing record:

If you chose to create a new SOW, you'll be presented with the familiar 'Add by wizard / Add by Upload' creation method that you are already acquainted with.

Keep in mind that if identical fields exist in both the contract and the SOW, the SOW will automatically populate those fields in the creation form.

The second method to create and view SOWs is from the Related panel icon located at the top right of your screen:

A third option to create SOWs is from any file in the Files tab of the contract by clicking on the ellipses next to the file and selecting "Create contract from file".

Select the appropriate option and fill out the fields as desired, ensuring that any required fields (those with a red asterisk next to them) are mandatory.

The SOW inherits the members of the original contract. When a person is added as a member to the contract, they will be automatically added to the SOW as well.

The Contract value fields within each individual SOW are collated and displayed as the Total Value in the Statements of Work tab.

Within an SOW, you can perform the same actions as you would within regular contracts:

  • set approval stages

  • move between lifecycle stages

  • edit details

  • add files

  • start a conversation, etc.

  • restrict the SOW so only named members can access it, etc.

View related records

Explore all records related to your contract by opening the Related panel icon located at the top right of your contract. Here you can view all SOWs linked to your contract and have the option to generate new or link to existing ones.

View info about SOWs from the grid

To view SOWs from the grid, add the Related As column to your Contracts grid using the attribute selector button.


The Related As column shows if the contract record is linked as a Statement of Work (SOW) or Amendment. You can filter on the Statements of Work column to only display SOWs.

You can see the number of SOWs attached to each contract and their total value by adding the SOW Count and SOW Value columns to your Contracts grid.

​

Example of how to use an SOW

In the animation below, you will see two SOWs nested within one contract. The document itself is found under the Contract file section from the Overview tab. Once you update the 'contract value' field, the total value gets updated as well to reflect the change.

Did this answer your question?