Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2025-05-16
Duplicate Statements of Work

Duplicate Statements of Work

Client users must have the
sow.create
 permission and can only duplicate Statements of Work (SOWs) that they have permission to view.
If you’re a client user with necessary permissions, you can duplicate existing SOWs in any status. This feature can help you save time while creating new SOWs, especially if your program:
  • Uses recurring SOWs, such as annual service-level agreements (SLAs) with vendors.
  • Uses standard SOWs for specific projects.
  • Wants to preconfigure SOWs with certain settings, such as specific checklists or tracking for non-billable contractors.
You can also duplicate individual SOW roles, milestone payments, and fixed price payments. For more information, view Duplicate Roles and Payments on Statements of Work.
  1. From the header, select
    Statement of Work
    Statement of Work
    .
  2. Locate the SOW you want to duplicate.
  3. Click
    Duplicate
     next to the SOW’s name. Or, open the SOW and click
    Duplicate
     in the actions drop-down menu at the top of the page.
  4. Fill out the fields in the modal. Consider:
    Field Name
    Description
    Statement of Work Name
    By default, VNDLY uses the original SOW’s name appended by “ - Copy”, but you can enter a new name.
    Confirm Organization Unit
    This field populates with the organization unit from the original SOW. You can edit the organization unit in the new SOW’s settings, or save time by editing it here.
    Select the Vendor for this SOW
    This field populates with the vendor from the original SOW. Once the new SOW is in
    Draft
     status, you won’t be able to change the vendor.
  5. Click
    Create New Statement of Work
    .
After duplicating, VNDLY immediately redirects you to the new
Draft
 SOW’s
Overview
 tab. You can customize the fields on the duplicated version, like on any other SOW.
All SOW payments and roles on the new SOW are set to their initial status:
  • Fixed price payments are set to
    Scheduled
    .
  • Milestone payments are set to
    Not Started
    .
  • Unit payments aren’t copied over to the new SOW. However, unit types are copied over.
  • SOW roles are set to
    Draft
    .
VNDLY doesn’t copy inactive or invalid data, such as inactive resource managers or locations, over to the duplicated SOW. If an optional field contains inactive or invalid data, VNDLY removes that data on the new SOW and logs the removal on its activity log. If a required field contains inactive or invalid data, VNDLY displays a message on the new SOW notifying you to update the field.
VNDLY also doesn’t copy over unique data from the original SOW, such as:
  • Change orders
  • Attachments that are manually added
  • Contractors, work orders, and applicants
  • Unit payments
  • SOW participants
  • Workday position IDs (for client users who use the Workday integration)